@ryuenn3123/agentic-senior-core 3.0.37 → 3.0.39

package/.agent-context/state/architecture-map.md

@@ -1,25 +1,40 @@
-# Architecture Map (State Awareness)
+# Architecture Map
 
-> This file defines protected architectural boundaries for AI-assisted changes.
+Use this file as repo-local agent context. It records the current governance architecture and the boundaries agents must protect.
 
 ## Boundary Classification
 
-| Module/Path Pattern | Criticality | Change Policy | Required Checks |
-|---------------------|-------------|---------------|-----------------|
-| `src/modules/payment/**` | critical | Must preserve transactional behavior and idempotency | Unit + integration + rollback test |
-| `src/modules/authentication/**` | critical | Never bypass auth guards or token validation | Security audit + integration tests |
-| `src/modules/**/repository/**` | high | Preserve query contracts and avoid N+1 regressions | Query plan review + performance audit |
-| `src/features/**` | medium | Keep UI contracts stable and avoid API drift | Component tests + contract checks |
-| `src/shared/**` | high | Backward compatibility required for public utilities | Cross-module usage validation |
+| Surface | Criticality | Change Policy | Required Checks |
+| --- | --- | --- | --- |
+| `.instructions.md`, `AGENTS.md`, generated adapters | critical | Keep `.instructions.md` canonical and adapters thin/hash-synced | `npm run sync:adapters`, `npm run check:adapters`, `npm run validate` |
+| `.agent-context/rules/**`, `.agent-context/prompts/**`, `.agent-context/review-checklists/**` | critical | Keep rules imperative, compact, scope-resolved, and non-duplicative | adapter sync, validation, targeted smoke tests |
+| `.agent-context/state/**` | high | Track only seed/config and current operational state; keep generated reports local-only | `npm pack --dry-run`, state README review |
+| `lib/cli/compiler.mjs`, `scripts/sync-thin-adapters.mjs` | critical | Preserve generated surface compatibility across Codex, Cursor, Windsurf, Copilot, Claude, and Gemini | adapter tests, smoke tests, validation |
+| `lib/cli/commands/init.mjs`, `lib/cli/commands/upgrade.mjs` | high | Preserve fresh-project and existing-project behavior without silent stack/style decisions | CLI smoke tests, onboarding report checks |
+| `lib/cli/project-scaffolder/**` | high | Preserve docs-first and design-contract behavior without hardcoded house style | design/detection smoke tests, validation |
+| `scripts/validate*.mjs`, `scripts/validate/**` | high | Keep validation mechanical and aligned with current shipped surfaces | `node ./scripts/validate.mjs`, targeted script checks |
+| `tests/**` | high | Test behavior and contracts, not private implementation trivia | `npm test` |
+| `package.json`, `package-lock.json`, package allowlist | high | Keep release metadata and tarball contents synchronized | `npm pack --dry-run`, release gate |
 
-## Required Agent Behavior
+## Frontend Governance Context
 
-1. Before editing a `critical` area, load `.agent-context/review-checklists/pr-checklist.md` and `.agent-context/review-checklists/architecture-review.md`.
-2. For boundary-crossing changes, verify no circular dependencies are introduced (see `dependency-map.md`).
-3. Every critical-path change must include explicit risk notes in PR description.
+- Frontend guidance is efficient enough for the current architecture because it is scope-resolved: UI tasks load `bootstrap-design.md` and `frontend-architecture.md`; backend-only tasks do not.
+- Keep the current design contract. It does not prescribe a palette or layout; it requires product evidence, anchor-derived tokens, motion/spatial fit decisions, and accessibility.
+- Do not reduce motion, 3D, canvas, WebGL, or animation guidance. These are capability unlocks, not mandatory decoration.
+- Treat product categories as heuristics only. They must not become style presets.
+- Treat grid, line, glow, blob, and abstract-logo backgrounds as review findings unless they serve a named product function.
 
-## Project-Specific Notes
+## Backend Governance Context
 
-- Replace placeholder path patterns with your actual module map.
-- Mark payment, identity, and financial reconciliation flows as `critical`.
-- Keep this file updated whenever module ownership changes.
+- Backend guidance is efficient enough for the current architecture because backend/API rules are lazy-loaded by scope.
+- Keep global backend principles stack-agnostic: architecture boundaries, validation, safe errors, security, testing, event boundaries, and data design.
+- Do not add framework-specific governance adapters unless real repo evidence proves a repeated project need.
+- New dependencies are allowed when they improve efficiency, delivery time, correctness, or maintainability, and current official docs support the choice.
+
+## Agent Behavior
+
+1. Load the smallest relevant rule set.
+2. Use README only for overview/install/user context when governance files conflict.
+3. Preserve generated adapter sync before release.
+4. Treat stale generated state, dual lockfiles, and obsolete V2/V3 transition files as cleanup findings.
+5. Before claiming done, run the relevant validation gate and report any skipped checks.

package/.agent-context/state/dependency-map.md

@@ -1,32 +1,41 @@
-# Dependency Map (State Awareness)
+# Dependency Map
 
-> This map documents allowed dependency direction to prevent circular references during refactors.
+Use this map to keep Agentic-Senior-Core's CLI, governance, and validation layers from collapsing into circular or over-coupled code.
 
-## Layer Dependency Rules
+## Allowed Dependency Direction
 
-1. Transport layer may depend on Service layer.
-2. Service layer may depend on Domain contracts and Repository interfaces.
-3. Infrastructure layer may implement Repository interfaces.
-4. Domain layer must not depend on Transport or Infrastructure.
+1. `bin/` may call command modules only.
+2. `lib/cli/commands/**` may orchestrate detector, compiler, scaffolder, memory, token, backup, rollback, preflight, and utility modules.
+3. `lib/cli/compiler.mjs` may read constants and utilities, but must not import command modules.
+4. `lib/cli/project-scaffolder/**` may use utilities and local scaffolder submodules; validation logic stays below the scaffolder entrypoint.
+5. `scripts/**` may call CLI library modules for audits and reports, but release/validation scripts must avoid mutating generated state unless that is their explicit job.
+6. `tests/**` may exercise public CLI commands, public module exports, scripts, and generated artifacts.
+7. `.agent-context/**` stores governance data and must not depend on generated adapter content as its authority.
 
-## Module-Level Constraints
+## Module Constraints
 
-| Source Module | Allowed Dependencies | Forbidden Dependencies |
-|---------------|----------------------|------------------------|
-| `authentication` | `shared`, `user` | `payment` internals |
-| `payment` | `shared`, `billing`, `notification` contracts | `authentication` internals |
-| `reporting` | `shared`, read-only repository ports | write-side service internals |
-| `frontend` | public API clients only | direct repository access |
+| Source | Allowed Dependencies | Forbidden Dependencies |
+| --- | --- | --- |
+| `bin/agentic-senior-core.js` | `lib/cli/commands/*` | direct compiler, scaffolder, or validation internals |
+| `lib/cli/commands/init.mjs` | detector, compiler, scaffolder, token/memory continuity, setup helpers | UI style presets, backend framework defaults, generated adapters as source |
+| `lib/cli/commands/upgrade.mjs` | detector, compiler, scaffolder seeds, backup/rollback, shared setup helpers | duplicated setup-policy helpers, silent stack migration |
+| `lib/cli/project-scaffolder.mjs` | stable public scaffolder exports | private validation helpers that do not need public API exposure |
+| `lib/cli/project-scaffolder/design-contract.mjs` | validation submodule, constants, utilities | hardcoded final palettes, fixed layouts, external design memory |
+| `scripts/sync-thin-adapters.mjs` | canonical instructions and adapter targets | hand-maintained duplicate policy blocks |
+| `scripts/validate*.mjs` | config, coverage checks, file evidence | stale V2 skill-marketplace artifacts |
+| `.agent-context/prompts/bootstrap-design.md` | current repo evidence and frontend rule | prior-chat visuals, unrelated screenshots, template style presets |
 
 ## Circular Dependency Guardrail
 
-When refactoring:
+- Reject `commands -> project-scaffolder -> commands`.
+- Reject `compiler -> commands`.
+- Reject `scripts/validate -> tests`.
+- Reject generated adapters becoming inputs for `.instructions.md` or `.agent-context/`.
+- Move repeated command setup policy into shared helper modules instead of copying local functions.
 
-1. Detect import graph changes before applying bulk edits.
-2. Reject any change introducing `A -> B -> A` cycles.
-3. Move shared contracts to `shared` module when two-way dependencies appear.
+## Package Hygiene
 
-## Project-Specific Notes
-
-- Replace sample modules with your real domain modules.
-- Keep this map synchronized with architecture decisions and ADRs.
+- Keep one npm lockfile: `package-lock.json`.
+- Ignore Bun lockfiles unless the package manager strategy changes explicitly.
+- Keep generated reports out of the shipped package.
+- Keep `onboarding-report.json` tracked only as current repo operational state; installed projects regenerate it.

package/.cursor/mcp.json

@@ -0,0 +1,10 @@
+{
+  "mcpServers": {
+    "agentic-senior-core": {
+      "command": "node",
+      "args": ["./scripts/mcp-server.mjs"],
+      "cwd": "${workspaceFolder}"
+    }
+  }
+}
+

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.39
+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.