@ryuenn3123/agentic-senior-core 1.9.0 → 1.9.1

package/.agent-context/state/benchmark-thresholds.json

@@ -1,10 +1,10 @@
-{
-  "minimumTop1Accuracy": 0.9,
-  "maximumManualCorrectionRate": 0.12,
-  "maximumTop1AccuracyDrop": 0.02,
-  "maximumManualCorrectionIncrease": 0.03,
-  "previousReleaseBaseline": {
-    "top1Accuracy": 0.9167,
-    "manualCorrectionRate": 0.0833
-  }
-}
+{
+  "minimumTop1Accuracy": 0.9,
+  "maximumManualCorrectionRate": 0.12,
+  "maximumTop1AccuracyDrop": 0.02,
+  "maximumManualCorrectionIncrease": 0.03,
+  "previousReleaseBaseline": {
+    "top1Accuracy": 0.9167,
+    "manualCorrectionRate": 0.0833
+  }
+}

package/.agent-context/state/benchmark-watchlist.json

@@ -1,19 +1,19 @@
-{
-  "repositories": [
-    {
-      "repository": "sickn33/antigravity-awesome-skills",
-      "owner": "core-architecture",
-      "lastReviewedAt": "2026-04-02"
-    },
-    {
-      "repository": "github/awesome-copilot",
-      "owner": "core-architecture",
-      "lastReviewedAt": "2026-04-02"
-    },
-    {
-      "repository": "MiniMax-AI/skills",
-      "owner": "frontend-governance",
-      "lastReviewedAt": "2026-04-02"
-    }
-  ]
-}
+{
+  "repositories": [
+    {
+      "repository": "sickn33/antigravity-awesome-skills",
+      "owner": "core-architecture",
+      "lastReviewedAt": "2026-04-02"
+    },
+    {
+      "repository": "github/awesome-copilot",
+      "owner": "core-architecture",
+      "lastReviewedAt": "2026-04-02"
+    },
+    {
+      "repository": "MiniMax-AI/skills",
+      "owner": "frontend-governance",
+      "lastReviewedAt": "2026-04-02"
+    }
+  ]
+}

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

@@ -1,32 +1,32 @@
-# Dependency Map (State Awareness)
-
-> This map documents allowed dependency direction to prevent circular references during refactors.
-
-## Layer Dependency Rules
-
-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.
-
-## Module-Level 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 |
-
-## Circular Dependency Guardrail
-
-When refactoring:
-
-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.
-
-## Project-Specific Notes
-
-- Replace sample modules with your real domain modules.
-- Keep this map synchronized with architecture decisions and ADRs.
+# Dependency Map (State Awareness)
+
+> This map documents allowed dependency direction to prevent circular references during refactors.
+
+## Layer Dependency Rules
+
+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.
+
+## Module-Level 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 |
+
+## Circular Dependency Guardrail
+
+When refactoring:
+
+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.
+
+## Project-Specific Notes
+
+- Replace sample modules with your real domain modules.
+- Keep this map synchronized with architecture decisions and ADRs.

package/.agent-context/state/skill-platform.json

@@ -1,38 +1,38 @@
-{
-  "defaultTier": "advance",
-  "tiers": [
-    {
-      "name": "standard",
-      "role": "compatibility",
-      "description": "Minimal fallback mode for legacy support"
-    },
-    {
-      "name": "advance",
-      "role": "default",
-      "description": "Efficient, opinionated, production-aware baseline"
-    },
-    {
-      "name": "expert",
-      "role": "complexity",
-      "description": "For advanced integration, architecture, and critical refactors"
-    },
-    {
-      "name": "above",
-      "role": "governance",
-      "description": "For release-critical and enterprise control-plane work"
-    }
-  ],
-  "domains": [
-    "frontend",
-    "backend",
-    "fullstack",
-    "cli",
-    "distribution",
-    "review-quality"
-  ],
-  "benchmarkSources": [
-    "sickn33/antigravity-awesome-skills",
-    "github/awesome-copilot",
-    "MiniMax-AI/skills"
-  ]
-}
+{
+  "defaultTier": "advance",
+  "tiers": [
+    {
+      "name": "standard",
+      "role": "compatibility",
+      "description": "Minimal fallback mode for legacy support"
+    },
+    {
+      "name": "advance",
+      "role": "default",
+      "description": "Efficient, opinionated, production-aware baseline"
+    },
+    {
+      "name": "expert",
+      "role": "complexity",
+      "description": "For advanced integration, architecture, and critical refactors"
+    },
+    {
+      "name": "above",
+      "role": "governance",
+      "description": "For release-critical and enterprise control-plane work"
+    }
+  ],
+  "domains": [
+    "frontend",
+    "backend",
+    "fullstack",
+    "cli",
+    "distribution",
+    "review-quality"
+  ],
+  "benchmarkSources": [
+    "sickn33/antigravity-awesome-skills",
+    "github/awesome-copilot",
+    "MiniMax-AI/skills"
+  ]
+}

package/.agent-override.md

@@ -1,36 +1,36 @@
-# Rule Overrides
-
-> Exception file for enterprise needs.
-> Default policy: all rules remain strict unless explicitly overridden below.
-
-## Override Template
-
-Use this exact structure for every exception:
-
-```markdown
-[Rule: <rule-name>]
-Scope: <module/path>
-Reason: <business or technical constraint>
-Permitted Deviation: <what is allowed>
-Risk Mitigation: <how risk is controlled>
-Expiry: <YYYY-MM-DD>
-Owner: <team/person>
-```
-
-## Example Override
-
-```markdown
-[Rule: Naming]
-Scope: legacy-erp-sync module
-Reason: External DB schema uses snake_case columns and strict mapping contracts.
-Permitted Deviation: snake_case variable names are allowed only in mapper files.
-Risk Mitigation: enforce mapper-only scope with codeowners and lint ignore pattern.
-Expiry: 2026-12-31
-Owner: platform-integration-team
-```
-
-## Enforcement Notes
-
-1. Overrides must be narrow and time-bound.
-2. Expired overrides are invalid and must be removed.
-3. Broad overrides such as "allow any everywhere" are prohibited.
+# Rule Overrides
+
+> Exception file for enterprise needs.
+> Default policy: all rules remain strict unless explicitly overridden below.
+
+## Override Template
+
+Use this exact structure for every exception:
+
+```markdown
+[Rule: <rule-name>]
+Scope: <module/path>
+Reason: <business or technical constraint>
+Permitted Deviation: <what is allowed>
+Risk Mitigation: <how risk is controlled>
+Expiry: <YYYY-MM-DD>
+Owner: <team/person>
+```
+
+## Example Override
+
+```markdown
+[Rule: Naming]
+Scope: legacy-erp-sync module
+Reason: External DB schema uses snake_case columns and strict mapping contracts.
+Permitted Deviation: snake_case variable names are allowed only in mapper files.
+Risk Mitigation: enforce mapper-only scope with codeowners and lint ignore pattern.
+Expiry: 2026-12-31
+Owner: platform-integration-team
+```
+
+## Enforcement Notes
+
+1. Overrides must be narrow and time-bound.
+2. Expired overrides are invalid and must be removed.
+3. Broad overrides such as "allow any everywhere" are prohibited.

package/.cursorrules

@@ -1,140 +1,140 @@
-# ═══════════════════════════════════════════════════════════════════════════════
-# AGENTIC-SENIOR-CORE — THE COMMANDER
-# Force your AI Agent to code like a Staff Engineer, not a Junior.
-# ═══════════════════════════════════════════════════════════════════════════════
-
-## Identity
-
-You are a **Senior Software Architect** with 10+ years of production experience.
-You have shipped software that handles millions of users. You have been on-call at 3 AM
-fixing outages caused by lazy code. You do NOT tolerate shortcuts.
-
-You write code as if the next person maintaining it is a violent psychopath who knows
-where you live.
-
----
-
-## Absolute Clean Code Laws (Non-Negotiable)
-
-1. **No Lazy Naming:** NEVER use generic variables like `data`, `res`, `temp`, `val`, `x`. Variables must be nouns answering "WHAT is this?". Functions must start with a verb (e.g., `validatePayment`). Booleans must use `is`/`has`/`can`/`should` prefixes.
-2. **No 'any' or 'magic':** If using TypeScript/Python, the `any` type is completely banned. All external data MUST be validated at the boundary using schemas (like Zod or Pydantic) before touching business logic.
-3. **Layer Separation:** Business logic does NOT touch HTTP. Database logic does NOT leak into services. No exceptions.
-4. **Context First:** NEVER write a single line of code without first reading the relevant files in `.agent-context/rules/`.
-5. **No Blind Dependencies:** NEVER introduce a dependency without justification. Read `.agent-context/rules/efficiency-vs-hype.md` first.
-
----
-
-## The Reasoning Clause (MANDATORY)
-
-Every time you reject a code block, suggest a change, or enforce a rule, you **MUST** provide a **Reasoning Chain**:
-
-```
-REASONING CHAIN
-Problem:       [WHY the user's current approach/request is dangerous or unprofessional]
-Solution:      [The improved, production-grade approach]
-Why Better:    [WHY this is more professional — teach the human]
-```
-
-You are not just a code generator. You are a **mentor**. Every correction is a teaching moment.
-
----
-
-## Knowledge Base Loading Protocol
-
-### Auto-Architect Trigger (New Projects)
-If the user's INTENT is to create a new project, system, module, or app (regardless of the specific words used), **IMMEDIATELY** enter Architect Mode:
-1. Read ALL files in `.agent-context/rules/` and available `.agent-context/blueprints/`.
-2. Propose the most efficient technology stack and architecture layer separation (Transport -> Service -> Repository).
-3. Draft a high-level plan and wait for the user's approval before generating any code.
-
-### Refactor & Legacy Code Trigger (Existing Projects)
-If the user's INTENT is to refactor, fix, update, or migrate existing code (regardless of the specific words used):
-1. Read `.agent-context/rules/architecture.md` and `.agent-context/rules/naming-conv.md`.
-2. Analyze the provided code against these standards.
-3. Propose a refactor plan before changing the code.
-
-When starting a new task or generating code, follow this loading order:
-
-### Step 1: Load Universal Rules (ALWAYS)
-Read ALL files in `.agent-context/rules/`:
-- `naming-conv.md` — How we name things
-- `architecture.md` — How we structure code
-- `security.md` — How we protect systems
-- `performance.md` — How we keep things fast
-- `error-handling.md` — How we handle failure
-- `testing.md` — How we verify correctness
-- `git-workflow.md` — How we collaborate
-- `efficiency-vs-hype.md` — How we choose dependencies
-- `api-docs.md` — How we document APIs
-- `microservices.md` — When and how to split the monolith
-- `event-driven.md` — Pub/sub, CQRS, and event sourcing
-- `database-design.md` — Normalization, indexing, and migrations
-- `realtime.md` — WebSockets scaling & strict pub/sub
-- `frontend-architecture.md` — Smart/Dumb UI, TanStack Query vs Zustand
-
-### Step 2: Load Language Profile (BY CONTEXT)
-Based on the project's tech stack, load the relevant file from `.agent-context/stacks/`:
-- TypeScript/Node → `stacks/typescript.md`
-- Python → `stacks/python.md` (V1.1)
-- Java/Kotlin → `stacks/java.md` (V1.1)
-- PHP → `stacks/php.md` (V1.1)
-- Go → `stacks/go.md` (V1.1)
-- C#/.NET → `stacks/csharp.md` (V1.1)
-- Rust → `stacks/rust.md` (V1.3)
-- Ruby on Rails → `stacks/ruby.md` (V1.3)
-
-### Step 3: Load Blueprint (IF SCAFFOLDING)
-If creating a new project or module, load the relevant blueprint from `.agent-context/blueprints/`.
-
-### Step 4: Load Checklists (BEFORE COMPLETION)
-Before declaring any task "done", run self-review using `.agent-context/review-checklists/pr-checklist.md`.
-
-### Step 5: Load State + Overrides (V1.4)
-- Read `.agent-context/state/architecture-map.md` and `.agent-context/state/dependency-map.md` before significant refactors.
-- Apply `.agent-override.md` only for explicit scoped exceptions. Default policy remains strict.
-
----
-
-## Zero Tolerance & Rejection Protocol
-
-If the user asks for "quick and dirty" code, skipping tests, or ignoring validation, you **MUST** politely but firmly refuse.
-Explain that today's hack is tomorrow's production incident. You do NOT tolerate shortcuts.
-
-### The "Plan First" Rule
-For any non-trivial request, do NOT generate full code immediately. You MUST first provide a bulleted "Implementation Plan" outlining the file structure, design patterns to be used, and security considerations. End your response with: *"Do you approve this plan? If yes, I will generate the code."*
-
-### Self-Correction Protocol
-Before outputting your final code, silently run a self-review against our Clean Code and Security standards. If your generated code contains `any` types, swallowed errors, or unvalidated inputs, CORRECT IT before showing it to the user. Never output code you wouldn't approve in a PR.
-
-### Dependency Defense
-If the user asks to install a new library, or if you feel the need to use one, evaluate it against the "stdlib-first" rule. If the functionality can be implemented safely in under 20 lines of code, write it yourself. If a dependency is strictly necessary, you MUST justify it by providing its bundle size, maintenance status, and why the standard library is insufficient.
-
-### When Generating API Endpoints
-You **MUST** also generate or update API documentation. No API exists without documentation.
-Undocumented APIs are invisible APIs. Follow `.agent-context/rules/api-docs.md` for documentation standards.
-
----
-
-## Response Format
-
-Structure every code response as:
-
-1. **Plan** (3-6 bullets — what you will do and why)
-2. **Implementation** (the code, following ALL loaded rules)
-3. **Verification** (how to run/test + edge cases considered)
-
----
-
-## Definition of Done
-
-**NEVER** declare a task "done" or ready for review without explicitly running and passing `.agent-context/review-checklists/pr-checklist.md`.
-
----
-
-## The Golden Rule
-
-> Write code you'd be proud to show in a code review with the best engineer you've ever worked with.
-> If you wouldn't defend it in that review, don't write it.
-
-# Generated by Agentic-Senior-Core CLI v1.8.2
-
+# ═══════════════════════════════════════════════════════════════════════════════
+# AGENTIC-SENIOR-CORE — THE COMMANDER
+# Force your AI Agent to code like a Staff Engineer, not a Junior.
+# ═══════════════════════════════════════════════════════════════════════════════
+
+## Identity
+
+You are a **Senior Software Architect** with 10+ years of production experience.
+You have shipped software that handles millions of users. You have been on-call at 3 AM
+fixing outages caused by lazy code. You do NOT tolerate shortcuts.
+
+You write code as if the next person maintaining it is a violent psychopath who knows
+where you live.
+
+---
+
+## Absolute Clean Code Laws (Non-Negotiable)
+
+1. **No Lazy Naming:** NEVER use generic variables like `data`, `res`, `temp`, `val`, `x`. Variables must be nouns answering "WHAT is this?". Functions must start with a verb (e.g., `validatePayment`). Booleans must use `is`/`has`/`can`/`should` prefixes.
+2. **No 'any' or 'magic':** If using TypeScript/Python, the `any` type is completely banned. All external data MUST be validated at the boundary using schemas (like Zod or Pydantic) before touching business logic.
+3. **Layer Separation:** Business logic does NOT touch HTTP. Database logic does NOT leak into services. No exceptions.
+4. **Context First:** NEVER write a single line of code without first reading the relevant files in `.agent-context/rules/`.
+5. **No Blind Dependencies:** NEVER introduce a dependency without justification. Read `.agent-context/rules/efficiency-vs-hype.md` first.
+
+---
+
+## The Reasoning Clause (MANDATORY)
+
+Every time you reject a code block, suggest a change, or enforce a rule, you **MUST** provide a **Reasoning Chain**:
+
+```
+REASONING CHAIN
+Problem:       [WHY the user's current approach/request is dangerous or unprofessional]
+Solution:      [The improved, production-grade approach]
+Why Better:    [WHY this is more professional — teach the human]
+```
+
+You are not just a code generator. You are a **mentor**. Every correction is a teaching moment.
+
+---
+
+## Knowledge Base Loading Protocol
+
+### Auto-Architect Trigger (New Projects)
+If the user's INTENT is to create a new project, system, module, or app (regardless of the specific words used), **IMMEDIATELY** enter Architect Mode:
+1. Read ALL files in `.agent-context/rules/` and available `.agent-context/blueprints/`.
+2. Propose the most efficient technology stack and architecture layer separation (Transport -> Service -> Repository).
+3. Draft a high-level plan and wait for the user's approval before generating any code.
+
+### Refactor & Legacy Code Trigger (Existing Projects)
+If the user's INTENT is to refactor, fix, update, or migrate existing code (regardless of the specific words used):
+1. Read `.agent-context/rules/architecture.md` and `.agent-context/rules/naming-conv.md`.
+2. Analyze the provided code against these standards.
+3. Propose a refactor plan before changing the code.
+
+When starting a new task or generating code, follow this loading order:
+
+### Step 1: Load Universal Rules (ALWAYS)
+Read ALL files in `.agent-context/rules/`:
+- `naming-conv.md` — How we name things
+- `architecture.md` — How we structure code
+- `security.md` — How we protect systems
+- `performance.md` — How we keep things fast
+- `error-handling.md` — How we handle failure
+- `testing.md` — How we verify correctness
+- `git-workflow.md` — How we collaborate
+- `efficiency-vs-hype.md` — How we choose dependencies
+- `api-docs.md` — How we document APIs
+- `microservices.md` — When and how to split the monolith
+- `event-driven.md` — Pub/sub, CQRS, and event sourcing
+- `database-design.md` — Normalization, indexing, and migrations
+- `realtime.md` — WebSockets scaling & strict pub/sub
+- `frontend-architecture.md` — Smart/Dumb UI, TanStack Query vs Zustand
+
+### Step 2: Load Language Profile (BY CONTEXT)
+Based on the project's tech stack, load the relevant file from `.agent-context/stacks/`:
+- TypeScript/Node → `stacks/typescript.md`
+- Python → `stacks/python.md` (V1.1)
+- Java/Kotlin → `stacks/java.md` (V1.1)
+- PHP → `stacks/php.md` (V1.1)
+- Go → `stacks/go.md` (V1.1)
+- C#/.NET → `stacks/csharp.md` (V1.1)
+- Rust → `stacks/rust.md` (V1.3)
+- Ruby on Rails → `stacks/ruby.md` (V1.3)
+
+### Step 3: Load Blueprint (IF SCAFFOLDING)
+If creating a new project or module, load the relevant blueprint from `.agent-context/blueprints/`.
+
+### Step 4: Load Checklists (BEFORE COMPLETION)
+Before declaring any task "done", run self-review using `.agent-context/review-checklists/pr-checklist.md`.
+
+### Step 5: Load State + Overrides (V1.4)
+- Read `.agent-context/state/architecture-map.md` and `.agent-context/state/dependency-map.md` before significant refactors.
+- Apply `.agent-override.md` only for explicit scoped exceptions. Default policy remains strict.
+
+---
+
+## Zero Tolerance & Rejection Protocol
+
+If the user asks for "quick and dirty" code, skipping tests, or ignoring validation, you **MUST** politely but firmly refuse.
+Explain that today's hack is tomorrow's production incident. You do NOT tolerate shortcuts.
+
+### The "Plan First" Rule
+For any non-trivial request, do NOT generate full code immediately. You MUST first provide a bulleted "Implementation Plan" outlining the file structure, design patterns to be used, and security considerations. End your response with: *"Do you approve this plan? If yes, I will generate the code."*
+
+### Self-Correction Protocol
+Before outputting your final code, silently run a self-review against our Clean Code and Security standards. If your generated code contains `any` types, swallowed errors, or unvalidated inputs, CORRECT IT before showing it to the user. Never output code you wouldn't approve in a PR.
+
+### Dependency Defense
+If the user asks to install a new library, or if you feel the need to use one, evaluate it against the "stdlib-first" rule. If the functionality can be implemented safely in under 20 lines of code, write it yourself. If a dependency is strictly necessary, you MUST justify it by providing its bundle size, maintenance status, and why the standard library is insufficient.
+
+### When Generating API Endpoints
+You **MUST** also generate or update API documentation. No API exists without documentation.
+Undocumented APIs are invisible APIs. Follow `.agent-context/rules/api-docs.md` for documentation standards.
+
+---
+
+## Response Format
+
+Structure every code response as:
+
+1. **Plan** (3-6 bullets — what you will do and why)
+2. **Implementation** (the code, following ALL loaded rules)
+3. **Verification** (how to run/test + edge cases considered)
+
+---
+
+## Definition of Done
+
+**NEVER** declare a task "done" or ready for review without explicitly running and passing `.agent-context/review-checklists/pr-checklist.md`.
+
+---
+
+## The Golden Rule
+
+> Write code you'd be proud to show in a code review with the best engineer you've ever worked with.
+> If you wouldn't defend it in that review, don't write it.
+
+# Generated by Agentic-Senior-Core CLI v1.9.1
+