gennady 0.8.3 → 0.8.4-draft.2

package/ai/kit/anti-pattern/testing/AP_TRY_CATCH_FLAG_ANTIPATTERN.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/node-test.xml -->
+<AntiPattern id="AP_TRY_CATCH_FLAG_ANTIPATTERN">
+      <Bad>`let threw = false; try { await client.reserveStock(''); } catch (e) { threw = true; assert.ok((e as Error).message.includes('idempotency')); } assert.ok(threw);`</Bad>
+      <WhyBad>Manual try/catch + boolean flag instead of `assert.rejects()` (`AX_ASSERT_API_CHOICE`). `includes()` on error message (inherited `AX_PARTIAL_STRING_VIA_MATCH`). Test can silently pass if the code stops throwing — `threw` stays false, only fallback gate is `assert.ok(threw)`.</WhyBad>
+      <Good>`await assert.rejects(() => client.reserveStock(''), (error) => { assert.match((error as Error).message, /idempotency.*empty|empty.*idempotency/i); return true; });`</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/testing/AP_UNJUSTIFIED_VI_MOCK.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/vitest-rules.xml -->
+<AntiPattern id="AP_UNJUSTIFIED_VI_MOCK">
+  <Bad>`vi.mock('./http-client.ts', () => ({ httpClient: { get: vi.fn(...) } }))` for an in-process module; SUT instantiated as `new CatalogSync()` without injection.</Bad>
+  <WhyBad>`vi.mock` introduced without operator confirm and without justification (`AX_MOCK_REQUIRES_OPERATOR_CONFIRM`, inherited `AX_MOCK_AS_LAST_RESORT`). `httpClient` is in-process — the SUT could have accepted it as a constructor argument (`AX_HTTP_BOUNDARY_INJECTION`).</WhyBad>
+  <Good>SUT exposes injection seam: `class CatalogSync { constructor(deps: { httpRequest: HttpRequest }) {} }`. Test uses unified factory + `vi.fn()` stub through the seam (see `PT_DI_OVER_MOCK`).</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/testing/ap-atomic-noise-anchors.xml

@@ -0,0 +1,20 @@
+<!-- source: ai/directives/coding/typescript-rules.xml -->
+<AntiPattern id="AP_ATOMIC_NOISE_ANCHORS">
+<Bad>Anchors around a single `const`; anchor name `START_CHECK_RETRIES` (names syntax, not intent); comment restates the `if`; `Error("Limit")` without Trace-Prefix or cause.</Bad>
+<WhyBad>Atomic noise (violates `AX_ANCHOR_TRIVIAL_EXCEPTION`); name violates `AX_ANCHOR_INTENTFUL_NAMES`; comment violates `AX_COMMENT_VOCABULARY`; Error violates `AX_TRACE_PREFIXED_ERRORS`, `AX_ERROR_CHAINING_CAUSE`.</WhyBad>
+<Good language="typescript">
+```typescript
+const maxRetries = 3;
+
+// #region START_ENFORCE_RETRY_POLICY
+// purpose: stop retry fan-out before a degraded upstream turns one request into cascading load
+// failure mode: removing this guard converts transient upstream latency into duplicate pressure
+if (attempts > maxRetries) {
+    throw new TessellError(ErrKind.ERR_CHECKOUT_CHARGE_UPSTREAM_UNRESPONSIVE, "[Checkout#charge] Upstream provider unresponsive", {
+      cause: { attempts, maxRetries }
+    });
+}
+// #endregion END_ENFORCE_RETRY_POLICY
+```
+</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/testing/ap-before-each-let-pileup.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/vitest-rules.xml -->
+<AntiPattern id="AP_BEFORE_EACH_LET_PILEUP">
+  <Bad>Describe scope hosts `let sut, saveOrder, publish, order, now`; `beforeEach` assigns them; second case re-assigns shared `sut` to a different config (leaks state).</Bad>
+  <WhyBad>Pile of `let`-variables (inherited `AX_NO_DESCRIBE_LET_PILEUP`). Per-case data built in `beforeEach` without teardown reason (inherited `AX_HOOKS_ONLY_FOR_LIFECYCLE` + `AX_PREFER_FACTORY_OVER_HOOKS`). No unified context type/factory (inherited `AX_ONE_UNIFIED_CONTEXT_PER_FILE`).</WhyBad>
+  <Good>ONE context type + ONE `createOrderLifecycleContext(overrides)` factory used by every case. Each case destructures the fields it uses; failure case overrides one field. No `beforeEach`, no shared `let`s.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/testing/ap-contains-on-error-and-private-inspection.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/vitest-rules.xml -->
+<AntiPattern id="AP_CONTAINS_ON_ERROR_AND_PRIVATE_INSPECTION">
+  <Bad>`try { await client.reserveStock(''); expect.fail('should have thrown'); } catch (e) { expect((e as Error).message).toContain('idempotency'); }` AND inspecting `client._inflightCount` with `@ts-expect-error`.</Bad>
+  <WhyBad>Manual `try/catch + expect.fail` instead of `rejects.toThrow` (`AX_VITEST_ASSERT_API_CHOICE`). `toContain` on `error.message` (inherited `AX_PARTIAL_STRING_VIA_MATCH`). Inspecting protected internal field (inherited `AX_CONTRACT_OVER_IMPLEMENTATION`).</WhyBad>
+  <Good>`await expect(client.reserveStock('')).rejects.toThrow(/idempotency.*empty|empty.*idempotency/i);` and subscribe to public lifecycle event for observation.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/testing/ap-duplicate-bdd-group.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-spec-drafting.xml -->
+<AntiPattern id="AP_DUPLICATE_BDD_GROUP">
+      <Bad>Один BDD-заголовок на несколько размеров: `### Primary / Accent (все размеры)`.</Bad>
+      <WhyBad>Разные размеры имеют разные ожидаемые значения (height, pads). Сгруппированные BDD нельзя верифицировать.</WhyBad>
+      <Good>Отдельный BDD-заголовок на каждый (appearance, mode), внутри указывается representative size и конкретные значения.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/testing/ap-leaked-lifecycle-and-global-reliance.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/vitest-rules.xml -->
+<AntiPattern id="AP_LEAKED_LIFECYCLE_AND_GLOBAL_RELIANCE">
+  <Bad>Test file has no imports (relies on `globals: true`). Inside a case: `vi.useFakeTimers(); vi.setSystemTime(...); vi.stubEnv('TICK', '1000');` without paired teardown.</Bad>
+  <WhyBad>Reliance on `globals: true` (`AX_EXPLICIT_VITEST_IMPORTS`). Fake timers and env stubs without paired teardown (`AX_TIME_ENV_GLOBAL_LIFECYCLE`). State leaks into subsequent cases → order-dependent flicker.</WhyBad>
+  <Good>Explicit imports; `beforeEach` enables fake timers + env stubs; `afterEach` calls `vi.useRealTimers()` + `vi.unstubAllEnvs()` (see `PT_LIFECYCLE_CONTEXT_WITH_CLEANUP`).</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/testing/ap-parallel-factories.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/vitest-rules.xml -->
+<AntiPattern id="AP_PARALLEL_FACTORIES">
+  <Bad>One file declares `createOrderContextHappy()`, `createOrderContextWithDiscount()`, `createOrderContextFailing()`.</Bad>
+  <WhyBad>Three parallel factories for one SUT (inherited `AX_ONE_UNIFIED_CONTEXT_PER_FILE`). Each drifts independently; structural changes in `OrderLifecycle` require N edits, not one. Reader-agent must learn three shapes instead of one + a set of overrides.</WhyBad>
+  <Good>Single `createOrderLifecycleContext(overrides)` factory; happy / discount / failure cases pass different overrides through the same factory.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/testing/ap-private-inspection.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/node-test.xml -->
+<AntiPattern id="AP_PRIVATE_INSPECTION">
+      <Bad>Test inspects `client._inflightCount` (protected/internal field) via `@ts-expect-error` to bypass encapsulation.</Bad>
+      <WhyBad>Violates inherited `AX_CONTRACT_OVER_IMPLEMENTATION`. A refactor renaming `_inflightCount` to `_pending` breaks the test without changing the contract.</WhyBad>
+      <Good>Subscribe to `client.on('reservation.requested', e => events.push(e))` and assert `events.length` + `events[0].idempotencyKey`. Public lifecycle event is the observable.</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/testing/ap-shared-mutable-state-and-non-english-narration.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/node-test.xml -->
+<AntiPattern id="AP_SHARED_MUTABLE_STATE_AND_NON_ENGLISH_NARRATION">
+      <Bad>`const cart = new Cart()` shared between tests; test names in Russian («добавляет товар»); `Шаг 1: добавляем` / `Шаг 2: проверяем` comments; second test depends on state from first.</Bad>
+      <WhyBad>Shared mutable state breaks isolation (inherited `AX_NO_DESCRIBE_LET_PILEUP`); creates order dependency. Non-English names/comments (inherited `AX_ENGLISH_ONLY_NAMES_AND_COMMENTS`). Step-by-step human narration (inherited `AX_TESTS_NO_HUMAN_NARRATION`).</WhyBad>
+      <Good>Single context factory `createCartContext(overrides?)` called inside each case; English titles like `should expose count = 1 after a single add`; direct assertions.</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/testing/ap-skip-instead-of-fix.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-storybook.xml -->
+<AntiPattern id="AP_SKIP_INSTEAD_OF_FIX">
+      <Bad>Failing story is marked `.skip` or deleted to make `run-story-tests` green.</Bad>
+      <WhyBad>Failure silenced instead of fixed. The story was the only test coverage for that code path — skipping it removes the failure signal without removing the defect. The self-verification loop is now blind to that variant.</WhyBad>
+      <Good>Fix the component or the story, re-run until green. If the failure is environment-dependent, surface as a blocker with deferred-ownership reference.</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/testing/ap-snapshot-for-scalar.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/node-test.xml -->
+<AntiPattern id="AP_SNAPSHOT_FOR_SCALAR">
+      <Bad>`it('returns 42', (t) => { const result = compute(); t.assert.snapshot(result); });`</Bad>
+      <WhyBad>Snapshot for a scalar — violates inherited `AX_SNAPSHOT_USAGE_GATE`. Failure shows diff of snapshot blobs instead of «42 ≠ 41».</WhyBad>
+      <Good>`assert.strictEqual(result, 42)` — direct, clear, no snapshot file overhead.</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/testing/ap-try-catch-flag-antipattern.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/node-test.xml -->
+<AntiPattern id="AP_TRY_CATCH_FLAG_ANTIPATTERN">
+      <Bad>`let threw = false; try { await client.reserveStock(''); } catch (e) { threw = true; assert.ok((e as Error).message.includes('idempotency')); } assert.ok(threw);`</Bad>
+      <WhyBad>Manual try/catch + boolean flag instead of `assert.rejects()` (`AX_ASSERT_API_CHOICE`). `includes()` on error message (inherited `AX_PARTIAL_STRING_VIA_MATCH`). Test can silently pass if the code stops throwing — `threw` stays false, only fallback gate is `assert.ok(threw)`.</WhyBad>
+      <Good>`await assert.rejects(() => client.reserveStock(''), (error) => { assert.match((error as Error).message, /idempotency.*empty|empty.*idempotency/i); return true; });`</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/testing/ap-unjustified-vi-mock.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/testing/vitest-rules.xml -->
+<AntiPattern id="AP_UNJUSTIFIED_VI_MOCK">
+  <Bad>`vi.mock('./http-client.ts', () => ({ httpClient: { get: vi.fn(...) } }))` for an in-process module; SUT instantiated as `new CatalogSync()` without injection.</Bad>
+  <WhyBad>`vi.mock` introduced without operator confirm and without justification (`AX_MOCK_REQUIRES_OPERATOR_CONFIRM`, inherited `AX_MOCK_AS_LAST_RESORT`). `httpClient` is in-process — the SUT could have accepted it as a constructor argument (`AX_HTTP_BOUNDARY_INJECTION`).</WhyBad>
+  <Good>SUT exposes injection seam: `class CatalogSync { constructor(deps: { httpRequest: HttpRequest }) {} }`. Test uses unified factory + `vi.fn()` stub through the seam (see `PT_DI_OVER_MOCK`).</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_DROPPED_VARIANTS.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-spec-drafting.xml -->
+<AntiPattern id="AP_DROPPED_VARIANTS">
+      <Bad>Пропуск строки в таблице Variants, потому что «этот вариант не в extraction».</Bad>
+      <WhyBad>Closed-world нарушен. Последующий SpecValidator не сможет отличить «пропущен осознанно» от «забыли».</WhyBad>
+      <Good>Строка присутствует, но состояния помечены `⚠️ not in extraction`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_FABRICATED_MEASUREMENTS.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-spec-drafting.xml -->
+<AntiPattern id="AP_FABRICATED_MEASUREMENTS">
+      <Bad>BDD-сценарий с выдуманными значениями: `background = #0077FF`, когда в extraction нет такого цвета.</Bad>
+      <WhyBad>SpecValidator обнаружит расхождение. Фабрикация данных подрывает доверие к спекам.</WhyBad>
+      <Good>Все Then-значения берутся из `MeasurementSet` соответствующего варианта: `rectFill`, `height`, `borderRadius`, etc.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_HARDCODED_PIXELS.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_HARDCODED_PIXELS">
+<Bad>`.module.css` with `height: 28px;` instead of `var(--vkui--size_button_small_height--compact)`.</Bad>
+<WhyBad>Token not consumed via custom property (`AX_CSS_TOKENS_VIA_ROOT`). The value cannot be overridden, themed, or traced back to the VKUI token system. When the design system updates the token, this component silently stays at the old value.</WhyBad>
+<Good>`height: var(--vkui--size_button_small_height--compact);` — the token from `.tokens.css` flows through.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_HOST_SELECTOR.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_HOST_SELECTOR">
+<Bad>`.module.css` containing `:host([mode="primary"]) { background: blue; }`.</Bad>
+<WhyBad>`:host()` compound selectors fail in headless Chromium (`AX_DATA_ATTRS_NOT_HOST`). Padding returns `0px` from `getComputedStyle`, breaking visual tests. The inner-wrapper approach is the proven alternative.</WhyBad>
+<Good>Inner wrapper with data-attribute: `.btn[data-mode="primary"] { background: var(--vkui--color_background_accent); }`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_IMG_TAG_ICON.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_IMG_TAG_ICON">
+<Bad>Icon rendered as `<img src="icon.svg" alt="" />`.</Bad>
+<WhyBad>Icon fill cannot be controlled via CSS when using `<img>` (`AX_ICON_SVG_TIGHT_VIEWBOX`). Each appearance/mode combination would need a separate SVG file with hardcoded fill. Inlined SVG with `fill: currentColor` or CSS variable solves this.</WhyBad>
+<Good>Inline the SVG with tight viewBox; control fill via CSS on the `.icon` container or the SVG paths directly.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_MISSING_A11Y_AUDIT.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-storybook.xml -->
+<AntiPattern id="AP_MISSING_A11Y_AUDIT">
+      <Bad>Story or meta lacks `parameters: { a11y: { test: 'error' } }`.</Bad>
+      <WhyBad>A11y audit not configured (`AX_A11Y_AUDIT_PARAMETERS`). axe-core does not run during `run-story-tests`; a11y violations (missing labels, wrong contrast, invalid roles) pass silently.</WhyBad>
+      <Good>Add `parameters: { a11y: { test: 'error' } }` to `meta` (applies to all stories) or to each individual story.</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_MISSING_ARIA.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_MISSING_ARIA">
+<Bad>Button component with `<div class="btn" onclick={handler}>` and no ARIA attributes.</Bad>
+<WhyBad>A11y contract not fulfilled (`AX_A11Y_REQUIREMENTS`). Screen readers cannot identify the element as a button, cannot announce its label, cannot report its disabled state. Keyboard users cannot focus or activate it.</WhyBad>
+<Good>`<div class="btn" role="button" aria-label={label} aria-disabled={disabled} tabindex={disabled ? -1 : 0}>`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_MISSING_DATA_STATE.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_MISSING_DATA_STATE">
+<Bad>Component relies on CSS `:hover` pseudo-class for hover styling, with no `data-state` attribute.</Bad>
+<WhyBad>Headless test environments cannot trigger `:hover` programmatically (`AX_DATA_STATE_FOR_TESTABILITY`). The hover variant is untestable — visual regression tests pass trivially without actually verifying hover appearance.</WhyBad>
+<Good>Add `data-state={resolvedState}` attribute and use `.btn[data-state="hover"]` selectors. Tests assert `toHaveAttribute('data-state', 'hover')`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_OVERRIDE_WITHOUT_COMMENT.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_OVERRIDE_WITHOUT_COMMENT">
+<Bad>`.tokens.css` with `--vkui--size_button_tertiary_small_padding_horizontal_icon--regular: 14px;` and no override comment.</Bad>
+<WhyBad>Override without audit trail (`AX_TOKEN_OVERRIDE_COMMENT`). Cannot distinguish intentional override from accidental drift. SpecValidator cannot trace the value back to the Token Mapping table.</WhyBad>
+<Good>`/* override: was 8px */` on the line above the declaration.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_PASCAL_CASE_FILENAME.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_PASCAL_CASE_FILENAME">
+<Bad>Component file named `Button.svelte` or `Button.module.css`.</Bad>
+<WhyBad>Violates kebab-case convention (`AX_FILE_STRUCTURE_KEBAB_CASE`, D-UC03). Inconsistent with existing project files (`app.svelte`, `app.stories.ts`). Breaks the closed-world `ComponentArtefact` contract.</WhyBad>
+<Good>`button.svelte`, `button.module.css`, `button.tokens.css`, `button.stories.ts`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/AP_SILENT_MISSING_TOKEN.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-spec-drafting.xml -->
+<AntiPattern id="AP_SILENT_MISSING_TOKEN">
+      <Bad>Пропуск строки в Token Mapping, когда токен не найден.</Bad>
+      <WhyBad>Измерение теряется. SpecValidator не может проверить, что все измерения покрыты.</WhyBad>
+      <Good>Строка с `⚠️ no token` в колонке Token и `Action = ⚠️`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-dropped-variants.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-spec-drafting.xml -->
+<AntiPattern id="AP_DROPPED_VARIANTS">
+      <Bad>Пропуск строки в таблице Variants, потому что «этот вариант не в extraction».</Bad>
+      <WhyBad>Closed-world нарушен. Последующий SpecValidator не сможет отличить «пропущен осознанно» от «забыли».</WhyBad>
+      <Good>Строка присутствует, но состояния помечены `⚠️ not in extraction`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-fabricated-measurements.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-spec-drafting.xml -->
+<AntiPattern id="AP_FABRICATED_MEASUREMENTS">
+      <Bad>BDD-сценарий с выдуманными значениями: `background = #0077FF`, когда в extraction нет такого цвета.</Bad>
+      <WhyBad>SpecValidator обнаружит расхождение. Фабрикация данных подрывает доверие к спекам.</WhyBad>
+      <Good>Все Then-значения берутся из `MeasurementSet` соответствующего варианта: `rectFill`, `height`, `borderRadius`, etc.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-hardcoded-pixels.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_HARDCODED_PIXELS">
+<Bad>`.module.css` with `height: 28px;` instead of `var(--vkui--size_button_small_height--compact)`.</Bad>
+<WhyBad>Token not consumed via custom property (`AX_CSS_TOKENS_VIA_ROOT`). The value cannot be overridden, themed, or traced back to the VKUI token system. When the design system updates the token, this component silently stays at the old value.</WhyBad>
+<Good>`height: var(--vkui--size_button_small_height--compact);` — the token from `.tokens.css` flows through.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-host-selector.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_HOST_SELECTOR">
+<Bad>`.module.css` containing `:host([mode="primary"]) { background: blue; }`.</Bad>
+<WhyBad>`:host()` compound selectors fail in headless Chromium (`AX_DATA_ATTRS_NOT_HOST`). Padding returns `0px` from `getComputedStyle`, breaking visual tests. The inner-wrapper approach is the proven alternative.</WhyBad>
+<Good>Inner wrapper with data-attribute: `.btn[data-mode="primary"] { background: var(--vkui--color_background_accent); }`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-img-tag-icon.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_IMG_TAG_ICON">
+<Bad>Icon rendered as `<img src="icon.svg" alt="" />`.</Bad>
+<WhyBad>Icon fill cannot be controlled via CSS when using `<img>` (`AX_ICON_SVG_TIGHT_VIEWBOX`). Each appearance/mode combination would need a separate SVG file with hardcoded fill. Inlined SVG with `fill: currentColor` or CSS variable solves this.</WhyBad>
+<Good>Inline the SVG with tight viewBox; control fill via CSS on the `.icon` container or the SVG paths directly.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-missing-a11y-audit.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-storybook.xml -->
+<AntiPattern id="AP_MISSING_A11Y_AUDIT">
+      <Bad>Story or meta lacks `parameters: { a11y: { test: 'error' } }`.</Bad>
+      <WhyBad>A11y audit not configured (`AX_A11Y_AUDIT_PARAMETERS`). axe-core does not run during `run-story-tests`; a11y violations (missing labels, wrong contrast, invalid roles) pass silently.</WhyBad>
+      <Good>Add `parameters: { a11y: { test: 'error' } }` to `meta` (applies to all stories) or to each individual story.</Good>
+    </AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-missing-aria.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_MISSING_ARIA">
+<Bad>Button component with `<div class="btn" onclick={handler}>` and no ARIA attributes.</Bad>
+<WhyBad>A11y contract not fulfilled (`AX_A11Y_REQUIREMENTS`). Screen readers cannot identify the element as a button, cannot announce its label, cannot report its disabled state. Keyboard users cannot focus or activate it.</WhyBad>
+<Good>`<div class="btn" role="button" aria-label={label} aria-disabled={disabled} tabindex={disabled ? -1 : 0}>`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-missing-data-state.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_MISSING_DATA_STATE">
+<Bad>Component relies on CSS `:hover` pseudo-class for hover styling, with no `data-state` attribute.</Bad>
+<WhyBad>Headless test environments cannot trigger `:hover` programmatically (`AX_DATA_STATE_FOR_TESTABILITY`). The hover variant is untestable — visual regression tests pass trivially without actually verifying hover appearance.</WhyBad>
+<Good>Add `data-state={resolvedState}` attribute and use `.btn[data-state="hover"]` selectors. Tests assert `toHaveAttribute('data-state', 'hover')`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-override-without-comment.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_OVERRIDE_WITHOUT_COMMENT">
+<Bad>`.tokens.css` with `--vkui--size_button_tertiary_small_padding_horizontal_icon--regular: 14px;` and no override comment.</Bad>
+<WhyBad>Override without audit trail (`AX_TOKEN_OVERRIDE_COMMENT`). Cannot distinguish intentional override from accidental drift. SpecValidator cannot trace the value back to the Token Mapping table.</WhyBad>
+<Good>`/* override: was 8px */` on the line above the declaration.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-pascal-case-filename.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-component-svelte.xml -->
+<AntiPattern id="AP_PASCAL_CASE_FILENAME">
+<Bad>Component file named `Button.svelte` or `Button.module.css`.</Bad>
+<WhyBad>Violates kebab-case convention (`AX_FILE_STRUCTURE_KEBAB_CASE`, D-UC03). Inconsistent with existing project files (`app.svelte`, `app.stories.ts`). Breaks the closed-world `ComponentArtefact` contract.</WhyBad>
+<Good>`button.svelte`, `button.module.css`, `button.tokens.css`, `button.stories.ts`.</Good>
+</AntiPattern>

package/ai/kit/anti-pattern/uikit/ap-silent-missing-token.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/coding/uikit-spec-drafting.xml -->
+<AntiPattern id="AP_SILENT_MISSING_TOKEN">
+      <Bad>Пропуск строки в Token Mapping, когда токен не найден.</Bad>
+      <WhyBad>Измерение теряется. SpecValidator не может проверить, что все измерения покрыты.</WhyBad>
+      <Good>Строка с `⚠️ no token` в колонке Token и `Action = ⚠️`.</Good>
+</AntiPattern>

package/ai/kit/axiom/agent-inbox/ax-complexity-budget.xml

@@ -0,0 +1,9 @@
+<!-- new for TSK-136: mission-adequacy brick (D-122/AI-43) -->
+<Axiom id="AX_COMPLEXITY_BUDGET">
+  Complexity — branching, indirection, state held in memory, number of concepts a reader must
+  hold at once — is a budget spent against the problem's ACTUAL shape, not the imagined future
+  one. Judge whether the complexity the diff adds is proportional to what today's requirement
+  needs; generality/config/abstraction built for a need that is not yet real is over-spend, flagged
+  regardless of how clean the code looks in isolation. This is a language-independent practice no
+  linter measures — it is read from the diff against the stated problem, not from style rules.
+</Axiom>

package/ai/kit/axiom/agent-inbox/ax-minimal-change-suspicion.xml

@@ -0,0 +1,9 @@
+<!-- new for TSK-136: mrShape trigger brick, isTiny (D-123/AI-44) -->
+<Axiom id="AX_MINIMAL_CHANGE_SUSPICION">
+  A change touching exactly one line in exactly one file is NOT automatically safe — small size is
+  not a proxy for low risk. Treat it with heightened, not relaxed, scrutiny: a one-character diff
+  can be a typo fix, or it can be an off-by-one, a flipped operator, a silently changed default, or
+  a fix at the wrong layer masking a deeper root cause. Before accepting a tiny diff at face value,
+  actively look at the neighbouring lines and callers the one line touches — the smallness of the
+  edit says nothing about the smallness of its effect.
+</Axiom>

package/ai/kit/axiom/agent-inbox/ax-review-purpose.xml

@@ -0,0 +1,10 @@
+<!-- new for TSK-136: mission-adequacy brick (D-122/AI-43) -->
+<Axiom id="AX_REVIEW_PURPOSE">
+  The mission is judging ADEQUACY, not bug-hunting. Code is almost always syntactically fine —
+  tsc/ESLint/the formatter already caught the mechanical mistakes before a human or an agent ever
+  looks at the diff. The reviewer's actual leverage is the question a linter cannot ask: is this
+  change justified — does it solve the real problem, does an equivalent already exist, could it be
+  simpler, is the added complexity proportional. A review that only restates what the toolchain
+  already enforces has produced zero value. Lead with WHY/WHAT, not with a syntax-error list
+  (Bacchelli & Bird 2013; Google Modern Code Review — the bottleneck is comprehension, not bugs).
+</Axiom>

package/ai/kit/axiom/agent-inbox/ax-simpler-alternative.xml

@@ -0,0 +1,9 @@
+<!-- new for TSK-136: mission-adequacy brick (D-122/AI-43) -->
+<Axiom id="AX_SIMPLER_ALTERNATIVE">
+  For every non-trivial construct the diff introduces, ask ONE question before anything else:
+  could this achieve the same result with less code, less indirection, fewer moving parts? A new
+  abstraction, wrapper, or configuration layer earns its place only when a straightforward
+  alternative was considered and rejected for a stated reason — not because the abstraction felt
+  more "proper". Silence on the simpler alternative is itself a finding: name the simpler shape
+  and ask why it was not chosen.
+</Axiom>

package/ai/kit/axiom/audit/ax-audit-modes.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_AUDIT_MODES">
+      Per-task vs epic-level.
+      - **Per-task** (default): operator passes single task-ID. Audit bounded to its scope.
+      - **Epic-level**: operator passes a list of task-IDs or a general scope (e.g., «everything in scope payments»). Audit produces aggregated summary + checks cross-task consistency (Decision Log entries, absence of conflicting contracts between tasks of one module).
+    </Axiom>

package/ai/kit/axiom/audit/ax-audit-reads-code.xml

@@ -0,0 +1,11 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_AUDIT_READS_CODE">
+      Audit is the only SDD directive allowed to read code. Reading scope is bounded:
+      - all files listed in per-phase `Target Files` under ticket Phases;
+      - artifacts list passed by orchestrator (union of phase Handoffs);
+      - related ports/adapters/services in `Spec References`;
+      - files flagged in Execution Log `intro <X> ← <Y>` lines;
+      - **all files modified during ticket execution** (see `AX_GIT_DIFF_SCAN`).
+
+      Reading unrelated parts of the project is forbidden — derails focus, consumes context.
+    </Axiom>

package/ai/kit/axiom/audit/ax-bdd-coverage-verification.xml

@@ -0,0 +1,8 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_BDD_COVERAGE_VERIFICATION">
+      BDD ↔ test code must align.
+      - Every Acceptance Scenario from ticket has a corresponding test case in the specified test file.
+      - Canonical case name from `Test Scenario Coverage` matches actual `it` / `test` name verbatim.
+
+      Mismatch → `BDD_COVERAGE_MISMATCH` with proposal: update test or update ticket.
+    </Axiom>

package/ai/kit/axiom/audit/ax-closed-world-primary-check.xml

@@ -0,0 +1,4 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_CLOSED_WORLD_PRIMARY_CHECK">
+      Closed-world drift is the priority check — the main pain audit prevents. The entity world is closed by exactly two sources: the module spec Entity Inventory, and the `intro <X> ← <Y>` lines phase agents logged in the Execution Log. Drift = (public entities in code) ∖ (inventory ∪ logged-introductions); every element of that set is a `CLOSED_WORLD_DRIFT` finding (`BLOCKER`).
+    </Axiom>

package/ai/kit/axiom/audit/ax-completeness-check.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_COMPLETENESS_CHECK">
+      Two-sided.
+      - **Forward:** every Port, Adapter, Entity, operation from Entity Surface, Acceptance Scenario has a corresponding artifact in code.
+      - **Backward:** every artifact in code has a corresponding mention in spec/ticket. Prone to false positives (utility helpers, internal abstractions). Apply with judgment — explicit public surface checked strictly; internal helpers informational only.
+    </Axiom>

package/ai/kit/axiom/audit/ax-drift-taxonomy.xml

@@ -0,0 +1,21 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_DRIFT_TAXONOMY">
+      Findings are classified by type. Every finding has exactly one:
+
+      | Type | Meaning |
+      |---|---|
+      | `CLOSED_WORLD_DRIFT` | entity present in code but absent from module spec Entity Inventory AND no `intro` log line |
+      | `COMPLETENESS_GAP` | entity / contract / scenario promised in spec but not implemented |
+      | `RUNTIME_BACKING_VIOLATION` | declared `real-runtime` actually backed by simulation seam without deferred marker; OR declared `Verification Level` not achievable in test setup |
+      | `RULES_COMPLIANCE_VIOLATION` | code violates rules listed in a phase's `Rules:` (any category); OR diff has artefact whose category is unhandled by any active phase |
+      | `RULES_CASCADE_MISMATCH` | a phase's `Rules:` list ≠ what scaffolder would derive now from cascade × that phase's `Target Files` + kind |
+      | `TASK_ID_DRIFT` | `@tasks` field references non-existent ticket ID (orphan); OR Task-ID duplicated across ticket files (collision); OR `@tasks` field lost prior IDs (regression of append-only) |
+      | `BDD_COVERAGE_MISMATCH` | canonical case names in ticket Test Scenario Coverage ≠ real test cases |
+      | `EXECUTION_LOG_INCOMPLETE` | mandatory closing lines missing (`ver` / `DONE` per phase, `DONE` at Round close); OR `intro` line absent for an entity that appears in code but not in module Inventory; OR a previous round was edited (round log is append-only); OR `[x]` line with unreplaced `<…>` placeholder (fabricated done) |
+      | `INSIGHT_BACKFLOW` | Phase agent discovered something that changes contract / requirement understanding; should flow back into spec |
+      | `STALE_AFTER_PIVOT` | scope spec was reworked in `pivot` mode (Pivot Invalidation List exists) but downstream artifacts named in the list have not been refined / reopened / updated |
+      | `RULE_FILE_INCOMPLETE` | activated rule file lacks one of the universal checkable sections (`<BeliefState>` / `<AntiPatterns>` / `<VerificationHooks>` / `<RewardCriteria>`) per `AX_RULES_COMPLIANCE_AGAINST_ACTIVATED_RULES`; audit can partially proceed but the gap blocks full coverage |
+      | `LANGUAGE_QUALITY` | operator-facing prose fails `AX_LANGUAGE_QUALITY_CHECK` — calques (from the `SDD_LANGUAGE_CALQUE` pre-filter) or literary/ornate style the deterministic lint cannot catch |
+      | `YAGNI_WAIVER_INCOMPLETE` | a contract `Usage Waiver` label exists for a symbol, but the round's Execution Log has no matching `yagni <name> ← <reason>` line (`AX_AUDIT_YAGNI_CROSSCHECK`) |
+      | `ENVIRONMENT_GATE_UNAVAILABLE` | a required gate command (`sdd-verify`, `gennady lint`, `gennady testcov`, or a ticket §5 command) could not execute at all — missing runner, missing script, no network, crashed before producing a pass/fail — as opposed to executing and reporting a red result |
+    </Axiom>

package/ai/kit/axiom/audit/ax-ephemeral-output.xml

@@ -0,0 +1,8 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_EPHEMERAL_OUTPUT">
+      The audit summary itself does not create files in `audits/`. Output is an ephemeral session-summary emitted in chat per `AUDIT_SESSION_SUMMARY_FORMAT`: counts by severity + findings table + proposed changes per `AX_FINDING_ROUTING`.
+
+      Reopen-history of a ticket is persisted *inside the ticket file* — see `AX_REOPEN_ROUNDS_IN_TICKET`. Long-term audit history = git history of the affected spec and ticket files.
+
+      Epic-level audit: cross-task findings (e.g., two modules with conflicting contracts) → Decision Log entry in the relevant scope spec.
+    </Axiom>

package/ai/kit/axiom/audit/ax-execution-log-verification.xml

@@ -0,0 +1,6 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_EXECUTION_LOG_VERIFICATION">
+      Token vocabulary in `scaffold.directive.xml` Execution Log Template. Required per phase block: `ver` (one final result), `DONE`, `**Handoff →**`, `intro <X> ← <reason>` for every entity in code but not in module Inventory (cross-check via git diff), `verified` for `config`-kind, `BLOCKED <cause>` if phase ended blocked.
+
+      Missing required line → `EXECUTION_LOG_INCOMPLETE`. Unreplaced `<…>` placeholder on `[x]` line → `EXECUTION_LOG_INCOMPLETE` (BLOCKER, «fabricated done»). Line with a token outside the vocabulary → `EXECUTION_LOG_INCOMPLETE` (MINOR, «padding»).
+    </Axiom>

package/ai/kit/axiom/audit/ax-finding-routing.xml

@@ -0,0 +1,22 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_FINDING_ROUTING">
+      Every finding is routed to the artifact that owns the remediation:
+
+      | Finding type | Action |
+      |---|---|
+      | `CLOSED_WORLD_DRIFT` | spec edit (add entity to Inventory) OR ticket reopen |
+      | `COMPLETENESS_GAP` | ticket reopen — new Round N |
+      | `RUNTIME_BACKING_VIOLATION` | spec edit (Deferred Runtime Scope) OR ticket reopen |
+      | `RULES_COMPLIANCE_VIOLATION` | ticket reopen, new Round N |
+      | `RULES_CASCADE_MISMATCH` | ticket update (per-phase `Rules:` list) |
+      | `BDD_COVERAGE_MISMATCH` | ticket reopen OR ticket update (canonical case names) |
+      | `EXECUTION_LOG_INCOMPLETE` | ticket update / reopen |
+      | `INSIGHT_BACKFLOW` | spec edit (scope or module spec) |
+      | `STALE_AFTER_PIVOT` | reopen / refine the affected downstream artifact |
+      | `TASK_ID_DRIFT` | code-fix via ticket reopen |
+      | `ENVIRONMENT_GATE_UNAVAILABLE` | operator escalation — NOT a phase fix and NOT something audit or the worker repairs itself; spin out as a separate infra/environment task if the fix is non-trivial |
+      | `DEAD_CODE_SUSPECT` (spotted incidentally during a probe) | spin out as a separate task (background task / new ticket) — never fixed inside the current task; keeps the current blast radius bounded |
+      | operator-acknowledged risk | Decision Log entry in the scope spec |
+
+      The audit agent proposes a concrete edit (diff or instruction). The operator decides and applies. The audit agent does not modify code autonomously (per `AX_NO_AUTO_FIX`).
+    </Axiom>

package/ai/kit/axiom/audit/ax-findings-as-proposals.xml

@@ -0,0 +1,7 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_FINDINGS_AS_PROPOSALS">
+      Every finding contains a proposed remediation. Agent does not modify code. Three remediation types:
+      - `code-fix` — concrete change in code (with location).
+      - `spec-update` — concrete spec update (module or scope) with proposed diff.
+      - `ticket-update` — ticket update (canonical case names, deferred scope, etc.).
+    </Axiom>

package/ai/kit/axiom/audit/ax-git-diff-scan.xml

@@ -0,0 +1,11 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_GIT_DIFF_SCAN">
+      Audit widens its read scope via git diff. Per-phase `Target Files` alone is insufficient for reliable closed-world detection: a phase agent could create a helper in `src/utils/`, modify shared types, add a migration without mentioning it. Without diff scan, audit relies on log honesty — contradicting audit's mission.
+
+      Mechanics:
+      - `git diff <round-start-ref>..<round-done-ref>` (or `git diff` against last pre-round commit if refs unavailable);
+      - collect modified / added / deleted files;
+      - in-scope set = union(all phases' `Target Files`, diff files, `intro` log).
+
+      Files in diff but absent from ticket declaration + Execution Log → candidates for `CLOSED_WORLD_DRIFT` (public entities) or `EXECUTION_LOG_INCOMPLETE` (utility-only changes).
+    </Axiom>

package/ai/kit/axiom/audit/ax-insight-backflow-capture.xml

@@ -0,0 +1,10 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_INSIGHT_BACKFLOW_CAPTURE">
+      Insights flow back into the spec. If Execution Log or code analysis shows:
+      - real complexity of contract turned out higher or lower than spec;
+      - new edge cases discovered, not in Requirements & Constraints;
+      - spec assumptions turned out incorrect;
+      - new dependency emerged, not in Inter-Module Dependencies,
+
+      → `INSIGHT_BACKFLOW` finding with proposed spec-update diff.
+    </Axiom>

package/ai/kit/axiom/audit/ax-learning-context.xml

@@ -0,0 +1,2 @@
+<!-- source: ai/directives/dbc-audit.directive.xml -->
+<Axiom id="AX_LEARNING_CONTEXT">Treat contracts, anchors, intent comments as learning context embedded into code for future agents. Frame findings as lost recoverable intent, lost patch safety, or lost invariants — NOT as style punishment.</Axiom>

package/ai/kit/axiom/audit/ax-mechanical-via-sdd-check.xml

@@ -0,0 +1,9 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_MECHANICAL_VIA_SDD_CHECK">
+      Deterministic mechanical checks are NOT hand-coded in this directive — they live in one tool, `sdd-check`, which the whole-tree reporter and this directive both consume. Single source of mechanical truth → no drift between the SDD reviewers. Take its findings as given; do NOT hand-redo them.
+
+      - `sdd-check --task <ticket-path>` → one ticket: section-anchor balance · Meta + Execution Log present · Task-ID / Status parseable · fabricated DONE · DONE-with-active-blocker · DONE-with-placeholders · phase graph (deps resolve + acyclic) · phase ↔ `PHASE_Pn` section coverage · DONE ⇒ every phase checked.
+      - `sdd-check --all [root]` → the whole tree, additionally: the task DAG (Task-ID collisions · unresolved dependencies · cycles) · tracker ↔ ticket coherence (status drift · missing rows · orphan rows) · spec-link resolution + spec-anchor balance · portal integrity (scope-graph acyclicity · graph↔table↔spec · orphan specs · dangling deps).
+
+      Audit owns only what the tool cannot decide mechanically: closed-world symbol diff (code↔inventory), BDD↔test substance, rules-cascade resolution, stale-after-pivot, runtime-backing real-vs-stub, `@consumers` resolvability, append-only `@tasks` vs git. File-header presence (`@file`/`@consumers`/`@tasks`) is checked by `sdd-verify`, not here.
+    </Axiom>

package/ai/kit/axiom/audit/ax-neutral-findings.xml

@@ -0,0 +1,4 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_NEUTRAL_FINDINGS">
+      Findings are objective, free of value judgments. No «bad», «should be better», «ugly». Use «X is missing from Y», «Z contradicts W», «case name `foo` in ticket does not match `bar` in test». Criticism appeals to an axiom or rule: «violates `AX_CLOSED_WORLD_INVENTORY` of module spec».
+    </Axiom>

package/ai/kit/axiom/audit/ax-no-auto-fix.xml

@@ -0,0 +1,4 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_NO_AUTO_FIX">
+      Audit does not modify code or specs autonomously. Any remediation is a proposal per `AX_FINDING_ROUTING`. If operator approves inline changes during the session, audit agent may apply them to spec/ticket files (not code). Creating commits or editing code files independently is forbidden.
+    </Axiom>

package/ai/kit/axiom/audit/ax-provenance-is-a-product.xml

@@ -0,0 +1,2 @@
+<!-- source: ai/directives/dev-review.directive.xml -->
+<Axiom id="AX_PROVENANCE_IS_A_PRODUCT">Report explicitly separates external findings from locally-validated findings.</Axiom>

package/ai/kit/axiom/audit/ax-reopen-rounds-in-ticket.xml

@@ -0,0 +1,10 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_REOPEN_ROUNDS_IN_TICKET">
+      When an audit round triggers a ticket reopen, the round's audit summary is appended to the ticket file under a new `## Audit Rounds` section so the reopen history lives next to the Execution Log rounds it caused. Format per `TICKET_AUDIT_ROUND_FORMAT`. Append-only: prior audit rounds in the ticket are immutable.
+
+      Rationale: full ephemeral output loses reopen-causation between rounds; `audits/<task-id>.audit.md` separate-tree was overkill. Co-locating the audit round with the Execution Log it caused keeps history reviewable in one file.
+
+      Per-task audits that PASS without triggering a reopen do not write to the ticket — they remain ephemeral.
+
+      Epic-level audits never touch ticket files; their consolidated output is ephemeral OR routed to a scope-spec Decision Log entry.
+    </Axiom>

package/ai/kit/axiom/audit/ax-rules-cascade-verification.xml

@@ -0,0 +1,17 @@
+<!-- source: ai/directives/sdd/audit.directive.xml -->
+<Axiom id="AX_RULES_CASCADE_VERIFICATION">
+      For each phase block in Phases: that phase's `Rules:` list must equal what scaffolder would derive now from cascade × THAT PHASE's `Target Files` + `kind` — this re-derivation is irreducibly semantic (it needs the current cascade tiers, not just the declared list), so it stays audit's job.
+
+      Cascade tiers (sources of truth):
+
+      | Tier | Source |
+      |---|---|
+      | traversed-scopes | Cascade Table in `specs/<scope>/<scope>.3-tasks.md` traversed-scope rows |
+      | target-scope | `specs/<scope>/<scope>.3-tasks.md` target-scope row + scope spec Architecture/Rules |
+      | module | `specs/<scope>/<scope>.3-tasks.md` module row + module spec Module Rules Additions |
+      | task | additions appearing as extra entries in a phase's `Rules:` bullet list |
+
+      The transitive `<DependsOn>` closure of the *declared* list is `sdd-check`'s RULES_CASCADE_CLOSURE (`SDD_RULES_CASCADE_UNRESOLVED`, per `AX_MECHANICAL_VIA_SDD_CHECK`) — take that finding as given, do NOT open rule files and walk `<DependsOn>` by hand.
+
+      Plan rows ≠ derived from the cascade tiers → `RULES_CASCADE_MISMATCH` (`MAJOR`, HIGH).
+    </Axiom>