@ryuenn3123/agentic-senior-core 4.2.3 → 4.2.5

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

@@ -1,5 +1,4 @@
 # Bootstrap Dynamic Design Contract
-
 Use this prompt for UI, UX, frontend layout, screen, Tailwind, animation, 3D, canvas, or redesign work.
 
 Create or refine `docs/DESIGN.md` for human reasoning and `docs/design-intent.json` for machine-readable design intent, guardrails, and review signals.
@@ -10,8 +9,9 @@ This contract is a decision scaffold, not a style preset. We guide the agent; we
 - Treat `README.md` as public and developer overview, setup, usage, and user-facing context only. Do not use it as coding, architecture, or design authority when `.agent-context/` gives a stricter rule.
 - Use current repo evidence, product copy, route names, component names, user goals, and existing constraints as the source of truth.
 - Treat prior-chat visuals, unrelated project memory, benchmark screenshots, and famous-product aesthetics as tainted context unless the user explicitly approves continuity.
-- Keep external references non-copying; extract constraints only.
+- Keep external references non-copying and research vocabulary internal; extract constraints only, and do not leak evidence, dossier, anchor, category-code, morphology, rename-test, or source-freshness labels into UI copy or final rationale unless requested.
 - Before choosing a new UI, animation, scroll, 3D, canvas, chart, icon, styling, or component library, research current official docs.
+- For design research, use the session current date as the rolling freshness reference. Prefer the newest relevant official or primary evidence; never define modern by a fixed calendar range.
 ## Required Order
 1. Read `AGENTS.md`, this prompt, `research-design.md`, `../rules/frontend-architecture.md`, current UI code, current project docs, and existing design docs.
 2. Refine existing `docs/DESIGN.md` and `docs/design-intent.json`; do not replace them blindly.
@@ -22,17 +22,16 @@ This contract is a decision scaffold, not a style preset. We guide the agent; we
 7. Complete the Section 3-5 gates from `research-design.md` before UI implementation: `conceptualAnchor.categoryCodes.candidateEntries`, `conceptualAnchor.morphologicalExploration` (selected and uncomfortable combinations), and `conceptualAnchor.anchorCandidates.candidates` (exactly five, each with the strengthened rename test recorded).
 8. Set `derivedTokenLogic.tokenContinuityClassification` for each of typography, palette, motion, and spacing. Use `anchor-derived` only when the token choice is causally tied to the anchor's real-world reality. Use `continuity-retained` when the token is kept from a previous design iteration without re-derivation. Use `newly-introduced` when the token is fresh but not anchor-derived. If any token category is `continuity-retained`, the typography, palette, or motion entry in `researchDossier.metadata.antiRepeatLedger` stays as historical record, and the classification declares the retention is intentional with explicit rationale recorded in the matching `derivationSource` field.
 9. After agent and user select an anchor, set `researchDossier.metadata.researchVerifiedAt` to today's ISO date and flip `status` from any seed value to `active`. This closes the freshness window for additive UI tasks within `freshnessWindowDays`.
+10. Complete the Live Source Freshness Gate from `research-design.md` before claiming that a visual pattern, library, browser feature, accessibility requirement, or interaction style is current. Record `sourceFreshness` and `evidenceTable[]` in `docs/design-intent.json`.
 ## Creative Commitment Gate
 Before broad compliance review or UI implementation, record an agent-chosen visual direction in both design docs:
 - one concrete real-world anchor reference
 - one signature motion behavior more specific than "smooth"
 - one typographic decision with meaningful role contrast
 - one authored visual bet visible in the first viewport
-
 Reject generic anchors. Do not accept "modern", "clean", "premium", "expressive", "minimal", or "bold" as the anchor. Name a material, instrument, artifact class, architectural system, editorial genre, cinematic behavior, exhibition system, scientific apparatus, or industrial mechanism.
 ## Dynamic Avant-Garde Anchor Engine
 If no current-task research or visual reference exists, activate the Dynamic Avant-Garde Anchor Engine before coding.
-
 Rules:
 - Treat old design docs, prior UI, and scaffold seeds as evidence, not research.
 - Internally consider at least three high-variance anchors.
@@ -50,7 +49,6 @@ Before UI code, record:
 - one signature motion, spatial, or interaction behavior
 - one morphology or composition choice that avoids interchangeable card stacks when the product allows it
 - at least three at-a-glance product-specific signals for new screens or broad redesigns
-
 Do not ship AI-safe UI. Record exact drift signals in `reviewRubric`; at minimum reject decorative grid wallpaper, default line backgrounds, calibration-mark wallpaper, soft glow backgrounds, generic abstract marks, testing/demo/placeholder UI copy, terminal-only user flows, and first-output composition with only local copy swapped in when they have no product function. Treat measurement, calibration, crop, route, timeline, and inspection marks as task overlays or control affordances only; never promote them to the page background, hero backdrop, or first-output visual texture. If a conceptual anchor suggests a forbidden motif, the forbidden motif wins; express the anchor through workflow, hierarchy, density, typography, material behavior, state design, and interaction grammar instead of literal wallpaper.
 ## Brave Redesign Default
 For UI design work, the agent owns the ambition decision. For broad screens, redesigns, or new visual systems, treat expressive motion, spatial hierarchy, distinctive composition, and product-specific interaction as the baseline even when the user did not say "rich". Do not reduce the request to a safer version of the existing UI, a static implementation, or a component-kit rearrangement because research or dependency selection feels inconvenient.
@@ -63,6 +61,10 @@ Only downshift ambition after naming the concrete blocker: product fit, content
 ## External Inspiration Boundary
 Using outside websites, benchmark apps, galleries, or component examples is useful for constraint discovery, interaction mechanics, and implementation options, but never as a style source to imitate. Extract why a pattern works, then translate it into a current-project rule. Do not copy layout rhythm, palette, component skin, visual metaphor, or brand posture from a reference unless the user explicitly approves that continuity and it passes product fit.
 
+## Adaptive Research Freshness
+Modern is relative to the current date, not a fixed release year: implementation/platform claims require current official docs or primary release notes; trend, category-code, and visual-language claims prefer sources published or materially updated within the last 24 months; older sources must be labeled `old-timeless` and cannot prove a current-year trend.
+User-provided concepts are first-class constraints; adapt research to support, refine, or challenge the concept, and if live research is unavailable set source freshness to pending verification instead of claiming current-year modernity.
+
 ## AI Color and Template Residue Audit
 AI color drift happens when a palette uses safe defaults before product meaning.
 
@@ -133,7 +135,6 @@ Define viewport mutation rules:
 - For each viewport, name what is reordered, merged, hidden, disclosed, promoted, and forbidden.
 
 ## Required `docs/DESIGN.md` Sections
-
 1. Design Intent and Product Personality
 2. Audience and Use-Context Signals
 3. Visual Direction and Distinctive Moves

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

@@ -15,6 +15,33 @@ This brief is a single document with five sections. Sections 1 and 2 set up the
 - Treat external websites, benchmark apps, prior chats, and unrelated-project memory as candidate evidence for constraints, mechanics, and quality bars only. Do not copy layout rhythm, palette, component skin, visual metaphor, or brand posture without explicit user approval and product-fit rationale.
 - WCAG 2.2 AA is the hard compliance floor. APCA may be used only as advisory perceptual tuning.
 
+## Live Source Freshness Gate
+
+Run this gate before Section 2 whenever web search is available. Treat modernity as rolling-current: use the session's current date as the freshness reference, and prefer the newest stable evidence that is relevant to the product and implementation surface.
+
+Rules:
+
+- For browser capability, framework setup, UI library, animation, 3D, canvas, charting, styling, accessibility, and package/API claims, use current official documentation or primary release notes first. Do not use trend posts as implementation authority.
+- For design trend, category-code, visual-language, motion-pattern, typography, color, and interaction claims, prefer sources published or materially updated within the last 24 months from the current date. If stronger older evidence is used, label it `old-timeless` and restrict it to durable principles, not "current modern" claims.
+- For product-category defaults, observe the current live category for this task. Do not rely on old examples, old galleries, or remembered benchmark screenshots as proof of what the category defaults to now.
+- If web search is unavailable, set `sourceFreshnessStatus` to `pending-live-verification`; use repo evidence and user-provided material only, and do not claim a direction is current-year modern.
+- If sources disagree, choose by product fit, accessibility, browser/runtime support, maintainability, and implementation feasibility, then record the disagreement.
+- If the user provides a concept, treat it as a first-class constraint. Research should support, refine, or challenge that concept with evidence; it must not override the concept with generic trend defaults unless there is a concrete product, accessibility, technical, or evidence conflict.
+
+Output: `sourceFreshness` block with `freshnessAnchorDate`, `rollingLookbackMonths` (default 24 for trend evidence), `sourceFreshnessStatus`, `officialDocsRequiredFor`, `oldSourcePolicy`, `userConceptAdaptation`, and `disagreements[]`.
+
+Every important research claim must also appear in `evidenceTable[]` with:
+
+- `claim`
+- `sourceUrl`
+- `sourceType` (`official`, `primary`, `industry`, `opinion`, `old-timeless`, `repo-evidence`, `user-provided`)
+- `publishedOrUpdatedAt` when visible, otherwise `unknown`
+- `fetchedAt`
+- `confidence` (`high`, `medium`, `low`)
+- `decisionImpact`
+
+Research vocabulary is internal-only. Use `sourceFreshness`, `evidenceTable[]`, `researchDossier`, `anchor`, `categoryCodes`, `morphologicalExploration`, and `renameTest` to audit decisions, but do not expose those labels in UI copy, public-facing docs, section headings, or final user-facing rationale unless the user explicitly asks for the research trace.
+
 ## Anti-Repeat Ledger Gate (read first)
 
 If `docs/design-intent.json` already exists and carries `researchDossier.metadata.antiRepeatLedger`, treat every entry under `previousAnchors`, `previousPalettes`, and `previousMotionSignatures` as a hard blocklist before producing any candidate in Sections 3-5.

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

@@ -31,9 +31,12 @@ Load this rule for UI-facing work. Keep the loaded surface small.
 3. Treat `README.md` as public and developer overview, setup, usage, and user-facing context only when design or architecture rules conflict.
 4. Do not choose final style, framework, palette, typography, layout paradigm, or animation library offline.
 5. Research current official docs before adding a new UI, animation, scroll, 3D, canvas, charting, icon, styling, or primitive library.
-6. Dynamic UI Foundation: do not hardcode shadcn/ui, Tailwind-only, native-only, or any component library as the universal answer, and do not avoid them out of guardrail fear when they fit. Tailwind-first is valid when the stack, token model, and team workflow support it; pure Tailwind, vanilla CSS, shadcn/ui, or any kit is not neutral by itself. Modern primitives, motion/canvas/WebGL helpers, charting libraries, and styling tools are valid when product evidence, accessibility, runtime constraints, and official docs support them.
-7. For fresh projects, prefer official framework scaffolders or setup commands when official docs show they produce the current supported shape. Build files manually only when approved architecture, repo constraints, or learning/prototype scope makes that better.
-8. Keep design continuity opt-in. Repo evidence outranks memory residue.
+6. Use the current date as the freshness anchor for design research. Trend and category-default claims should come from the newest relevant evidence, preferably material published or updated within the last 24 months. Older sources are acceptable only as labeled durable principles, not proof that a direction is currently modern.
+7. Treat user-provided concepts as first-class constraints. Adapt research to support, refine, or challenge the concept with evidence; do not override it with trend defaults unless a concrete product, accessibility, technical, or evidence conflict is recorded.
+8. Keep research vocabulary internal. Evidence, dossier, anchor, category-code, morphology, rename-test, and freshness labels may guide decisions, but must not appear in UI copy, public-facing docs, or final user-facing rationale unless the user explicitly asks for the research trace.
+9. Dynamic UI Foundation: do not hardcode shadcn/ui, Tailwind-only, native-only, or any component library as the universal answer, and do not avoid them out of guardrail fear when they fit. Tailwind-first is valid when the stack, token model, and team workflow support it; pure Tailwind, vanilla CSS, shadcn/ui, or any kit is not neutral by itself. Modern primitives, motion/canvas/WebGL helpers, charting libraries, and styling tools are valid when product evidence, accessibility, runtime constraints, and official docs support them.
+10. For fresh projects, prefer official framework scaffolders or setup commands when official docs show they produce the current supported shape. Build files manually only when approved architecture, repo constraints, or learning/prototype scope makes that better.
+11. Keep design continuity opt-in. Repo evidence outranks memory residue.
 
 ## FE-003: Required Design Contract
 

package/README.md

@@ -26,6 +26,7 @@ Options:
 - Add `--mcp-template` to generate VS Code MCP workspace config.
 - Default init keeps MCP files opt-in.
 - Add `--no-token-optimize` only when you do not want ASCX command guidance enabled.
+- Add `--local-only` to ignore instructions (AGENTS.md, .agent-context/, and bridges) in .gitignore so they are not pushed to GitHub.
 - Local backup snapshots are written under `.agentic-backup/` and excluded from version control.
 
 ## Upgrade
@@ -41,6 +42,9 @@ Preview changes with `--dry-run`, then apply with `--yes`. Upgrade prunes obsole
 
 ## Core Commands
 
+> [!NOTE]
+> To run commands directly without `npx` (e.g., `ascx` or `agentic-senior-core`), install the CLI globally: `npm install -g @ryuenn3123/agentic-senior-core`.
+
 | Command | Purpose |
 |---------|---------|
 | `agentic-senior-core init` | Initialize the compact project guidance pack and native agent entrypoints |

package/lib/cli/backup.mjs

@@ -12,6 +12,15 @@ const RUNTIME_ARTIFACT_GITIGNORE_ENTRIES = [
 ];
 const RUNTIME_ARTIFACT_GITIGNORE_COMMENT = '# agentic-senior-core: local runtime artifacts';
 
+const GOVERNANCE_GITIGNORE_ENTRIES = [
+  '.agent-context/',
+  'AGENTS.md',
+  'CLAUDE.md',
+  'GEMINI.md',
+  'mcp.json',
+];
+const GOVERNANCE_GITIGNORE_COMMENT = '# agentic-senior-core: local-only governance files';
+
 /**
  * Calculates a SHA-256 hash of a file's contents.
  */
@@ -192,3 +201,10 @@ export async function ensureRuntimeArtifactGitignoreEntries(targetDirectoryPath)
     entries: RUNTIME_ARTIFACT_GITIGNORE_ENTRIES,
   });
 }
+
+export async function ensureLocalGovernanceGitignoreEntries(targetDirectoryPath) {
+  return ensureGitignoreEntries(targetDirectoryPath, {
+    comment: GOVERNANCE_GITIGNORE_COMMENT,
+    entries: GOVERNANCE_GITIGNORE_ENTRIES,
+  });
+}

package/lib/cli/commands/init.mjs

@@ -49,6 +49,7 @@ import {
   createBackup,
   ensureBackupGitignoreEntry,
   ensureRuntimeArtifactGitignoreEntries,
+  ensureLocalGovernanceGitignoreEntries,
 } from '../backup.mjs';
 import {
   runProjectDiscovery,
@@ -384,6 +385,25 @@ export async function runInitCommand(targetDirectoryArgument, initOptions = {})
       );
     }
 
+    const shouldKeepLocalOnly = typeof initOptions.localOnly === 'boolean'
+      ? initOptions.localOnly
+      : isInteractiveSession
+        ? await askYesNo(
+            'Add AI instructions and governance files to .gitignore? (Prevents pushing them to GitHub/Git)',
+            userInterface,
+            false
+          )
+        : false;
+
+    if (shouldKeepLocalOnly) {
+      const localGovernanceGitignoreResult = await ensureLocalGovernanceGitignoreEntries(resolvedTargetDirectoryPath);
+      if (localGovernanceGitignoreResult.status !== 'unchanged') {
+        console.log(
+          `AI governance files ignored in .gitignore (${localGovernanceGitignoreResult.addedEntries.join(', ')}).`
+        );
+      }
+    }
+
     await copyGovernanceAssetsToTarget(resolvedTargetDirectoryPath, {
       includeMcpTemplate: shouldIncludeMcpTemplate,
     });
@@ -523,6 +543,7 @@ export async function runInitCommand(targetDirectoryArgument, initOptions = {})
       selectedBlueprintFileName: selectedResolvedBlueprintFileName,
       selectedAdditionalBlueprintFileNames,
       includeCiGuardrails,
+      localOnly: shouldKeepLocalOnly,
       setupDurationMs,
       projectDetection,
       runtimeEnvironment: {
@@ -577,6 +598,7 @@ export async function runInitCommand(targetDirectoryArgument, initOptions = {})
     console.log('- Generated files: AGENTS.md, CLAUDE.md, GEMINI.md, .agent-context/, and .agent-context/state/onboarding-report.json');
     console.log('- Default activation cues: Adaptive Context bootstrap, ASCX command wrappers, Compact Natural final replies');
     console.log('- Default response mode: Compact Natural Mode enabled (.agent-context/prompts/compact-natural-mode.md)');
+    console.log('- CLI Usage: Install globally (`npm i -g @ryuenn3123/agentic-senior-core`) to use `ascx` directly, or prefix commands with `npx`.');
     if (scaffoldingResult?.bootstrapMode === 'ai-synthesis') {
       console.log(`- Bootstrap prompts: ${(scaffoldingResult.generatedPromptFileNames || []).length} files generated in .agent-context/prompts/`);
       if ((scaffoldingResult.materializedFileNames || []).length > 0) {

package/lib/cli/compiler.mjs

@@ -145,6 +145,7 @@ export async function writeOnboardingReport({
   selectedBlueprintFileName,
   selectedAdditionalBlueprintFileNames = [],
   includeCiGuardrails,
+  localOnly = false,
   setupDurationMs,
   projectDetection,
   runtimeEnvironment = null,
@@ -197,6 +198,7 @@ export async function writeOnboardingReport({
       agentDecisionRequired: !hasExplicitRuntimeDecision,
     },
     ciGuardrailsEnabled: includeCiGuardrails,
+    localOnly,
     setupDurationMs,
     runtimeEnvironment,
     containerizationStrategy: buildContainerizationStrategySnapshot(dockerStrategy),

package/lib/cli/init-options.mjs

@@ -24,6 +24,7 @@ export function parseInitArguments(commandArguments) {
     memoryContinuity: true,
     tokenAgent: 'copilot',
     includeMcpTemplate: false,
+    localOnly: undefined,
     scaffoldDocs: undefined,
     docsLang: 'en',
     docsLangProvided: false,
@@ -143,6 +144,16 @@ export function parseInitArguments(commandArguments) {
       continue;
     }
 
+    if (currentArgument === '--local-only') {
+      parsedInitOptions.localOnly = true;
+      continue;
+    }
+
+    if (currentArgument === '--no-local-only') {
+      parsedInitOptions.localOnly = false;
+      continue;
+    }
+
     if (currentArgument === '--scaffold-docs') {
       parsedInitOptions.scaffoldDocs = true;
       continue;

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

@@ -90,6 +90,30 @@ function buildDesignIntentContractObject({
       requireSummaryOfUsedSignals: true,
       requireFitFiltering: true,
       requireOfficialDocsVerificationForTechnologyClaims: true,
+      sourceFreshnessPolicy: {
+        mode: 'rolling-current-date',
+        currentDateAnchor: 'session-current-date',
+        trendLookbackMonths: 24,
+        implementationClaimsRequire: 'current-official-docs-or-primary-release-notes',
+        olderSourcePolicy: 'older sources may support durable principles only when labeled old-timeless; they cannot prove current modernity',
+        noLiveResearchFallback: 'set sourceFreshnessStatus to pending-live-verification and do not claim current-year modernity',
+      },
+      internalVocabularyPolicy: { terms: ['evidence', 'dossier', 'anchor', 'category-code', 'morphology', 'rename-test', 'source-freshness'], rule: 'Use research vocabulary for internal audit only; translate it into product-native language before UI copy, public docs, or user-facing rationale unless the user asks for the research trace.' },
+      adaptiveUserConceptPolicy: {
+        userConceptIsFirstClassConstraint: true,
+        researchRole: 'support-refine-or-challenge-user-concept-with-evidence',
+        overrideRequires: 'recorded product accessibility technical or evidence conflict',
+        trendDefaultsCannotOverrideUserConceptSilently: true,
+      },
+      requiredEvidenceTableFields: [
+        'claim',
+        'sourceUrl',
+        'sourceType',
+        'publishedOrUpdatedAt',
+        'fetchedAt',
+        'confidence',
+        'decisionImpact',
+      ],
       candidateDomains: [
         'visual-direction',
         'motion-and-scroll',
@@ -127,6 +151,39 @@ function buildDesignIntentContractObject({
     conceptualAnchor: buildConceptualAnchorSection(),
     researchDossier: {
       metadata: buildResearchDossierMetadata(),
+      sourceFreshness: {
+        status: 'agent-must-complete-before-ui-implementation',
+        freshnessAnchorDate: 'session-current-date',
+        rollingLookbackMonths: 24,
+        officialDocsRequiredFor: [
+          'browser-capability',
+          'framework-setup',
+          'ui-library',
+          'animation-library',
+          '3d-canvas-charting-library',
+          'styling-tool',
+          'accessibility-claim',
+        ],
+        sourceTypePolicy: {
+          official: 'required for implementation and package/API claims when available',
+          primary: 'preferred for product/studio/release claims',
+          industry: 'allowed for trend discovery after fit filtering',
+          opinion: 'advisory only; cannot lock design decisions alone',
+          oldTimeless: 'allowed for durable principles only, not current-year modern claims',
+          repoEvidence: 'highest authority for product constraints',
+          userProvided: 'candidate evidence and concept constraint, not automatic final prescription',
+        },
+        evidenceTableRequiredFields: [
+          'claim',
+          'sourceUrl',
+          'sourceType',
+          'publishedOrUpdatedAt',
+          'fetchedAt',
+          'confidence',
+          'decisionImpact',
+        ],
+        evidenceTable: [],
+      },
     },
     derivedTokenLogic: {
       anchorReference: 'agent-defined-anchor-reference',

package/lib/cli/project-scaffolder/prompt-builders.mjs

@@ -188,10 +188,13 @@ export function buildDesignBootstrapPrompt({
     '26. forbiddenPatterns',
     '27. requiredDesignSections',
     '28. implementation',
-    '29. repoEvidence when onboarding or detector evidence exists',
+    '29. researchDossier',
+    '30. repoEvidence when onboarding or detector evidence exists',
     '',
     '## Mechanical Gates',
     '0. Read `.agent-context/prompts/research-design.md` first. Sections 3 (Category Code Identification), 4 (Morphological Exploration), and 5 (Anchor Candidates) are gates: each must produce an auditable artifact before UI implementation.',
+    '0a. Complete the Live Source Freshness Gate from research-design.md before claiming a pattern, library, browser feature, accessibility requirement, or interaction style is current. Use the session current date as the rolling freshness reference; modern means relative to that date, not a fixed calendar range.',
+    '0b. Keep research vocabulary internal: evidence, dossier, anchor, category-code, morphology, rename-test, and source-freshness labels guide decisions but must not leak into UI copy, public-facing docs, or final user-facing rationale unless the user asks for the research trace.',
     '1. Do not copy external style guides.',
     '2. Do not anchor the final design language to famous products, benchmark visuals, or external reference surfaces.',
     '3. Do not choose final style, library, palette, typography, motion, or layout from this offline scaffold.',
@@ -216,6 +219,7 @@ export function buildDesignBootstrapPrompt({
     '21. Treat motion, 3D, canvas, WebGL, scroll choreography, and modern animation libraries as first-class options.',
     '22. If motion or spatial UI is omitted, document the product-fit reason and replacement interaction quality.',
     '23. If the user supplies research files, library lists, screenshots, articles, or benchmark notes, read them as candidate evidence and verify technology claims.',
+    '23a. User-provided concepts are first-class constraints: support, refine, or challenge them with evidence; do not override them with trend defaults unless a product, accessibility, technical, or evidence conflict is recorded.',
     '24. If no user-supplied research or reference exists, activate the Dynamic Avant-Garde Anchor Engine before coding; old design docs do not count as research.',
     '25. In Dynamic Avant-Garde mode, consider three high-variance anchors, discard the two safest or most predictable options, and output only the chosen anchor.',
     '26. Reject final anchors named dashboard, portal, cards, admin panel, SaaS shell, web app shell, or minimalist interface.',
@@ -241,6 +245,7 @@ export function buildDesignBootstrapPrompt({
     '41. Use external websites and benchmark examples as candidate evidence for constraints, mechanics, and quality bars only; do not copy layout rhythm, palette, component skin, visual metaphor, or brand posture.',
     '',
     '## Research-Design Brief Gates (research-design.md)',
+    '41a. Live Source Freshness Gate: record researchDossier.sourceFreshness and evidenceTable[] with claim, sourceUrl, sourceType, publishedOrUpdatedAt, fetchedAt, confidence, and decisionImpact. Use current official docs or primary release notes for implementation claims. Trend, category-code, and visual-language claims prefer sources published or materially updated within the last 24 months from the current date. Older sources must be labeled old-timeless and may support durable principles only.',
     '42. Section 3 — Category Code Identification: list at least three category codes per product surface in `conceptualAnchor.categoryCodes.candidateEntries`. Each entry must record `description`, `specificityEvidence`, `categoryDefaultReason`, and `rejectionNote`. The specificity floor is: a reader unfamiliar with the project must be able to visualize a specific aesthetic direction from the text alone, without seeing the UI and without knowing the product name. Reject placeholder phrases like "clean typography", "modern color palette", or "smooth animations". Anti-leakage rule: listing a cliche identifies a trap, not a target; the example cliches in the brief are not aesthetic candidates for any project. If the project pattern-matches a common AI-safe default (dev-tool dark slate, AI-startup purple-pink gradient, health-app mint, SaaS admin three-card KPI, marketing-site three-tile hero), name that cliche in `candidateEntries` with an explicit rejection note.',
     '43. Section 4 — Morphological Exploration: build a 5x5 or 6x5 matrix in `conceptualAnchor.morphologicalExploration`. Choose 5 or 6 dimensions and 5 values per dimension. Do not seed the matrix with the Section 3 category codes as values. Highlight the selected combination, and ALSO highlight at least one uncomfortable combination that feels instinctively wrong but can be argued with product logic. The uncomfortable combination must record `combinationLabel`, `discomfortReason`, and `productLogicJustification`. If you cannot produce an uncomfortable-but-arguable combination, the dimensions are too narrow; widen at least one and regenerate.',
     '44. Section 5 — Anchor Candidates: produce exactly five entries in `conceptualAnchor.anchorCandidates.candidates`. Each candidate must record `anchorReference`, `conceptualFamily`, `jobFit`, `hierarchyImplication`, `densityImplication`, `typeImplication`, `stateLanguage`, `motionImplication`, `whatItRulesOut`, `renameTest`, and `categoryCodeOverlap`.',

package/package.json

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

package/scripts/frontend-usability-audit.mjs

@@ -59,6 +59,8 @@ const REQUIRED_FRONTEND_RULE_SNIPPETS = [
   'Do not choose final style, framework, palette, typography, layout paradigm, or animation library offline.',
   'Keep design continuity opt-in.',
   'Repo evidence outranks memory residue.',
+  'Use the current date as the freshness anchor for design research.',
+  'Treat user-provided concepts as first-class constraints.',
   '## FE-003: Required Design Contract',
   '## FE-004: Anti-Generic UI Gate',
   'Do not ship interchangeable dashboard chrome',
@@ -96,6 +98,9 @@ const REQUIRED_BOOTSTRAP_DESIGN_SNIPPETS = [
   'APCA may be used only as advisory perceptual tuning',
   'unresearched dependency choices',
   'Dynamic UI Foundation Selection',
+  'Adaptive Research Freshness',
+  'fixed calendar range',
+  'research vocabulary internal',
   'A new dependency, package count, or vague performance concern is not a blocker by itself.',
   'default component-kit styling without product rationale',
   'genericity findings that cannot name the exact drift signal',

package/scripts/validate/config.mjs

@@ -358,6 +358,9 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'APCA may be used only as advisory perceptual tuning',
       'unresearched dependency choices',
       'Dynamic UI Foundation Selection',
+      'Adaptive Research Freshness',
+      'fixed calendar range',
+      'research vocabulary internal',
       'locked outcomes from flexible expression',
       'A new dependency, package count, or vague performance concern is not a blocker by itself.',
       'default component-kit styling without product rationale',
@@ -378,6 +381,11 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'STRONG PASS',
       'DISCARD',
       'Anti-Repeat Ledger Gate',
+      'Live Source Freshness Gate',
+      'rolling-current',
+      'evidenceTable[]',
+      'old-timeless',
+      'Research vocabulary is internal-only',
       'previousAnchors',
       'previousMotionSignatures',
       'Dimensional split',