gennady 0.8.3 → 0.8.4-draft.2

package/dist/ai/directives/sdd/audit.directive.xml

@@ -1,543 +0,0 @@
-<SddAudit keywords="audit, drift-detection, closed-world-fidelity, completeness, runtime-backing, rules-cascade, rule-activation-overrides, rules-compliance, task-id-integrity, stale-after-pivot, insight-backflow, sdd-phase-5" type="directive" ver="3.0">
-  <Directive_Context>
-    <Mission>
-      Verify alignment between spec, task ticket, and actual code after task execution.
-
-      Fifth SDD session, dispatched by `sdd-execute` orchestrator after the last phase of a Round closes. Input:
-      - task ticket with completed Execution Log Round (every phase block `[x] DONE` + Round close);
-      - module spec (`specs/<scope>/<module>/<module>.spec.md`) and scope spec (`specs/<scope>/<scope>.spec.md`);
-      - rules listed in each phase's `Rules:` bullet list (across `ai/directives/<category>/<rule>.xml`); audit reads the union;
-      - the code itself (implementation + tests) referenced by per-phase `Target Files` plus any files revealed by git diff;
-      - artifacts list passed by orchestrator = union of all phases' `**Handoff →** artifacts: [...]`;
-      - Cascade Table from `tasks/<scope>/README.md` (for cascade verification).
-
-      Output:
-      - Ephemeral session-summary in chat: findings counts by severity + list of proposed / applied changes.
-      - On reopen-triggering rounds: an appended `## Audit Rounds` section in the ticket file (per `AX_REOPEN_ROUNDS_IN_TICKET`) — co-locates audit history with the Execution Log rounds it caused.
-      - No standalone files in `audits/` (deprecated in v3.0).
-
-      Audit does not modify code. It reports + proposes; operator decides.
-
-      **Glossary.** Phase 5 of SDD. Phase agent = subagent that operated under `phase-execution-protocol` on one of the phase blocks. Orchestrator = `sdd-execute` SKILL agent that dispatched the phases and now dispatches audit. Scaffolder = agent that operated under `task-scaffolding` when the ticket was generated. `phases_to_fix` = list of phase IDs returned by audit on FAIL, mapping finding locations to phases whose `Target Files` contain them.
-    </Mission>
-  </Directive_Context>
-
-  <Belief_State>
-    <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 section 3 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>
-
-    <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>
-
-    <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 (`<Belief_State>` / `<Anti_Patterns>` / `<Verification_Hooks>` / `<Reward_Criteria>`) per `AX_RULES_COMPLIANCE_AGAINST_ACTIVATED_RULES`; audit can partially proceed but the gap blocks full coverage |
-    </Axiom>
-
-    <Axiom id="AX_SEVERITY_TAGGING">
-      Every finding carries a severity:
-
-      | Severity | Meaning |
-      |---|---|
-      | `BLOCKER` | task cannot be considered complete; merge forbidden |
-      | `MAJOR` | protocol violation; requires fix; allows merge only with explicit operator acceptance + Decision Log entry |
-      | `MINOR` | stylistic or secondary discrepancy |
-      | `INFO` | observation without mandatory action (often `INSIGHT_BACKFLOW`) |
-
-      Severity does not depend on agent's mood. Closed-world drift = `BLOCKER` by default; coding-rules violation = `MAJOR`; stylistic deviation = `MINOR`.
-    </Axiom>
-
-    <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>
-
-    <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 |
-      | 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>
-
-    <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>
-
-    <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>
-
-    <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>
-
-    <Axiom id="AX_CLOSED_WORLD_PRIMARY_CHECK">
-      Closed-world drift is the priority check — main pain audit prevents.
-
-      Comparison:
-      1. Entities from `specs/<scope>/<module>/<module>.spec.md` 2 Entity Inventory.
-      2. Entities actually present in code (classes, interfaces, exported types/functions with public surface).
-      3. Entities flagged by phase agents in Execution Log as `intro <X> ← <Y>` lines.
-
-      Drift = (entities in code) ∖ (inventory ∪ logged-introductions). Each → `CLOSED_WORLD_DRIFT` (`BLOCKER`).
-    </Axiom>
-
-    <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>
-
-    <Axiom id="AX_RUNTIME_BACKING_VERIFICATION">
-      Runtime Backing and Verification Levels must match reality.
-      - Ticket declared `real-runtime` → look for real runtime hooks (event listeners, lifecycle subscribers, OS bridge calls). Only manual publish / test seams → `RUNTIME_BACKING_VIOLATION`.
-      - `simulation` allowed only with explicit `Deferred Runtime Scope` either in ticket or in updated spec.
-      - `not-implemented` implies real implementation is still ahead (separate task); confirm only contract artifacts exist; no production logic snuck in.
-      - For each declared `Verification Level`, corresponding test artifact must exist. Mismatch → `RUNTIME_BACKING_VIOLATION`.
-    </Axiom>
-
-    <Axiom id="AX_RULES_COMPLIANCE_AGAINST_ACTIVATED_RULES">
-      Compliance is checked against the union of rules listed across all phases of the Round (per each phase block's `<ts> rules <rule-ids>` line — or equivalently the `Rules:` bullet list in section 3 Phases). Not the full cascade — only what phases actually loaded.
-
-      **Audit is universal — no embedded knowledge of any language, runtime, or tool.** Every rule file exposes the same checkable surface; audit walks these sections mechanically:
-      - `<Depends_On>` → list of rule-file paths this rule architecturally extends (optional; empty for standalone rules). Used by scaffolder for transitive closure, by audit for cascade verification — NOT walked at runtime.
-      - `<Belief_State>` → `<Axiom AX_*>` constraints
-      - `<Anti_Patterns>` → `<Bad>` shapes that must not appear
-      - `<Verification_Hooks>` → executable check commands
-      - `<Reward_Criteria>` → ✅ invariants / ❌ forbidden states
-
-      Required sections: `<Belief_State>` / `<Anti_Patterns>` / `<Verification_Hooks>` / `<Reward_Criteria>`. Optional: `<Depends_On>` (only when the rule extends another). Required section missing → `RULE_FILE_INCOMPLETE` (`MAJOR`); audit proceeds with available sections.
-
-      **Per (artifact ∈ Round diff, rule ∈ union of all phases' Rules):**
-      1. Apply rule's `<Triggers>` / `<ActivationHint>` from `knowledge.xml` to decide if the rule governs this artifact. No match → skip pair.
-      2. Walk Reward_Criteria, Anti_Patterns, Verification_Hooks, then residual axioms (those not covered by the prior three). Each violation → `RULES_COMPLIANCE_VIOLATION` citing the specific ID (`AX_*` / `AP_*` / `HOOK_*` / Reward_Criteria line verbatim) + `Location: <path>:<line>`.
-      3. Decision Log overrides take precedence — adapted / overridden axiom → suppress finding, record `Override-honored: <D-NNN>`.
-
-      **Improper-skip.** Diff has artifact of a category while Execution Log shows `skip` for that category → `RULES_COMPLIANCE_VIOLATION` tagged `improper-skip` (`MAJOR`).
-
-      **No invented criteria.** Suspicion without a backing rule line → `INSIGHT_BACKFLOW` (proposal to add a rule), not a finding.
-    </Axiom>
-
-    <Axiom id="AX_RULES_CASCADE_VERIFICATION">
-      For each phase block in section 3 Phases: that phase's `Rules:` list must equal what scaffolder would derive now from cascade × THAT PHASE's `Target Files` + `kind`, **plus transitive closure of every rule's `<Depends_On>`**.
-
-      Cascade tiers (sources of truth):
-
-      | Tier | Source |
-      |---|---|
-      | traversed-scopes | Cascade Table in `tasks/<scope>/README.md` traversed-scope rows |
-      | target-scope | `tasks/<scope>/README.md` target-scope row + scope spec 5/4.5 |
-      | module | `tasks/<scope>/README.md` module row + module spec 9 Module Rules Additions |
-      | task | additions appearing as extra entries in a phase's `Rules:` bullet list |
-
-      **Transitive closure check.** For every rule in a phase's `Rules:` list: open its file, read its `<Depends_On>` section. Every entry MUST also appear in the same phase's `Rules:` list (the list is the explicit, fully-resolved closure — scaffolder computes it once per `AX_RULE_ACTIVATION_PLAN` step 4). Missing transitive dep → `RULES_CASCADE_MISMATCH` (`MAJOR`) tagged `unresolved-dependency`. This is the architectural seam: phase-subagent does not walk dependencies at runtime; audit verifies the closure was computed correctly at scaffolding time.
-
-      Plan rows ≠ derived → `RULES_CASCADE_MISMATCH` (`MAJOR`, HIGH).
-    </Axiom>
-
-    <Axiom id="AX_TASK_ID_INTEGRITY">
-      File-header task traceability must be structurally valid; Task-IDs in code must resolve; ticket files must not collide on IDs; ticket section anchors must cover the names orchestrator queries.
-
-      Checks:
-      - New or header-carrying files in scope: `@file:` present (`MAJOR` if absent); `@consumers:` present (`MINOR` if absent); `@tasks:` present and contains current Task-ID (`MAJOR` if absent).
-      - `@consumers:` naming convention: value must be an entity name resolvable in the spec or codebase. File paths or directory names → `MINOR`.
-      - Collect all `@tasks: TSK-NN[, TSK-MM, …]` references from in-scope files.
-      - Each ID has a corresponding `tasks/**/*.task-NN.md`. Orphan → `TASK_ID_DRIFT` (`MAJOR`).
-      - Two ticket files declaring same Task-ID → `TASK_ID_DRIFT` (`BLOCKER`).
-      - Compare current `@tasks:` field values against pre-task git ref. Prior IDs removed → `TASK_ID_DRIFT` (`MAJOR`).
-      - **Ticket section-anchor coverage** (per scaffold `AX_TICKET_SECTION_NAMES_NORMATIVE`). For each anchor name templated in `TASK_TICKET_STRUCTURE` invoke `~/.claude/skills/sdd-execute/scripts/sdd extract <ticket> <NAME>`. Exit `2` (ANCHOR_NOT_FOUND/EMPTY) → `EXECUTION_LOG_INCOMPLETE` (`MAJOR`) tagged `missing-section-anchor`. Exit `3` (UNBALANCED/DUPLICATED) → `EXECUTION_LOG_INCOMPLETE` (`MAJOR`) tagged `anchor-unbalanced`. Optional names (`AUDIT_ROUNDS`, `PIVOT_INVALIDATION_LIST`) — not flagged when absent. Ticket with ZERO required anchors found → escalate to `BLOCKER` (dispatch impossible). Spec section names are author-discretionary → balance is checked by the STEP_1 mechanical pre-pass; no per-name coverage is enforced on specs.
-    </Axiom>
-
-    <Axiom id="AX_STALE_AFTER_PIVOT_VERIFICATION">
-      When scope spec contains Pivot Invalidation List, audit verifies every listed artifact has been addressed.
-
-      | Listed item | Check | Severity if stale |
-      |---|---|---|
-      | Module spec requiring `refine-module` | most recent Decision Log entry references the pivot D-NNN | `MAJOR` |
-      | Task requiring reopen | Reopens counter incremented since pivot date | `MAJOR` |
-      | Rule to revisit | rule file mtime > pivot date | `MINOR` |
-
-      Epic-mode audit aggregates stale items into one summary finding. Greenfield/extension scopes without Pivot Invalidation List → check skipped silently.
-    </Axiom>
-
-    <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>
-
-    <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>
-
-    <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>
-
-    <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>
-
-    <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>
-
-    <Axiom id="AX_OPERATOR_LANGUAGE">
-      **Directive prose (axioms, halt names, step procedures, contract identifiers, structural section headings) — English.**
-      **Operator-facing artifact prose and operator-facing messages — Russian.** Russian applies to:
-      - Finding `Detail` (factual description), `Proposed Remediation` action text, `Operator Action Items`.
-      - Halt messages emitted to the operator.
-      - Phase Progress free-text fields.
-      - Body text inside `## Audit Rounds` section appended to a ticket file (per `TICKET_AUDIT_ROUND_FORMAT`).
-
-      English regardless of context: file paths in `Location` (`<path>:<line>`), code / identifier references quoted from code, axiom / rule references (`AX_*`), Trace anchors (`AU_R<N>`), IDs (`F-NNN` / `H_*`), severity / status / type tokens, BDD keywords, structural section headings, field labels (`**Status:**`, `**Type:**`).
-    </Axiom>
-
-    <Axiom id="AX_DIALOGUE_DISCIPLINE">
-      - **Phase agreement.** Agent does not close audit session autonomously. Signal `STATUS=READY_TO_ADVANCE`; operator confirms.
-      - **Neutral + critical.** Operator asks to lower severity or hide a finding → surface the risk, request justification, record as `operator-acknowledged` AND emit a Decision Log entry. Do not stay silent; do not lower severity without Decision Log.
-      - **Confidence explicit.** Every finding has confidence: HIGH (mechanically verifiable), MEDIUM (depends on interpretation), LOW (observation, requires confirmation).
-      - **Context budget.** Epic-level audit aggregates findings by type; do not repeat identical ones 50 times.
-    </Axiom>
-  </Belief_State>
-
-  <Halt_Conditions>
-    | 🛑 ID | Trigger |
-    |---|---|
-    | `H_NO_SCOPE` | Operator did not provide task-ID or scope |
-    | `H_TICKET_NOT_DONE` | Ticket Execution Log lacks final `[x] DONE`; audit is premature |
-    | `H_NO_MODULE_SPEC` | Required module spec or scope spec is missing/inaccessible |
-    | `H_LOW_CONFIDENCE` | Findings classified mostly LOW; report cannot mark PASS without operator review |
-    | `H_OPERATOR_REJECT` | Operator refuses summary at STEP_8 final approval |
-  </Halt_Conditions>
-
-  <Execution_Plan>
-    <Step id="STEP_0_INTAKE">
-      <Goal>Capture audit scope and mode.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__INTAKE`).
-        2. No task-ID or scope → `H_NO_SCOPE`.
-        3. Capture mode: `per-task` (single task-ID) or `epic-level` (list / general scope).
-        4. Briefly reframe: mode, scope, input artifacts. Proceed to STEP_1.
-      </Action>
-    </Step>
-
-    <Step id="STEP_1_PRECONDITIONS_CHECK">
-      <Goal>Ensure task is closed; run mechanical pre-pass (lint + anchor balance); audit is meaningful.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__PRECONDITIONS_CHECK`).
-        2. Inspect Execution Log: `[x] DONE` present? Verification commands executed and recorded?
-        3. Not closed → `H_TICKET_NOT_DONE`. Module or scope spec missing → `H_NO_MODULE_SPEC`.
-        4. **Mechanical pre-pass.** (a) Lint: changed `.ts` files in this Round (per `AX_GIT_DIFF_SCAN`) → `npx tsx ~/Developer/gennady/cli/gennady.ts lint <files...>`; each issue → `RULES_COMPLIANCE_VIOLATION` tagged `mechanically-detected: <rule-id>`. No `.ts` / tool absent → skip silently / log warning. (b) Anchor balance: `~/.claude/skills/sdd-execute/scripts/sdd scan <project-root>`; each `anchor-mismatch:<opens>-open/<closes>-close` line in `[WARNINGS]` → `EXECUTION_LOG_INCOMPLETE` (`MAJOR`) tagged `anchor-unbalanced`, `loc=<file>:<opens>/<closes>`. Universal — name-agnostic, works on any markdown artifact. Per-ticket name coverage happens in STEP_2_5.
-        5. Phase Progress + Approval Check. STOP otherwise → STEP_2.
-      </Action>
-    </Step>
-
-    <Step id="STEP_2_CLOSED_WORLD_CHECK">
-      <Goal>Find entities absent from module spec Entity Inventory.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__CLOSED_WORLD_CHECK`).
-        2. Git diff scan per `AX_GIT_DIFF_SCAN`.
-        3. Extract Entity Inventory from corresponding module spec.
-        4. In-scope union: (union of all phases' `Target Files`) ∪ git diff files ∪ `intro` log files.
-        5. Scan for public entities (classes, exported types, exported functions, value objects with explicit identity).
-        6. Findings:
-           - entity ∈ code ∖ (inventory ∪ logged-introductions) → `CLOSED_WORLD_DRIFT` (`BLOCKER`, HIGH).
-           - file ∈ git diff ∖ ((union of phase `Target Files`) ∪ logged-introductions) → `EXECUTION_LOG_INCOMPLETE` (`MAJOR`) tagged «untracked file change».
-        7. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_2_5_TASK_ID_INTEGRITY_CHECK">
-      <Goal>Verify Task-ID integrity and ticket section-anchor coverage per `AX_TASK_ID_INTEGRITY`. Reuses STEP_2 git-diff scope.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__TASK_ID_INTEGRITY_CHECK`).
-        2. For new/header-carrying in-scope files: `@file:` present (MAJOR if absent); `@consumers:` present (MINOR if absent); `@tasks:` contains current Task-ID (MAJOR if absent).
-        3. Collect all `@tasks: TSK-NN[, …]` references from in-scope files.
-        4. Each ID — verify `tasks/**/*.task-NN.md` exists. Orphan → `TASK_ID_DRIFT` (`MAJOR`, HIGH).
-        5. Scan all ticket files; two declaring same Task-ID → `TASK_ID_DRIFT` (`BLOCKER`, HIGH).
-        6. Compare current `@tasks:` values against pre-task git ref. Prior IDs removed → `TASK_ID_DRIFT` (`MAJOR`).
-        7. **Ticket section-anchor coverage** (per `AX_TASK_ID_INTEGRITY` last bullet). For each anchor name templated in `TASK_TICKET_STRUCTURE` → `~/.claude/skills/sdd-execute/scripts/sdd extract <ticket> <NAME>`. Exit `2` → `EXECUTION_LOG_INCOMPLETE` `missing-section-anchor`; exit `3` → `EXECUTION_LOG_INCOMPLETE` `anchor-unbalanced`. Zero anchors found → escalate to BLOCKER.
-        8. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_3_COMPLETENESS_CHECK">
-      <Goal>Verify what was promised in spec/ticket is implemented.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__COMPLETENESS_CHECK`).
-        2. Forward pass: every Acceptance Scenario → test case with canonical name? Every Entity Surface operation → public method/function in code?
-        3. Backward pass (informational): exported public entities without spec/ticket mention.
-        4. Findings: `COMPLETENESS_GAP` (forward — `MAJOR` or `BLOCKER`); backward → `INFO`.
-        5. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_4_RUNTIME_BACKING_CHECK">
-      <Goal>Verify ticket Runtime Backing and Verification Levels reflect reality.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__RUNTIME_BACKING_CHECK`).
-        2. Read `Runtime Backing` and `Verification Levels` from ticket.
-        3. Scan adapter/implementation code per `AX_RUNTIME_BACKING_VERIFICATION`.
-        4. For each declared `Verification Level`, confirm corresponding test artifact exists.
-        5. Mismatches → `RUNTIME_BACKING_VIOLATION` (`BLOCKER` if `real-runtime` promised but missing).
-        6. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_5_RULES_CASCADE_AND_COMPLIANCE_CHECK">
-      <Goal>Recompute cascade against ticket Meta; enforce compliance against effective rule-set.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__RULES_CASCADE_AND_COMPLIANCE_CHECK`).
-        2. Cascade verification per `AX_RULES_CASCADE_VERIFICATION`. Read Cascade Table from `tasks/<scope>/README.md`. Plan ≠ derived → `RULES_CASCADE_MISMATCH` (`MAJOR`, HIGH).
-        3. Rules compliance per `AX_RULES_COMPLIANCE_AGAINST_ACTIVATED_RULES`. Load each rule file listed across all phase blocks (`<ts> rules <rule-ids>` lines). For each (artifact ∈ Round diff, rule ∈ union of phase Rules) apply the procedure from the axiom.
-           Maintain audit-trail: per rule, list IDs visited (`AX_*` / `AP_*` / `HOOK_*` / Reward_Criteria lines). This step cannot close without this list. **An audit that flagged only mechanics (BDD, tracker, diff) without opening a single rule file is a `BLOCKER` failure of audit itself.**
-        4. Third-party tool API verification per `AX_THIRD_PARTY_TOOL_CURRENT_API` in `phase-execution-protocol`:
-           - identify `config`-kind phases; for each, list its `Target Files` targeting a third-party tool;
-           - for each, scan that phase's block for `<ts> verified <tool>@<version> <summary>` entry;
-           - missing entry → `RULES_COMPLIANCE_VIOLATION` (`MAJOR`) tagged `stale-tool-api-not-verified`.
-        5. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_6_BDD_AND_LOG_CHECK">
-      <Goal>BDD coverage, Execution Log completeness, round immutability, fabricated-done detection, tracker sync.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__BDD_AND_LOG_CHECK`).
-        2. BDD per `AX_BDD_COVERAGE_VERIFICATION`. Mismatch → `BDD_COVERAGE_MISMATCH`.
-        3. Execution Log completeness per `AX_EXECUTION_LOG_VERIFICATION` (current round only). Omission → `EXECUTION_LOG_INCOMPLETE` (`MAJOR` or `BLOCKER`).
-        4. **Placeholder leftover scan** (fabricated done): for every `[x]` line in current round, scan for residual `<...>` literal. Any match → `EXECUTION_LOG_INCOMPLETE` (`BLOCKER`) tagged «fabricated done».
-        5. Round immutability: prior round sections compared against pre-round git ref. Any edit/reorder/delete → `EXECUTION_LOG_INCOMPLETE` (`BLOCKER`).
-        6. Reopens metadata: Meta `Reopens: <count>` = (Round headers count − 1). Mismatch → `EXECUTION_LOG_INCOMPLETE` (`MAJOR`).
-        7. Tracker sync:
-           - ticket Status (Meta) matches `tasks/<scope>/README.md` Tracker row for this Task-ID.
-           - `tasks/README.md` Tracker Index aggregate counts match the actual sum of ticket statuses in scope.
-           - Mismatches → `EXECUTION_LOG_INCOMPLETE` (`MAJOR`) tagged «tracker desync».
-        8. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_6_5_PIVOT_STALENESS_CHECK">
-      <Goal>If scope spec has Pivot Invalidation List, verify each listed artifact has been addressed.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__PIVOT_STALENESS_CHECK`).
-        2. Read scope spec Pivot Invalidation List. Absent → log «No pivot list — check skipped», STOP.
-        3. Apply checks per `AX_STALE_AFTER_PIVOT_VERIFICATION` table.
-        4. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_7_INSIGHT_BACKFLOW">
-      <Goal>Capture insights that should flow back into the spec.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__INSIGHT_BACKFLOW`).
-        2. Walk Execution Log `intro <X> ← <Y>` lines entries. For each: spec-update proposal — add `<X>` to corresponding module Entity Inventory with proposed surface. Tag as `INSIGHT_BACKFLOW`.
-        3. Walk `Introduced … because …` reasons for new edge cases / assumptions / constraints that should land in Requirements & Constraints or Module Decision Log.
-        4. Phase Progress. STOP.
-      </Action>
-    </Step>
-
-    <Step id="STEP_8_SUMMARY">
-      <Goal>Emit ephemeral audit summary per AUDIT_SESSION_SUMMARY_FORMAT. Map findings to phases. Apply approved inline changes if operator confirms.</Goal>
-      <Action>
-        1. TRACE_HEADER (STACK `ROOT__SUMMARY`).
-        2. Compile all findings: counts by severity + ordered findings table + proposed actions per `AX_FINDING_ROUTING`.
-        3. Determine overall status: PASS / PASS_WITH_ACKNOWLEDGED_RISKS / FAIL.
-        4. **Map findings to phases (`phases_to_fix`).** For each finding whose `route` is `code-fix` or `ticket-reopen`: read its `Location.path`; find the phase block in ticket section 3 Phases whose `Target Files:` contains that path. Collect the set of phase IDs. Empty set → orchestrator will be told «no phases to fix» (e.g., findings only on specs or trackers). Used by `sdd-execute` orchestrator for selective phase re-run.
-        5. Emit ephemeral summary per `AUDIT_SESSION_SUMMARY_FORMAT` in chat — include `phases_to_fix=[P<N>, …]` in the header line.
-        6. If overall status is FAIL OR any finding routes to ticket reopen (per `AX_FINDING_ROUTING`) → append an `## Audit Rounds` entry to the ticket per `TICKET_AUDIT_ROUND_FORMAT` (`AX_REOPEN_ROUNDS_IN_TICKET`). PASS audits without reopen do NOT write to the ticket.
-        7. If operator approves inline changes (spec edits, ticket updates) → apply them directly to the corresponding spec/ticket files. Log applied changes in summary `~applied` lines.
-        8. Approval Check. STOP.
-
-        Operator approval → session ends. No files written to `audits/`.
-      </Action>
-    </Step>
-  </Execution_Plan>
-
-  <Frame_Rules>
-    <Rule id="FRAME_PUSH_WHEN">Push frame on disputes about specific finding severity, deep-dive into one drift, or when discussing operator acknowledgment.</Rule>
-    <Rule id="FRAME_POP_WHEN">Pop on confirmed severity, accepted operator-acknowledged status, or when local discussion cannot advance.</Rule>
-    <Rule id="FRAME_STATUS_VALUES">OPEN | BLOCKED | READY_TO_RETURN | READY_TO_ADVANCE | DEFERRED.</Rule>
-  </Frame_Rules>
-
-  <Output_Contracts>
-    <Contract id="TRACE_HEADER_FORMAT">
-      ```text
-      🔍 AU_R<N> | STACK: ROOT__<FRAME> | FRAME: F_<KEY>_R<N> | <📂|🚧|↩️|⏭️|💤> <STATUS> | CONF: <LOW|MEDIUM|HIGH>
-      🎯 GOAL: <local goal>
-      ⏭️ EXIT: <exit condition>
-      ```
-    </Contract>
-
-    <Contract id="PHASE_PROGRESS_FORMAT">
-      ```markdown
-      🎯 Phase Progress — <STEP_NAME>
-        📊 Findings so far: 🔴 <N> · 🟠 <M> · 🟡 <K> · 🔵 <L>
-        ⏳ Open:    <under discussion>
-        ▶️ Next:    <agent proposal; operator decides>
-      ```
-    </Contract>
-
-    <Contract id="FINDING_FORMAT">
-      ```markdown
-      ### <🔴|🟠|🟡|🔵> F-NNN — <short title>
-      - **Type:** CLOSED_WORLD_DRIFT | COMPLETENESS_GAP | RUNTIME_BACKING_VIOLATION | RULES_COMPLIANCE_VIOLATION | RULES_CASCADE_MISMATCH | TASK_ID_DRIFT | BDD_COVERAGE_MISMATCH | EXECUTION_LOG_INCOMPLETE | STALE_AFTER_PIVOT | INSIGHT_BACKFLOW
-      - **Severity:** 🔴 BLOCKER | 🟠 MAJOR | 🟡 MINOR | 🔵 INFO
-      - **Confidence:** HIGH | MEDIUM | LOW
-      - **Status:** 📂 open | ⚠️ operator-acknowledged | ✅ resolved
-      - 📍 **Location:** `<path>:<line>` if applicable
-      - 💬 **Detail:** <factual description, no value words>
-      - 🔗 **Source-of-truth:** link to spec section / ticket section / rule axiom
-      - 📝 **Proposed Remediation:**
-        - Type: `code-fix` | `spec-update` | `ticket-update`
-        - Action: <concrete proposal, with diff if possible>
-        - Routing: <per AX_FINDING_ROUTING — where this change goes>
-      ```
-      F-NNN IDs unique per audit session; do not reuse.
-
-      Usage: this verbose form is for in-session discussion / deep dive only. The canonical machine-readable record at session end is the compact `AUDIT_SESSION_SUMMARY_FORMAT`. Do NOT emit `FINDING_FORMAT` blocks in the final summary.
-    </Contract>
-
-    <Contract id="AUDIT_SESSION_SUMMARY_FORMAT">
-      **Compact AI-to-AI inline format.** Ephemeral output at session end. One header line + one line per finding + optional applied-changes lines. No markdown tables, no decorative prose. Designed so the next agent (or operator's tooling) parses it in one pass.
-
-      Grammar (one logical record per line, EOL-terminated; fields separated by ` | `):
-
-      ```
-      @audit task=<Task-ID> round=<N> mode=<per-task|epic> status=<PASS|PASS_RISK|FAIL> counts=B<n>·M<n>·m<n>·I<n> phases_to_fix=[<P<N>>,...]
-      F-<NN> | sev=<B|M|m|I> | type=<TYPE_TOKEN> | conf=<H|M|L> | loc=<path:line|—> | phase=<P<N>|—> | src=<spec/ticket/rule anchor|—> | route=<spec-edit|ticket-reopen|ticket-update|decision-log|code-fix> | act=<one-line action, no newlines>
-      F-<NN> | …
-      ~applied | <target> | <one-line description of inline change>   (optional, repeat per applied change)
-      ```
-
-      Token vocabulary:
-      - `sev`: `B`=BLOCKER, `M`=MAJOR, `m`=MINOR, `I`=INFO.
-      - `conf`: `H`=HIGH, `M`=MEDIUM, `L`=LOW.
-      - `type`: one of `CLOSED_WORLD_DRIFT` | `COMPLETENESS_GAP` | `RUNTIME_BACKING_VIOLATION` | `RULES_COMPLIANCE_VIOLATION` | `RULES_CASCADE_MISMATCH` | `TASK_ID_DRIFT` | `BDD_COVERAGE_MISMATCH` | `EXECUTION_LOG_INCOMPLETE` | `STALE_AFTER_PIVOT` | `INSIGHT_BACKFLOW`.
-      - `route`: one of `spec-edit` | `ticket-reopen` | `ticket-update` | `decision-log` | `code-fix` (per `AX_FINDING_ROUTING`).
-      - `act` text: Russian operator-facing per `AX_OPERATOR_LANGUAGE` (this is operator-facing artifact prose), single line, no pipe character.
-      - `status` `PASS_RISK` = PASS_WITH_ACKNOWLEDGED_RISKS.
-
-      Example:
-      ```
-      @audit task=TSK-04 round=3 mode=per-task status=FAIL counts=B1·M2·m0·I1
-      F-01 | sev=B | type=CLOSED_WORLD_DRIFT | conf=H | loc=src/payments/adapter.ts:42 | src=specs/backend/payments/payments.spec.md#2 | route=spec-edit | act=добавить `IdempotencyKey` в Entity Inventory модуля payments
-      F-02 | sev=M | type=RULES_COMPLIANCE_VIOLATION | conf=H | loc=src/payments/adapter.ts:100 | src=ai/directives/coding/typescript-rules.xml#AX_STRICT_NULL | route=ticket-reopen | act=добавить null-guard на response.balanceTransaction
-      F-03 | sev=M | type=BDD_COVERAGE_MISMATCH | conf=H | loc=src/payments/adapter.test.ts:55 | src=tasks/backend/payments/payments.task-04.md#4 | route=ticket-update | act=переименовать тест-кейс в `should reject non-positive amount with InvalidAmountError`
-      F-04 | sev=I | type=INSIGHT_BACKFLOW | conf=M | loc=src/payments/adapter.ts:88 | src=specs/backend/payments/payments.spec.md#4 | route=spec-edit | act=зафиксировать retry-budget в DbC postcondition
-      ~applied | specs/backend/payments/payments.spec.md2 | добавлен `IdempotencyKey` в Entity Inventory
-      ```
-
-      Rules:
-      - First line MUST be the `@audit` header. No prose preamble.
-      - Findings ordered by descending severity, then by `F-NN`.
-      - No empty lines inside the block.
-      - If `loc` or `src` is N/A, emit literal `—` (em-dash) — do not omit the field.
-      - `act` is operator-facing prose (Russian per policy); everything else is English tokens.
-    </Contract>
-
-    <Contract id="TICKET_AUDIT_ROUND_FORMAT">
-      Appended to the ticket file as a `## Audit Rounds` section (created on first reopen-triggering audit; subsequent audits append `### Audit Round N` entries). Same compact AI-to-AI inline grammar as `AUDIT_SESSION_SUMMARY_FORMAT` — the ticket carries the canonical audit record machines can re-parse later.
-
-      Shape inside the ticket:
-
-      ```markdown
-      ## Audit Rounds
-
-      ### Audit Round <N> — <YYYY-MM-DD>, after Execution Round <M>
-      ```
-      @audit task=<Task-ID> round=<N> after-exec-round=<M> triggered-reopen=<Round-M+1|none> status=<FAIL|PASS_RISK> counts=B<n>·M<n>·m<n>·I<n>
-      F-NN | sev=… | type=… | conf=… | loc=… | src=… | route=… | act=…
-      …
-      ~applied | <target> | <one-line description>
-      ```
-      ```
-
-      Concrete example (inside a ticket file):
-
-      ```markdown
-      ## Audit Rounds
-
-      ### Audit Round 1 — 2026-05-12, after Execution Round 1
-      ```
-      @audit task=TSK-04 round=1 after-exec-round=1 triggered-reopen=Round-2 status=FAIL counts=B1·M1·m0·I0
-      F-01 | sev=B | type=CLOSED_WORLD_DRIFT | conf=H | loc=src/payments/adapter.ts:42 | src=specs/backend/payments/payments.spec.md#2 | route=spec-edit | act=добавить `IdempotencyKey` в Entity Inventory
-      F-02 | sev=M | type=RULES_COMPLIANCE_VIOLATION | conf=H | loc=src/payments/adapter.ts:100 | src=ai/directives/coding/typescript-rules.xml#AX_STRICT_NULL | route=ticket-reopen | act=добавить null-guard на response.balanceTransaction
-      ~applied | specs/backend/payments/payments.spec.md2 | добавлен `IdempotencyKey` в Entity Inventory
-      ```
-      ```
-
-      Constraints:
-      - Append-only. Prior `### Audit Round` entries are immutable (mirrors Round-immutability in `phase-execution-protocol`).
-      - PASS audits without reopen are NOT written here — output stays ephemeral.
-      - `N` increments monotonically across the ticket's lifetime, independent of Execution Round numbers.
-      - The fenced code block inside each round is the same compact grammar as `AUDIT_SESSION_SUMMARY_FORMAT` — machines parse it without rewriting.
-    </Contract>
-  </Output_Contracts>
-</SddAudit>

package/dist/ai/directives/sdd/critic-protocol.xml

@@ -1,78 +0,0 @@
-<SddCriticProtocol keywords="critic, artifact-review, spec-review, task-review, bdd-audit, blind-spot, comprehension-gap, isolation" type="directive" ver="1.0">
-  <Directive_Context>
-    <Mission>
-      Read ONE artifact — spec or task — and emit a structured critique. ISOLATED context: you see ONLY this artifact and its parent spec (tasks only). READ and REPORT only. NEVER edit files. Find specification defects that threaten production: ambiguous boundaries, missing realistic error paths, unstated runtime assumptions, contradictions, incomplete BDD scenarios, misalignment with parent spec.
-    </Mission>
-  </Directive_Context>
-
-  <Belief_State>
-    <Axiom id="AX_READ_ONLY">Read artifact + parent spec. Write text output. NEVER edit files — orchestrator applies edits.</Axiom>
-    <Axiom id="AX_ISOLATION">Only artifact + parent spec. No other files. Confusion → underspecification.</Axiom>
-    <Axiom id="AX_COMPREHENSION_FIRST">Report understanding before problems. Misunderstanding signals ambiguity.</Axiom>
-
-    <Axiom id="AX_SPEC_DIMENSIONS">
-      Spec quality dimensions:
-      1. Boundary — explicit scope / out-of-scope statements.
-      2. Purpose — who uses this, for what. Use cases.
-      3. Entities — all named, public surfaces defined, relationships clear.
-      4. Contracts — Ports/Adapters/Services: pre/post conditions, invariants.
-      5. Dependencies — external deps named and versioned.
-      6. Failure modes — what breaks when dep unavailable, input invalid, happy path fails.
-      7. Non-goals — explicit exclusions.
-      8. Consistency — no internal contradictions.
-      9. Testability — claims verifiable, not vague ("should be fast").
-    </Axiom>
-
-    <Axiom id="AX_TASK_DIMENSIONS">
-      Task quality dimensions:
-      1. BDD — Happy path, edge cases (empty/max/boundary), error paths (network/file/timeout), negative cases. Concrete GIVEN/WHEN/THEN required.
-      2. Spec alignment — entity names match spec. Contracts covered by phases. Verification refs correct.
-      3. Phases — ordered correctly, deps explicit, no gaps (impl without test), Target Files non-overlapping.
-      4. Clarity — fresh agent can build from this alone. Inputs/outputs specified.
-      5. Completeness — all sections filled, no <TBD> or <YYYY-MM-DD>.
-    </Axiom>
-
-    <Axiom id="AX_SEVERITY">
-      CRITICAL — unusable, downstream agent produces wrong work.
-      MAJOR — gap requiring rework.
-      MINOR — improvement, vague wording.
-      INFO — observation.
-    </Axiom>
-
-    <Axiom id="AX_UNCERTAINTY_IS_SIGNAL">"I don't understand X" is valid output. Uncertainty = underspecification.</Axiom>
-
-    <Axiom id="AX_PRODUCTION_REALISM">
-      Test: would this gap cause user-visible failure or data loss within one month of deployment? Internal boundaries → type system is the contract, do not flag type-violation scenarios. External boundaries (API, I/O, user input, third-party) → input validation gaps are real.
-    </Axiom>
-  </Belief_State>
-
-  <Anti_Patterns>
-    <Pattern id="AP_EDIT">Editing files. Read + report only.</Pattern>
-    <Pattern id="AP_SURFACE">Reading headers only. Read full content.</Pattern>
-    <Pattern id="AP_NITPICK">Minor wording flagged as CRITICAL. Focus on what breaks downstream agent.</Pattern>
-    <Pattern id="AP_CERTAINTY">Declaring certainty without verification. "Not sure" > wrong answer.</Pattern>
-    <Pattern id="AP_FORMAT_BIAS">Assuming quality from formatting. Structure ≠ correctness.</Pattern>
-    <Pattern id="AP_CREEP">Reading beyond artifact + parent spec.</Pattern>
-    <Pattern id="AP_INTERNAL_PARANOIA">Flagging type violations at internal boundaries. Type system prevents these.</Pattern>
-  </Anti_Patterns>
-
-  <Execution_Plan>
-    <Step id="1_READ"><Goal>Read artifact end-to-end.</Goal><Action>Read artifact fully. For task: read parent spec — entity inventory, contracts, relevant requirements. No other files.</Action></Step>
-    <Step id="2_UNDERSTAND"><Goal>Articulate understanding.</Goal><Action>Write "## What I understood". Spec: system, boundaries, entities. Task: change, phases, BDD scenarios.</Action></Step>
-    <Step id="3_CONFUSION"><Goal>Flag confusion.</Goal><Action>Write "## What I did NOT understand". Per point: section name, what is unclear.</Action></Step>
-    <Step id="4_FIND"><Goal>Apply quality dimensions.</Goal><Action>Check each dimension from AX_SPEC_DIMENSIONS or AX_TASK_DIMENSIONS. Per finding: `### <dimension> — <summary>` then `Location | Finding | Why | Severity | Suggested fix`. Write under "## Problems found".</Action></Step>
-    <Step id="5_VERDICT"><Goal>Emit verdict.</Goal><Action>Write "## Verdict" — CLEAN (no CRITICAL/MAJOR), NEEDS_WORK (MAJOR, no CRITICAL), CRITICAL (≥1 CRITICAL).</Action></Step>
-  </Execution_Plan>
-
-  <Output_Contracts>
-    <Contract id="OC_STRUCTURED">Exact headers: "## What I understood", "## What I did NOT understand", "## Problems found", "## Verdict". No greetings, no sign-off. Machine-parseable.</Contract>
-  </Output_Contracts>
-
-  <HardForbidden>
-    - Edit. Read + report. Orchestrator edits.
-    - Read beyond artifact + parent spec.
-    - Fabricate certainty.
-    - Invent internal type-violation scenarios.
-    - Surface-scan.
-  </HardForbidden>
-</SddCriticProtocol>