@ryuenn3123/agentic-senior-core 3.0.31 → 3.0.33

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
 
@@ -100,6 +101,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 +112,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
@@ -142,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/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.
@@ -71,6 +72,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/frontend-architecture.md

@@ -69,6 +69,23 @@ 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.
+- 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-26T02:26:19.926Z",
+  "generatedAt": "2026-04-26T22:56:14.192Z",
   "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.31
+Generated by Agentic-Senior-Core CLI v3.0.33
 Timestamp: 2026-04-24T06:02:48.303Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 

package/.gemini/instructions.md

@@ -2,13 +2,14 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: c2aef70028abc43f5e3f110a2fa90086cd6697bac42ec97a8d4db3c4477880d4
+Canonical Snapshot SHA256: a49781782fac817a8a979e7937563b67826fd088af160a12cf84bdab4d038624
 
 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 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.
@@ -23,6 +24,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,13 +2,14 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: c2aef70028abc43f5e3f110a2fa90086cd6697bac42ec97a8d4db3c4477880d4
+Canonical Snapshot SHA256: a49781782fac817a8a979e7937563b67826fd088af160a12cf84bdab4d038624
 
 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 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.
@@ -23,6 +24,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,27 @@ 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.
+
+### 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/`
@@ -184,10 +205,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,6 +1,6 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.31
+Generated by Agentic-Senior-Core CLI v3.0.33
 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: c2aef70028abc43f5e3f110a2fa90086cd6697bac42ec97a8d4db3c4477880d4
+Canonical Snapshot SHA256: a49781782fac817a8a979e7937563b67826fd088af160a12cf84bdab4d038624
 
 This file is an adapter entrypoint for agent discovery.
 The canonical policy source is [.instructions.md](.instructions.md).
@@ -14,6 +14,7 @@ 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 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.
@@ -31,6 +32,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/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/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.31",
+  "version": "3.0.33",
   "type": "module",
   "description": "Force your AI Agent to code like a Staff Engineer, not a Junior.",
   "bin": {

package/scripts/sync-thin-adapters.mjs

@@ -43,6 +43,7 @@ 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 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.
@@ -60,6 +61,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.
@@ -82,6 +87,7 @@ 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 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.
@@ -96,6 +102,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.
@@ -114,6 +124,7 @@ 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 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.
@@ -128,6 +139,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/config.mjs

@@ -265,6 +265,8 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'docs/DESIGN.md',
       'docs/design-intent.json',
       'does not replace bootstrap loading',
+      'Motion/Palette Decision',
+      'product categories are heuristics',
       'perform live web research',
     ],
   },
@@ -275,6 +277,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 +296,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 +355,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

@@ -384,6 +384,34 @@ 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',
+  ];
+  const requiredUiReadabilitySnippets = [
+    'Motion/Palette Decision',
+    'product categories are heuristics',
+  ];
+
+  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 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);
@@ -404,6 +432,22 @@ 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}`);
+      }
+    }
+
+    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`);