npm - gennady - Versions diffs - 0.8.3 → 0.8.4-draft.2 - Mend

gennady 0.8.3 → 0.8.4-draft.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2907) hide show

package/ai/directives/coding/uikit-spec-drafting.xml CHANGED Viewed

@@ -1,5 +1,5 @@
 <UiKitSpecDrafting keywords="uikit, spec-drafting, extraction-result, ui-spec, token-mapping, variant-grouping, bdd-generation, a11y-defaults" type="drafting-rules" ver="1.0">
-  <Directive_Context>
+  <DirectiveContext>
     <Mission>
       Convert an ExtractionResult — the JSON output of `figma-utils extract &lt;component&gt;` — into a draft `.ui.spec.md` (per `spec-format.md`). The draft is a starting point for operator refinement; it must preserve ALL data from the extraction (all variants, all token candidates, all elements) without loss.
@@ -10,9 +10,9 @@
       - Validating the draft (SpecValidator is a separate check);
       - Finalising the spec (operator approves after review).
     </Mission>
-  </Directive_Context>
+  </DirectiveContext>
-  <Belief_State>
+  <BeliefState>
     <Axiom id="AX_EXTRACTION_INPUT">
       The input is an `ExtractionResult` object with shape:
       ```json
@@ -112,9 +112,9 @@
       ```
       This signals to the operator that the spec is machine-generated and requires human approval.
     </Axiom>
-  </Belief_State>
+  </BeliefState>
-  <Drafting_Procedure>
+  <DraftingProcedure>
     <Step id="STEP_1_LOAD_EXTRACTION">
       <Goal>Receive and validate the ExtractionResult.</Goal>
       <Action>
@@ -192,35 +192,35 @@
         3. Save as `specs/uikit/components/&lt;component&gt;.ui.spec.md`.
       </Action>
     </Step>
-  </Drafting_Procedure>
+  </DraftingProcedure>
-  <Anti_Patterns>
-    <Anti_Pattern id="AP_DROPPED_VARIANTS">
+  <AntiPatterns>
+    <AntiPattern id="AP_DROPPED_VARIANTS">
       <Bad>Пропуск строки в таблице Variants, потому что «этот вариант не в extraction».</Bad>
-      <Why_Bad>Closed-world нарушен. Последующий SpecValidator не сможет отличить «пропущен осознанно» от «забыли».</Why_Bad>
+      <WhyBad>Closed-world нарушен. Последующий SpecValidator не сможет отличить «пропущен осознанно» от «забыли».</WhyBad>
       <Good>Строка присутствует, но состояния помечены `⚠️ not in extraction`.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_SILENT_MISSING_TOKEN">
+    <AntiPattern id="AP_SILENT_MISSING_TOKEN">
       <Bad>Пропуск строки в Token Mapping, когда токен не найден.</Bad>
-      <Why_Bad>Измерение теряется. SpecValidator не может проверить, что все измерения покрыты.</Why_Bad>
+      <WhyBad>Измерение теряется. SpecValidator не может проверить, что все измерения покрыты.</WhyBad>
       <Good>Строка с `⚠️ no token` в колонке Token и `Action = ⚠️`.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_DUPLICATE_BDD_GROUP">
+    <AntiPattern id="AP_DUPLICATE_BDD_GROUP">
       <Bad>Один BDD-заголовок на несколько размеров: `### Primary / Accent (все размеры)`.</Bad>
-      <Why_Bad>Разные размеры имеют разные ожидаемые значения (height, pads). Сгруппированные BDD нельзя верифицировать.</Why_Bad>
+      <WhyBad>Разные размеры имеют разные ожидаемые значения (height, pads). Сгруппированные BDD нельзя верифицировать.</WhyBad>
       <Good>Отдельный BDD-заголовок на каждый (appearance, mode), внутри указывается representative size и конкретные значения.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_FABRICATED_MEASUREMENTS">
+    <AntiPattern id="AP_FABRICATED_MEASUREMENTS">
       <Bad>BDD-сценарий с выдуманными значениями: `background = #0077FF`, когда в extraction нет такого цвета.</Bad>
-      <Why_Bad>SpecValidator обнаружит расхождение. Фабрикация данных подрывает доверие к спекам.</Why_Bad>
+      <WhyBad>SpecValidator обнаружит расхождение. Фабрикация данных подрывает доверие к спекам.</WhyBad>
       <Good>Все Then-значения берутся из `MeasurementSet` соответствующего варианта: `rectFill`, `height`, `borderRadius`, etc.</Good>
-    </Anti_Pattern>
-  </Anti_Patterns>
+    </AntiPattern>
+  </AntiPatterns>
-  <Reward_Criteria>
+  <RewardCriteria>
     ✅ Draft содержит все 6 обязательных секций (Vision, Variants, Token Mapping, Element Structure, A11y, BDD).
     ✅ Variants — closed-world таблица, все комбинации size × appearance × mode перечислены.
     ✅ Token Mapping — каждая строка имеет валидный VKUI токен или явную пометку `⚠️ no token`.
@@ -234,5 +234,5 @@
     ❌ BDD без реальных данных (фабрикация).
     ❌ Отсутствует a11y-секция.
     ❌ Draft без пометки `DRAFT`.
-  </Reward_Criteria>
+  </RewardCriteria>
 </UiKitSpecDrafting>

package/ai/directives/infra/eslint-setup.xml CHANGED Viewed

@@ -11,7 +11,7 @@
     Non-goal: this directive is NOT a curated rule list. It is meta-policy about which rules belong in the lint config and how the pipeline is structured.
   </Mission>
-  <Belief_State>
+  <BeliefState>
     <Axiom id="AX_BINARY_SEVERITY">
       **Every rule in `eslint.config.ts` has severity `'error'` (or numeric `2`), or it is `'off'`. There is no third state.**
@@ -142,7 +142,7 @@
       The config itself is the source of truth for the lint contract.
     </Axiom>
-  </Belief_State>
+  </BeliefState>
   <Definitions>
     <Definition id="DEF_AUTOFIXABLE_RULE">
@@ -159,7 +159,7 @@
     </Definition>
   </Definitions>
-  <Config_Patterns>
+  <ConfigPatterns>
     <Pattern id="PT_LINT_CONFIG_SHAPE">
       <Intent>Flat config where every enabled rule is either trivially autofixable or carries the explanatory comment. Severity always `'error'` — never `'warn'`. Stylistic rules off-loaded to Prettier; type-aware rules off-loaded to `tsc`. Auditable by grep.</Intent>
       <Snippet language="typescript">
@@ -321,41 +321,41 @@
       </Snippet>
       <Why>`lint:fix` is agent's default (mechanical, mutating); `lint:check` is CI's default (read-only, fails on drift). `typecheck` is its own script — type-aware concerns are routed to TS, not lint.</Why>
     </Pattern>
-  </Config_Patterns>
+  </ConfigPatterns>
-  <Anti_Patterns>
-    <Anti_Pattern id="AP_WARN_LEVEL_USAGE">
+  <AntiPatterns>
+    <AntiPattern id="AP_WARN_LEVEL_USAGE">
       <Bad>Config has rules at `'warn'` (e.g., `'@typescript-eslint/no-explicit-any': 'warn'`, `'no-console': 'warn'`, `'@typescript-eslint/no-floating-promises': ['warn']`).</Bad>
-      <Why_Bad>Forbidden by `AX_BINARY_SEVERITY`. A warning is a finding nobody owns: CI green, agent moves on, warning rots. `no-floating-promises` as warning is especially dangerous — a class of bugs (lost errors, broken ordering) discovered and ignored on every CI run. No path back from `'warn'` to a real fix the agent will take on its own.</Why_Bad>
+      <WhyBad>Forbidden by `AX_BINARY_SEVERITY`. A warning is a finding nobody owns: CI green, agent moves on, warning rots. `no-floating-promises` as warning is especially dangerous — a class of bugs (lost errors, broken ordering) discovered and ignored on every CI run. No path back from `'warn'` to a real fix the agent will take on its own.</WhyBad>
       <Good>Each rule resolved to `'error'` (with motivation comment if non-autofix) or `'off'` (with one-line reason).</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_UNMOTIVATED_NON_AUTOFIX_RULE">
+    <AntiPattern id="AP_UNMOTIVATED_NON_AUTOFIX_RULE">
       <Bad>Non-autofix rules turned on without explanatory comment: `'complexity': ['error', 10]`, `'max-lines': ['error', 500]`, `'no-magic-numbers': 'error'`, `'@typescript-eslint/no-explicit-any': 'error'`, `'@typescript-eslint/no-floating-promises': 'error'` (no comment).</Bad>
-      <Why_Bad>None of these ship a `fix`. Each adds findings the agent cannot resolve mechanically. None carry the explanatory comment required by `AX_AUTOFIX_PREFERRED`. `complexity`/`max-lines`/`no-magic-numbers` belong to other channels per `AX_NON_AUTOFIX_PREFER_DELEGATION`. Without motivation, the rules cannot be distinguished from accidentally-enabled ones during audit.</Why_Bad>
+      <WhyBad>None of these ship a `fix`. Each adds findings the agent cannot resolve mechanically. None carry the explanatory comment required by `AX_AUTOFIX_PREFERRED`. `complexity`/`max-lines`/`no-magic-numbers` belong to other channels per `AX_NON_AUTOFIX_PREFER_DELEGATION`. Without motivation, the rules cannot be distinguished from accidentally-enabled ones during audit.</WhyBad>
       <Good>Off-load to right channels: `'complexity': 'off'` (testing/architecture); `'no-magic-numbers': 'off'` (review); `'no-explicit-any': 'off'` (review per call-site). Keep `'no-floating-promises': 'error'` WITH the motivation comment naming the bug class and channel-coverage gap.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_AGENT_DISABLE_COMMENT">
+    <AntiPattern id="AP_AGENT_DISABLE_COMMENT">
       <Bad>Agent commits `// eslint-disable-next-line @typescript-eslint/no-floating-promises` above `void doWork(input)` to silence a finding.</Bad>
-      <Why_Bad>Agent silenced finding instead of fixing it (`AX_NO_DISABLE_COMMENTS_BY_AGENT`). The explanatory comment for the rule in `eslint.config.ts` exists exactly to point the agent at the right fix (`await`, `.catch`, or explicit logger). The agent skipped that. No `--` justification accompanies the disable, so the form is also non-compliant.</Why_Bad>
+      <WhyBad>Agent silenced finding instead of fixing it (`AX_NO_DISABLE_COMMENTS_BY_AGENT`). The explanatory comment for the rule in `eslint.config.ts` exists exactly to point the agent at the right fix (`await`, `.catch`, or explicit logger). The agent skipped that. No `--` justification accompanies the disable, so the form is also non-compliant.</WhyBad>
       <Good>Agent fixes the floating promise per the rule's motivation: `export async function adapt(input) { await doWork(input); }`. OR if the rule is genuinely wrong here, agent stops and surfaces it for a config change. No source-level disable.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_FORMATTING_DUPLICATION">
+    <AntiPattern id="AP_FORMATTING_DUPLICATION">
       <Bad>`eslint.config.ts` enables `'indent'`, `'quotes'`, `'semi'`, `'comma-dangle'`, `'max-len'` while `.prettierrc.json` disagrees on tabWidth/printWidth. ESLint rewrites what Prettier wrote, then Prettier rewrites it back.</Bad>
-      <Why_Bad>ESLint stylistic rules enabled while Prettier owns the same dimensions (`AX_PRETTIER_OWNS_FORMATTING`). Two tools disagree → each `--fix` undoes the other → CI bounces, agents waste cycles. Config also lacks `eslint-config-prettier` at the end.</Why_Bad>
+      <WhyBad>ESLint stylistic rules enabled while Prettier owns the same dimensions (`AX_PRETTIER_OWNS_FORMATTING`). Two tools disagree → each `--fix` undoes the other → CI bounces, agents waste cycles. Config also lacks `eslint-config-prettier` at the end.</WhyBad>
       <Good>`eslint-config-prettier/flat` appended LAST in flat config — disables stylistic rules from any preset. Formatting lives entirely in Prettier.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_TYPE_AWARE_DUPLICATION">
+    <AntiPattern id="AP_TYPE_AWARE_DUPLICATION">
       <Bad>`tsconfig.json` has `strict: true, noUnusedLocals: true`. `eslint.config.ts` also enables `'no-unused-vars': 'error'`, `'@typescript-eslint/no-unused-vars': 'error'`, `'no-undef': 'error'`, `'consistent-return': 'error'`.</Bad>
-      <Why_Bad>Every enabled rule duplicates a check `tsc --strict` already performs (`AX_TYPE_AWARE_PREFER_TS`). Same problem reported twice with different messages and different exit codes; agents and humans waste effort reconciling.</Why_Bad>
+      <WhyBad>Every enabled rule duplicates a check `tsc --strict` already performs (`AX_TYPE_AWARE_PREFER_TS`). Same problem reported twice with different messages and different exit codes; agents and humans waste effort reconciling.</WhyBad>
       <Good>All four rules `'off'`. The npm `typecheck` script runs `tsc --noEmit` and is the authoritative gate.</Good>
-    </Anti_Pattern>
-  </Anti_Patterns>
+    </AntiPattern>
+  </AntiPatterns>
-  <Setup_Steps>
+  <SetupSteps>
     <!-- Ordered actions for initial ESLint configuration.
          Axioms in Belief_State define the WHY and invariants; these steps define the HOW and sequence.
          Workflow_Outline (below) covers runtime usage after setup is complete. -->
@@ -384,17 +384,17 @@
       Run `npm run lint:fix` on the current codebase. Exit 0 = config valid and codebase clean. Non-zero = fix findings or adjust rules (never add disable comments).
       Ref: AX_LINT_RUN_IS_MECHANICAL, AX_NO_DISABLE_COMMENTS_BY_AGENT.
     </Step>
-  </Setup_Steps>
+  </SetupSteps>
-  <Workflow_Outline>
+  <WorkflowOutline>
     <Step id="WF_1_RUN_THE_PIPELINE">Default agent action when touching code: `npm run lint:fix`. Exit 0 means lint contract satisfied.</Step>
     <Step id="WF_2_HANDLE_REMAINING_FINDINGS">Non-zero exit = finding remains after `--fix`. The finding belongs to a motivated non-autofix rule. Read the rule's explanatory comment in `eslint.config.ts`, fix the code accordingly, re-run. Disable comments NOT an option.</Step>
     <Step id="WF_3_PROPOSE_RULE_CHANGES_VIA_AUDIT">To add or remove a rule, run audit protocol (`PT_RULE_AUDIT_PROTOCOL`): inspect `meta.fixable`, route into autofix or motivated-non-autofix, draft explanatory comment, dry-run, present evidence + diff. Wait for explicit operator confirmation. Severity at registration always `'error'`.</Step>
     <Step id="WF_4_KEEP_THE_CONFIG_AUDITABLE">Editing `eslint.config.ts`: preserve one-block-per-concern shape. Every `'error'` rule trivially autofixable or carries explanatory comment; every `'off'` after preset spread carries one-line reason; no `'warn'` anywhere.</Step>
     <Step id="WF_5_VERIFY_AND_FINALIZE">Before closing a task: `npm run lint:fix && npm run typecheck && npm test` all green AND `git diff` shows only the intended change. Any environment blocker → declared EXPLICITLY in the ticket.</Step>
-  </Workflow_Outline>
+  </WorkflowOutline>
-  <Verification_Hooks>
+  <VerificationHooks>
     <Hook id="HOOK_LINT_FIX_GREEN">
       <Purpose>Canonical green-gate check: unified pipeline exits 0.</Purpose>
       <Command>npm run lint:fix</Command>
@@ -435,9 +435,9 @@
       <Command>npx tsc --noEmit</Command>
       <Expected>Exit 0; no TS errors.</Expected>
     </Hook>
-  </Verification_Hooks>
+  </VerificationHooks>
-  <Reward_Criteria>
+  <RewardCriteria>
     ✅ Every rule is `'error'` — and only `'error'`. No `'warn'` / `1` / informational levels anywhere in the resolved config, including after preset spreads.
     ✅ Autofix rules are default; non-autofix rules kept ONLY with plain-prose comment naming the bug class and channel-coverage gap.
     ✅ Full quality pass is one named script (`lint:fix`); pipeline exits 0 and `git diff` empty.
@@ -463,5 +463,5 @@
     ❌ Type-aware rule duplicated between `tsc` and ESLint.
     ❌ `eslint-config-prettier` absent or not last in flat-config array.
     ❌ Any of `lint:fix` / `typecheck` / test pipeline fails silently without an EXPLICIT blocker statement.
-  </Reward_Criteria>
+  </RewardCriteria>
 </EslintSetup>

package/ai/directives/infra/git-setup.xml CHANGED Viewed

@@ -7,7 +7,7 @@
     Scope is git itself. Tool choice for hooks runner (lefthook / husky / simple-git-hooks) is the `git-hooks` category in the infrastructure scope discovery session. CI provider is the `ci` category. Both distinct from this rule.
   </Mission>
-  <Belief_State>
+  <BeliefState>
     <Axiom id="AX_GITIGNORE_BASELINE">
       `.gitignore` covers three layers.
@@ -155,9 +155,9 @@
       Git history is forever. Once a secret reaches the remote, assume it's harvested by scanners within minutes. Rotation is mandatory; history rewrite is hygiene, not security.
     </Axiom>
-  </Belief_State>
+  </BeliefState>
-  <Setup_Steps>
+  <SetupSteps>
     <!-- Ordered actions for initial git repository configuration.
          Axioms in Belief_State define the WHY and invariants; these steps define the HOW and sequence. -->
     <Step id="STEP_1_INIT_REPO">
@@ -181,41 +181,41 @@
     <Step id="STEP_7_VERIFY">
       Confirm: `git status` clean; `.gitignore` covers all tool-generated paths; hooks fire on test commit; remote branch protection active.
     </Step>
-  </Setup_Steps>
+  </SetupSteps>
-  <Anti_Patterns>
-    <Anti_Pattern id="AP_NODE_MODULES_COMMITTED">
+  <AntiPatterns>
+    <AntiPattern id="AP_NODE_MODULES_COMMITTED">
       <Bad>`git add node_modules/` or `node_modules/` not in `.gitignore`</Bad>
-      <Why_Bad>10–500 MB bloat; macOS-compiled native binaries fail on Linux CI; PR diffs become unreadable. Lock file already encodes the dep tree deterministically.</Why_Bad>
+      <WhyBad>10–500 MB bloat; macOS-compiled native binaries fail on Linux CI; PR diffs become unreadable. Lock file already encodes the dep tree deterministically.</WhyBad>
       <Good>`node_modules/` in `.gitignore`. `npm ci` / `pnpm install --frozen-lockfile` restores from lock file.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_FORCE_PUSH_TO_MAIN">
+    <AntiPattern id="AP_FORCE_PUSH_TO_MAIN">
       <Bad>`git push --force origin main`</Bad>
-      <Why_Bad>Silently rewrites history collaborators already pulled. Recovery requires every team member to reset their local branch — error-prone, sometimes impossible if uncommitted work is on top.</Why_Bad>
+      <WhyBad>Silently rewrites history collaborators already pulled. Recovery requires every team member to reset their local branch — error-prone, sometimes impossible if uncommitted work is on top.</WhyBad>
       <Good>Force-push only on personal branches. Shared-branch issues fixed via revert commits.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_SECRET_IN_HISTORY">
+    <AntiPattern id="AP_SECRET_IN_HISTORY">
       <Bad>Committed `.env` with real API key, then `git rm` in next commit.</Bad>
-      <Why_Bad>The secret is in history. Anyone can `git log -p` and recover it. Public repos expose to scanners within seconds.</Why_Bad>
+      <WhyBad>The secret is in history. Anyone can `git log -p` and recover it. Public repos expose to scanners within seconds.</WhyBad>
       <Good>Rotate the credential immediately. Then rewrite history with `git filter-repo` and force-push (coordinate with team). Add `.env` to `.gitignore` BEFORE first push.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_NO_VERIFY_AS_HABIT">
+    <AntiPattern id="AP_NO_VERIFY_AS_HABIT">
       <Bad>`git commit --no-verify` because pre-commit hook is «too slow».</Bad>
-      <Why_Bad>Hooks exist to catch mistakes locally. Routinely bypassing shifts mistakes into CI (slower, more expensive) or main (worse). Slow hook = fix the hook, don't skip it.</Why_Bad>
+      <WhyBad>Hooks exist to catch mistakes locally. Routinely bypassing shifts mistakes into CI (slower, more expensive) or main (worse). Slow hook = fix the hook, don't skip it.</WhyBad>
       <Good>Diagnose hook slowness (lint scope too wide? full test suite in pre-commit instead of pre-push?). Optimize. `--no-verify` only with explicit operator authorization, documented in commit body.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_LIGHTWEIGHT_TAG">
+    <AntiPattern id="AP_LIGHTWEIGHT_TAG">
       <Bad>`git tag v1.2.3` (no `-a`).</Bad>
-      <Why_Bad>No tagger / date / message metadata. Looks identical to a branch ref in some tools. Release lineage unrecoverable.</Why_Bad>
+      <WhyBad>No tagger / date / message metadata. Looks identical to a branch ref in some tools. Release lineage unrecoverable.</WhyBad>
       <Good>`git tag -a v1.2.3 -m "Release 1.2.3 — <summary>"`. Always annotated for release tags.</Good>
-    </Anti_Pattern>
-  </Anti_Patterns>
+    </AntiPattern>
+  </AntiPatterns>
-  <Verification_Hooks>
+  <VerificationHooks>
     <Hook id="HOOK_GITIGNORE_PRESENT">
       <Purpose>Verify `.gitignore` exists and is non-empty.</Purpose>
       <Command>test -s .gitignore && echo "OK"</Command>
@@ -241,9 +241,9 @@
       <Command>for t in $(git tag); do test "$(git cat-file -t $t)" = "tag" || echo "FAIL: $t is lightweight"; done; echo "OK"</Command>
       <Expected>Prints only `OK`; exit 0.</Expected>
     </Hook>
-  </Verification_Hooks>
+  </VerificationHooks>
-  <Reward_Criteria>
+  <RewardCriteria>
     ✅ `.gitignore` covers mandatory + tool-derived layers; first commit only after `.gitignore` in place.
     ✅ Default branch is `main`; remote branch protection prevents direct push, requires PR + green checks.
     ✅ Commits follow chosen convention; subjects ≤72 chars, imperative mood.
@@ -257,5 +257,5 @@
     ❌ `--no-verify` as habit; default branch named `master` in new project.
     ❌ Destructive command run as «let me just reset --hard» reflex without operator authorization.
     ❌ `.claude/settings.local.json` tracked.
-  </Reward_Criteria>
+  </RewardCriteria>
 </GitSetup>

package/ai/directives/infra/nodejs-npm-setup.xml CHANGED Viewed

@@ -9,7 +9,7 @@
     **Base axiom:** one package manager, one module system, one Node version per project. All three committed as files, not assumed.
   </Mission>
-  <Belief_State>
+  <BeliefState>
     <Axiom id="AX_SINGLE_PACKAGE_MANAGER">
       One package manager per project: **npm only**. Forbidden alongside npm: yarn, pnpm, bun. `package-lock.json` is the lock; all other lock files must be absent and gitignored.
@@ -125,9 +125,9 @@
       Skipping these introduces incompatibilities that surface as cryptic runtime errors, not install errors.
     </Axiom>
-  </Belief_State>
+  </BeliefState>
-  <Setup_Steps>
+  <SetupSteps>
     <!-- Ordered actions for initial Node.js/npm project configuration.
          Axioms in Belief_State define the WHY and invariants; these steps define the HOW and sequence. -->
     <Step id="STEP_1_CREATE_NVMRC">
@@ -156,7 +156,7 @@
     <Step id="STEP_8_VERIFY_REPRODUCIBILITY_TRIAD">
       Confirm three files committed: `.nvmrc`, `package.json`, `package-lock.json` (`npm ci` reads all three). Run HOOK_NVMRC_EXACT and HOOK_NPMRC_REGISTRY. Run each primary script — must exit within 2 minutes; hang = watch-mode violation.
     </Step>
-  </Setup_Steps>
+  </SetupSteps>
   <Definitions>
     <Definition id="DEF_REPRODUCIBILITY_TRIAD">Three committed files guaranteeing reproducible Node.js environment: `.nvmrc` (Node version), `package.json` (declared deps), `package-lock.json` (resolved dep tree). `npm ci` reads all three.</Definition>
@@ -165,7 +165,7 @@
     <Definition id="DEF_CJS">CommonJS. Default when `"type"` is absent or `"commonjs"`. Syntax: `require`/`module.exports`. Synchronous resolution.</Definition>
   </Definitions>
-  <Code_Patterns>
+  <CodePatterns>
     <Pattern id="PT_MINIMAL_PACKAGE_JSON">
       <Intent>Minimal valid `package.json`: explicit module system, engines aligned, exact dev-tool pins.</Intent>
       <Snippet language="json">
@@ -237,59 +237,59 @@
       </Snippet>
       <Why>Verification before install prevents silent incompatibilities. Committing lock with package.json closes the reproducibility triad.</Why>
     </Pattern>
-  </Code_Patterns>
+  </CodePatterns>
-  <Anti_Patterns>
-    <Anti_Pattern id="AP_MULTIPLE_LOCK_FILES">
+  <AntiPatterns>
+    <AntiPattern id="AP_MULTIPLE_LOCK_FILES">
       <Bad>Repo has both `package-lock.json` AND `yarn.lock` AND/OR `pnpm-lock.yaml`.</Bad>
-      <Why_Bad>Each manager resolves transitive deps differently. `npm ci` reads `package-lock.json`; developer running `yarn` writes `yarn.lock` with different versions. Builds diverge silently.</Why_Bad>
+      <WhyBad>Each manager resolves transitive deps differently. `npm ci` reads `package-lock.json`; developer running `yarn` writes `yarn.lock` with different versions. Builds diverge silently.</WhyBad>
       <Good>Only `package-lock.json` tracked. Foreign locks deleted + added to `.gitignore`.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_NVMRC_ENGINES_MISMATCH">
+    <AntiPattern id="AP_NVMRC_ENGINES_MISMATCH">
       <Bad>`.nvmrc=22.14.0` + `"engines": { "node": ">=18.0.0 <20.0.0" }`.</Bad>
-      <Why_Bad>`.nvmrc` installs Node 22; `engines` rejects Node 22. npm warns; CI may enforce constraint and fail. Local dev and CI run on different Node versions.</Why_Bad>
+      <WhyBad>`.nvmrc` installs Node 22; `engines` rejects Node 22. npm warns; CI may enforce constraint and fail. Local dev and CI run on different Node versions.</WhyBad>
       <Good>`.nvmrc=22.14.0` + `"engines": { "node": ">=22.0.0 <23.0.0" }`.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_NVMRC_RANGE">
+    <AntiPattern id="AP_NVMRC_RANGE">
       <Bad>`.nvmrc` contains `22` (range) or `lts/iron` (alias).</Bad>
-      <Why_Bad>`nvm use 22` resolves to whatever the latest 22.x is at install time — different on different machines and at different moments.</Why_Bad>
+      <WhyBad>`nvm use 22` resolves to whatever the latest 22.x is at install time — different on different machines and at different moments.</WhyBad>
       <Good>`.nvmrc` contains `22.14.0` exact.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_NODE_MODULES_COMMITTED">
+    <AntiPattern id="AP_NODE_MODULES_COMMITTED">
       <Bad>`git ls-files | grep '^node_modules/'` returns hits.</Bad>
-      <Why_Bad>10–500 MB bloat. Platform-specific native binaries compiled on macOS won't run on Linux CI. PR diffs become unreadable.</Why_Bad>
+      <WhyBad>10–500 MB bloat. Platform-specific native binaries compiled on macOS won't run on Linux CI. PR diffs become unreadable.</WhyBad>
       <Good>`.gitignore` includes `node_modules/`, `dist/`. `npm ci` restores from `package-lock.json` deterministically.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_MIXED_MODULE_SYSTEM">
+    <AntiPattern id="AP_MIXED_MODULE_SYSTEM">
       <Bad>`package.json` has `"type": "module"`, but `src/loader.js` uses `const fs = require('fs'); module.exports = …`.</Bad>
-      <Why_Bad>`"type": "module"` makes all `.js` files ESM. Using `require` in ESM file throws `ReferenceError: require is not defined` at runtime.</Why_Bad>
+      <WhyBad>`"type": "module"` makes all `.js` files ESM. Using `require` in ESM file throws `ReferenceError: require is not defined` at runtime.</WhyBad>
       <Good>ESM project: `import { readFile } from 'node:fs/promises'; export { load };`.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_BUILTIN_WITHOUT_PREFIX">
+    <AntiPattern id="AP_BUILTIN_WITHOUT_PREFIX">
       <Bad>`import { readFile } from 'fs/promises';` / `import { join } from 'path';`.</Bad>
-      <Why_Bad>A third-party package named `fs` or `path` would shadow the built-in silently. Intent ambiguous: built-in or dependency?</Why_Bad>
+      <WhyBad>A third-party package named `fs` or `path` would shadow the built-in silently. Intent ambiguous: built-in or dependency?</WhyBad>
       <Good>`import { readFile } from 'node:fs/promises';` / `import { join } from 'node:path';`.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_TOOL_RANGE_PIN">
+    <AntiPattern id="AP_TOOL_RANGE_PIN">
       <Bad>`"devDependencies": { "vite": "^5.2.0", "prettier": "3.x" }`.</Bad>
-      <Why_Bad>Semver-compatible update can silently change build output. CI installs 5.2.11 today, 5.2.12 next week — builds diverge.</Why_Bad>
+      <WhyBad>Semver-compatible update can silently change build output. CI installs 5.2.11 today, 5.2.12 next week — builds diverge.</WhyBad>
       <Good>`"devDependencies": { "vite": "5.2.11", "prettier": "3.2.5" }`.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_NPMRC_ABSENT">
+    <AntiPattern id="AP_NPMRC_ABSENT">
       <Bad>No `.npmrc` in the repository.</Bad>
-      <Why_Bad>Each developer and CI runner resolves from whatever registry their global `~/.npmrc` points to. Private-registry users silently fall back to public or fail with 404.</Why_Bad>
+      <WhyBad>Each developer and CI runner resolves from whatever registry their global `~/.npmrc` points to. Private-registry users silently fall back to public or fail with 404.</WhyBad>
       <Good>Committed `.npmrc` with `registry=https://registry.npmjs.org/`.</Good>
-    </Anti_Pattern>
-  </Anti_Patterns>
+    </AntiPattern>
+  </AntiPatterns>
-  <Verification_Hooks>
+  <VerificationHooks>
     <Hook id="HOOK_NVMRC_EXACT">
       <Purpose>`.nvmrc` exists, one line, semver-exact.</Purpose>
       <Command>test -f .nvmrc && [ "$(wc -l < .nvmrc)" -eq 1 ] && grep -qE '^[0-9]+\.[0-9]+\.[0-9]+$' .nvmrc && echo "OK"</Command>
@@ -325,9 +325,9 @@
       <Command>node -e "const p=require('./package.json'); console.log('module system:', p.type || 'commonjs (default)')"</Command>
       <Expected>Prints `module system: module` or `module system: commonjs (default)`.</Expected>
     </Hook>
-  </Verification_Hooks>
+  </VerificationHooks>
-  <Reward_Criteria>
+  <RewardCriteria>
     ✅ `.nvmrc` exists, one line, exact semver. `package.json#engines.node` accepts the version in `.nvmrc`.
     ✅ Only `npm` used; `package-lock.json` committed; no foreign lock files. `node_modules/` gitignored.
     ✅ Module system declared once; not mixed. All Node built-in imports use `node:` prefix.
@@ -350,5 +350,5 @@
     ❌ `check` script omits a phase covered by an active rule (e.g., lint active but not in `check`).
     ❌ Any phase sub-command in `check` defaults to watch / persistent mode — agent invocations hang indefinitely.
     ❌ `npm install` without env-prefix in sandbox; modifying operator's `~/.npmrc`; committing project `.npmrc` with corp registry URL.
-  </Reward_Criteria>
+  </RewardCriteria>
 </NodeJSNpmSetup>

package/ai/directives/infra/storybook-setup.xml CHANGED Viewed

@@ -7,7 +7,7 @@
     Companion (runtime usage after setup): `ai/directives/testing/storybook-usage.xml`.
   </Mission>
-  <Belief_State>
+  <BeliefState>
     <Axiom id="AX_SB_INIT_VIA_OFFICIAL_INSTALLER">
       Storybook installation starts with the official initializer (`npx storybook@latest init`). Manually scaffolding `.storybook/main.*`, `.storybook/preview.*`, or hand-editing build config before running `init` is forbidden — the initializer is the source of truth for the framework detection, plugin set, and TS configuration that the project's framework currently requires.
@@ -44,7 +44,7 @@
     <Axiom id="AX_SB_NO_PARALLEL_TEST_HARNESSES">
       Story-level tests use ONE harness — the test addon shipped/recommended with Storybook for the project's framework. Introducing a parallel harness (e.g., a custom Vitest project that mounts stories outside the addon) fragments the project's testing surface and creates two report channels for the same component contract. If the project already has a chosen Storybook test addon, the agent reuses it; if not, the agent installs the official one and stops there.
     </Axiom>
-  </Belief_State>
+  </BeliefState>
   <Definitions>
     <Definition id="DEF_SB_MCP_SERVER">
@@ -55,7 +55,7 @@
     </Definition>
   </Definitions>
-  <Setup_Steps>
+  <SetupSteps>
     <Step id="STEP_SB_1_RUN_INIT">
       Run `npx storybook@latest init` and answer prompts based on observed project structure. Do NOT pre-scaffold `.storybook/` before this step.
       Ref: AX_SB_INIT_VIA_OFFICIAL_INSTALLER.
@@ -84,35 +84,35 @@
       Add a Storybook section to `AGENTS.md`: MCP tools available, story-file conventions (`*.stories.ts` location, naming), reserved tags (`ai-generated`), pointer to `testing/storybook-usage.xml`.
       Ref: AX_SB_AGENTS_MD_UPDATED_AS_PART_OF_SETUP.
     </Step>
-  </Setup_Steps>
+  </SetupSteps>
-  <Anti_Patterns>
-    <Anti_Pattern id="AP_SB_MANUAL_SCAFFOLD_BEFORE_INIT">
+  <AntiPatterns>
+    <AntiPattern id="AP_SB_MANUAL_SCAFFOLD_BEFORE_INIT">
       <Bad>Agent hand-creates `.storybook/main.ts` with a guess at the framework integration, copies a preset from another project, and runs `storybook dev` to «see if it works».</Bad>
-      <Why_Bad>Bypasses the official initializer (`AX_SB_INIT_VIA_OFFICIAL_INSTALLER`). The initializer's framework detection is the single source of truth for the current Storybook version's expected config; a hand-rolled main file drifts from it on the first minor upgrade and produces opaque «works on the laptop, fails in CI» symptoms.</Why_Bad>
+      <WhyBad>Bypasses the official initializer (`AX_SB_INIT_VIA_OFFICIAL_INSTALLER`). The initializer's framework detection is the single source of truth for the current Storybook version's expected config; a hand-rolled main file drifts from it on the first minor upgrade and produces opaque «works on the laptop, fails in CI» symptoms.</WhyBad>
       <Good>Delete the hand-rolled `.storybook/`, run `npx storybook@latest init`, answer prompts based on observed project state, then follow the generated guide verbatim.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_SB_NO_MCP_INTEGRATION">
+    <AntiPattern id="AP_SB_NO_MCP_INTEGRATION">
       <Bad>Agent installs base Storybook, gets `storybook dev` running, and marks the ticket done without installing the test/MCP addon or registering the MCP server.</Bad>
-      <Why_Bad>Storybook present but unreachable by agents (`AX_SB_MCP_IS_MANDATORY`). Every subsequent component task must either rediscover props from source code or fall back to human-driven preview. The integration is structurally incomplete; calling it «done» misrepresents project state.</Why_Bad>
+      <WhyBad>Storybook present but unreachable by agents (`AX_SB_MCP_IS_MANDATORY`). Every subsequent component task must either rediscover props from source code or fall back to human-driven preview. The integration is structurally incomplete; calling it «done» misrepresents project state.</WhyBad>
       <Good>Install the recommended test/MCP addon (`STEP_SB_3_INSTALL_TEST_ADDON`), register the MCP server with the agent runner (`STEP_SB_5_REGISTER_MCP_SERVER`), and verify at least one MCP tool call returns a non-error response.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_SB_VERIFY_SKIPPED">
+    <AntiPattern id="AP_SB_VERIFY_SKIPPED">
       <Bad>Agent finishes the install steps and reports «Storybook configured» based solely on `npm install` exit code, without booting `storybook dev` or running any story test.</Bad>
-      <Why_Bad>Setup declared complete without end-to-end verification (`AX_SB_VERIFY_BEFORE_HANDOFF`). Misses Playwright browser missing, MCP server not registered, addon misconfigured, port conflict — all of which compile fine but break the first real use.</Why_Bad>
+      <WhyBad>Setup declared complete without end-to-end verification (`AX_SB_VERIFY_BEFORE_HANDOFF`). Misses Playwright browser missing, MCP server not registered, addon misconfigured, port conflict — all of which compile fine but break the first real use.</WhyBad>
       <Good>Boot `storybook dev` and confirm preview URL responds; call one MCP tool; run `run-story-tests` on one story. If any fails, surface the exact error to the operator before marking the ticket complete.</Good>
-    </Anti_Pattern>
+    </AntiPattern>
-    <Anti_Pattern id="AP_SB_AGENTS_MD_SKIPPED">
+    <AntiPattern id="AP_SB_AGENTS_MD_SKIPPED">
       <Bad>Setup verified end-to-end, but `AGENTS.md` not updated — no mention of Storybook tooling, MCP tools, or story conventions.</Bad>
-      <Why_Bad>Integration becomes tribal knowledge (`AX_SB_AGENTS_MD_UPDATED_AS_PART_OF_SETUP`). Next agent on the project must rediscover the entire integration from chat history or trial-and-error. Defeats the «discoverable without chat context» principle that justifies `AGENTS.md` in the first place.</Why_Bad>
+      <WhyBad>Integration becomes tribal knowledge (`AX_SB_AGENTS_MD_UPDATED_AS_PART_OF_SETUP`). Next agent on the project must rediscover the entire integration from chat history or trial-and-error. Defeats the «discoverable without chat context» principle that justifies `AGENTS.md` in the first place.</WhyBad>
       <Good>Append a Storybook section to `AGENTS.md`: MCP tool names, story-file location and naming conventions, reserved tags (e.g. `ai-generated`), pointer to `testing/storybook-usage.xml`.</Good>
-    </Anti_Pattern>
-  </Anti_Patterns>
+    </AntiPattern>
+  </AntiPatterns>
-  <Verification_Hooks>
+  <VerificationHooks>
     <Hook id="HOOK_SB_PREVIEW_BOOTS">
       <Purpose>Storybook dev server boots without errors and serves the preview.</Purpose>
       <Command>npx storybook dev --ci --quiet &amp; PID=$!; sleep 8; curl -fsS http://localhost:6006/index.json > /dev/null; STATUS=$?; kill $PID 2>/dev/null; wait $PID 2>/dev/null; exit $STATUS</Command>
@@ -133,9 +133,9 @@
       <Command>npx playwright install --dry-run chromium 2>&amp;1 | grep -E "browser is already installed|is downloaded" || echo MISSING</Command>
       <Expected>Output indicates Chromium is already installed. `MISSING` means the browser still needs `npx playwright install chromium`.</Expected>
     </Hook>
-  </Verification_Hooks>
+  </VerificationHooks>
-  <Reward_Criteria>
+  <RewardCriteria>
     ✅ Storybook installed via the official initializer; generated guide applied verbatim.
     ✅ Test/MCP addon installed and present in `.storybook/main.*`.
     ✅ MCP server registered in the agent runner; at least one MCP tool call succeeds.
@@ -149,5 +149,5 @@
     ❌ Setup declared done without booting `storybook dev` or running a story test.
     ❌ `AGENTS.md` not updated; integration left as tribal knowledge.
     ❌ Parallel story-test harness introduced alongside the official addon.
-  </Reward_Criteria>
+  </RewardCriteria>
 </StorybookSetupRules>