@ryuenn3123/agentic-senior-core 2.0.4 → 2.0.5

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/quality-trend-report.json

@@ -0,0 +1,79 @@
+{
+  "generatedAt": "2026-04-11T09:46:02.646Z",
+  "reportName": "quality-trend-report",
+  "methodology": {
+    "gateSources": [
+      "scripts/release-gate.mjs",
+      "scripts/benchmark-gate.mjs",
+      "scripts/benchmark-intelligence.mjs"
+    ],
+    "rollbackSource": "git log commit subjects within 30-day window",
+    "tokenSource": ".agent-context/state/token-optimization-benchmark.json"
+  },
+  "governanceHealth": {
+    "gateSummaries": [
+      {
+        "scriptPath": "scripts/release-gate.mjs",
+        "gateName": "release-gate",
+        "exitCode": 0,
+        "passed": true,
+        "parseError": null,
+        "failureCount": 0,
+        "generatedAt": "2026-04-11T09:46:02.441Z"
+      },
+      {
+        "scriptPath": "scripts/benchmark-gate.mjs",
+        "gateName": "benchmark-gate",
+        "exitCode": 0,
+        "passed": true,
+        "parseError": null,
+        "failureCount": 0,
+        "generatedAt": "2026-04-11T09:46:02.545Z"
+      },
+      {
+        "scriptPath": "scripts/benchmark-intelligence.mjs",
+        "gateName": "benchmark-intelligence",
+        "exitCode": 0,
+        "passed": true,
+        "parseError": null,
+        "failureCount": 0,
+        "generatedAt": "2026-04-11T09:46:02.595Z"
+      }
+    ],
+    "availableGateCount": 3,
+    "passedGateCount": 3,
+    "gatePassRatePercent": 100
+  },
+  "rejectionCategories": [],
+  "rollbackSignals": {
+    "windowDays": 30,
+    "commitCount": 44,
+    "rollbackCommitCount": 1,
+    "rollbackFrequencyPercent": 2.27,
+    "source": "git-log",
+    "error": null
+  },
+  "tokenEfficiency": {
+    "isAvailable": true,
+    "generatedAt": "2026-04-11T06:14:10.052Z",
+    "averageNativeSavingsPercent": 83.64,
+    "averageRtkSavingsPercent": 18.95,
+    "scenarioCount": 3
+  },
+  "artifact": {
+    "path": "E:\\Project\\Agentic-Senior-Core\\.agent-context\\state\\quality-trend-report.json",
+    "writeMode": "stdout-and-file"
+  },
+  "history": [
+    {
+      "generatedAt": "2026-04-11T09:46:02.646Z",
+      "gatePassRatePercent": 100,
+      "passedGateCount": 3,
+      "availableGateCount": 3,
+      "rollbackFrequencyPercent": 2.27,
+      "averageNativeSavingsPercent": 83.64,
+      "averageRtkSavingsPercent": 18.95,
+      "rejectionCategoryCount": 0
+    }
+  ]
+}

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,6 +1,6 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v2.0.4
+Generated by Agentic-Senior-Core CLI v2.0.5
 Timestamp: 2026-04-08T14:58:53.570Z
 Selected profile: beginner
 Selected policy file: .agent-context/policies/llm-judge-threshold.json

package/.gemini/instructions.md

@@ -1,97 +1,21 @@
-# Antigravity / Gemini Agent Instructions
-
-> These instructions are loaded automatically by Antigravity (Google's AI coding agent).
-> The authoritative knowledge base is in `.agent-context/`.
-
-## Identity
-
-You are a Senior Software Architect with 10+ years of production experience.
-You enforce professional engineering standards. No shortcuts. No "good enough" code.
-
-## Knowledge Base Protocol
-
-Before generating or modifying any code, load the relevant rules:
-
-### Auto-Architect Trigger (MANDATORY FOR NEW PROJECTS)
-If the user's INTENT is to create a new project, system, module, or app (regardless of the exact words used), **IMMEDIATELY** enter Architect Mode:
-1. Read `.agent-context/rules/`, `.agent-context/stacks/`, and `.agent-context/blueprints/` without being asked.
-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
-If the user's INTENT is to refactor, fix, update, or change existing code:
-1. Read `.agent-context/rules/architecture.md` and `.agent-context/rules/naming-conv.md`.
-2. Propose a refactor plan adhering to our standards before modifying any code.
-
-### Step 1: Universal Rules (Always Load)
-Read ALL files in `.agent-context/rules/`:
-- `naming-conv.md` — Descriptive naming, no single-letter variables
-- `architecture.md` — Separation of Concerns, feature-based grouping
-- `security.md` — Validate all input, parameterize queries, never hardcode secrets
-- `performance.md` — Evidence-based optimization, N+1 death penalty
-- `error-handling.md` — Never swallow errors, typed error codes, structured logging
-- `testing.md` — Test pyramid, behavior over implementation
-- `git-workflow.md` — Conventional Commits, atomic changes
-- `efficiency-vs-hype.md` — Stable dependencies over trendy ones
-- `api-docs.md` — OpenAPI mandatory, zero-doc death penalty
-- `microservices.md` — Monolith first, split triggers, strangler fig
-- `event-driven.md` — Event sourcing, CQRS, idempotency
-- `database-design.md` — 3NF default, index FKs, safe migrations
-- `realtime.md` — WebSockets scaling & strict pub/sub
-- `frontend-architecture.md` — Smart/Dumb UI, TanStack Query vs Zustand
-
-### Step 2: Language Profile (By Stack)
-Load the relevant stack from `.agent-context/stacks/`:
-- TypeScript/Node → `stacks/typescript.md`
-- Python → `stacks/python.md`
-- Java/Kotlin → `stacks/java.md`
-- PHP → `stacks/php.md`
-- Go → `stacks/go.md`
-- C#/.NET → `stacks/csharp.md`
-- Rust → `stacks/rust.md`
-- Ruby on Rails → `stacks/ruby.md`
-
-### Step 3: Blueprint (If Scaffolding)
-Load from `.agent-context/blueprints/` when creating new projects.
-
-### Step 4: Review (Before Completion)
-Run `.agent-context/review-checklists/pr-checklist.md` before declaring done.
-
-### Step 5: State + Override (V1.4)
-- Read `.agent-context/state/architecture-map.md` and `.agent-context/state/dependency-map.md` before high-impact refactors.
-- Use `.agent-override.md` only for explicit scoped exceptions.
-
-## 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]
-```
-
-## 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 Security Halt
-If you detect critical security vulnerabilities (e.g., hardcoded secrets, SQL injection, bypassing auth), you MUST halt feature development and refuse to proceed until the vulnerability is patched.
-
-### 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.
-
-## Absolute Clean Code Laws
-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 code without checking `.agent-context/rules/` first.
-5. **No Blind Dependencies:** NEVER introduce dependencies without justification.
-
-## Definition of Done
-**NEVER** declare a task "done" or ready for review without explicitly running and passing `.agent-context/review-checklists/pr-checklist.md`.
+# Gemini Instructions - Thin Adapter
+
+Adapter Mode: thin
+Adapter Source: .instructions.md
+Canonical Snapshot SHA256: ed18aa02954cf7e669d2ade4ea8c36c382bcae66e12b731c6e1ea69a59742480
+
+Canonical policy source: [.instructions.md](../.instructions.md).
+
+## Bootstrap Sequence
+
+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).
+
+## Completion Gate
+
+Run [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring completion.

package/.github/ISSUE_TEMPLATE/v1.7-frontend-work-item.yml

@@ -1,54 +1,54 @@
-name: V1.7 Frontend Work Item
-description: Track a V1.7 frontend task with quality-gate ready acceptance criteria.
-title: "[V1.7][QX] "
-labels:
-  - v1.7
-body:
-  - type: textarea
-    id: background
-    attributes:
-      label: Background
-      description: Why this item exists and what user problem it addresses.
-    validations:
-      required: true
-  - type: textarea
-    id: scope
-    attributes:
-      label: Scope
-      description: What is included in this issue.
-    validations:
-      required: true
-  - type: textarea
-    id: out_of_scope
-    attributes:
-      label: Out of Scope
-      description: What is intentionally excluded.
-    validations:
-      required: true
-  - type: textarea
-    id: acceptance_criteria
-    attributes:
-      label: Acceptance Criteria
-      description: Use measurable and testable criteria.
-      placeholder: |
-        - [ ] ...
-        - [ ] ...
-    validations:
-      required: true
-  - type: textarea
-    id: dependencies
-    attributes:
-      label: Dependencies
-      description: Link prerequisite issues or blockers.
-  - type: textarea
-    id: definition_of_done
-    attributes:
-      label: Definition of Done
-      description: Include testing, documentation, and evidence requirements.
-    validations:
-      required: true
-  - type: textarea
-    id: evidence
-    attributes:
-      label: Evidence
-      description: Screenshots, benchmark output, links to reports.
+name: V1.7 Frontend Work Item
+description: Track a V1.7 frontend task with quality-gate ready acceptance criteria.
+title: "[V1.7][QX] "
+labels:
+  - v1.7
+body:
+  - type: textarea
+    id: background
+    attributes:
+      label: Background
+      description: Why this item exists and what user problem it addresses.
+    validations:
+      required: true
+  - type: textarea
+    id: scope
+    attributes:
+      label: Scope
+      description: What is included in this issue.
+    validations:
+      required: true
+  - type: textarea
+    id: out_of_scope
+    attributes:
+      label: Out of Scope
+      description: What is intentionally excluded.
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance_criteria
+    attributes:
+      label: Acceptance Criteria
+      description: Use measurable and testable criteria.
+      placeholder: |
+        - [ ] ...
+        - [ ] ...
+    validations:
+      required: true
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies
+      description: Link prerequisite issues or blockers.
+  - type: textarea
+    id: definition_of_done
+    attributes:
+      label: Definition of Done
+      description: Include testing, documentation, and evidence requirements.
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Evidence
+      description: Screenshots, benchmark output, links to reports.