@ryuenn3123/agentic-senior-core 3.0.32 → 3.0.34

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

@@ -18,6 +18,7 @@ The agent must:
 5. Treat prior-chat visuals, unrelated project memory, benchmark screenshots, and famous-product aesthetics as tainted context unless the user explicitly asks for continuity.
 6. When choosing a new UI, animation, styling, or component library, research current official docs and choose the latest stable compatible option for this project. Do not rely on offline defaults.
 7. Keep external references non-copying: extract constraints and reasoning only, never clone the surface.
+8. Record a Motion/Palette Decision before UI implementation; product categories are heuristics, not style presets, so override them with task, content density, brand intent, device/performance, and accessibility evidence.
 
 ## Creative Commitment Gate
 
@@ -144,6 +145,7 @@ For every UI task, define how major surfaces change across mobile, tablet, and d
 The JSON must stay machine-readable and project-specific. It should record:
 - the confirmed project context and assumptions to validate
 - agent-chosen visual direction, not scaffold-chosen direction
+- `motionPaletteDecision` with motion density source, required interaction states, palette autopilot risk, and whether 3D/canvas is useful or unnecessary
 - `conceptualAnchor` and how typography, spacing, morphology, motion, and responsive composition derive from it when no external research was provided
 - `derivedTokenLogic` with exact `anchorReference` traceability for color, spacing, typography, and motion tokens
 - `libraryResearchStatus` plus `libraryDecisions[]` with verified source metadata or explicit native/project-local fallbacks

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

@@ -20,6 +20,15 @@ If the user describes a project or feature, the agent must:
 4. Draft a high-level structure plan plus the docs/bootstrap artifacts that must exist before coding.
 5. Wait for user approval before scaffolding the project.
 
+## Documentation-First Requests
+
+If the user asks to create, complete, fix, or review project docs, documentation, dokumen, `docs/*`, architecture docs, flow docs, API docs, or "lengkapkan docs", treat the request as documentation-first.
+
+The agent must:
+1. Materialize or refine required project docs before implementation: `docs/project-brief.md`, `docs/architecture-decision-record.md`, `docs/flow-overview.md`, `docs/api-contract.md` when APIs, firmware endpoints, CLI commands, or web application flows exist, `docs/database-schema.md` when persistent data exists, and `docs/DESIGN.md` plus `docs/design-intent.json` for UI scope.
+2. Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+3. Stop after docs when the user only asked for docs. Do not write application, firmware, or UI code until the user explicitly asks for implementation or approves the implementation plan.
+
 ## Direct Constraint Mode
 
 If the user specifies a framework, runtime, or architecture constraint, the agent must:

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

@@ -60,6 +60,8 @@ Run this before declaring a task done. Apply only the sections relevant to the c
 - [ ] Scope applied: This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations
 - [ ] Style scope review is advisory and does not block merge when API docs are synced in the same commit and contract details are correct
 - [ ] Required docs exist before implementation: project brief, architecture decision, flow overview, API/public contract when relevant, data model when relevant, and UI design contract when relevant.
+- [ ] For docs-only or docs-first requests, implementation code was not changed unless the user explicitly asked for it or approved an implementation plan.
+- [ ] Formal project docs use English by default unless the user requested another language or existing docs established one.
 - [ ] Docs cover feature plan, architecture rationale, public contracts, data model, UI/design, security assumptions, testing strategy, delivery flow, and next validation actions where relevant.
 - [ ] API, event, CLI, library, data, and UI contract changes update docs in the same scope.
 - [ ] Public surface changes fail review if documentation updates are missing or stale in the same scope
@@ -72,6 +74,7 @@ Run this before declaring a task done. Apply only the sections relevant to the c
 
 - [ ] UI work follows `docs/DESIGN.md` and `docs/design-intent.json`.
 - [ ] Visual direction is project-specific and not a template/default component-kit habit.
+- [ ] UI work includes a Motion/Palette Decision, and product categories were treated as heuristics rather than style presets.
 - [ ] Responsive behavior recomposes content and priority, not only shrinking desktop layout.
 - [ ] Accessibility hard requirements are preserved: keyboard access, focus visibility, contrast, target size, status feedback, and no color-only meaning.
 - [ ] Motion is treated as part of the design language for modern UI work, with reduced-motion and performance safeguards instead of defaulting to static screens.

package/.agent-context/rules/api-docs.md

@@ -24,6 +24,10 @@ If a change affects an API, CLI command, exported library behavior, schema, even
 This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations.
 API docs and README updates are included in this scope.
 
+### Language Default
+
+Write formal project docs in English by default, even when the user prompt is in another language. Use another documentation language only when the user explicitly asks for it or when existing project docs already establish that language.
+
 ### Style Baseline
 
 1. Write for native English speakers.

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

@@ -69,6 +69,15 @@ 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`.
 
+## Contextual Motion and Palette Intelligence
+
+- Product categories are heuristics, not style presets. Use them only as a starting signal, then choose motion density from user task, content density, brand intent, device/performance budget, and accessibility needs.
+- If the category is unclear, infer from the dominant task: reading, scanning, form completion, data comparison, product inspection, storytelling, learning, play, or spatial exploration.
+- For interactive UI, map the required states before coding: default, hover, focus-visible, active/pressed, disabled, loading, empty, error, success, and transition.
+- Do not default to dark slate, cream/beige/tan, purple-blue gradients, monochrome palettes, or uniform card surfaces unless current project evidence supports them. If one of those palettes is used, document why it fits and add enough role contrast that the UI does not read as a template.
+- Use the existing motion stack first. Add animation, 3D, canvas, or scroll dependencies only when they materially improve delivery speed, interaction quality, maintainability, or product understanding.
+- Motion should be absent only for a named reason: repeated high-frequency workflow, long-form reading focus, data-density scanning, reduced-motion need, or performance constraint.
+
 ## 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.

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

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-26T15:47:19.183Z",
+  "generatedAt": "2026-04-26T23:40:08.786Z",
   "reportName": "memory-continuity-benchmark",
   "schemaVersion": "1.0.0",
   "passed": true,

package/.cursorrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.32
-Timestamp: 2026-04-24T06:02:48.303Z
+Generated by Agentic-Senior-Core CLI v3.0.34
+Timestamp: 2026-04-26T23:31:29.580Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 
 ## GOVERNANCE PRECEDENCE
@@ -54,15 +54,20 @@ For an existing project, inspect repo markers and current files directly before
 Do not silently choose a stack from offline defaults.
 ## LAYER 2 POLICY: LAZY RULE LOADING
 Primary runtime constraint: unresolved until agent recommendation is approved
-Additional runtime guidance loads only when explicitly selected by the user or required by touched code.
-Load runtime-specific guidance only when task scope touches that runtime.
-Avoid eager loading unrelated runtime guidance to prevent instruction conflicts.
+No stack-specific governance adapter is loaded by default.
+Load global domain rules only when task scope touches that domain.
+Avoid eager loading unrelated runtime or domain guidance to prevent instruction conflicts.
 ## LAYER 5: EXECUTION PROMPTS AND UI TRIGGERS
 Load these prompt contracts only when their trigger matches the user request:
+0. Documentation-first mode -> docs, documentation, dokumen, docs/*, architecture docs, flow docs, API docs, lengkapkan docs
 1. .agent-context/prompts/init-project.md -> create, build, new project, scaffold
 2. .agent-context/prompts/refactor.md -> refactor, improve, clean up, fix
 3. .agent-context/prompts/review-code.md -> review, audit, check, analyze
 4. .agent-context/prompts/bootstrap-design.md -> ui, ux, layout, screen, tailwind, frontend, redesign
+Documentation-first policy:
+- Create or refine required project docs before implementation: docs/project-brief.md, docs/architecture-decision-record.md, docs/flow-overview.md, docs/api-contract.md when APIs, firmware endpoints, CLI commands, or web application flows exist, docs/database-schema.md when persistent data exists, and docs/DESIGN.md plus docs/design-intent.json for UI scope.
+- Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+- For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.
 UI trigger policy:
 - Load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md first.
 - Keep UI-only requests context-isolated and do not eagerly load backend-only rules such as database-design.md, docker-runtime.md, microservices.md, git-workflow.md, or general implementation-theory rules unless the task explicitly crosses those boundaries.

package/.gemini/instructions.md

@@ -2,14 +2,16 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 58ca52e08f9503f55d49dfc64f800bb1124774251db4614478dbdfa618834445
+Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
 
 Canonical policy source: [.instructions.md](../.instructions.md).
 
 If your host stops at this file, follow this minimum floor:
 - Read `.agent-instructions.md` next when it exists.
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 

package/.github/copilot-instructions.md

@@ -2,14 +2,16 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 58ca52e08f9503f55d49dfc64f800bb1124774251db4614478dbdfa618834445
+Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
 
 The canonical policy source for this repository is [.instructions.md](../.instructions.md).
 
 If your host stops at this file, follow this minimum floor:
 - Read `.agent-instructions.md` next when it exists.
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 

package/.instructions.md

@@ -29,6 +29,14 @@ Required fields:
 
 Keep the receipt short. Do not load every rule just to fill it out; scoped loading remains mandatory.
 
+### Output and Command Economy
+
+Avoid repeated command output. Do not rerun the same broad inspection command unless new edits changed its result. Prefer targeted reads, targeted searches, concise diffs, and final validation gates; summarize long logs instead of copying full command output into the response.
+
+### UI Motion and Palette Readability Floor
+
+For any UI-facing request, `bootstrap-design.md` and `frontend-architecture.md` must appear in `selected_rules` before UI code edits. The plan or receipt must include a one-line Motion/Palette Decision: motion density source, required interaction states, palette autopilot risk, and whether 3D/canvas is useful or unnecessary. Product categories are heuristics, not style presets; override them with user task, content density, brand intent, device/performance, and accessibility evidence.
+
 ### Layer 1: Rules (15 Files) [SCOPE-RESOLVED]
 
 **Location**: `.agent-context/rules/`
@@ -153,7 +161,18 @@ Use available MCP tools when you need validation, linting, or test execution.
 
 ## Mandatory Triggers
 
-### 1. New Project Planning
+### 1. Documentation-First Mode
+
+**Trigger**: User asks to create, complete, fix, or review project docs, documentation, dokumen, `docs/*`, architecture docs, flow docs, API docs, or "lengkapkan docs".
+
+**Workflow**:
+
+1. Load `architecture.md` and `api-docs.md`, then load only additional rules needed by the documented scope.
+2. Create or refine the required project docs before implementation: `docs/project-brief.md`, `docs/architecture-decision-record.md`, `docs/flow-overview.md`, `docs/api-contract.md` when APIs, firmware endpoints, CLI commands, or web application flows exist, `docs/database-schema.md` when persistent data exists, and `docs/DESIGN.md` plus `docs/design-intent.json` for UI scope.
+3. Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+4. Stop after documentation when the user only asked for docs. Do not write application, firmware, or UI code until the user explicitly asks for implementation or approves the implementation plan.
+
+### 2. New Project Planning
 
 **Trigger**: User says "create", "build", "new project", or "scaffold"
 
@@ -165,7 +184,7 @@ Use available MCP tools when you need validation, linting, or test execution.
 4. Produce scope, required docs, implementation boundaries, and a runtime/architecture recommendation when those decisions are unresolved.
 5. **WAIT for user approval** before generating code.
 
-### 2. Refactor Mode (EXISTING CODE)
+### 3. Refactor Mode (EXISTING CODE)
 
 **Trigger**: User says "refactor", "improve", "fix", or "clean up"
 
@@ -177,7 +196,7 @@ Use available MCP tools when you need validation, linting, or test execution.
 4. Propose plan before executing changes.
 5. **WAIT for approval**.
 
-### 3. Code Review Mode
+### 4. Code Review Mode
 
 **Trigger**: User says "review", "audit", "check", or "analyze"
 
@@ -188,7 +207,7 @@ Use available MCP tools when you need validation, linting, or test execution.
 3. Execute review against the active rules and contracts.
 4. Generate a structured report.
 
-### 4. UI Design Mode
+### 5. UI Design Mode
 
 **Trigger**: User says "ui", "ux", "layout", "screen", "tailwind", "frontend", or "redesign"
 
@@ -197,10 +216,11 @@ Use available MCP tools when you need validation, linting, or test execution.
 1. Read `.agent-context/prompts/bootstrap-design.md`.
 2. Read `.agent-context/rules/frontend-architecture.md`.
 3. Read UI-relevant repository evidence from `.agent-context/state/onboarding-report.json`, current UI code, and `docs/*`.
-4. Before UI implementation, record a concrete creative commitment in the design contract: one specific real-world anchor reference, one signature motion behavior, and one typographic decision with meaningful role contrast.
-5. Ensure `docs/design-intent.json` includes `conceptualAnchor.anchorReference`, top-level `derivedTokenLogic`, `libraryResearchStatus`, and `libraryDecisions[]` before UI code.
-6. Generate or refine `docs/DESIGN.md` plus `docs/design-intent.json` before UI implementation.
-7. Keep context isolated and do not eagerly load unrelated backend-only rules unless the task explicitly touches those boundaries.
+4. Add a short Motion/Palette Decision before UI implementation; product categories are heuristics, not style presets.
+5. Before UI implementation, record a concrete creative commitment in the design contract: one specific real-world anchor reference, one signature motion behavior, and one typographic decision with meaningful role contrast.
+6. Ensure `docs/design-intent.json` includes `conceptualAnchor.anchorReference`, top-level `derivedTokenLogic`, `libraryResearchStatus`, `libraryDecisions[]`, and motion/palette decisions before UI code.
+7. Generate or refine `docs/DESIGN.md` plus `docs/design-intent.json` before UI implementation.
+8. Keep context isolated and do not eagerly load unrelated backend-only rules unless the task explicitly touches those boundaries.
 
 ---
 

package/.windsurfrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.32
-Timestamp: 2026-04-24T06:02:48.303Z
+Generated by Agentic-Senior-Core CLI v3.0.34
+Timestamp: 2026-04-26T23:31:29.580Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 
 ## GOVERNANCE PRECEDENCE
@@ -54,15 +54,20 @@ For an existing project, inspect repo markers and current files directly before
 Do not silently choose a stack from offline defaults.
 ## LAYER 2 POLICY: LAZY RULE LOADING
 Primary runtime constraint: unresolved until agent recommendation is approved
-Additional runtime guidance loads only when explicitly selected by the user or required by touched code.
-Load runtime-specific guidance only when task scope touches that runtime.
-Avoid eager loading unrelated runtime guidance to prevent instruction conflicts.
+No stack-specific governance adapter is loaded by default.
+Load global domain rules only when task scope touches that domain.
+Avoid eager loading unrelated runtime or domain guidance to prevent instruction conflicts.
 ## LAYER 5: EXECUTION PROMPTS AND UI TRIGGERS
 Load these prompt contracts only when their trigger matches the user request:
+0. Documentation-first mode -> docs, documentation, dokumen, docs/*, architecture docs, flow docs, API docs, lengkapkan docs
 1. .agent-context/prompts/init-project.md -> create, build, new project, scaffold
 2. .agent-context/prompts/refactor.md -> refactor, improve, clean up, fix
 3. .agent-context/prompts/review-code.md -> review, audit, check, analyze
 4. .agent-context/prompts/bootstrap-design.md -> ui, ux, layout, screen, tailwind, frontend, redesign
+Documentation-first policy:
+- Create or refine required project docs before implementation: docs/project-brief.md, docs/architecture-decision-record.md, docs/flow-overview.md, docs/api-contract.md when APIs, firmware endpoints, CLI commands, or web application flows exist, docs/database-schema.md when persistent data exists, and docs/DESIGN.md plus docs/design-intent.json for UI scope.
+- Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+- For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.
 UI trigger policy:
 - Load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md first.
 - Keep UI-only requests context-isolated and do not eagerly load backend-only rules such as database-design.md, docker-runtime.md, microservices.md, git-workflow.md, or general implementation-theory rules unless the task explicitly crosses those boundaries.

package/AGENTS.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 58ca52e08f9503f55d49dfc64f800bb1124774251db4614478dbdfa618834445
+Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
 
 This file is an adapter entrypoint for agent discovery.
 The canonical policy source is [.instructions.md](.instructions.md).
@@ -14,7 +14,9 @@ If your host stops at this file instead of following the full chain, obey the Cr
 - If `.agent-instructions.md` exists, prefer it immediately after this file because it is the compiled project-specific snapshot.
 - Memory continuity does not replace bootstrap loading. It is host-dependent project memory, not a guarantee that instructions were reloaded for this session.
 - For UI, UX, layout, screen, tailwind, frontend, or redesign requests: load [.agent-context/prompts/bootstrap-design.md](.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](.agent-context/rules/frontend-architecture.md) before editing code.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - For UI scope: if `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize or refine them before implementing UI changes.
+- For documentation-first requests: create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend, API, data, auth, error, event, queue, worker, or distributed-system requests: load the relevant global rules from [.agent-context/rules/](.agent-context/rules); do not create stack-specific governance adapters.
 - For refactor, improve, clean up, or fix requests: inspect the active rules and propose a plan before editing.
 - For new project or module requests: clarify constraints, runtime decisions, and required docs before generating code.

package/lib/cli/compiler.mjs

@@ -348,10 +348,15 @@ export async function buildCompiledRulesContent({
     [
       '## LAYER 5: EXECUTION PROMPTS AND UI TRIGGERS',
       'Load these prompt contracts only when their trigger matches the user request:',
+      '0. Documentation-first mode -> docs, documentation, dokumen, docs/*, architecture docs, flow docs, API docs, lengkapkan docs',
       '1. .agent-context/prompts/init-project.md -> create, build, new project, scaffold',
       '2. .agent-context/prompts/refactor.md -> refactor, improve, clean up, fix',
       '3. .agent-context/prompts/review-code.md -> review, audit, check, analyze',
       '4. .agent-context/prompts/bootstrap-design.md -> ui, ux, layout, screen, tailwind, frontend, redesign',
+      'Documentation-first policy:',
+      '- Create or refine required project docs before implementation: docs/project-brief.md, docs/architecture-decision-record.md, docs/flow-overview.md, docs/api-contract.md when APIs, firmware endpoints, CLI commands, or web application flows exist, docs/database-schema.md when persistent data exists, and docs/DESIGN.md plus docs/design-intent.json for UI scope.',
+      '- Write formal project docs in English by default unless the user explicitly asks for another documentation language.',
+      '- For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.',
       'UI trigger policy:',
       '- Load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md first.',
       '- Keep UI-only requests context-isolated and do not eagerly load backend-only rules such as database-design.md, docker-runtime.md, microservices.md, git-workflow.md, or general implementation-theory rules unless the task explicitly crosses those boundaries.',
@@ -536,6 +541,7 @@ export async function buildCompiledRulesContent({
         '- docs/flow-overview.md must also exist before coding continues.',
         '- Add docs/database-schema.md when persistent data is involved.',
         '- Add docs/api-contract.md when API or web application flows are involved.',
+        '- For docs-only/docs-first requests, stop after docs unless the user asks for implementation or approves an implementation plan.',
         '- If docs/project-brief.md is missing, execute bootstrap-project-context prompt immediately.',
         hasBootstrapDesignPrompt
           ? '- For UI scope: if docs/DESIGN.md or docs/design-intent.json is missing, execute bootstrap-design prompt before implementing UI surfaces.'

package/lib/cli/project-scaffolder/design-contract.mjs

@@ -224,6 +224,13 @@ function buildDesignIntentContractObject({
       motionDerivationSource: 'Agent must explain how duration, easing, choreography, and reduced-motion alternatives derive from the chosen anchorReference.',
       validationRule: 'Every primitive, semantic, component, typography, spacing, and motion token must trace back to anchorReference; if a token cannot be explained from the anchor, revise the token.',
     },
+    motionPaletteDecision: {
+      productCategorySignal: 'agent-inferred-starting-heuristic',
+      densityDecisionSource: 'Agent must choose motion density from task, content density, brand intent, device/performance, and accessibility evidence; product categories are heuristics, not style presets.',
+      requiredInteractionStates: ['default', 'hover', 'focus-visible', 'active', 'disabled', 'loading', 'empty', 'error', 'success', 'transition'],
+      paletteAutopilotRisks: ['dark-slate-default', 'cream-beige-default', 'purple-blue-gradient-default', 'monochrome-template-default', 'uniform-card-surface-default'],
+      spatialDecision: 'Agent must state whether 3D/canvas/WebGL is useful or unnecessary for product understanding, exploration, or storytelling.',
+    },
     libraryResearchStatus: 'pending-verification',
     libraryDecisions: [
       {
@@ -270,6 +277,7 @@ function buildDesignIntentContractObject({
       rolePolicy: 'minimum-semantic-scaffold',
       rolesAreMinimumScaffold: true,
       rolesMustBeAgentDefined: true,
+      forbidAutopilotPalettesWithoutEvidence: true,
       intent: inferredKeywords.colorIntent,
     },
     crossViewportAdaptation: {
@@ -281,13 +289,14 @@ function buildDesignIntentContractObject({
       allowMeaningfulMotion: true,
       purpose: inferredKeywords.motionPurpose,
       seedToneLocked: false,
+      densitySource: 'task-content-brand-device-accessibility',
       respectReducedMotion: true,
     },
     componentMorphology: {
       requireStateBehaviorMatrix: true,
       preserveIdentityAcrossViewports: true,
       seedBehaviorsRequireRefinement: true,
-      stateKeys: ['default', 'focus', 'loading', 'error'],
+      stateKeys: ['default', 'hover', 'focus-visible', 'active', 'disabled', 'loading', 'empty', 'error', 'success', 'transition'],
       viewportBehavior: inferredKeywords.componentMorphology,
     },
     accessibilityPolicy: {

package/package.json

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

package/scripts/sync-thin-adapters.mjs

@@ -43,7 +43,9 @@ If your host stops at this file instead of following the full chain, obey the Cr
 - If \`.agent-instructions.md\` exists, prefer it immediately after this file because it is the compiled project-specific snapshot.
 - Memory continuity does not replace bootstrap loading. It is host-dependent project memory, not a guarantee that instructions were reloaded for this session.
 - For UI, UX, layout, screen, tailwind, frontend, or redesign requests: load [.agent-context/prompts/bootstrap-design.md](.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](.agent-context/rules/frontend-architecture.md) before editing code.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - For UI scope: if \`docs/DESIGN.md\` or \`docs/design-intent.json\` is missing, materialize or refine them before implementing UI changes.
+- For documentation-first requests: create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend, API, data, auth, error, event, queue, worker, or distributed-system requests: load the relevant global rules from [.agent-context/rules/](.agent-context/rules); do not create stack-specific governance adapters.
 - For refactor, improve, clean up, or fix requests: inspect the active rules and propose a plan before editing.
 - For new project or module requests: clarify constraints, runtime decisions, and required docs before generating code.
@@ -86,7 +88,9 @@ The canonical policy source for this repository is [.instructions.md](../.instru
 If your host stops at this file, follow this minimum floor:
 - Read \`.agent-instructions.md\` next when it exists.
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and \`docs/DESIGN.md\` or \`docs/design-intent.json\` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 
@@ -122,7 +126,9 @@ Canonical policy source: [.instructions.md](../.instructions.md).
 If your host stops at this file, follow this minimum floor:
 - Read \`.agent-instructions.md\` next when it exists.
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
+- For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and \`docs/DESIGN.md\` or \`docs/design-intent.json\` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 

package/scripts/validate/config.mjs

@@ -24,6 +24,7 @@ export const REQUIRED_HUMAN_WRITING_SNIPPETS = [
       '## Human Writing Standard (Mandatory)',
       'This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations.',
       'Style baseline findings are advisory by default and must not block endpoint-change commits that already include accurate docs/spec updates.',
+      'Write formal project docs in English by default',
       'No emoji in formal artifacts.',
     ],
   },
@@ -32,6 +33,7 @@ export const REQUIRED_HUMAN_WRITING_SNIPPETS = [
     snippets: [
       'Scope applied: This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations',
       'Style scope review is advisory and does not block merge when API docs are synced in the same commit and contract details are correct',
+      'Formal project docs use English by default',
       'No emoji in formal documentation or review summaries',
       'Documentation uses plain English and avoids AI cliches',
     ],
@@ -179,6 +181,14 @@ export const REQUIRED_STACK_DECISION_BOUNDARY_SNIPPETS = [
   },
 ];
 export const REQUIRED_UNIVERSAL_SOP_SNIPPETS = [
+  {
+    path: '.instructions.md',
+    snippets: [
+      '### 1. Documentation-First Mode',
+      'Stop after documentation when the user only asked for docs.',
+      'Do not write application, firmware, or UI code',
+    ],
+  },
   {
     path: '.agent-context/rules/architecture.md',
     snippets: [
@@ -187,6 +197,14 @@ export const REQUIRED_UNIVERSAL_SOP_SNIPPETS = [
       'If required project context docs are missing, stop implementation and bootstrap docs before writing application code.',
     ],
   },
+  {
+    path: '.agent-context/prompts/init-project.md',
+    snippets: [
+      '## Documentation-First Requests',
+      'Stop after docs when the user only asked for docs.',
+      'Write formal project docs in English by default',
+    ],
+  },
   {
     path: '.agent-context/review-checklists/pr-checklist.md',
     snippets: [
@@ -212,6 +230,8 @@ export const REQUIRED_UNIVERSAL_SOP_SNIPPETS = [
     snippets: [
       'Universal SOP hard block policy:',
       'Hard block: do not write application code until docs/project-brief.md and docs/architecture-decision-record.md exist.',
+      'Documentation-first policy:',
+      'For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.',
       'For UI scope: if docs/DESIGN.md or docs/design-intent.json is missing, execute bootstrap-design prompt before implementing UI surfaces.',
     ],
   },
@@ -265,6 +285,11 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'docs/DESIGN.md',
       'docs/design-intent.json',
       'does not replace bootstrap loading',
+      'documentation-first requests',
+      'English by default',
+      'do not write application, firmware, or UI code',
+      'Motion/Palette Decision',
+      'product categories are heuristics',
       'perform live web research',
     ],
   },
@@ -275,6 +300,8 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'UI Design Mode',
       'bootstrap-design.md',
       'frontend-architecture.md',
+      'Motion/Palette Decision',
+      'product categories are heuristics',
       'do not eagerly load unrelated backend-only rules',
       'valid style context',
       'External references, prior-chat memory, unrelated-project visuals, and remembered screenshots are tainted',
@@ -292,6 +319,8 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'Responsive Recomposition Plan',
       'source of truth',
       'research current official docs',
+      'motionPaletteDecision',
+      'product categories are heuristics',
       'Responsive design means recomposition, not resizing.',
       'agent-chosen visual direction',
       'viewport mutation rules',
@@ -349,9 +378,12 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'seedPolicy',
       'structure-first-scaffold',
       'colorTruth',
+      'motionPaletteDecision',
+      'forbidAutopilotPalettesWithoutEvidence',
       'rolesAreMinimumScaffold',
       'crossViewportAdaptation',
       'motionSystem',
+      'densitySource',
       'seedToneLocked',
       'componentMorphology',
       'seedBehaviorsRequireRefinement',

package/scripts/validate/coverage-checks.mjs

@@ -392,6 +392,10 @@ export async function validateInstructionAdapters(context) {
     'unreachable_files',
     'validation_plan',
   ];
+  const requiredUiReadabilitySnippets = [
+    'Motion/Palette Decision',
+    'product categories are heuristics',
+  ];
 
   for (const requiredBootstrapReceiptSnippet of requiredBootstrapReceiptSnippets) {
     if (canonicalInstructionContent.includes(requiredBootstrapReceiptSnippet)) {
@@ -401,6 +405,14 @@ export async function validateInstructionAdapters(context) {
     }
   }
 
+  for (const requiredUiReadabilitySnippet of requiredUiReadabilitySnippets) {
+    if (canonicalInstructionContent.includes(requiredUiReadabilitySnippet)) {
+      pass(`.instructions.md includes UI readability snippet: ${requiredUiReadabilitySnippet}`);
+    } else {
+      fail(`.instructions.md is missing UI readability snippet: ${requiredUiReadabilitySnippet}`);
+    }
+  }
+
   for (const thinAdapterPath of THIN_ADAPTER_PATHS) {
     const absoluteAdapterPath = join(ROOT_DIR, thinAdapterPath);
 
@@ -428,6 +440,14 @@ export async function validateInstructionAdapters(context) {
       }
     }
 
+    for (const requiredUiReadabilitySnippet of requiredUiReadabilitySnippets) {
+      if (thinAdapterContent.includes(requiredUiReadabilitySnippet)) {
+        pass(`${thinAdapterPath} includes UI readability snippet: ${requiredUiReadabilitySnippet}`);
+      } else {
+        fail(`${thinAdapterPath} is missing UI readability snippet: ${requiredUiReadabilitySnippet}`);
+      }
+    }
+
     const hashMatch = thinAdapterContent.match(/Canonical Snapshot SHA256:\s*([a-f0-9]{64})/);
     if (!hashMatch) {
       fail(`${thinAdapterPath} must declare Canonical Snapshot SHA256`);