@ryuenn3123/agentic-senior-core 2.5.22 → 3.0.2

package/.agent-context/prompts/bootstrap-design.md

@@ -0,0 +1,22 @@
+
+# Bootstrap DESIGN.md (UI/UX Art Direction)
+
+When a user requests frontend design or redesign, the agent should automatically synthesize a complete DESIGN.md covering:
+- Visual identity (color palette, typography, spacing, iconography)
+- Layout and navigation principles
+- Component library and atomic design system
+- Accessibility and responsive guidelines
+- User journey and interaction flows
+- Design tokens and handoff notes for developers
+
+The agent must:
+1. Read [AGENTS.md](../../AGENTS.md) for project context and team roles.
+2. Scan all files in [.agent-context/rules/](../rules/) for UI/UX and accessibility standards.
+3. Reference [docs/deep-dive.md](../../docs/deep-dive.md) and [docs/faq.md](../../docs/faq.md) for architecture and product background.
+4. If [docs/DESIGN.md](../../docs/DESIGN.md) exists, check for drift and propose improvements instead of rewriting from scratch.
+5. All references to docs or rules must be clickable markdown links.
+
+Output:
+- Write a full DESIGN.md in markdown, with clear sections and clickable links to referenced docs/rules.
+- Use practical, modern, and accessible design language.
+- Wait for user approval before generating Figma or code assets.

package/.agent-context/prompts/init-project.md

@@ -1,7 +1,41 @@
-# Prompts: Initialize Project
 
-> Copy-paste one of these prompts to your AI agent (Cursor, Windsurf, Copilot, Antigravity) right after cloning this repository.
-> V1.4 recommendation: run `bunx @fatidaprilian/agentic-senior-core init` first to compile dynamic rules operations context (Federated Governance baseline).
+# Project Initialization Prompts
+
+This prompt boots a repository with strict rules operations context (Federated Governance baseline).
+
+When a new project is created or initialized, the agent should automatically:
+1. Read [AGENTS.md](../../AGENTS.md) to understand available roles and knowledge base.
+2. Scan all files in [.agent-context/rules/](../rules/) for mandatory engineering standards.
+3. Review dynamic stack and architecture signals from [docs/deep-dive.md](../../docs/deep-dive.md), [docs/faq.md](../../docs/faq.md), and task constraints.
+
+## Architect Mode (Recommended)
+If the user describes a project or feature, the agent should:
+1. Propose the most efficient technology stack based on requirements and evidence.
+2. Explain why this stack is the best choice for the project.
+3. Draft a high-level architecture plan.
+4. Wait for user approval before scaffolding the project using the selected architecture playbook.
+
+## Direct Blueprint Mode
+If the user specifies a framework/blueprint, the agent should:
+1. Read [AGENTS.md](../../AGENTS.md) for role context.
+2. Scan all files in [.agent-context/rules/](../rules/) for engineering standards.
+3. Reference [docs/deep-dive.md](../../docs/deep-dive.md) and [docs/faq.md](../../docs/faq.md) for stack/blueprint guidance.
+4. Scaffold the initial project structure following the blueprint exactly:
+	- Create all directories and files from the blueprint
+	- Set up environment config and validation (e.g., Zod, Pydantic, FluentValidation)
+	- Set up error handling foundation (base error class + global handler)
+	- Set up the logger
+	- Create a health check endpoint
+	- Initialize the ORM/Database connection
+	- Every file must follow [naming conventions](../rules/naming-conv.md)
+	- Every module must follow [architecture.md](../rules/architecture.md)
+	- Every dependency must be justified per [efficiency-vs-hype.md](../rules/efficiency-vs-hype.md)
+
+## Stacks & Blueprints Reference
+See [docs/roadmap.md](../../docs/roadmap.md) and [docs/deep-dive.md](../../docs/deep-dive.md) for the latest stack and blueprint list.
+
+## UI/UX Bootstrap
+When a user requests frontend or UI/UX design, the agent should automatically execute the [bootstrap-design.md](./bootstrap-design.md) prompt to synthesize DESIGN.md.
 
 ---
 
@@ -16,15 +50,15 @@ Context: You are a Principal Software Architect operating in a workspace with st
 Step 1: Context Gathering
 1. Read `AGENTS.md` to understand your role and available knowledge base.
 2. Scan all files in `.agent-context/rules/` to understand our mandatory engineering laws.
-3. Review the available technology stacks in `.agent-context/stacks/` and blueprints in `.agent-context/blueprints/`.
+3. Review dynamic stack and architecture signals from project docs, repository evidence, and task constraints.
 
 Step 2: Architecture Proposal
 Based strictly on my project description and our repository's existing rules (especially `efficiency-vs-hype.md`):
-1. Propose the most efficient technology stack from our approved profiles.
+1. Propose the most efficient technology stack based on requirements and evidence.
 2. Explain WHY this stack is the best choice for this specific project.
 3. Draft a high-level architecture plan.
 
-Do not write any application code yet. Write your proposal and wait for my approval. Once I approve, you will scaffold the project using the relevant blueprint.
+Do not write any application code yet. Write your proposal and wait for my approval. Once I approve, you will scaffold the project using the selected architecture playbook.
 ```
 
 ---
@@ -38,8 +72,8 @@ I want to build [PROJECT NAME].
 Before writing any code:
 1. Read `AGENTS.md` to understand your role.
 2. Read ALL files in `.agent-context/rules/` to understand our engineering standards.
-3. Read `.agent-context/stacks/[STACK].md` for language-specific guidelines.
-4. Read `.agent-context/blueprints/[BLUEPRINT].md` for the project structure.
+3. Resolve language-specific guidance from dynamic stack signals.
+4. Resolve the project structure from the selected architecture playbook.
 
 Now scaffold the initial project structure following the blueprint exactly:
 - Create all directories and files from the blueprint
@@ -49,38 +83,20 @@ Now scaffold the initial project structure following the blueprint exactly:
 - Create a health check endpoint
 - Initialize the ORM/Database connection
 
-Every file MUST follow the naming conventions from rules/naming-conv.md.
-Every module MUST follow the architecture from rules/architecture.md.
-Every dependency MUST be justified per rules/efficiency-vs-hype.md.
+
+Setiap file harus mengikuti [naming conventions](../rules/naming-conv.md).
+Setiap modul harus mengikuti [architecture.md](../rules/architecture.md).
+Setiap dependency harus justified sesuai [efficiency-vs-hype.md](../rules/efficiency-vs-hype.md).
 ```
 
 ---
 
-## Available Stacks & Blueprints Reference
-
-### Stacks (`[STACK].md`)
-- `typescript`
-- `python`
-- `java`
-- `php`
-- `go`
-- `csharp`
-- `rust`
-- `ruby`
-
-### Blueprints (`[BLUEPRINT].md`)
-| Blueprint | Use When |
-|-----------|----------|
-| `api-nextjs` | Next.js App Router API project |
-| `nestjs-logic` | NestJS backend service |
-| `fastapi-service` | Python FastAPI backend service |
-| `laravel-api` | PHP Laravel 13 API |
-| `spring-boot-api`| Java Spring Boot 4 API |
-| `go-service` | Go chi HTTP service |
-| `aspnet-api` | C# ASP.NET Minimal API |
-| `ci-github-actions`| GitHub Actions CI/CD pipeline |
-| `ci-gitlab`      | GitLab CI/CD pipeline |
-| `observability`  | OpenTelemetry stack |
-| `graphql-grpc-api` | GraphQL / gRPC API definitions |
-| `infrastructure-as-code` | Infrastructure as Code (Terraform | Pulumi) |
-| `kubernetes-manifests` | Kubernetes manifests structure |
+## Referensi Stacks & Blueprints
+
+Lihat [docs/roadmap.md](../../docs/roadmap.md) dan [docs/deep-dive.md](../../docs/deep-dive.md) untuk daftar stack/blueprint terbaru.
+
+---
+
+## Bootstrap UI/UX (DESIGN.md)
+
+Untuk memulai desain UI/UX dari nol, gunakan prompt [bootstrap-design.md](./bootstrap-design.md) agar AI langsung membangunkan Art Director digital Anda.

package/.agent-context/prompts/refactor.md

@@ -13,8 +13,9 @@ Before making changes:
 1. Read .agent-context/rules/architecture.md — ensure proper layer separation.
 2. Read .agent-context/rules/naming-conv.md — fix all naming violations.
 3. Read .agent-context/rules/error-handling.md — fix error handling patterns.
-4. Read .agent-context/stacks/typescript.md — fix TypeScript-specific issues.
+4. Resolve active language guidance from dynamic stack signals (TypeScript in this repository).
 5. Enforce backend universal principles: no clever hacks, no premature abstraction, readability over brevity.
+6. Enforce Universal SOP hard gate: stop implementation if `docs/architecture-decision-record.md` is missing, and for UI scope stop if `docs/DESIGN.md` is missing.
 
 For every change you make, provide a Reasoning Chain:
 - What was wrong (rule reference)

package/.agent-context/prompts/review-code.md

@@ -12,7 +12,7 @@ Run a comprehensive code review on the current codebase (or the files I'm about
 
 Use these checklists:
 1. Read .agent-context/review-checklists/pr-checklist.md — apply every item.
-2. Read .agent-context/review-checklists/security-audit.md — apply every item.
+2. Read .agent-context/review-checklists/architecture-review.md — apply every item.
 3. Apply documentation scope rules exactly: This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations.
 4. Treat scope-style findings as advisory unless they hide factual errors, contract mismatches, or non-negotiable violations.
 5. Enforce documentation hard blockers on changed boundaries: public surface changes, API contract changes, and database structure changes must include synchronized documentation updates.
@@ -20,6 +20,7 @@ Use these checklists:
 7. Enforce cross-session consistency guardian: session handoff must include active architecture contract summary, drift detection must warn before direction changes, and direction changes require explicit user confirmation.
 8. Enforce explain-on-demand state visibility: default responses must avoid unnecessary state-file internals, state internals are exposed only on explicit request, and diagnostic mode must explain relevant state decisions when needed.
 9. Enforce single-source and lazy-loading policy: canonical rule source must be explicitly enforced, language-specific guidance must load lazily based on detected scope, and conflicting duplicate rule instructions must not appear during normal flow.
+10. Enforce Universal SOP hard gate: block coding flow when required project docs are missing (`docs/architecture-decision-record.md`, and for UI scope `docs/DESIGN.md`).
 
 For EVERY violation found:
 - State the exact file and line
@@ -44,7 +45,7 @@ If you want a faster review focusing on the most critical items:
 
 ```
 Quick review the current code. Check ONLY:
-1. Any use of `any` type? (rules/stacks/typescript.md)
+1. Any use of `any` type? (dynamic TypeScript stack guidance)
 2. Any empty catch blocks? (rules/error-handling.md)
 3. Any N+1 queries? (rules/performance.md)
 4. Any hardcoded secrets? (rules/security.md)

package/.agent-context/review-checklists/pr-checklist.md

@@ -44,7 +44,7 @@ VERDICT: PASS / FAIL (X/Y items passed)
 - [ ] No premature abstraction (base classes/util layers created only after repeated stable patterns)
 - [ ] Readability over brevity for maintainability (no compressed one-liners that hide intent)
 
-### 3. Type Safety (→ stacks/typescript.md)
+### 3. Type Safety (→ dynamic TypeScript stack guidance)
 - [ ] No `any` type anywhere (use `unknown` + narrowing)
 - [ ] No `// @ts-ignore` (use `@ts-expect-error` with justification comment)
 - [ ] All function return types are explicit
@@ -129,3 +129,10 @@ VERDICT: PASS / FAIL (X/Y items passed)
 - [ ] Canonical rule source is explicitly defined and enforced
 - [ ] Language-specific guidance is loaded lazily based on detected scope
 - [ ] No conflicting duplicate rule instructions during normal flow
+
+### 15. Universal SOP Consolidation
+- [ ] `.agent-context/rules/` remains the default guidance source for implementation and review
+- [ ] Backend and frontend mindset checks are both applied when scope spans API and UI boundaries
+- [ ] Security and testing requirements remain mandatory after static template purge
+- [ ] Coding flow is blocked if `docs/architecture-decision-record.md` (or `docs/Architecture-Decision-Record.md`) is missing
+- [ ] UI implementation flow is blocked if `docs/DESIGN.md` is missing

package/.agent-context/rules/architecture.md

@@ -13,6 +13,17 @@ These principles are mandatory for backend and shared core modules.
 
 If a short and a clear implementation are functionally equivalent, choose the clear implementation.
 
+## Universal SOP Baseline (Mandatory)
+
+The `.agent-context/rules/` directory is the default guidance source for implementation and review.
+
+- Backend and frontend mindset checks are both required when a task spans API and UI boundaries.
+- Security and testing are non-negotiable baseline requirements.
+- Hard block before coding:
+  - `docs/architecture-decision-record.md` (alias: `docs/Architecture-Decision-Record.md`) must exist.
+  - For UI scope, `docs/DESIGN.md` must exist.
+- If required project context docs are missing, stop implementation and bootstrap docs before writing application code.
+
 ## Rules as Guardian (Cross-Session Consistency)
 
 These guardrails are mandatory to preserve architecture direction across sessions.

package/.agent-context/rules/frontend-architecture.md

@@ -11,8 +11,8 @@ UI scope trigger signals (any one is enough):
 - feature requests that include frontend deliverables even when backend changes are also included
 
 Mandatory behavior when triggered:
-- apply frontend excellence rubric checks from `.agent-context/review-checklists/frontend-excellence-rubric.md`
-- apply usability checks from `.agent-context/review-checklists/frontend-usability.md`
+- apply consolidated review checks from `.agent-context/review-checklists/pr-checklist.md`
+- apply structural checks from `.agent-context/review-checklists/architecture-review.md`
 - score and review generated UI work against visual intent, interaction quality, and conversion clarity
 - reject template-only repetitive outputs and force a distinct layout direction
 

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

@@ -14,7 +14,7 @@
 
 ## Required Agent Behavior
 
-1. Before editing a `critical` area, load `.agent-context/review-checklists/security-audit.md` and `.agent-context/review-checklists/performance-audit.md`.
+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.
 

package/.agent-context/state/memory-continuity-benchmark.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-18T05:17:09.876Z",
+  "generatedAt": "2026-04-18T13:21:21.615Z",
   "reportName": "memory-continuity-benchmark",
   "schemaVersion": "1.0.0",
   "passed": true,

package/.agents/workflows/init-project.md

@@ -8,13 +8,13 @@ description: Initialize a new project using Agentic-Senior-Core blueprints and e
 
 1. Read all rule files from `.agent-context/rules/` to understand engineering standards.
 
-2. Read the language-specific profile from `.agent-context/stacks/` based on the project's tech stack.
+2. Resolve language-specific guidance from dynamic stack signals based on the project's goals and constraints.
 
-3. Read the chosen blueprint from `.agent-context/blueprints/` (e.g., `api-nextjs.md` or `nestjs-logic.md`).
+3. Resolve the chosen architecture playbook (e.g., `api-nextjs` or `nestjs-logic`).
 
 4. Scaffold the complete project structure following the blueprint exactly:
    - Create all directories and files
-   - Set up strict `tsconfig.json` (all flags from `stacks/typescript.md`)
+   - Set up strict `tsconfig.json` (using active TypeScript guidance)
    - Create `.env.example` with placeholder values
    - Set up Zod-validated environment config
    - Set up error handling foundation (base error class + global handler)

package/.agents/workflows/refactor.md

@@ -10,7 +10,7 @@ description: Refactor code or extract a module following architecture and naming
 
 3. Read `.agent-context/rules/error-handling.md` to understand error handling patterns.
 
-4. Read the active language profile from `.agent-context/stacks/` (e.g., `typescript.md`).
+4. Resolve the active language profile from dynamic stack signals (e.g., TypeScript guidance).
 
 5. Analyze the target code for violations:
    - Layer leaks (business logic in controllers, SQL in services)

package/.agents/workflows/review-code.md

@@ -1,12 +1,11 @@
----
-description: Run a comprehensive code review using PR checklist and security audit
+description: Run a comprehensive code review using PR and architecture checklists
 ---
 
 ## Workflow: Review Code
 
 1. Read `.agent-context/review-checklists/pr-checklist.md` and apply every item against the current codebase.
 
-2. Read `.agent-context/review-checklists/security-audit.md` and apply every item against the current codebase.
+2. Read `.agent-context/review-checklists/architecture-review.md` and apply every item against the current codebase.
 
 3. For every violation found, provide a Reasoning Chain:
    - State the exact file and line
@@ -21,8 +20,8 @@ description: Run a comprehensive code review using PR checklist and security aud
 - PASS or FAIL for each item
 - Reasoning Chain for each failure
 
-## SECURITY AUDIT RESULTS
-- Severity rating (CRITICAL / HIGH / MEDIUM / LOW) for each finding
+## ARCHITECTURE REVIEW RESULTS
+- Boundary violation summary and risk level for each finding
 - Specific remediation for each finding
 
 ## VERDICT: PASS or FAIL

package/.cursorrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v2.5.22
-Timestamp: 2026-04-18T03:00:00.000Z
+Generated by Agentic-Senior-Core CLI v3.0.2
+Timestamp: 2026-04-18T00:00:00.000Z
 Selected profile: beginner
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 
@@ -9,85 +9,41 @@ Selected policy file: .agent-context/policies/llm-judge-threshold.json
 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.
+4. Enforce pr-checklist.md and architecture-review.md before declaring completion.
 
 ## BOOTSTRAP CHAIN (MANDATORY)
 Load every layer before responding. Do not skip steps:
 1. .agent-context/rules/
-2. .agent-context/stacks/
-3. .agent-context/blueprints/
-4. .agent-context/skills/
-5. .agent-context/prompts/
-6. .agent-context/profiles/
-7. .agent-context/state/
-8. .agent-context/policies/llm-judge-threshold.json
+2. Dynamic stack strategy signals from project context and live evidence.
+3. Dynamic architecture playbook signals from requirements and repository state.
+4. .agent-context/prompts/
+5. .agent-context/review-checklists/
+6. .agent-context/state/
+7. .agent-context/policies/llm-judge-threshold.json
+8. docs/ project context (or bootstrap prompts when docs are not materialized)
 
 Primary entrypoint: .cursorrules
 Mirror entrypoint: .windsurfrules
 Canonical baseline: .instructions.md
-## LAYER 1: UNIVERSAL RULES (MANDATORY)
-Read every file under .agent-context/rules/ before implementation:
-1. .agent-context/rules/api-docs.md
-2. .agent-context/rules/architecture.md
-3. .agent-context/rules/database-design.md
-4. .agent-context/rules/efficiency-vs-hype.md
-5. .agent-context/rules/error-handling.md
-6. .agent-context/rules/event-driven.md
-7. .agent-context/rules/frontend-architecture.md
-8. .agent-context/rules/git-workflow.md
-9. .agent-context/rules/microservices.md
-10. .agent-context/rules/naming-conv.md
-11. .agent-context/rules/performance.md
-12. .agent-context/rules/realtime.md
-13. .agent-context/rules/security.md
-14. .agent-context/rules/testing.md
 
+## LAYER 1: UNIVERSAL RULES (MANDATORY)
+Read every file under .agent-context/rules/ before implementation.
 Conflict resolution: prioritize data safety and API contract integrity first, then writing polish.
-## LAYER 2: STACK PROFILE (typescript.md)
-Source: .agent-context/stacks/typescript.md
-Summary: TypeScript Stack Profile — The "Galak" Standard
-Load this stack profile to enforce language-specific conventions.
-## LAYER 3: BLUEPRINT PROFILE (api-nextjs.md)
-Source: .agent-context/blueprints/api-nextjs.md
-Summary: Blueprint: Next.js API Project (App Router)
-Load this blueprint when scaffolding or changing architecture boundaries.
-## LAYER 3B: CI/CD GUARDRAILS
-Load these CI blueprints when pipeline or release logic is touched:
-1. .agent-context/blueprints/ci-github-actions.md
-2. .agent-context/blueprints/ci-gitlab.md
-## SKILL PACK: Frontend
-Source: .agent-context/skills/frontend.md
-Default tier: advance
-Selected tier: advance
-Evidence: Frontend usability audit, accessibility checks, and visual regression output.
-Purpose: Unified frontend delivery covering UI architecture, motion, accessibility, and conversion clarity.
-Load this skill pack and apply every Must-Have Check.
-## SKILL PACK: Fullstack
-Source: .agent-context/skills/fullstack.md
-Default tier: advance
-Selected tier: advance
-Evidence: End-to-end tests, contract validation, and feature parity review.
-Purpose: Single-path product delivery across frontend and backend boundaries.
-Load this skill pack and apply every Must-Have Check.
-## SKILL PACK: CLI
-Source: .agent-context/skills/cli.md
-Default tier: advance
-Selected tier: advance
-Evidence: CLI smoke tests, dry-run output, and automation-friendly reports.
-Purpose: Smart command-line delivery with safe defaults, machine-readable output, and upgrade flows.
-Load this skill pack and apply every Must-Have Check.
-## 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.
+
+## LAYER 2 POLICY: DYNAMIC STACK STRATEGY
+Resolve stack guidance lazily from project evidence. Do not depend on deleted static stack directories.
+
+## LAYER 3 POLICY: DYNAMIC ARCHITECTURE PLAYBOOKS
+Resolve architecture guidance lazily from project docs and task boundaries. Do not depend on deleted static blueprint directories.
+
+## STATE AWARENESS (MANDATORY)
+Load .agent-context/state/architecture-map.md and .agent-context/state/dependency-map.md before touching critical paths.
+
 ## REVIEW CHECKLISTS (MANDATORY)
 1. .agent-context/review-checklists/pr-checklist.md
-2. .agent-context/review-checklists/security-audit.md (when security-sensitive)
-3. .agent-context/review-checklists/performance-audit.md (when perf-critical)
+2. .agent-context/review-checklists/architecture-review.md
 Do not claim done before checklist pass.
+
+## UNIVERSAL SOP HARD GATES
+- Stop coding if docs/architecture-decision-record.md (or docs/Architecture-Decision-Record.md) is missing.
+- For UI scope, stop coding if docs/DESIGN.md is missing.

package/.gemini/instructions.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 2a2a036b4fb90f9e668163b83614f2339044c0d021a6eaf2f380e626dfe72de0
+Canonical Snapshot SHA256: 354edbbfaedec284ddcc6d4a5bb5393a7f5385650d1a6ae84a2d9633b5a6d10d
 
 Canonical policy source: [.instructions.md](../.instructions.md).
 
@@ -10,12 +10,11 @@ Canonical policy source: [.instructions.md](../.instructions.md).
 
 1. Load [.instructions.md](../.instructions.md) first.
 2. Apply baseline rules from [.agent-context/rules/](../.agent-context/rules).
-3. Load language profile from [.agent-context/stacks/](../.agent-context/stacks).
-4. Use [.agent-context/blueprints/](../.agent-context/blueprints) when creating new modules/projects.
-5. Load domain skills from [.agent-context/skills/](../.agent-context/skills).
-6. Load request templates from [.agent-context/prompts/](../.agent-context/prompts).
-7. Apply team defaults from [.agent-context/profiles/](../.agent-context/profiles), state awareness from [.agent-context/state/](../.agent-context/state), and policy thresholds from [.agent-context/policies/](../.agent-context/policies).
+3. Load request templates from [.agent-context/prompts/](../.agent-context/prompts).
+4. Apply review contracts from [.agent-context/review-checklists/](../.agent-context/review-checklists).
+5. Apply state awareness from [.agent-context/state/](../.agent-context/state) and policy thresholds from [.agent-context/policies/](../.agent-context/policies).
+6. Resolve stack and architecture choices dynamically from project context docs plus live evidence.
 
 ## Completion Gate
 
-Run [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring completion.
+Run [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring completion.

package/.github/copilot-instructions.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 2a2a036b4fb90f9e668163b83614f2339044c0d021a6eaf2f380e626dfe72de0
+Canonical Snapshot SHA256: 354edbbfaedec284ddcc6d4a5bb5393a7f5385650d1a6ae84a2d9633b5a6d10d
 
 The canonical policy source for this repository is [.instructions.md](../.instructions.md).
 
@@ -10,11 +10,10 @@ The canonical policy source for this repository is [.instructions.md](../.instru
 
 1. Read [.instructions.md](../.instructions.md) first.
 2. Read baseline rules in [.agent-context/rules/](../.agent-context/rules).
-3. Load language profile from [.agent-context/stacks/](../.agent-context/stacks).
-4. Load blueprints from [.agent-context/blueprints/](../.agent-context/blueprints) for scaffolding requests.
-5. Load domain skills from [.agent-context/skills/](../.agent-context/skills).
-6. Load request templates from [.agent-context/prompts/](../.agent-context/prompts).
-7. Apply team defaults from [.agent-context/profiles/](../.agent-context/profiles), state awareness from [.agent-context/state/](../.agent-context/state), and thresholds from [.agent-context/policies/](../.agent-context/policies).
+3. Load request templates from [.agent-context/prompts/](../.agent-context/prompts).
+4. Apply review contracts from [.agent-context/review-checklists/](../.agent-context/review-checklists).
+5. Apply state awareness from [.agent-context/state/](../.agent-context/state) and thresholds from [.agent-context/policies/](../.agent-context/policies).
+6. Resolve stack and architecture choices dynamically from project context docs plus live evidence.
 
 ## Completion Gate
 

package/.windsurfrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v2.5.22
-Timestamp: 2026-04-18T03:00:00.000Z
+Generated by Agentic-Senior-Core CLI v3.0.2
+Timestamp: 2026-04-18T00:00:00.000Z
 Selected profile: beginner
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 
@@ -9,85 +9,41 @@ Selected policy file: .agent-context/policies/llm-judge-threshold.json
 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.
+4. Enforce pr-checklist.md and architecture-review.md before declaring completion.
 
 ## BOOTSTRAP CHAIN (MANDATORY)
 Load every layer before responding. Do not skip steps:
 1. .agent-context/rules/
-2. .agent-context/stacks/
-3. .agent-context/blueprints/
-4. .agent-context/skills/
-5. .agent-context/prompts/
-6. .agent-context/profiles/
-7. .agent-context/state/
-8. .agent-context/policies/llm-judge-threshold.json
+2. Dynamic stack strategy signals from project context and live evidence.
+3. Dynamic architecture playbook signals from requirements and repository state.
+4. .agent-context/prompts/
+5. .agent-context/review-checklists/
+6. .agent-context/state/
+7. .agent-context/policies/llm-judge-threshold.json
+8. docs/ project context (or bootstrap prompts when docs are not materialized)
 
 Primary entrypoint: .cursorrules
 Mirror entrypoint: .windsurfrules
 Canonical baseline: .instructions.md
-## LAYER 1: UNIVERSAL RULES (MANDATORY)
-Read every file under .agent-context/rules/ before implementation:
-1. .agent-context/rules/api-docs.md
-2. .agent-context/rules/architecture.md
-3. .agent-context/rules/database-design.md
-4. .agent-context/rules/efficiency-vs-hype.md
-5. .agent-context/rules/error-handling.md
-6. .agent-context/rules/event-driven.md
-7. .agent-context/rules/frontend-architecture.md
-8. .agent-context/rules/git-workflow.md
-9. .agent-context/rules/microservices.md
-10. .agent-context/rules/naming-conv.md
-11. .agent-context/rules/performance.md
-12. .agent-context/rules/realtime.md
-13. .agent-context/rules/security.md
-14. .agent-context/rules/testing.md
 
+## LAYER 1: UNIVERSAL RULES (MANDATORY)
+Read every file under .agent-context/rules/ before implementation.
 Conflict resolution: prioritize data safety and API contract integrity first, then writing polish.
-## LAYER 2: STACK PROFILE (typescript.md)
-Source: .agent-context/stacks/typescript.md
-Summary: TypeScript Stack Profile — The "Galak" Standard
-Load this stack profile to enforce language-specific conventions.
-## LAYER 3: BLUEPRINT PROFILE (api-nextjs.md)
-Source: .agent-context/blueprints/api-nextjs.md
-Summary: Blueprint: Next.js API Project (App Router)
-Load this blueprint when scaffolding or changing architecture boundaries.
-## LAYER 3B: CI/CD GUARDRAILS
-Load these CI blueprints when pipeline or release logic is touched:
-1. .agent-context/blueprints/ci-github-actions.md
-2. .agent-context/blueprints/ci-gitlab.md
-## SKILL PACK: Frontend
-Source: .agent-context/skills/frontend.md
-Default tier: advance
-Selected tier: advance
-Evidence: Frontend usability audit, accessibility checks, and visual regression output.
-Purpose: Unified frontend delivery covering UI architecture, motion, accessibility, and conversion clarity.
-Load this skill pack and apply every Must-Have Check.
-## SKILL PACK: Fullstack
-Source: .agent-context/skills/fullstack.md
-Default tier: advance
-Selected tier: advance
-Evidence: End-to-end tests, contract validation, and feature parity review.
-Purpose: Single-path product delivery across frontend and backend boundaries.
-Load this skill pack and apply every Must-Have Check.
-## SKILL PACK: CLI
-Source: .agent-context/skills/cli.md
-Default tier: advance
-Selected tier: advance
-Evidence: CLI smoke tests, dry-run output, and automation-friendly reports.
-Purpose: Smart command-line delivery with safe defaults, machine-readable output, and upgrade flows.
-Load this skill pack and apply every Must-Have Check.
-## 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.
+
+## LAYER 2 POLICY: DYNAMIC STACK STRATEGY
+Resolve stack guidance lazily from project evidence. Do not depend on deleted static stack directories.
+
+## LAYER 3 POLICY: DYNAMIC ARCHITECTURE PLAYBOOKS
+Resolve architecture guidance lazily from project docs and task boundaries. Do not depend on deleted static blueprint directories.
+
+## STATE AWARENESS (MANDATORY)
+Load .agent-context/state/architecture-map.md and .agent-context/state/dependency-map.md before touching critical paths.
+
 ## REVIEW CHECKLISTS (MANDATORY)
 1. .agent-context/review-checklists/pr-checklist.md
-2. .agent-context/review-checklists/security-audit.md (when security-sensitive)
-3. .agent-context/review-checklists/performance-audit.md (when perf-critical)
+2. .agent-context/review-checklists/architecture-review.md
 Do not claim done before checklist pass.
+
+## UNIVERSAL SOP HARD GATES
+- Stop coding if docs/architecture-decision-record.md (or docs/Architecture-Decision-Record.md) is missing.
+- For UI scope, stop coding if docs/DESIGN.md is missing.