@ryuenn3123/agentic-senior-core 3.0.30 → 3.0.32

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

@@ -100,6 +100,7 @@ Do:
 - Synthesize a visual direction from the project context and explain why it fits.
 - Choose color, typography, spacing, motion, density, and component morphology dynamically from the product and audience.
 - Use modern, expressive interaction and motion as part of the core design language, especially when it improves hierarchy, feedback, delight, confidence, or memorability.
+- Use 3D or spatial/canvas experiences as primary UI only when they improve product understanding or exploration while preserving navigation, content clarity, user actions, performance, accessibility, and non-3D fallbacks.
 - Keep frontend code clean, componentized, accessible, and easy to maintain.
 - Use tokens and semantic aliases so future changes do not require rewriting components.
 - Make design decisions explicit before coding, then implement consistently.
@@ -110,6 +111,7 @@ Do not:
 - Let heading, body, data, and metadata collapse into one safe typographic treatment without rationale.
 - Reuse colors, layout shapes, or motion signatures from unrelated memory.
 - Add decorative animation that hurts clarity, accessibility, or runtime performance.
+- Let 3D visuals hide navigation, replace readable content, block core actions, or require a powerful device before the product can be understood.
 - Choose a dependency because this repo scaffold mentioned it. The LLM must verify fit from current project context and official docs.
 
 ## Responsive Rule

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

@@ -5,6 +5,7 @@ Run this before declaring a task done. Apply only the sections relevant to the c
 ## 1. Repo Context
 
 - [ ] The agent read `AGENTS.md` and the smallest relevant rule set.
+- [ ] For non-trivial coding, review, planning, or governance work, the agent produced a Bootstrap Receipt with loaded files, selected rules, skipped rules, unreachable files, and validation plan before implementation output.
 - [ ] Existing project context came from real files, docs, package metadata, and changed code, not folder name alone.
 - [ ] Runtime, framework, library, topology, and design choices are explicit user constraints or agent recommendations from current evidence.
 - [ ] No offline default stack, blueprint, vendor, or visual style was treated as authoritative.

package/.agent-context/rules/efficiency-vs-hype.md

@@ -2,15 +2,17 @@
 
 ## Latest-Compatible-First Rule
 
-The LLM may choose modern libraries and tooling when they fit the project. This rule does not prefer "no library" or any fixed dependency set.
+The LLM may choose modern libraries and tooling when they fit the project. This rule does not prefer "no library", "always add a library", or any fixed dependency set.
+
+New dependencies are allowed when they create a better practical tradeoff than custom implementation. The decision should be based on whether the dependency meaningfully improves efficiency, shortens delivery time, improves correctness, reduces maintenance burden, or avoids unnecessary in-house code.
 
 Before adding or recommending a dependency:
 - check current official docs, release notes, and setup guidance when the ecosystem decision matters
 - choose the latest stable compatible dependency version unless a project constraint blocks it
 - use the official scaffolder or setup command when it creates the current supported project shape
 - Only step down to an older dependency version after documenting the exact compatibility, runtime, platform, or ecosystem reason.
-- explain why the dependency improves maintainability, UX, performance, security, or delivery speed
+- explain why the dependency is a better tradeoff than local implementation for the current task
 - avoid packages that are stale, thinly maintained, too heavy for the job, or added only because they are popular
 - keep dependency boundaries replaceable when the library would spread through many files
 
-Reject offline dependency decisions, outdated tutorial versions, and trend choices that are not grounded in the current repo and brief.
+Reject offline dependency decisions, outdated tutorial versions, trend choices, and dependency avoidance choices that are not grounded in the current repo, brief, and delivery tradeoffs.

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

@@ -69,6 +69,14 @@ Do not use this file to teach generic frontend basics the model already knows.
 - If live research is unavailable, mark `libraryResearchStatus` as `pending-verification`, record the library as `LIBRARY_TO_VERIFY`, and use native CSS, browser APIs, or already-present project dependencies until verification is possible.
 - Each `libraryDecisions[]` entry must have either verification metadata or a concrete `fallbackIfUnavailable`.
 
+## Spatial and 3D Experience Boundary
+
+- 3D, WebGL, canvas, and immersive spatial interfaces are allowed as the primary experience when they clarify the product, strengthen the chosen anchor, or make exploration meaningfully better than a flat UI.
+- 3D must not take over the jobs of navigation, content comprehension, or decisive user actions. Core routes, text, forms, and calls to action must remain discoverable, accessible, and usable without solving the scene.
+- Treat 3D as interaction architecture, not decoration. If it is only a modern-looking background or visual stunt, reduce it to a supporting accent or remove it.
+- Define performance and accessibility fallbacks before implementation: reduced motion, keyboard reachable controls, readable non-canvas content, mobile budgets, loading states, and a graceful non-3D path when rendering fails.
+- When 3D is central, document its product role, interaction model, fallback path, and library/runtime decision in `docs/DESIGN.md` and `docs/design-intent.json` before coding.
+
 ## Responsive Mutation Requirements
 
 - Responsive quality is not allowed to be scale-only. At least one surface must materially change position, grouping, priority, or disclosure strategy between mobile and desktop.

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

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-25T12:31:41.284Z",
+  "generatedAt": "2026-04-26T15:47:19.183Z",
   "reportName": "memory-continuity-benchmark",
   "schemaVersion": "1.0.0",
   "passed": true,

package/.cursorrules

@@ -1,6 +1,6 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.30
+Generated by Agentic-Senior-Core CLI v3.0.32
 Timestamp: 2026-04-24T06:02:48.303Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 

package/.gemini/instructions.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 5c955eab4c644e7139c0c5a5609ea9af7d47fdc8e69617f407af01ccc8c64e43
+Canonical Snapshot SHA256: 58ca52e08f9503f55d49dfc64f800bb1124774251db4614478dbdfa618834445
 
 Canonical policy source: [.instructions.md](../.instructions.md).
 
@@ -23,6 +23,10 @@ If your host stops at this file, follow this minimum floor:
 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.
 
+## 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 [.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: 5c955eab4c644e7139c0c5a5609ea9af7d47fdc8e69617f407af01ccc8c64e43
+Canonical Snapshot SHA256: 58ca52e08f9503f55d49dfc64f800bb1124774251db4614478dbdfa618834445
 
 The canonical policy source for this repository is [.instructions.md](../.instructions.md).
 
@@ -23,6 +23,10 @@ If your host stops at this file, follow this minimum floor:
 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.
 
+## 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 [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring work complete.

package/.instructions.md

@@ -16,6 +16,19 @@ You use clear, plain language in formal artifacts and do not use emoji.
 
 Resolve the smallest relevant layer set for the current request. Do not load every layer by default when the task is narrow.
 
+### Bootstrap Receipt
+
+For non-trivial coding, review, planning, or governance work, produce a concise bootstrap receipt before implementation output or file edits. The receipt is evidence of rule loading, not a request to expose hidden reasoning.
+
+Required fields:
+- `loaded_files`: entrypoint, canonical source, and project files actually read.
+- `selected_rules`: rule, prompt, checklist, state, or policy files selected for the current scope, with a short trigger.
+- `skipped_rules`: categories intentionally left unloaded because they are out of scope.
+- `unreachable_files`: required files that could not be read; stop instead of guessing when this list is non-empty.
+- `validation_plan`: commands or checks expected before completion.
+
+Keep the receipt short. Do not load every rule just to fill it out; scoped loading remains mandatory.
+
 ### Layer 1: Rules (15 Files) [SCOPE-RESOLVED]
 
 **Location**: `.agent-context/rules/`
@@ -29,7 +42,7 @@ Available engineering rule files:
 - `error-handling.md` - Never swallow errors, use typed error codes
 - `testing.md` - Test pyramid, behavior over implementation
 - `git-workflow.md` - Conventional commits and change hygiene
-- `efficiency-vs-hype.md` - Latest-compatible, stable deps over trendy ones
+- `efficiency-vs-hype.md` - Practical dependency and tooling decisions over trend or avoidance bias
 - `api-docs.md` - OpenAPI 3.1 and public surface documentation
 - `microservices.md` - Evidence-required service splits and distributed-system boundaries
 - `event-driven.md` - Idempotency and event boundaries
@@ -38,7 +51,7 @@ Available engineering rule files:
 - `frontend-architecture.md` - UI structure, anti-generic boundaries, responsive mutation
 - `docker-runtime.md` - Latest-docs-first Dockerfile and Compose generation
 
-**What to do**: Resolve only the rule files relevant to the current task. Do not read the entire rule directory by default. For UI-only work, start with `bootstrap-design.md` and `frontend-architecture.md` and keep backend or DevOps rules unloaded unless the task explicitly crosses those boundaries. For Docker or Compose work, load `docker-runtime.md` and verify the latest official Docker docs before authoring container assets. For framework or package setup work, use the latest stable compatible dependency set and official setup flow unless a documented compatibility constraint blocks it.
+**What to do**: Resolve only the rule files relevant to the current task. Do not read the entire rule directory by default. For UI-only work, start with `bootstrap-design.md` and `frontend-architecture.md` and keep backend or DevOps rules unloaded unless the task explicitly crosses those boundaries. For Docker or Compose work, load `docker-runtime.md` and verify the latest official Docker docs before authoring container assets. For framework or package setup work, use the latest stable compatible dependency set and official setup flow unless a documented compatibility constraint blocks it. New dependencies are allowed when they produce a better practical tradeoff than custom implementation, including meaningful efficiency, delivery-time, correctness, or maintainability gains.
 
 ### Global Backend/API Governance Routing
 

package/.windsurfrules

@@ -1,6 +1,6 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.30
+Generated by Agentic-Senior-Core CLI v3.0.32
 Timestamp: 2026-04-24T06:02:48.303Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 

package/AGENTS.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 5c955eab4c644e7139c0c5a5609ea9af7d47fdc8e69617f407af01ccc8c64e43
+Canonical Snapshot SHA256: 58ca52e08f9503f55d49dfc64f800bb1124774251db4614478dbdfa618834445
 
 This file is an adapter entrypoint for agent discovery.
 The canonical policy source is [.instructions.md](.instructions.md).
@@ -31,6 +31,10 @@ If your host stops at this file instead of following the full chain, obey the Cr
 7. Enforce policy thresholds from [.agent-context/policies/](.agent-context/policies).
 8. Use runtime evidence, structure, and live research signals from project context docs.
 
+## 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`.
+
 ## Trigger Rules
 
 - New project or module requests: propose scope, constraints, and required docs first, then wait for approval.

package/lib/cli/utils.mjs

@@ -179,6 +179,14 @@ function isPathWithinPrefix(relativePath, prefixPath) {
     || normalizedRelativePath.startsWith(`${normalizedPrefixPath}/`);
 }
 
+const localOnlyGovernanceFiles = new Set([
+  '.agent-context/state/active-memory.json',
+]);
+
+function isLocalOnlyGovernanceFile(relativePath) {
+  return localOnlyGovernanceFiles.has(toPosixRelativePath(relativePath));
+}
+
 async function collectRelativeTreeEntries(baseDirectoryPath, relativeRootPath) {
   const files = [];
   const directories = [];
@@ -203,6 +211,10 @@ async function collectRelativeTreeEntries(baseDirectoryPath, relativeRootPath) {
         continue;
       }
 
+      if (isLocalOnlyGovernanceFile(relativeEntryPath)) {
+        continue;
+      }
+
       files.push(relativeEntryPath);
     }
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ryuenn3123/agentic-senior-core",
-  "version": "3.0.30",
+  "version": "3.0.32",
   "type": "module",
   "description": "Force your AI Agent to code like a Staff Engineer, not a Junior.",
   "bin": {

package/scripts/sync-thin-adapters.mjs

@@ -60,6 +60,10 @@ If your host stops at this file instead of following the full chain, obey the Cr
 7. Enforce policy thresholds from [.agent-context/policies/](.agent-context/policies).
 8. Use runtime evidence, structure, and live research signals from project context docs.
 
+## 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\`.
+
 ## Trigger Rules
 
 - New project or module requests: propose scope, constraints, and required docs first, then wait for approval.
@@ -96,6 +100,10 @@ If your host stops at this file, follow this minimum floor:
 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.
 
+## 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 [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring work complete.
@@ -128,6 +136,10 @@ If your host stops at this file, follow this minimum floor:
 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.
 
+## 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 [.agent-context/review-checklists/pr-checklist.md](../.agent-context/review-checklists/pr-checklist.md) before declaring completion.

package/scripts/validate/coverage-checks.mjs

@@ -384,6 +384,22 @@ export async function validateInstructionAdapters(context) {
 
   const canonicalInstructionContent = normalizeLineEndings(await readTextFile(CANONICAL_INSTRUCTION_PATH));
   const canonicalSnapshotHash = createHash('sha256').update(canonicalInstructionContent).digest('hex');
+  const requiredBootstrapReceiptSnippets = [
+    'Bootstrap Receipt',
+    'loaded_files',
+    'selected_rules',
+    'skipped_rules',
+    'unreachable_files',
+    'validation_plan',
+  ];
+
+  for (const requiredBootstrapReceiptSnippet of requiredBootstrapReceiptSnippets) {
+    if (canonicalInstructionContent.includes(requiredBootstrapReceiptSnippet)) {
+      pass(`.instructions.md includes bootstrap receipt snippet: ${requiredBootstrapReceiptSnippet}`);
+    } else {
+      fail(`.instructions.md is missing bootstrap receipt snippet: ${requiredBootstrapReceiptSnippet}`);
+    }
+  }
 
   for (const thinAdapterPath of THIN_ADAPTER_PATHS) {
     const absoluteAdapterPath = join(ROOT_DIR, thinAdapterPath);
@@ -404,6 +420,14 @@ export async function validateInstructionAdapters(context) {
       fail(`${thinAdapterPath} must declare Adapter Mode: thin and Adapter Source: .instructions.md`);
     }
 
+    for (const requiredBootstrapReceiptSnippet of requiredBootstrapReceiptSnippets) {
+      if (thinAdapterContent.includes(requiredBootstrapReceiptSnippet)) {
+        pass(`${thinAdapterPath} includes bootstrap receipt snippet: ${requiredBootstrapReceiptSnippet}`);
+      } else {
+        fail(`${thinAdapterPath} is missing bootstrap receipt snippet: ${requiredBootstrapReceiptSnippet}`);
+      }
+    }
+
     const hashMatch = thinAdapterContent.match(/Canonical Snapshot SHA256:\s*([a-f0-9]{64})/);
     if (!hashMatch) {
       fail(`${thinAdapterPath} must declare Canonical Snapshot SHA256`);