@ryuenn3123/agentic-senior-core 3.0.16 → 3.0.19

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

@@ -30,6 +30,16 @@ The agent must:
 14. Do not reuse a color palette, component skin, or motion signature from prior chats, memories, or unrelated projects unless current repo evidence or the active brand brief explicitly asks for that continuity.
 15. Treat prior website memory, old portfolio styles, and remembered screenshots as tainted context unless the user explicitly asks to continue or evolve that specific visual system.
 16. Do not default to balanced card grids, soft startup gradients, safe centered heroes, or neutral dashboard chrome unless the product context explicitly justifies them.
+17. For design work, only these count as valid style context by default: current repo evidence, the current user brief, current project docs, and explicitly approved reference systems.
+18. Design continuity is opt-in. If the user does not explicitly ask for continuity with an older system, prefer fresh synthesis from the current repo and brief.
+19. Accessibility must be split into a hard compliance floor and an advisory readability layer. Use WCAG 2.2 AA as the blocking baseline, and use APCA only as advisory perceptual tuning. APCA must never waive a WCAG failure.
+20. Accessibility planning must cover more than color contrast. It must explicitly address focus visibility, focus appearance, target size, keyboard access, accessible authentication, and dynamic state/status access.
+21. Structured design execution must stay representation-first. Define a surface plan, component graph, content-priority map, viewport mutation plan, and interaction-state matrix before relying on semantic review.
+22. Do not depend on screenshot capture, browser automation, or image diff artifacts as the default path. The contract must be strong enough to guide precise UI from repo evidence, component logic, and user intent alone.
+23. Semantic review should judge contract fidelity, distinctiveness, hierarchy, state behavior, and viewport mutation directly from the contract and changed UI code.
+24. Distinctive design review must use a stable review rubric. The contract should define how to judge distinctiveness, contract fidelity, visual consistency, heuristic UX quality, and motion discipline without collapsing those into one vague taste score.
+25. Genericity findings must name the actual drift signal. Do not say "generic" without tying it to a rubric dimension or explicit anti-pattern.
+26. Separate taste from failure. A bold design is valid when it still follows the contract, serves the product, and respects accessibility and runtime constraints.
 
 Required `docs/DESIGN.md` sections:
 1. Design Intent and Product Personality
@@ -42,9 +52,10 @@ Required `docs/DESIGN.md` sections:
 8. Responsive Strategy and Cross-Viewport Adaptation Matrix
 9. Interaction, Motion, and Feedback Rules
 10. Component Language, Morphology, and Shared Patterns
-11. Accessibility Non-Negotiables
-12. Anti-Patterns to Avoid
-13. Implementation Notes for Future UI Tasks
+11. Context Hygiene and Approved Reference Boundaries
+12. Accessibility Non-Negotiables
+13. Anti-Patterns to Avoid
+14. Implementation Notes for Future UI Tasks
 
 Required `docs/design-intent.json` fields:
 - `mode`
@@ -60,6 +71,11 @@ Required `docs/design-intent.json` fields:
 - `crossViewportAdaptation`
 - `motionSystem`
 - `componentMorphology`
+- `accessibilityPolicy`
+- `designExecutionPolicy`
+- `designExecutionHandoff`
+- `reviewRubric`
+- `contextHygiene`
 - `experiencePrinciples`
 - `forbiddenPatterns`
 - `validationHints`
@@ -73,13 +89,24 @@ Output:
 - `docs/design-intent.json` must define a real token system, not just loose style notes. Include primitive, semantic, and component layers plus aliasing rules and naming constraints.
 - `docs/design-intent.json` must include deterministic fields for `colorTruth.format`, `colorTruth.allowHexDerivatives`, and `crossViewportAdaptation.mutationRules.mobile/tablet/desktop`.
 - `docs/design-intent.json` must also include `motionSystem` and `componentMorphology` so future UI work preserves state behavior and purposeful motion without collapsing into generic static output.
+- `docs/design-intent.json` must also include `accessibilityPolicy` so the hard compliance floor, advisory contrast model, and blocking-vs-advisory checks stay machine-readable.
+- `docs/design-intent.json` must also include `designExecutionPolicy` so structured handoff rules, representation strategy, semantic review focus, and non-screenshot execution boundaries stay machine-readable.
+- `docs/design-intent.json` must also include `designExecutionHandoff` so surface plans, component graph relationships, content priority, viewport mutation, interaction states, and signature move rationale are explicit before implementation begins.
+- `docs/design-intent.json` must also include `reviewRubric` so distinctiveness, genericity drift, taste-vs-failure boundaries, and motion discipline are judged with stable dimensions instead of ad hoc opinion.
+- `docs/design-intent.json` must include `contextHygiene` so valid design sources, tainted carryover sources, and continuity rules are machine-readable.
 - If onboarding or detector evidence exists, preserve it under `repoEvidence.designEvidenceSummary` instead of throwing away the machine-readable snapshot of the current UI system.
 - Token intent must stay structure-first: primitive tokens hold raw values, semantic tokens carry purpose, and component tokens consume semantic tokens instead of bypassing them with raw values.
 - Color intent must be defined in a perceptual or relational color model first. Hex values may appear only as implementation derivatives.
 - The contract must encode viewport mutation rules, not just breakpoint names.
 - Motion guidance must preserve creativity: allow meaningful animation, define reduced-motion behavior, and optimize choreography instead of suppressing it by default.
+- Accessibility guidance must split hard compliance from advisory tuning: treat WCAG 2.2 AA as the minimum blocking floor and APCA as advisory perceptual guidance for readability nuance, especially in typography and dark mode.
+- Accessibility scope must include focus visibility, focus appearance, target size, accessible authentication, keyboard access, use-of-color-only failures, and dynamic status/state access.
+- Structured design execution guidance must define the surface plan, component graph, content-priority map, viewport mutation plan, interaction-state matrix, and semantic review focus without relying on screenshot capture.
+- Structured design execution must include an explicit structured handoff in `docs/design-intent.json`, not just policy booleans. The handoff should be detailed enough that a future agent can implement the UI without falling back to generic layout defaults.
+- The review rubric must define stable dimensions, genericity signals, valid bold signals, and reporting rules that force the agent to explain why something is generic or valid.
 - Color direction must come from the current project context. Similarity to prior unrelated projects is drift unless the brief or repo evidence explicitly supports it.
 - If no approved reference system exists, synthesize the design from zero using current product context, constraints, and content only.
-- The resulting system should feel authored and recognizable in screenshots, not politely interchangeable with common template kits.
+- Explicitly record which sources are allowed to shape the visual language and which sources are tainted unless the user opts into continuity.
+- The resulting system should feel authored and recognizable in implementation, not politely interchangeable with common template kits.
 - Use practical, modern, accessible language grounded in the project, not generic SaaS defaults or copycat brand systems.
 - Wait for user approval before generating Figma or code assets.

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

@@ -17,6 +17,32 @@ Mandatory behavior when triggered:
 - reject template-only repetitive outputs and force a distinct layout direction
 - treat prior website memory or old-project visual carryover as invalid evidence unless the user explicitly requests continuity with that exact system
 - do not flatten ambitious visual or motion ideas by default; keep them when they are optimized, intentional, and accessible
+- let current repo evidence, the active brief, current project docs, and explicitly approved reference systems outrank remembered style residue every time
+
+## Context Hygiene and Reference Boundaries (Mandatory)
+
+- Valid visual-context sources are limited to the current repo evidence, the current user brief, current project docs, and explicitly approved reference systems.
+- Design continuity is opt-in. If the user does not request continuity with a prior visual system, synthesize from the current project context instead.
+- Old project screenshots, remembered website styles, and cross-chat visual residue are tainted context unless the user explicitly authorizes them.
+- When repo evidence and memory residue conflict, repo evidence wins.
+- If a reference system is approved, adapt its reasoning and constraints. Do not copy its surface 1:1.
+
+## Accessibility Split (Mandatory)
+
+- Treat WCAG 2.2 AA as the hard compliance floor for release-blocking accessibility issues.
+- Treat APCA as an advisory readability model for perceptual tuning, especially for typography, dark mode, and nuanced contrast review.
+- Advisory APCA findings must never waive a WCAG hard failure.
+- Hard accessibility checks must cover more than contrast alone. They must include focus visibility, focus appearance, target size, keyboard access, use-of-color-only failures, accessible authentication, and status or dynamic state access.
+- Keep accessibility compatible with expressive design. Fix the violation without flattening the interface into generic low-risk layouts unless that is the only safe option.
+
+## Structured Design Execution Boundaries (Mandatory)
+
+- UI review must stay representation-first. The contract should define a surface plan, component graph, content-priority map, viewport mutation plan, interaction-state matrix, and task-flow narrative before implementation drifts into styling guesswork.
+- Semantic review should judge contract fidelity, distinctiveness, hierarchy, component-state behavior, and cross-viewport mutation directly from the contract plus changed UI code.
+- Do not make screenshot capture, browser automation, or pixel diff artifacts a baseline dependency for design quality in this repo.
+- Required coverage must still include mobile, tablet, and desktop behavior unless the product scope explicitly excludes one of those surfaces.
+- Escalate to semantic review only when deterministic evidence shows meaningful drift, missing required viewport coverage, or another contract-critical visual failure.
+- Do not use semantic review to invent aesthetic problems when deterministic evidence says the surface is stable.
 
 ## UI Consistency Guardrails (Mandatory)
 

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

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-22T12:33:03.350Z",
+  "generatedAt": "2026-04-23T10:22:34.642Z",
   "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.16
+Generated by Agentic-Senior-Core CLI v3.0.19
 Timestamp: 2026-04-22T12:30:18.799Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 

package/.gemini/instructions.md

@@ -2,10 +2,16 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 060b739f87a77375f261a13c3b2b295993ba67b4172420c4223ba1332d47b0a3
+Canonical Snapshot SHA256: 3ddc44d1c3cad20aa06e31c45b5d7289b1b4cde46decb668b0347817222fb022
 
 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.
+- If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- Memory continuity is host-dependent project memory and does not replace bootstrap loading.
+
 ## Bootstrap Sequence
 
 1. Load [.instructions.md](../.instructions.md) first as the canonical baseline.

package/.github/copilot-instructions.md

@@ -2,10 +2,16 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 060b739f87a77375f261a13c3b2b295993ba67b4172420c4223ba1332d47b0a3
+Canonical Snapshot SHA256: 3ddc44d1c3cad20aa06e31c45b5d7289b1b4cde46decb668b0347817222fb022
 
 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.
+- If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- Memory continuity is host-dependent project memory and does not replace bootstrap loading.
+
 ## Required Load Order
 
 1. Read [.instructions.md](../.instructions.md) first as the canonical baseline.

package/.instructions.md

@@ -134,6 +134,9 @@ Meta-prompts that provide complete workflows for common scenarios:
 
 **What to do**: When user request matches a trigger, load the full prompt to understand the workflow.
 For UI-only requests, keep context isolated: load `bootstrap-design.md` and `frontend-architecture.md` first, and do not eagerly load unrelated backend-only rules such as `database-design.md`, `docker-runtime.md`, or `microservices.md` unless the request explicitly crosses those boundaries.
+For design work, treat only the current repo evidence, the current brief, current project docs, and explicitly approved reference systems as valid style context. Do not let prior-chat or unrelated-project visual memory steer the result unless the user explicitly asks for continuity.
+For accessibility in UI work, treat WCAG 2.2 AA as the hard compliance floor and APCA as advisory perceptual tuning only.
+For UI review, use structured design execution evidence first: `designExecutionPolicy`, `docs/DESIGN.md`, `repoEvidence.designEvidenceSummary`, and the changed UI diff. Do not require screenshot capture as a baseline dependency.
 
 ---
 

package/.windsurfrules

@@ -1,6 +1,6 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.16
+Generated by Agentic-Senior-Core CLI v3.0.19
 Timestamp: 2026-04-22T12:30:18.799Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 

package/AGENTS.md

@@ -2,11 +2,23 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: 060b739f87a77375f261a13c3b2b295993ba67b4172420c4223ba1332d47b0a3
+Canonical Snapshot SHA256: 3ddc44d1c3cad20aa06e31c45b5d7289b1b4cde46decb668b0347817222fb022
 
 This file is an adapter entrypoint for agent discovery.
 The canonical policy source is [.instructions.md](.instructions.md).
 
+If your host stops at this file instead of following the full chain, obey the Critical Bootstrap Floor below before coding.
+
+## Critical Bootstrap Floor
+
+- 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: if `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize or refine them before implementing UI changes.
+- For refactor, improve, clean up, or fix requests: inspect the active rules and propose a plan before editing.
+- For new project or module requests: propose architecture before generating code.
+- For ecosystem, framework, dependency, or Docker claims: perform live web research instead of relying on stale local heuristics.
+
 ## Mandatory Bootstrap Chain
 
 1. Load [.instructions.md](.instructions.md) first as the canonical baseline.

package/lib/cli/commands/init.mjs

@@ -651,7 +651,7 @@ export async function runInitCommand(targetDirectoryArgument, initOptions = {})
       });
 
       await writeMemoryContinuityState(resolvedTargetDirectoryPath, memoryContinuityState);
-      console.log(`Memory continuity policy enabled (${memoryContinuityState.hydrationMode}).`);
+      console.log(`Project memory continuity metadata enabled (${memoryContinuityState.hydrationMode}, host-supported).`);
     }
 
     let tokenOptimizationState = null;
@@ -844,7 +844,7 @@ export async function runInitCommand(targetDirectoryArgument, initOptions = {})
     console.log(`- Repository workflows copied: no (workflows remain source-repo assets)`);
     console.log(`- MCP configuration: ${shouldIncludeMcpTemplate ? 'auto-configured for your IDEs (VS Code, Cursor, Zed, Gemini)' : 'disabled (--no-mcp-template)'}`);
     if (isMemoryContinuityEnabled) {
-      console.log('- Memory continuity policy: enabled (index + selective hydration)');
+      console.log('- Memory continuity policy: enabled (index + selective hydration; host support required)');
     } else {
       console.log('- Memory continuity policy: disabled (--no-memory-continuity)');
     }

package/lib/cli/memory-continuity.mjs

@@ -379,7 +379,7 @@ export function buildMemoryContinuityGuidanceBlock(memoryContinuityState) {
     : 2;
 
   return [
-    'Memory continuity mode is enabled.',
+    'Project memory continuity mode is enabled.',
     'Hydration mode: progressive-disclosure.',
     adapterGuidanceLine,
     '',
@@ -389,6 +389,7 @@ export function buildMemoryContinuityGuidanceBlock(memoryContinuityState) {
     '- Always redact sensitive text before persistence (<private> blocks and inline secret-like fields).',
     '',
     'Host compatibility scope:',
+    '- This memory layer does not replace reading bootstrap instruction files at the start of a session.',
     '- Works for local IDE, CLI, and cloud IDE chat hosts that implement the memory adapter contract or MCP retrieval path.',
     '- Generic web chat sessions without repository tools cannot auto-hydrate runtime memory and should rely on manual summary export/import.',
   ].join('\n');

package/lib/cli/project-scaffolder/constants.mjs

@@ -61,6 +61,7 @@ export const DESIGN_REQUIRED_SECTIONS = [
   'Responsive Strategy and Cross-Viewport Adaptation Matrix',
   'Interaction, Motion, and Feedback Rules',
   'Component Language, Morphology, and Shared Patterns',
+  'Context Hygiene and Approved Reference Boundaries',
   'Accessibility Non-Negotiables',
   'Anti-Patterns to Avoid',
   'Implementation Notes for Future UI Tasks',