@azure-id/orc 0.56.1 → 1.1.0

package/templates/skills/orc-claude/SKILL.md

@@ -1,199 +1,221 @@
----
-name: orc-claude
-description: >
-  CLAUDE.md builder/updater for the LOCAL project. Use for "/orc-claude",
-  "build a CLAUDE.md", "update the CLAUDE.md", or "refresh the CLAUDE.md".
-  Runs INDEPENDENTLY — no orchestrator, no run folder. Scans the repo for
-  ground-truth facts (verified commands, layout, conventions, boundaries) and
-  writes a section-fenced, version-stamped CLAUDE.md at the repo root — even
-  when ORC itself is installed globally. Never asks questions: P0 rules are a
-  template the user fills in themself. Refresh regenerates ONLY stale sections
-  and bumps the file version by 0.0.1. Never trims user-authored content;
-  never touches the orc-wiki pointer block. The skill dispatches the pinned
-  orc-claude-writer-opus-4-8-high agent — it never writes the file itself.
----
-
-# ORC-CLAUDE (standalone)
-
-Build or maintain the **local project's** `CLAUDE.md` from verified repo facts.
-The target is ALWAYS `<repo root>/CLAUDE.md` of the current working directory —
-never `~/.claude/CLAUDE.md`, even if ORC is installed globally.
-
-**Dispatch, don't do.** Whatever model this chat runs on, the skill itself only
-selects the mode and spawns `orc-claude-writer-opus-4-8-high` (the pinned
-engine) — so the scan + writing always run at Opus 4.8 high regardless of the
-caller's tier. When `opus5_only: true` the engine is
-`orc-claude-writer-opus-5-med` instead (that mode FORCES it — see
-`../_shared/opus5-only.md`), and it then needs an Opus 5 main session.
-The one exception: the skill also writes the
-trace pointer + a few markers around that spawn (behavior-trace logging is
-permanent; see "Behavior trace"); that
-tracing is its ONLY self-write — the `CLAUDE.md` write is always the writer's.
-**Fully non-interactive: ask the user NOTHING.** No AskUserQuestion, no
-confirmation prompts. Dispatch, relay the report, stop.
-
-**Worked example** (orient only — never execute from it):
-`examples/claude-run-mock.md`.
-
-## The three modes (auto-selected, in this order)
-
-1. **REFRESH** — `CLAUDE.md` exists AND contains an `orc-claude:meta` header.
-   Recompute section fingerprints; regenerate ONLY stale fenced sections;
-   bump `version` by exactly 0.0.1; update `updated:` (DD-MM-YYYY). Nothing
-   stale → report "up to date (vX.Y.Z)" and write NOTHING (no bump, no bak).
-   Protocol: `references/refresh.md`.
-2. **UPDATE** — `CLAUDE.md` exists but has NO `orc-claude:meta` header (a
-   foreign / hand-written file). Copy it to `CLAUDE.md.bak` first (one bak,
-   overwritten each run; offer a `.gitignore` line for it in the report). Then
-   inject the meta header at the top and append/merge fenced generated
-   sections at version `0.0.1`.
-   **NEVER trim, delete, reorder, or rewrite existing user content — not one
-   line.** If a generated section would duplicate what the user already wrote,
-   generate the slimmer remainder or skip that section. The merged file MAY
-   exceed the budget (e.g. 600 existing lines + generated → 800): that is OK
-   by design — end the report with a hard note that the user should trim
-   unused content themself for better instruction-following.
-3. **CREATE** — no `CLAUDE.md` at the repo root. Generate a fresh one from
-   `references/template.md` at version `0.0.1`.
-
-Not inside a git repo / no project root findable → say so and stop.
-
-## Dispatch (the skill's only real job)
-
-Behavior-trace logging is permanent (always on). Weave the **Trace:** steps below
-into the procedure — this skill owns a minimal one-dispatch trace (full marker
-set in "Behavior trace").
-
-1. Detect the repo root and pick the mode (REFRESH / UPDATE / CREATE above —
-   header sniff only; the writer re-verifies). **Trace:** open the run now —
-   write `log_dir/.current` = `run-claude-<slug>-<DDMMYY>-<HHMMSS>.txt` and
-   `touch the trace file` of that name in the SAME step, BEFORE the spawn (a
-   pointer to a file that does not exist reads as dangling — the hook rotates
-   away from it and the run splits across two files).
-2. Spawn `orc-claude-writer-opus-4-8-high` — or `orc-claude-writer-opus-5-med`
-   when `opus5_only` — with: `mode`, `repo_root`,
-   `budget` (from a `budget=N` argument, else null), and the paths to
-   `references/template.md` + `references/refresh.md`. **Trace:** emit
-   `DISPATCH orc-claude-writer :: <mode> expect=opus-4-8/high` just before the
-   spawn (`expect=opus-5/medium` under `opus5_only` — the expectation is
-   derived from the agent NAME you actually dispatched, never from this line's
-   default; the hook then adds `SPAWN`/`RETURN` on its own).
-3. On return, check `actual_model`/`actual_effort` against the pinned tier —
-   mismatch → prepend a tier-downgrade warning to the report. **Trace:** emit
-   `VERIFY writer actual=<model>/<effort> ✅ MATCH` (or
-   `⛔ DOWNGRADE expected=opus-4-8/high`).
-4. Relay the Phase-3 report verbatim. **Trace:** emit
-   `FINISH :: <mode_ran> CLAUDE.md v<X.Y.Z>` (mode_ran may be `noop`), then
-   delete `log_dir/.current`. Then stop. The skill NEVER writes CLAUDE.md
-   itself — not even in a "trivial" refresh.
-
-The writer performs Phases 1–3 below.
-
-## Phase 1 — ground-truth scan (facts, never guesses)
-
-Read-only. Detect from real files, never from memory:
-
-- **Stack & manifests:** `package.json`, `pyproject.toml`, `go.mod`,
-  `Cargo.toml`, `pom.xml`/`build.gradle`, `*.csproj`, `composer.json`,
-  `Gemfile`, `mix.exs` … Monorepo? (workspaces, `pnpm-workspace.yaml`,
-  `turbo.json`, `nx.json`, multiple manifests).
-- **Commands:** only invocations that PROVABLY exist — a script in a manifest,
-  a Makefile/Taskfile target, a CI step. Prefer the single-test form when the
-  runner supports one. **Never invent a command.** Unverifiable → omit.
-- **Conventions:** lint/format/type configs (eslint, prettier, biome, ruff,
-  black, clippy, tsconfig strictness…) + a small sample of real source files.
-  Record only DEVIATIONS from language defaults.
-- **Boundaries:** generated/vendored/build dirs (from `.gitignore` + tree),
-  lockfiles, migration dirs, obvious legacy zones.
-- **Environment:** env-var NAMES referenced in code/config/`.env.example`
-  (never values), external services.
-
-## Phase 2 — generate / merge
-
-Follow `references/template.md` exactly: the meta header, the section order
-(Zone A rules → Zone B reference), and the fence grammar. Every generated
-section sits inside `<!-- orc-claude:section <name> -->` …
-`<!-- /orc-claude:section -->` fences so refresh can replace it surgically.
-Sections whose scan came back empty are OMITTED, not stubbed.
-
-**P0 is user-authored, always.** Emit the P0 placeholder template from
-`references/template.md` with its hard fill-it-yourself note. Never invent P0
-rules, never ask for them. Same for the other `@user` sections (Boundaries'
-user half, Gotchas, Glossary): placeholder + note, then leave.
-
-**Line budget — generated content only.** Default 400 lines, persisted as
-`line-budget:` in the meta header. The budget counts ONLY orc-claude's own
-output (header + fenced sections) — existing user content NEVER counts against
-it and is NEVER trimmed to meet it. If generation would exceed the budget,
-trim Zone B first: move overflow to a `docs/` file and leave an `@docs/...`
-pointer. Zone A is never cut. The user may pass a different budget as an
-argument (`/orc-claude budget=600`) — honor it and persist it in the header.
-
-**Wiki block is untouchable.** If the file contains an `ORC-WIKI:START` /
-`ORC-WIKI:END` block (managed by orc-wiki), byte-preserve it and generate no
-wiki-overlapping content. orc-claude never writes inside another skill's
-markers.
-
-## Phase 3 — report
-
-Show a short summary and STOP:
-
-```
-ORC-CLAUDE — <create|update|refresh> → CLAUDE.md v<X.Y.Z> (<DD-MM-YYYY>)
-Sections written: <list>   ·   skipped (empty scan): <list>
-Sections stale→refreshed: <list>            (refresh mode only)
-Preserved untouched: user content (<n> lines), wiki block
-Conflicts flagged (scan contradicts existing text — NOT auto-edited):
-  - <file says X, repo shows Y>
-Backup: CLAUDE.md.bak <written|not needed>   (add it to .gitignore)
-NOTE: file is <n> lines total (budget covers generated content only) — trim
-unused user content yourself for better instruction-following.
-Fill in the P0 / Gotchas / Glossary placeholders yourself — orc-claude never
-writes them for you.
-```
-
-## Behavior trace (PERMANENT — a minimal one-dispatch orchestrator; always on)
-
-orc-claude owns the trace protocol for its run exactly
-like the full orchestrator — but it is a SINGLE-DISPATCH lane, so it emits ONLY
-the markers it can truthfully witness. It does **not** emit `PHASE`/`SCORE`/
-`FINDING`/`VERDICT`: the scan/generate/report phases run INSIDE the writer
-sub-agent (which self-traces nothing — it only returns `actual_model`/
-`actual_effort`), and there is no scoring or review in this lane. Resolve
-`log_dir` (`../orc/config.md` default + `.claude/orc.config.yaml`)
-at start and follow `../orc/references/trace-protocol.md`. The marker set, in
-order (all under actor `orc`, plus the hook's `SPAWN`/`RETURN`):
-
-1. `log_dir/.current` = `run-claude-<slug>-<DDMMYY>-<HHMMSS>.txt` — written FIRST
-   (the hook also bootstraps it on the writer dispatch, so the skeleton is never
-   lost, and the end-of-run packet renames a bootstrapped file).
-2. `DISPATCH orc-claude-writer :: <mode> expect=opus-4-8/high` — before the
-   spawn. The hook then appends `SPAWN`/`RETURN` around the dispatch. The mode
-   rides in this line's tail (and in `FINISH`), so no separate mode marker.
-3. `VERIFY writer actual=<model>/<effort> ✅ MATCH` or
-   `⛔ DOWNGRADE expected=opus-4-8/high` — from the writer's returned
-   `actual_model`/`actual_effort` (the one honesty signal this lane feeds
-   `/orc-retro`).
-4. `FINISH :: <mode_ran> CLAUDE.md v<X.Y.Z>` (mode_ran may be `noop`), then
-   delete `.current`.
-
-Narration is **dispatched, never remembered**: record each marker with its REAL
-timestamp as its event happens, then — as a single-dispatch lane — dispatch the
-trace writer ONCE with the whole event list plus `decisions` (the WHY: mode
-choice, what the user asked) after the writer return validates and BEFORE you
-delete `.current`. Stamps are the run's timeline, never the write time, and a run
-that ends with zero new trace lines is a protocol violation. A noop refresh still
-traces the full cycle (ending `FINISH :: noop`) and still deletes `.current`.
-
-## Boundaries
-
-- **Writes ONLY** `CLAUDE.md`, `CLAUDE.md.bak`, and (on budget overflow) a
-  `docs/` overflow file. Never edits source code, never commits, never pushes.
-- **Never asks the user anything.** Placeholders + report notes replace every
-  question.
-- **Never deletes or rewrites user-authored lines** — contradictions are
-  flagged in the report, not fixed.
-- **Never touches** the orc-wiki managed block or any other skill's markers.
-- Version bumps are always exactly +0.0.1; dates are always DD-MM-YYYY.
-- Reminder: to see usage limits, tell the user to run `/usage` (never invoke
-  it programmatically).
+---
+name: orc-claude
+description: >
+  CLAUDE.md builder/updater for the LOCAL project. Use for "/orc-claude",
+  "build a CLAUDE.md", "update the CLAUDE.md", or "refresh the CLAUDE.md".
+  Runs INDEPENDENTLY — no orchestrator, no run folder. Scans the repo for
+  ground-truth facts (verified commands, layout, conventions, boundaries) and
+  writes a section-fenced, version-stamped CLAUDE.md at the repo root — even
+  when ORC itself is installed globally. Never asks questions: P0 rules are a
+  template the user fills in themself. Refresh regenerates ONLY stale sections
+  and bumps the file version by 0.0.1. Never trims user-authored content;
+  never touches the orc-wiki pointer block. The skill dispatches the pinned
+  orc-claude-writer-opus-4-8-high agent — it never writes the file itself.
+---
+
+# ORC-CLAUDE (standalone)
+
+Build or maintain the **local project's** `CLAUDE.md` from verified repo facts.
+The target is ALWAYS `<repo root>/CLAUDE.md` of the current working directory —
+never `~/.claude/CLAUDE.md`, even if ORC is installed globally.
+
+**Dispatch, don't do.** Whatever model this chat runs on, the skill itself only
+selects the mode and spawns `orc-claude-writer-opus-4-8-high` (the pinned
+engine) — so the scan + writing always run at Opus 4.8 high regardless of the
+caller's tier. When `opus5_only: true` the engine is
+`orc-claude-writer-opus-5-med` instead (that mode FORCES it — see
+`../_shared/opus5-only.md`), and it then needs an Opus 5 main session.
+The one exception: the skill also writes the
+trace pointer + a few markers around that spawn (behavior-trace logging is
+permanent; see "Behavior trace"); that
+tracing is its ONLY self-write — the `CLAUDE.md` write is always the writer's.
+**Fully non-interactive: ask the user NOTHING.** No AskUserQuestion, no
+confirmation prompts. Dispatch, relay the report, stop.
+
+**Worked example** (orient only — never execute from it):
+`examples/claude-run-mock.md`.
+
+## The three modes (auto-selected, in this order)
+
+1. **REFRESH** — `CLAUDE.md` exists AND contains an `orc-claude:meta` header.
+   Recompute section fingerprints; regenerate ONLY stale fenced sections;
+   bump `version` by exactly 0.0.1; update `updated:` (DD-MM-YYYY). Nothing
+   stale → report "up to date (vX.Y.Z)" and write NOTHING (no bump, no bak).
+   Protocol: `references/refresh.md`.
+2. **UPDATE** — `CLAUDE.md` exists but has NO `orc-claude:meta` header (a
+   foreign / hand-written file). Copy it to `CLAUDE.md.bak` first (one bak,
+   overwritten each run; offer a `.gitignore` line for it in the report). Then
+   inject the meta header at the top and append/merge fenced generated
+   sections at version `0.0.1`.
+   **NEVER trim, delete, reorder, or rewrite existing user content — not one
+   line.** If a generated section would duplicate what the user already wrote,
+   generate the slimmer remainder or skip that section. The merged file MAY
+   exceed the budget (e.g. 600 existing lines + generated → 800): that is OK
+   by design — end the report with a hard note that the user should trim
+   unused content themself for better instruction-following.
+3. **CREATE** — no `CLAUDE.md` at the repo root. Generate a fresh one from
+   `references/template.md` at version `0.0.1`.
+
+Not inside a git repo / no project root findable → say so and stop.
+
+## Dispatch (the skill's only real job)
+
+Behavior-trace logging is permanent (always on). Weave the **Trace:** steps below
+into the procedure — this skill owns a minimal one-dispatch trace (full marker
+set in "Behavior trace").
+
+1. Detect the repo root and pick the mode (REFRESH / UPDATE / CREATE above —
+   header sniff only; the writer re-verifies). **Trace:** open the run now —
+   write `log_dir/.current` = `run-claude-<slug>-<DDMMYY>-<HHMMSS>.txt` and
+   `touch the trace file` of that name in the SAME step, BEFORE the spawn (a
+   pointer to a file that does not exist reads as dangling — the hook rotates
+   away from it and the run splits across two files).
+2. Spawn `orc-claude-writer-opus-4-8-high` — or `orc-claude-writer-opus-5-med`
+   when `opus5_only` — with: `mode`, `repo_root`,
+   `budget` (from a `budget=N` argument, else null), and the paths to
+   `references/template.md` + `references/refresh.md`. **Trace:** emit
+   `DISPATCH orc-claude-writer :: <mode> expect=opus-4-8/high` just before the
+   spawn (`expect=opus-5/medium` under `opus5_only` — the expectation is
+   derived from the agent NAME you actually dispatched, never from this line's
+   default; the hook then adds `SPAWN`/`RETURN` on its own).
+3. On return, check `actual_model`/`actual_effort` against the pinned tier —
+   mismatch → prepend a tier-downgrade warning to the report. **Trace:** emit
+   `VERIFY writer actual=<model>/<effort> ✅ MATCH` (or
+   `⛔ DOWNGRADE expected=opus-4-8/high`).
+4. Relay the Phase-3 report verbatim. **Trace:** emit
+   `FINISH :: <mode_ran> CLAUDE.md v<X.Y.Z>` (mode_ran may be `noop`), then
+   delete `log_dir/.current`. Then stop. The skill NEVER writes CLAUDE.md
+   itself — not even in a "trivial" refresh.
+
+The writer performs Phases 1–3 below.
+
+## Phases
+
+`orc lane phases orc-claude --json` is this lane's pipeline: the ordered list, where
+each phase lives, and how much of it to read. **The CLI owns the order** — never
+derive it from the headings below, and never renumber or rename one without the
+manifest, because a `read: section` pointer names a HEADING and a renamed heading
+is a pointer into nothing.
+
+## Phase 1 — ground-truth scan (facts, never guesses)
+
+Read-only. Detect from real files, never from memory:
+
+- **Stack & manifests:** `package.json`, `pyproject.toml`, `go.mod`,
+  `Cargo.toml`, `pom.xml`/`build.gradle`, `*.csproj`, `composer.json`,
+  `Gemfile`, `mix.exs` … Monorepo? (workspaces, `pnpm-workspace.yaml`,
+  `turbo.json`, `nx.json`, multiple manifests).
+- **Commands:** only invocations that PROVABLY exist — a script in a manifest,
+  a Makefile/Taskfile target, a CI step. Prefer the single-test form when the
+  runner supports one. **Never invent a command.** Unverifiable → omit.
+- **Conventions:** lint/format/type configs (eslint, prettier, biome, ruff,
+  black, clippy, tsconfig strictness…) + a small sample of real source files.
+  Record only DEVIATIONS from language defaults.
+- **Boundaries:** generated/vendored/build dirs (from `.gitignore` + tree),
+  lockfiles, migration dirs, obvious legacy zones.
+- **Environment:** env-var NAMES referenced in code/config/`.env.example`
+  (never values), external services.
+
+## Phase 2 — generate / merge
+
+Follow `references/template.md` exactly: the meta header, the section order
+(Zone A rules → Zone B reference), and the fence grammar. Every generated
+section sits inside `<!-- orc-claude:section <name> -->` …
+`<!-- /orc-claude:section -->` fences so refresh can replace it surgically.
+Sections whose scan came back empty are OMITTED, not stubbed.
+
+**P0 is user-authored, always.** Emit the P0 placeholder template from
+`references/template.md` with its hard fill-it-yourself note. Never invent P0
+rules, never ask for them. Same for the other `@user` sections (Boundaries'
+user half, Gotchas, Glossary): placeholder + note, then leave.
+
+**Line budget — generated content only.** Default 400 lines, persisted as
+`line-budget:` in the meta header. The budget counts ONLY orc-claude's own
+output (header + fenced sections) — existing user content NEVER counts against
+it and is NEVER trimmed to meet it. If generation would exceed the budget,
+trim Zone B first: move overflow to a `docs/` file and leave an `@docs/...`
+pointer. Zone A is never cut. The user may pass a different budget as an
+argument (`/orc-claude budget=600`) — honor it and persist it in the header.
+
+**Wiki block is untouchable.** If the file contains an `ORC-WIKI:START` /
+`ORC-WIKI:END` block (managed by orc-wiki), byte-preserve it and generate no
+wiki-overlapping content. orc-claude never writes inside another skill's
+markers.
+
+## Phase 3 — report
+
+Show a short summary and STOP:
+
+```
+ORC-CLAUDE — <create|update|refresh> → CLAUDE.md v<X.Y.Z> (<DD-MM-YYYY>)
+Sections written: <list>   ·   skipped (empty scan): <list>
+Sections stale→refreshed: <list>            (refresh mode only)
+Preserved untouched: user content (<n> lines), wiki block
+Conflicts flagged (scan contradicts existing text — NOT auto-edited):
+  - <file says X, repo shows Y>
+Backup: CLAUDE.md.bak <written|not needed>   (add it to .gitignore)
+NOTE: file is <n> lines total (budget covers generated content only) — trim
+unused user content yourself for better instruction-following.
+Fill in the P0 / Gotchas / Glossary placeholders yourself — orc-claude never
+writes them for you.
+```
+
+## Behavior trace (always on)
+
+`../_shared/phases/trace.md` (`core`, at run start; `orc lane phases` names
+the file and the layers). Lane token `claude`, tier **Single-dispatch** —
+exactly ONE end-of-run packet, dispatched solo after the writer return
+validates and BEFORE `.current` is deleted.
+At run start write `log_dir/.current` = `run-claude-<slug>-<DDMMYY>-<HHMMSS>.txt` AND
+`touch the trace file` of that name in the SAME step.
+Nothing else about the protocol is restated here; a phase that ends with
+`zero new trace lines is a protocol violation`.
+
+Dispatch-only lane: emit ONLY the markers it can truthfully witness — **not**
+`PHASE`/`SCORE`/`FINDING`/`VERDICT`, because scan/generate/report run INSIDE
+the writer sub-agent and there is no scoring or review here. The marker set, in
+order (actor `orc`, plus the hook's `SPAWN`/`RETURN`): `DISPATCH
+orc-claude-writer :: <mode> expect=opus-4-8/high` before the spawn (the mode
+rides in this tail and in `FINISH`, so no separate mode marker) · `VERIFY writer
+actual=<model>/<effort>` · `FINISH :: <mode_ran> CLAUDE.md v<X.Y.Z>`, where
+`mode_ran` may be `noop`. A noop refresh still traces the full cycle.
+
+## Boundaries
+
+- **Writes ONLY** `CLAUDE.md`, `CLAUDE.md.bak`, and (on budget overflow) a
+  `docs/` overflow file. Never edits source code, never commits, never pushes.
+- **Never asks the user anything.** Placeholders + report notes replace every
+  question.
+- **Never deletes or rewrites user-authored lines** — contradictions are
+  flagged in the report, not fixed.
+- **Never touches** the orc-wiki managed block or any other skill's markers.
+- Version bumps are always exactly +0.0.1; dates are always DD-MM-YYYY.
+- Reminder: to see usage limits, tell the user to run `/usage` (never invoke
+  it programmatically).
+
+## Config
+
+**ONE resolver, and it is not you:** `orc lane config orc-claude --json`. Obey
+`effective`, print every line in `announce[]` VERBATIM at preflight, and honour
+`stops[]` before wave 1. Never re-derive a value, a precedence or an inertness
+from `.claude/orc.config.yaml` — a key this lane does not read is not in the
+answer, and a key another key shadows comes back already marked. Exit ≠ 0 → say
+the CLI is unavailable and fall back to `../_shared/config-precedence.md`'s
+documented defaults, out loud. Priorities and families:
+`../_shared/config-precedence.md`.
+
+## Calls
+
+**ONE catalogue, and it is not you:** `orc lane calls orc-claude --json` names every
+CLI call this lane makes, each with its exit-code contract, its cost, when to run
+it, and what an EMPTY answer means. Never invent a spelling, never re-word an
+exit code, and never re-derive a state word — the CLI's state words are the only
+state words, and **an exit code is an ANSWER wherever that contract says so, not
+a failure**. A call the answer does not name is a call this lane does not make.
+Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
+command you are about to run, out loud, before running it.
+
+## Waiting mid-run (`/orc-wait`)
+
+Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**
+Checkpoint **none** · safe point **single dispatch**. Nothing here to checkpoint, so all three modes behave identically — say so rather than asking. Never begin a wait between a dispatch and its validated return, or before the smoke gate has reported.

package/templates/skills/orc-diy/README.md

@@ -68,7 +68,8 @@ The full key table lives in `references/flow-schema.md`. Highlights:
   full grid: `sonnet-4-6-{med,high}`, `opus-4-7-{med,high}`,
   `opus-4-8-{med,high,xhigh,max}`, `opus-5-{med,high,xhigh,max}`,
   `fable-5-{med,high,xhigh,max}` (default
-  `opus-4-8-high`). The effort guard enforces the effort half deterministically
+  `opus-5-high` — D29 moved it there at v1.0.0 so the wizard's own default
+  does not clip the two Opus 5 bands the score table ships). The effort guard enforces the effort half deterministically
   (the compiled effort OR higher on the ladder); the statusline warns on the
   model half. Executor choices above the tier are rejected at validate time; the
   score table is clipped to the tier at compile time.