@azure-id/orc 0.56.1 → 1.1.0

package/templates/skills/orc/references/effort-and-mode.md

@@ -106,33 +106,31 @@ risk ≠ [] → floor 70 (DERIVED from a cited risk facet, never remembered).
 clamp 0..100 → the RESOLVED table (below).
 ```
 
-**Which table (highest wins):** `opus5_only: true` (the 3-band Opus-5-only
-preset: `[0,40)` low · `[40,80)` medium · `[80,100]` high) → `rubric_bands_override`
-(hand-written rows) → the default 8-band table. All three are in `config.md`.
+**Which table (highest wins):** `opus5_only: true` (the 2-band Opus-5-only
+preset: `[0,90)` low · `[90,100]` medium) → `rubric_bands_override`
+(hand-written rows) → the default 6-band table. All three are in `config.md`.
 The formula, the facets and the risk floor are IDENTICAL in every case — only
 the score→agent mapping changes. Three consequences worth stating so nobody
 re-derives them per run:
 
 - **The risk floor still applies** — it raises the SCORE, then the resolved table
-  maps it. Under the Opus-5-only preset a floored task lands `opus-5-med`, not
-  `opus-4-7-high`.
+  maps it. A floored task (≥70) lands `opus-5-low` in the default table and
+  `opus-5-low` under the Opus-5-only preset too: since v1.0.0 both tables answer
+  the floor with the same agent, and only a score of 90+ moves it to `opus-5-med`.
 - **`opus5_only` FORCES** — while on, a hand-written `rubric_bands_override` is
-  ignored, and so is the entire Fable 5 block. It is the one selector that can
-  shadow another; that is deliberate.
-- **`fable5_roles` never covers executors** (analyze/plan/advisor/judge/review
-  only), so those two features are orthogonal and cannot disagree on a band.
+  ignored. It is the one selector that can shadow another; that is deliberate.
 
 Show the user the full table (task, the facet vector, the arithmetic
 `B+N+L+T+fan+U = raw`, any risk floor, final, override+reason if any, dispatched
 model) BEFORE dispatching — an un-shown number is not a scored number. **Head it
-with the RESOLVED table's name** (`8-band default` / `Opus-5-only ladder
+with the RESOLVED table's name** (`6-band default` / `Opus-5-only ladder
 (opus5_only)` / `custom (rubric_bands_override)`): the same logic
 applies to the mapping as to the number.
 
 **Extra (v0.50.0, `extra_enabled`) adds a `via` column and can make the head a
 PAIR.** An Extra route row is an OVERLAY that outranks the tables above **only
 for the scores it covers**, so a run can genuinely be running two tables at once
-and the head names both (`8-band default + extra rows [0,30) [30,70)`). The
+and the head names both (`6-band default + extra rows [0,30) [30,70)`). The
 column reads `claude` or `extra:<profile> (<engine>)` and comes from
 `orc extra resolve --json` — the formula, the facets and the risk floor are
 untouched, and **the score is computed before the routing, never after it**. Two
@@ -158,7 +156,7 @@ fix in a risk area from silently dropping to a cheap model:
 
 - **Inherit the ORIGINAL task's `risk` facets** when the fix touches its files —
   a fix in a risk-floor area keeps the ≥70 floor (a userID/context-key fix can
-  never dispatch below `opus-4-7-high` again);
+  never dispatch below `opus-5-low` again);
 - a **P0/P1 fix never dispatches below the band of the task that produced the
   finding.**
 
@@ -178,8 +176,8 @@ the band is what matters. Compare a new task to these facet-by-facet.
 | Isolated component from the design system | 3·new-surface·branching·new-tests · 0/0 · low | 6+18+8+8 = **40** | sonnet-4-6-high [40,55) |
 | Notification model + enum other tasks consume | 3·new-surface·stateful·new-tests · 0/3 · low | 6+18+16+8+9 = **57** | sonnet-5-high [55,65) |
 | Service-layer refactor behind a stable interface | 5·imitate·stateful·update-existing · 0/3 · medium | 10+8+16+4+9+6 = **53** | sonnet-4-6-high [40,55) |
-| Add role check to payment-refund endpoint | 3·imitate·branching·new-tests · 0/0 · low · **risk=[auth,money]** | 30 raw → **floor 70** | opus-4-7-high [70,80) |
-| Migrate orders table to split-name + backfill | 6·new-surface·stateful·new-tests · 1/3 · high · **risk=[migration,data-integrity]** | 15+18+16+8+5+9+12 = 83 (floor 70) → **83** | opus-4-8-high [80,90) |
+| Add role check to payment-refund endpoint | 3·imitate·branching·new-tests · 0/0 · low · **risk=[auth,money]** | 30 raw → **floor 70** | opus-5-low [65,90) |
+| Migrate orders table to split-name + backfill | 6·new-surface·stateful·new-tests · 1/3 · high · **risk=[migration,data-integrity]** | 15+18+16+8+5+9+12 = 83 (floor 70) → **83** | opus-5-low [65,90) |
 
 Two disciplines the vectors encode: (1) a small diff is NOT a low score when a
 cited `risk` facet forces the floor (the refund row — 30 raw, floored to 70); (2)
@@ -190,16 +188,16 @@ applies it silently.
 ## Model ladder → the single score→model table
 
 The score→model mapping is NOT hardcoded here — it lives in `config.md` as ONE
-canonical 8-band table (there is no longer a narrow/wide preset). Read config at
+canonical 6-band table (there is no longer a narrow/wide preset). Read config at
 run start and map each task's final score through that table (or
 `rubric_bands_override`). The orchestrator dispatches the executor agent BY NAME;
 it does not request a raw model. `rubric_bands` sets only how many bands the
 rubric REPORTS (score granularity), never which table is used.
 
-The 8 bands (see config.md for the exact edges): `haiku-4-5` [0,30) ·
+The 6 bands (see config.md for the exact edges): `haiku-4-5` [0,30) ·
 `sonnet-4-6-med` [30,40) · `sonnet-4-6-high` [40,55) · `sonnet-5-high` [55,65) ·
-`opus-4-7-med` [65,70) · `opus-4-7-high` [70,80) · `opus-4-8-high` [80,90) ·
-`opus-5-high` [90,100]. Effort tiers rank `low < medium < high < xhigh < max`.
+`opus-5-low` [65,90) · `opus-5-med` [90,100]. Effort tiers rank
+`low < medium < high < xhigh < max`.
 
 ## Fixed model assignments (not scored)
 

package/templates/skills/orc/references/phases/intake.md

@@ -0,0 +1,47 @@
+# Phase — Intake   (id: `intake`)
+
+> **`/orc` phase file.** Moved out of `orc/SKILL.md` at v1.0.0 W12. The spine is
+> loaded IN FULL when the skill activates; this is loaded when the phase fires,
+> and most runs skip most phases. ONE consumer today, so it stays in this lane —
+> `../../../_shared/phases/README.md`'s rule: a file with one consumer stays home.
+> When a second lane reads it (W13 `orc-diy`, W14 `orc-mini`/`orc-fast`) it moves
+> to `_shared/phases/` and gains a `composed` or `trim` layer beside this one.
+> `orc lane phases orc --json` names the file and the layers.
+
+<!-- orc:layer full -->
+
+## Intake (load ../../../_shared/phases/intake.md)
+
+**Plan-input trigger (check FIRST — load `../../../_shared/phases/plan-handoff.md`):** if the
+run input IS a plan (pasted planning-output, a `plan-{name}.md` path, or an
+`orc/planner/{name}/` checkpoint), follow that reference: bootstrap the trace,
+schema-validate, apply the `plan_head` staleness valve, RE-RUN the full Phase 1
+exit gate here (the deterministic catch for phantom-file drift), relay
+`open_questions[]`, then continue at Phase 2. A plan input never skips Phase 2/3
+nor executes task-by-task ad hoc.
+
+**Analyst auto-trigger:** on a document (PDF path, pasted doc, audit sheet)
+OR an ambiguous/underspecified requirement, FIRST dispatch the System Analyst
+(doc-optional — with no doc the request itself is the source). Offer
+standard/deep (`config.default_analysis_depth` presets it; mention `orc
+config set default_analysis_depth deep`); deep → you dispatch the scouts. On
+return run the analyst-return gates (analyst-gates.md); on build, continue at
+Phase 1 with the Requirement Planner.
+
+Emit `PHASE intake start` FIRST, then create `run/{run-slug}/` (slug from the
+intent). Then: rough-size →
+question tier (2/4/6) → ONE batched question round → draft the intent-spec
+(`../../schemas/intent-spec.md`) → **repo cross-check** (intake Step 3.5:
+Glob/Grep-confirm everything the spec names, or tag `UNVERIFIED`; tags become
+ONE batched sign-off question; >3 tags → recommend `orc-analyze`) → sign-off
+preference (gate/soft; DEFAULT GATE) → show spec → approval or edits. **No
+planning until approved (gate mode) and no unresolved `UNVERIFIED` tags
+either way.** On approval, emit `PHASE intake end`.
+
+The intent-spec's definition-of-done becomes Phase 6's acceptance criteria;
+its constraints become hard rules in every slice — at slice-assembly each
+task's `spec_invariants[]` is appended VERBATIM to that slice's
+`constraints[]`. Offer the opt-in **Test Authoring** (Phase 6.5; default
+`config.generate_tests`) in the sign-off round.
+
+<!-- /orc:layer -->

package/templates/skills/orc/references/phases/integration.md

@@ -0,0 +1,19 @@
+# Phase — Integration (worktrees)   (id: `integration`)
+
+> **`/orc` phase file.** Moved out of `orc/SKILL.md` at v1.0.0 W12. The spine is
+> loaded IN FULL when the skill activates; this is loaded when the phase fires,
+> and most runs skip most phases. ONE consumer today, so it stays in this lane —
+> `../../../_shared/phases/README.md`'s rule: a file with one consumer stays home.
+> When a second lane reads it (W13 `orc-diy`, W14 `orc-mini`/`orc-fast`) it moves
+> to `_shared/phases/` and gains a `composed` or `trim` layer beside this one.
+> `orc lane phases orc --json` names the file and the layers.
+
+<!-- orc:layer full -->
+
+## Integration (worktrees only)
+
+Emit `PHASE integration start`. Merge worker branches; conflicts → resolver
+subagent (Opus 4.8 medium) given BOTH tasks' specs/intents, not just the diff.
+Record merge state in checkpoint; emit `PHASE integration end`.
+
+<!-- /orc:layer -->

package/templates/skills/orc/references/preflight-report.md

@@ -25,7 +25,7 @@ after:     src/payments — 2 shipped files rewritten within 30 days of run stor
 crosslink: 2 boundaries (payments-api) — advisory
 extra:     ON — 4 of 9 tasks foreign · deepseek/deepseek-v4-flash via api [0,30)
                 · glm/glm-4.7 via cli [30,70) · 2 held back (risk: auth, money)
-scoring:   8-band default table
+scoring:   6-band default table
 tdd:       3 tasks with tests (T3, T6, T9) · 2 covered-by-existing · 2 no-behavior
            skipped: R4 translation strings (no-behavior) · R7 file split
                     (covered-by-existing → test/api/health.test.js:41)
@@ -95,16 +95,16 @@ waves:     3 planned — will pause after wave 2 (batch_pause_every=2)
     `EXTRA orphan` line from `trace_extras[]` once you have reported it.
 
   Canonical: `../../_shared/extra-dispatch.md`.
-- **scoring:** which executor table RESOLVED for this run — `8-band default
+- **scoring:** which executor table RESOLVED for this run — `6-band default
   table` · `Opus-5-only ladder (opus5_only)` · `custom
   (rubric_bands_override, <n> rows)`. An un-shown table is as unaccountable as
   an un-shown number, and the Opus-5-only ladder in particular means EVERY
   dispatch needs an Opus 5 main session — the user should see that before the
   first dispatch, not in a trace full of downgrades. When `opus5_only` is on,
   append ` · all fixed roles forced to Opus 5` and name any selector it
-  shadowed (`rubric_bands_override` / `fable5_*` present but INERT) — a setting
+  shadowed (a `rubric_bands_override` present but INERT) — a setting
   the user tuned and the run then ignored has to be said out loud. With Extra in
-  play the table is a COMPOSITE and reads as one (`8-band default table + extra
+  play the table is a COMPOSITE and reads as one (`6-band default table + extra
   rows [0,30) [30,70)`) — Extra is an overlay, so naming only one of the two would
   be naming the wrong half for every covered score.
 - **tdd:** ALWAYS printed on a lane whose TDD policy is on — BOTH branches, not

package/templates/skills/orc/references/ultra-mode.md

@@ -1,123 +1,117 @@
-# Reference — Ultra Lane (load only when `ultra_mode: true`)
-
-`/orc-ultra` runs the FULL pipeline with maximum rigor for complex and
-ultra-complex requests. Everything in SKILL.md still applies; this file adds
-the ultra deltas. Ultra exists ONLY here — never in orc-mini, never on a plain
-`/orc` run.
-
-Cost stance: ultra is costly by definition. State it once at intake
-("ultra adds an Opus 5 xhigh advisor + up to 3 judge dispatches + revision
-loops"), then never prompt about cost again.
-
-## Forced overrides (run-scoped — NEVER written to the user's config file)
-
-Apply at Phase 0, on top of the normal config resolution:
-- analysis depth = **deep**, no ask (the analyst's standard/deep gate is
-  bypassed; `default_analysis_depth` is ignored; scouts dispatch as usual).
-- `pattern_findings` = on · `generate_tests` = on · `security_review` = on.
-- Executor **tier floor**: remap the resolved score→model table so no task
-  dispatches below `orc-executor-sonnet-5-high`; bands at/above the preset's
-  opus boundary rise to at least `orc-executor-opus-4-8-high` — the floor only
-  ever raises a band, so the top `[90,100]` band keeps `orc-executor-opus-5-high`.
-  **Under `opus5_only` the floor raises EFFORT, not model** (every band
-  is already Opus 5, so there is no model left to raise): the `[0,40)` band rises
-  low → medium, and the other two are already at/above it. It is still a floor —
-  it never lowers a band, and it never raises `[80,100]` past high.
-  Show the remapped table with the Phase 2 scoring table.
-
-> Opus-5-only mode: if `opus5_only`, every role this lane dispatches is already
-> Opus 5 (advisor and judge are pinned there by default) and the scouts rise to
-> `orc-scout-opus-5-low`. It FORCES — the Fable 5 note below does not apply
-> while it is on. See `../../_shared/opus5-only.md`.
-
-> Fable 5 role override: (INERT while `opus5_only`) if `fable5_enabled` and
-> `advisor` / `judge` are in `fable5_roles`, dispatch the `orc-advisor-fable-5` /
-> `orc-judge-fable-5` variant instead of the Opus 5 xhigh default — same slice,
-> same contract. See `../../_shared/fable5-override.md`.
-
-## Phase U0 — Advisor (after intake sign-off, before the analyst)
-
-Dispatch `orc-advisor-opus-5-xhigh` (see `../../orc-advisor/SKILL.md`) with
-the request, the run-folder path, and the detected stack. Validate the return
-(`brief_path`, `open_questions[]`, `assumptions[]`, actual model/effort
-fields). Then:
-
-1. Relay `open_questions[]` to the user in ONE batched round. Fold answers
-   into the intent-spec; unanswered questions fall back to the advisor's
-   proposed default and enter the ledger as UNCONFIRMED.
-2. Create `run/{run-slug}/ultra/assumption-ledger.md` from `assumptions[]`.
-   Every later phase appends: `assumption → confirmed-by-user |
-   confirmed-by-code-evidence (anchor) | UNCONFIRMED`. You alone write it
-   (workers return candidate entries; you record them).
-3. Inject the brief VERBATIM (never a pointer) into the analyst slice, the
-   planner slice, every judge slice, and — as advisory notes — every executor
-   slice. The rubric section is what the judges score against.
-
-The advisor runs once; it is never re-dispatched. Record `ADVISE` into the U0
-packet — ultra adds ONE writer packet for U0 and one per judge gate on top of
-orc's phase packets (`../references/trace-protocol.md`), so the advisory brief,
-the questions relayed, and each verdict round are narrated like any other phase.
-
-## The three judgment gates (dispatch `orc-judge-opus-5-xhigh`)
-
-Shared mechanics — verdict validation, blocking-finding downgrade enforcement,
-REVISE loops (author echo `finding_id → resolution`, re-judge convergence
-rule, hard cap 2 per gate), the ESCALATE menu, advisory carry-forward, verdict
-persistence (`run/{run-slug}/ultra/verdict-<gate>-<round>.md`), and the
-`JUDGE` / `GATE judgment` trace events (packet-carried) — live in
-`../../orc-judge/SKILL.md`.
-Load it at the first gate. Loop counters + the ultra artifact paths go in the
-checkpoint (`ultra` block) so a resumed run continues mid-loop.
-
-Judge slices ALWAYS carry: the advisor brief (with rubric), the original
-request, the assumption ledger, and gate-specific evidence below. Never the
-author's reasoning or self-assessment.
-
-- **Gate 1 (analysis)** — after the analyst-return deterministic gates pass
-  (evidence spot-check + derivation lint) and the user's challenge round is
-  resolved. Slice adds: report + spec paths. REVISE → bounce to the analyst.
-  Gate approval does NOT replace the user's take-into-build choice.
-- **Gate 2 (plan)** — after the Phase 1 exit gate passes. FIRST build the
-  **blast-radius map** (deterministic, yours): for each task's declared
-  files, Grep the importers/callers of the symbols it touches; list any
-  caller file no task covers. Slice adds: planning-output + the map. REVISE →
-  bounce to the planner. Gate approval does not replace plan sign-off.
-- **Gate 3 (implementation)** — after Phase 6 (and 6.5). FIRST build two
-  deterministic inputs:
-  1. **Traceability matrix** (`run/{run-slug}/ultra/traceability-matrix.md`):
-     `R# → task → declared files → actual diff hunks (git diff) → verify
-     evidence`. An R# with an EMPTY diff column is a deterministically caught
-     missing implementation — dispatch the fix wave directly, no judge needed
-     for that miss.
-  2. **Static analysis**: run the project's own tooling on the changed files
-     when the stack detection found any (linter, sonar-scanner,
-     type-checker) — never install tooling. Inject results into the slice;
-     tool findings on changed lines are blocking input the judge triages.
-  Slice adds: matrix, changed-file LIST (never an inlined diff — the judge
-  reads matrix-guided via its own Read/Grep), verify report, static-analysis
-  results, the resolved pattern's blocking invariants. REVISE → scored
-  executor **fix wave** for only the affected tasks (findings verbatim in
-  slices) → re-verify → re-judge. All clear → Phase 7.
-
-## Verdict contract cross-check (validate like any worker return)
-
-`verdict` ∈ APPROVE|REVISE|ESCALATE · every blocking finding has a verbatim
-anchor + class-appropriate justification (`failure_consequence` for
-correctness/security; named category + concrete alternative for
-smell/simplification/placement) · `rubric_items_checked[]` covers the gate's
-rubric lines · `unconfirmed_assumptions_touched[]` present. Malformed →
-requeue the judge once, then escalate. Security findings with a concrete
-consequence are always blocking. APPROVE with zero findings is legitimate.
-
-## Phase 6.7 / 7 / 8 deltas
-
-The mock-example phase (spine Phase 6.7, `../../_shared/drift-recovery.md`)
-runs in ultra too — AFTER Gate 3 approves (an example of an unapproved
-implementation would demo drift the judge already caught); same `mock_example`
-config, same never-committed rule, same 2-loop drift cap. A drift-recovery
-patch wave re-enters Gate 3 (a changed implementation is re-judged).
-
-The summary additionally reports: per-gate verdicts + rounds, findings by
-severity and class, auto-downgrades, the assumption ledger's final state
-(UNCONFIRMED entries highlighted), and the traceability matrix path. Ship is
-unchanged — but never offer commit while a gate is unresolved.
+# Reference — Ultra Lane (load only when `ultra_mode: true`)
+
+`/orc-ultra` runs the FULL pipeline with maximum rigor for complex and
+ultra-complex requests. Everything in SKILL.md still applies; this file adds
+the ultra deltas. Ultra exists ONLY here — never in orc-mini, never on a plain
+`/orc` run.
+
+Cost stance: ultra is costly by definition. State it once at intake
+("ultra adds an Opus 5 xhigh advisor + up to 3 judge dispatches + revision
+loops"), then never prompt about cost again.
+
+## Forced overrides (run-scoped — NEVER written to the user's config file)
+
+Apply at Phase 0, on top of the normal config resolution:
+- analysis depth = **deep**, no ask (the analyst's standard/deep gate is
+  bypassed; `default_analysis_depth` is ignored; scouts dispatch as usual).
+- `pattern_findings` = on · `generate_tests` = on · `security_review` = on.
+- Executor **tier floor**: remap the resolved score→model table so no task
+  dispatches below `orc-executor-sonnet-5-high`; bands at/above the opus
+  boundary (65) rise to at least `orc-executor-opus-5-low`. The floor only ever
+  raises a band, so the top `[90,100]` band keeps `orc-executor-opus-5-med`.
+  **Under `opus5_only` the floor raises EFFORT, not model** (every band is
+  already Opus 5, so there is no model left to raise): the `[0,90)` band rises
+  low → medium, which makes both bands medium. It is still a floor — it never
+  lowers a band, and it never raises `[90,100]` past medium.
+  Show the remapped table with the Phase 2 scoring table.
+
+> Opus-5-only mode: if `opus5_only`, every role this lane dispatches is already
+> Opus 5 (advisor and judge are pinned there by default) and the scouts rise to
+> `orc-scout-opus-5-low`. It FORCES. See `../../_shared/opus5-only.md`.
+
+## Phase U0 — Advisor (after intake sign-off, before the analyst)
+
+Dispatch `orc-advisor-opus-5-xhigh` (see `../../orc-advisor/SKILL.md`) with
+the request, the run-folder path, and the detected stack. Validate the return
+(`brief_path`, `open_questions[]`, `assumptions[]`, actual model/effort
+fields). Then:
+
+1. Relay `open_questions[]` to the user in ONE batched round. Fold answers
+   into the intent-spec; unanswered questions fall back to the advisor's
+   proposed default and enter the ledger as UNCONFIRMED.
+2. Create `run/{run-slug}/ultra/assumption-ledger.md` from `assumptions[]`.
+   Every later phase appends: `assumption → confirmed-by-user |
+   confirmed-by-code-evidence (anchor) | UNCONFIRMED`. You alone write it
+   (workers return candidate entries; you record them).
+3. Inject the brief VERBATIM (never a pointer) into the analyst slice, the
+   planner slice, every judge slice, and — as advisory notes — every executor
+   slice. The rubric section is what the judges score against.
+
+The advisor runs once; it is never re-dispatched. Record `ADVISE` into the U0
+packet — ultra adds ONE writer packet for U0 and one per judge gate on top of
+orc's phase packets (`../../_shared/phases/trace.md`), so the advisory brief,
+the questions relayed, and each verdict round are narrated like any other phase.
+
+## The three judgment gates (dispatch `orc-judge-opus-5-xhigh`)
+
+Shared mechanics — verdict validation, blocking-finding downgrade enforcement,
+REVISE loops (author echo `finding_id → resolution`, re-judge convergence
+rule, hard cap 2 per gate), the ESCALATE menu, advisory carry-forward, verdict
+persistence (`run/{run-slug}/ultra/verdict-<gate>-<round>.md`), and the
+`JUDGE` / `GATE judgment` trace events (packet-carried) — live in
+`../../orc-judge/SKILL.md`.
+Load it at the first gate. Loop counters + the ultra artifact paths go in the
+checkpoint (`ultra` block) so a resumed run continues mid-loop.
+
+Judge slices ALWAYS carry: the advisor brief (with rubric), the original
+request, the assumption ledger, and gate-specific evidence below. Never the
+author's reasoning or self-assessment.
+
+- **Gate 1 (analysis)** — after the analyst-return deterministic gates pass
+  (evidence spot-check + derivation lint) and the user's challenge round is
+  resolved. Slice adds: report + spec paths. REVISE → bounce to the analyst.
+  Gate approval does NOT replace the user's take-into-build choice.
+- **Gate 2 (plan)** — after the Phase 1 exit gate passes. FIRST build the
+  **blast-radius map** (deterministic, yours): for each task's declared
+  files, Grep the importers/callers of the symbols it touches; list any
+  caller file no task covers. Slice adds: planning-output + the map. REVISE →
+  bounce to the planner. Gate approval does not replace plan sign-off.
+- **Gate 3 (implementation)** — after Phase 6 (and 6.5). FIRST build two
+  deterministic inputs:
+  1. **Traceability matrix** (`run/{run-slug}/ultra/traceability-matrix.md`):
+     `R# → task → declared files → actual diff hunks (git diff) → verify
+     evidence`. An R# with an EMPTY diff column is a deterministically caught
+     missing implementation — dispatch the fix wave directly, no judge needed
+     for that miss.
+  2. **Static analysis**: run the project's own tooling on the changed files
+     when the stack detection found any (linter, sonar-scanner,
+     type-checker) — never install tooling. Inject results into the slice;
+     tool findings on changed lines are blocking input the judge triages.
+  Slice adds: matrix, changed-file LIST (never an inlined diff — the judge
+  reads matrix-guided via its own Read/Grep), verify report, static-analysis
+  results, the resolved pattern's blocking invariants. REVISE → scored
+  executor **fix wave** for only the affected tasks (findings verbatim in
+  slices) → re-verify → re-judge. All clear → Phase 7.
+
+## Verdict contract cross-check (validate like any worker return)
+
+`verdict` ∈ APPROVE|REVISE|ESCALATE · every blocking finding has a verbatim
+anchor + class-appropriate justification (`failure_consequence` for
+correctness/security; named category + concrete alternative for
+smell/simplification/placement) · `rubric_items_checked[]` covers the gate's
+rubric lines · `unconfirmed_assumptions_touched[]` present. Malformed →
+requeue the judge once, then escalate. Security findings with a concrete
+consequence are always blocking. APPROVE with zero findings is legitimate.
+
+## Phase 6.7 / 7 / 8 deltas
+
+The mock-example phase (spine Phase 6.7, `../../_shared/drift-recovery.md`)
+runs in ultra too — AFTER Gate 3 approves (an example of an unapproved
+implementation would demo drift the judge already caught); same `mock_example`
+config, same never-committed rule, same 2-loop drift cap. A drift-recovery
+patch wave re-enters Gate 3 (a changed implementation is re-judged).
+
+The summary additionally reports: per-gate verdicts + rounds, findings by
+severity and class, auto-downgrades, the assumption ledger's final state
+(UNCONFIRMED entries highlighted), and the traceability matrix path. Ship is
+unchanged — but never offer commit while a gate is unresolved.