@ryuenn3123/agentic-senior-core 3.0.37 → 3.0.38

package/.cursor/rules/agentic-senior-core.mdc

@@ -0,0 +1,48 @@
+---
+description: Agentic Senior Core bootstrap adapter
+alwaysApply: true
+---
+
+# Cursor Rule - Thin Adapter
+
+Adapter Mode: thin
+Adapter Source: .instructions.md
+Canonical Snapshot SHA256: 75652106d1fc453e9407eb9301e7f38de2e0159190dc47fb0b6e377859d91a46
+
+This repository is governed by a strict instruction contract.
+Use [.instructions.md](../../.instructions.md) as the canonical policy source.
+Use .agent-context/ for technical rules, prompts, checklists, policies, and state.
+Treat README.md as overview/install/user context only when governance files conflict.
+
+## Critical Bootstrap Floor
+
+- If your host stops at this file, continue the chain manually before coding.
+- Read `.agent-instructions.md` next when it exists.
+- Memory continuity does not replace bootstrap loading.
+- For UI, UX, layout, screen, tailwind, frontend, or redesign requests, load [bootstrap-design.md](../../.agent-context/prompts/bootstrap-design.md) and [frontend-architecture.md](../../.agent-context/rules/frontend-architecture.md) before code edits.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
+- For UI scope, create or refine `docs/DESIGN.md` and `docs/design-intent.json` before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
+- For backend, API, data, auth, error, event, queue, worker, or distributed-system requests, load only relevant global rules from .agent-context/rules/ ([link](../../.agent-context/rules)).
+- For ecosystem, framework, dependency, or Docker claims, perform live web research.
+- Resolve runtime choices from project evidence and live official documentation; resolve structural planning from constraints and architecture boundaries.
+
+## Mandatory Bootstrap Chain
+
+1. Load [.instructions.md](../../.instructions.md).
+2. Load `.agent-instructions.md` when present.
+3. Load only relevant files from .agent-context/rules/ ([link](../../.agent-context/rules)).
+4. Apply matching prompts from .agent-context/prompts/ ([link](../../.agent-context/prompts)).
+5. Enforce .agent-context/review-checklists/ ([link](../../.agent-context/review-checklists/pr-checklist.md)).
+6. Use .agent-context/state/ ([link](../../.agent-context/state)) and .agent-context/policies/ ([link](../../.agent-context/policies)) only when relevant.
+7. Use project docs and live evidence for runtime, dependency, and architecture claims.
+
+## Bootstrap Receipt
+
+For non-trivial coding, review, planning, or governance work, produce a short Bootstrap Receipt before implementation output: `loaded_files`, `selected_rules`, `skipped_rules`, `unreachable_files`, and `validation_plan`.
+
+## Completion Gate
+
+Run [pr-checklist.md](../../.agent-context/review-checklists/pr-checklist.md) before declaring work complete.
+
+If this adapter drifts from canonical behavior, refresh from [.instructions.md](../../.instructions.md) and update the hash metadata.

package/.cursorrules

@@ -1,92 +1,26 @@
-# AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
+# .cursorrules - Legacy Thin Adapter
 
-Generated by Agentic-Senior-Core CLI v3.0.37
-Timestamp: 2026-04-26T23:31:29.580Z
-Selected policy file: .agent-context/policies/llm-judge-threshold.json
-
-## GOVERNANCE PRECEDENCE
-1. Follow this compiled rulebook as the primary source.
-2. Resolve exceptions from .agent-override.md only when explicitly defined.
-3. Use architecture-map.md and dependency-map.md as change safety boundaries.
-4. Enforce pr-checklist.md before declaring completion.
-
-## OVERRIDE PROTOCOL
-- Default: strict compliance with this file.
-- Exception path: .agent-override.md may explicitly allow narrow deviations.
-- Scope policy: every override must include module scope, rationale, and expiry date.
+Generated by Agentic-Senior-Core CLI v3.0.38
+Adapter Mode: legacy-thin
+Adapter Source: .agent-instructions.md when present; fallback .instructions.md
+Canonical baseline: .instructions.md
 
-## BOOTSTRAP CHAIN (MANDATORY)
-Resolve the smallest relevant layer set before responding. Do not eagerly load unrelated layers:
-1. .agent-context/rules/
-2. Resolve runtime and architecture signals from project context, repo evidence, and live research.
-3. .agent-context/prompts/
-4. Dynamic runtime and architecture decision signals (from project context + research evidence)
-5. .agent-context/state/
-6. .agent-context/policies/llm-judge-threshold.json
-7. docs/ project context (or bootstrap prompts when docs are not materialized)
+This file is kept only for older Cursor discovery.
+Read .agent-instructions.md for the compiled rulebook when present.
+Use .instructions.md as the canonical policy source.
 
-Project-specific compiled snapshot: .agent-instructions.md
-Compiled adapter entrypoints: .cursorrules, .windsurfrules, .clauderc, .gemini/instructions.md, .github/copilot-instructions.md
-Canonical baseline: .instructions.md
-## LAYER 1: RULES (SCOPE-RESOLVED)
-Available rule files under .agent-context/rules/:
-1. .agent-context/rules/api-docs.md
-2. .agent-context/rules/architecture.md
-3. .agent-context/rules/database-design.md
-4. .agent-context/rules/docker-runtime.md
-5. .agent-context/rules/efficiency-vs-hype.md
-6. .agent-context/rules/error-handling.md
-7. .agent-context/rules/event-driven.md
-8. .agent-context/rules/frontend-architecture.md
-9. .agent-context/rules/git-workflow.md
-10. .agent-context/rules/microservices.md
-11. .agent-context/rules/naming-conv.md
-12. .agent-context/rules/performance.md
-13. .agent-context/rules/realtime.md
-14. .agent-context/rules/security.md
-15. .agent-context/rules/testing.md
+Mandatory load floor:
+1. Read .agent-instructions.md when present; otherwise read .instructions.md.
+2. Load only relevant .agent-context/rules/ by task scope.
+3. Apply matching .agent-context/prompts/ contracts.
+4. Enforce .agent-context/review-checklists/ before completion.
+5. Use .agent-context/state/ and .agent-context/policies/ only when relevant.
+6. Resolve Runtime Decision Signals from repo evidence and live official docs.
+7. Resolve Structural Planning Signals from constraints and architecture boundaries.
 
-Resolution policy: load only the rule files relevant to the current task and prioritize data safety and API contract integrity first, then writing polish.
-## LAYER 2: RUNTIME DECISION REQUIRED
-No runtime stack was selected by the user.
-For a fresh project, the first implementation step is to ask the AI agent to recommend a runtime/framework from the brief, constraints, and live official documentation.
-For an existing project, inspect repo markers and current files directly before editing. Detection evidence is not a migration instruction.
-Do not silently choose a stack from offline defaults.
-## LAYER 2 POLICY: LAZY RULE LOADING
-Primary runtime constraint: unresolved until agent recommendation is approved
-No stack-specific governance adapter is loaded by default.
-Load global domain rules only when task scope touches that domain.
-Avoid eager loading unrelated runtime or domain guidance to prevent instruction conflicts.
-## LAYER 5: EXECUTION PROMPTS AND UI TRIGGERS
-Load these prompt contracts only when their trigger matches the user request:
-0. Documentation-first mode -> docs, documentation, dokumen, docs/*, architecture docs, flow docs, API docs, lengkapkan docs
-1. .agent-context/prompts/init-project.md -> create, build, new project, scaffold
-2. .agent-context/prompts/refactor.md -> refactor, improve, clean up, fix
-3. .agent-context/prompts/review-code.md -> review, audit, check, analyze
-4. .agent-context/prompts/bootstrap-design.md -> ui, ux, layout, screen, tailwind, frontend, redesign
-Documentation-first policy:
-- Create or refine required project docs before implementation: docs/project-brief.md, docs/architecture-decision-record.md, docs/flow-overview.md, docs/api-contract.md when APIs, firmware endpoints, CLI commands, or web application flows exist, docs/database-schema.md when persistent data exists, and docs/DESIGN.md plus docs/design-intent.json for UI scope.
-- Write formal project docs in English by default unless the user explicitly asks for another documentation language.
-- For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.
-UI trigger policy:
-- Load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md first.
-- Keep UI-only requests context-isolated and do not eagerly load backend-only rules such as database-design.md, docker-runtime.md, microservices.md, git-workflow.md, or general implementation-theory rules unless the task explicitly crosses those boundaries.
-- For UI scope, materialize docs/DESIGN.md and docs/design-intent.json before implementing UI surfaces.
-## LAYER 3: ARCHITECTURE DECISION REQUIRED
-No architecture blueprint was selected by the user.
-The AI agent must propose the architecture from the product brief, repo evidence, required docs, and live research before implementation.
-Do not map detected runtime markers into a blueprint automatically.
-## LAYER 3B: CI/CD GUARDRAILS
-Load these CI blueprints when pipeline or release logic is touched:
-1. ci-github-actions.md (dynamic CI policy signal)
-2. ci-gitlab.md (dynamic CI policy signal)
-## LAYER 7: STATE AWARENESS (MANDATORY)
-Load these files before touching critical paths:
-1. .agent-context/state/architecture-map.md
-2. .agent-context/state/dependency-map.md
-Use these maps to prevent unsafe cross-module changes.
-## REVIEW CHECKLISTS (MANDATORY)
-1. .agent-context/review-checklists/pr-checklist.md
-2. .agent-context/review-checklists/architecture-review.md
-Security and performance checks are consolidated inside these two checklist files.
-Do not claim done before checklist pass.
+Current bridges:
+- Cursor: .cursor/rules/agentic-senior-core.mdc
+- Windsurf: .windsurf/rules/agentic-senior-core.md
+- Claude: CLAUDE.md
+- Gemini: GEMINI.md and .gemini/instructions.md
+- Copilot: .github/copilot-instructions.md and .github/instructions/agentic-senior-core.instructions.md

package/.gemini/instructions.md

@@ -2,28 +2,35 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
+Canonical Snapshot SHA256: 75652106d1fc453e9407eb9301e7f38de2e0159190dc47fb0b6e377859d91a46
 
-Canonical policy source: [.instructions.md](../.instructions.md).
+This repository is governed by a strict instruction contract.
+Use [.instructions.md](../.instructions.md) as the canonical policy source.
+Use .agent-context/ for technical rules, prompts, checklists, policies, and state.
+Treat README.md as overview/install/user context only when governance files conflict.
 
-If your host stops at this file, follow this minimum floor:
+## Critical Bootstrap Floor
+
+- If your host stops at this file, continue the chain manually before coding.
 - Read `.agent-instructions.md` next when it exists.
-- For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
+- Memory continuity does not replace bootstrap loading.
+- For UI, UX, layout, screen, tailwind, frontend, or redesign requests, load [bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before code edits.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
-- If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- For UI scope, create or refine `docs/DESIGN.md` and `docs/design-intent.json` before UI implementation.
 - For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
-- For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
-- Memory continuity is host-dependent project memory and does not replace bootstrap loading.
+- For backend, API, data, auth, error, event, queue, worker, or distributed-system requests, load only relevant global rules from .agent-context/rules/ ([link](../.agent-context/rules)).
+- For ecosystem, framework, dependency, or Docker claims, perform live web research.
+- Resolve runtime choices from project evidence and live official documentation; resolve structural planning from constraints and architecture boundaries.
 
-## Bootstrap Sequence
+## Mandatory Bootstrap Chain
 
-1. Load [.instructions.md](../.instructions.md) first as the canonical baseline.
-2. If `.agent-instructions.md` exists, read it next as the compiled project-specific snapshot.
-3. Apply baseline rules from [.agent-context/rules/](../.agent-context/rules).
-4. Load request templates from [.agent-context/prompts/](../.agent-context/prompts).
-5. Apply review contracts from [.agent-context/review-checklists/](../.agent-context/review-checklists).
-6. Apply state awareness from [.agent-context/state/](../.agent-context/state) and policy thresholds from [.agent-context/policies/](../.agent-context/policies).
-7. Resolve runtime, structure, and dependency choices from project context docs plus live evidence.
+1. Load [.instructions.md](../.instructions.md).
+2. Load `.agent-instructions.md` when present.
+3. Load only relevant files from .agent-context/rules/ ([link](../.agent-context/rules)).
+4. Apply matching prompts from .agent-context/prompts/ ([link](../.agent-context/prompts)).
+5. Enforce .agent-context/review-checklists/ ([link](../.agent-context/review-checklists/pr-checklist.md)).
+6. Use .agent-context/state/ ([link](../.agent-context/state)) and .agent-context/policies/ ([link](../.agent-context/policies)) only when relevant.
+7. Use project docs and live evidence for runtime, dependency, and architecture claims.
 
 ## Bootstrap Receipt
 
@@ -31,4 +38,6 @@ For non-trivial coding, review, planning, or governance work, produce a short Bo
 
 ## Completion Gate
 
-Run [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring completion.
+Run [pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring work complete.
+
+If this adapter drifts from canonical behavior, refresh from [.instructions.md](../.instructions.md) and update the hash metadata.

package/.github/copilot-instructions.md

@@ -2,28 +2,35 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
+Canonical Snapshot SHA256: 75652106d1fc453e9407eb9301e7f38de2e0159190dc47fb0b6e377859d91a46
 
-The canonical policy source for this repository is [.instructions.md](../.instructions.md).
+This repository is governed by a strict instruction contract.
+Use [.instructions.md](../.instructions.md) as the canonical policy source.
+Use .agent-context/ for technical rules, prompts, checklists, policies, and state.
+Treat README.md as overview/install/user context only when governance files conflict.
 
-If your host stops at this file, follow this minimum floor:
+## Critical Bootstrap Floor
+
+- If your host stops at this file, continue the chain manually before coding.
 - Read `.agent-instructions.md` next when it exists.
-- For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
+- Memory continuity does not replace bootstrap loading.
+- For UI, UX, layout, screen, tailwind, frontend, or redesign requests, load [bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before code edits.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
-- If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- For UI scope, create or refine `docs/DESIGN.md` and `docs/design-intent.json` before UI implementation.
 - For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
-- For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
-- Memory continuity is host-dependent project memory and does not replace bootstrap loading.
+- For backend, API, data, auth, error, event, queue, worker, or distributed-system requests, load only relevant global rules from .agent-context/rules/ ([link](../.agent-context/rules)).
+- For ecosystem, framework, dependency, or Docker claims, perform live web research.
+- Resolve runtime choices from project evidence and live official documentation; resolve structural planning from constraints and architecture boundaries.
 
-## Required Load Order
+## Mandatory Bootstrap Chain
 
-1. Read [.instructions.md](../.instructions.md) first as the canonical baseline.
-2. If `.agent-instructions.md` exists, read it next as the compiled project-specific snapshot.
-3. Read baseline rules in [.agent-context/rules/](../.agent-context/rules).
-4. Load request templates from [.agent-context/prompts/](../.agent-context/prompts).
-5. Apply review contracts from [.agent-context/review-checklists/](../.agent-context/review-checklists).
-6. Apply state awareness from [.agent-context/state/](../.agent-context/state) and thresholds from [.agent-context/policies/](../.agent-context/policies).
-7. Resolve runtime, structure, and dependency choices from project context docs plus live evidence.
+1. Load [.instructions.md](../.instructions.md).
+2. Load `.agent-instructions.md` when present.
+3. Load only relevant files from .agent-context/rules/ ([link](../.agent-context/rules)).
+4. Apply matching prompts from .agent-context/prompts/ ([link](../.agent-context/prompts)).
+5. Enforce .agent-context/review-checklists/ ([link](../.agent-context/review-checklists/pr-checklist.md)).
+6. Use .agent-context/state/ ([link](../.agent-context/state)) and .agent-context/policies/ ([link](../.agent-context/policies)) only when relevant.
+7. Use project docs and live evidence for runtime, dependency, and architecture claims.
 
 ## Bootstrap Receipt
 
@@ -31,4 +38,6 @@ For non-trivial coding, review, planning, or governance work, produce a short Bo
 
 ## Completion Gate
 
-Run [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring work complete.
+Run [pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring work complete.
+
+If this adapter drifts from canonical behavior, refresh from [.instructions.md](../.instructions.md) and update the hash metadata.

package/.github/instructions/agentic-senior-core.instructions.md

@@ -0,0 +1,47 @@
+---
+applyTo: "**"
+---
+
+# GitHub Copilot Path Instructions - Thin Adapter
+
+Adapter Mode: thin
+Adapter Source: .instructions.md
+Canonical Snapshot SHA256: 75652106d1fc453e9407eb9301e7f38de2e0159190dc47fb0b6e377859d91a46
+
+This repository is governed by a strict instruction contract.
+Use [.instructions.md](../../.instructions.md) as the canonical policy source.
+Use .agent-context/ for technical rules, prompts, checklists, policies, and state.
+Treat README.md as overview/install/user context only when governance files conflict.
+
+## Critical Bootstrap Floor
+
+- If your host stops at this file, continue the chain manually before coding.
+- Read `.agent-instructions.md` next when it exists.
+- Memory continuity does not replace bootstrap loading.
+- For UI, UX, layout, screen, tailwind, frontend, or redesign requests, load [bootstrap-design.md](../../.agent-context/prompts/bootstrap-design.md) and [frontend-architecture.md](../../.agent-context/rules/frontend-architecture.md) before code edits.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
+- For UI scope, create or refine `docs/DESIGN.md` and `docs/design-intent.json` before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
+- For backend, API, data, auth, error, event, queue, worker, or distributed-system requests, load only relevant global rules from .agent-context/rules/ ([link](../../.agent-context/rules)).
+- For ecosystem, framework, dependency, or Docker claims, perform live web research.
+- Resolve runtime choices from project evidence and live official documentation; resolve structural planning from constraints and architecture boundaries.
+
+## Mandatory Bootstrap Chain
+
+1. Load [.instructions.md](../../.instructions.md).
+2. Load `.agent-instructions.md` when present.
+3. Load only relevant files from .agent-context/rules/ ([link](../../.agent-context/rules)).
+4. Apply matching prompts from .agent-context/prompts/ ([link](../../.agent-context/prompts)).
+5. Enforce .agent-context/review-checklists/ ([link](../../.agent-context/review-checklists/pr-checklist.md)).
+6. Use .agent-context/state/ ([link](../../.agent-context/state)) and .agent-context/policies/ ([link](../../.agent-context/policies)) only when relevant.
+7. Use project docs and live evidence for runtime, dependency, and architecture claims.
+
+## Bootstrap Receipt
+
+For non-trivial coding, review, planning, or governance work, produce a short Bootstrap Receipt before implementation output: `loaded_files`, `selected_rules`, `skipped_rules`, `unreachable_files`, and `validation_plan`.
+
+## Completion Gate
+
+Run [pr-checklist.md](../../.agent-context/review-checklists/pr-checklist.md) before declaring work complete.
+
+If this adapter drifts from canonical behavior, refresh from [.instructions.md](../../.instructions.md) and update the hash metadata.