@event4u/agent-config 9.25.0 → 9.26.0

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Bootstrap shim for the event4u agent-config suite. This plugin ships ONLY the dispatcher hooks plus one install-pointer skill — ALL content (skills, rules, commands) is installed via `npx -y @event4u/agent-config init`, which writes the file projection AND registers the same hooks in ~/.claude/settings.json. DEPRECATED as a content channel; kept so the marketplace listing stays discoverable and existing installs keep working hooks.",
-    "version": "9.25.0",
+    "version": "9.26.0",
     "keywords": [
       "agent-config",
       "skills",

package/CHANGELOG.md

@@ -303,6 +303,93 @@ Entry-shape contract: [`docs/contracts/CHANGELOG-conventions.md`](docs/contracts
 > that forces a new era split (`# Era: 9.24.x`, etc.) — see
 > [`docs/contracts/CHANGELOG-conventions.md § Era splits`](docs/contracts/CHANGELOG-conventions.md).
 
+## [9.26.0](https://github.com/event4u-app/agent-config/compare/9.25.0...9.26.0) (2026-08-07)
+
+### Release highlights
+
+<!-- Curated head: fill before merge, keep it under 10 lines, and leave `_none_` where it is genuinely the answer. The generated log below is unchanged. -->
+- **Behaviour changes:** _auto-derived, rewrite before merge:_ rule/schema diffs, breaking commits or removed public surface in 17c3716, 27e6649, f352c7a, 8fdcc7b, 581dfa0, a396442 +1 more.
+- **Default changes + migration:** _auto-derived, rewrite before merge:_ commits naming a default, migration or migrate in 3bae006.
+- **Security and correctness:** _none_
+- **Honest nulls:** _auto-derived, rewrite before merge:_ commits carrying an honest-null marker in cefcd37.
+- **Known limitations:** _none_
+
+### Features
+
+* **memory:** gate the session-end learning hook on the recorded consent ([79a6aa8](https://github.com/event4u-app/agent-config/commit/79a6aa892f2d772254ef91c0b19cb93007da2d70))
+* **settings:** resolve the nickname prefill through the documented chain ([e98a7cb](https://github.com/event4u-app/agent-config/commit/e98a7cba5cc76ccd62ab7b84be4b2a2b749d96e5))
+* **bench:** price the cost axis per token bucket in the v2 report ([b234b3e](https://github.com/event4u-app/agent-config/commit/b234b3e7076d401f9201610545528097e84490f2))
+* **bench:** preserve per-trial workspaces and add a real no-network selftest ([12df43b](https://github.com/event4u-app/agent-config/commit/12df43bc6e1ac2be87e62128accc00d1296db991))
+* **bench:** add the package-ladder and bare-principle arms ([c3f1c31](https://github.com/event4u-app/agent-config/commit/c3f1c316c270aa166ed3164165a02c083345319c))
+* **gates:** assert every authored skill REACHES the Claude tree, not just that it parses ([c42b1ad](https://github.com/event4u-app/agent-config/commit/c42b1adb2afb237d45182a59af705ef64eb4fe66))
+* **settings:** make the provenance stamp decide something, and condense the rule ([27e6649](https://github.com/event4u-app/agent-config/commit/27e664999a8894e1b146a556fa114daee3511676))
+* **settings:** normalise the just-in-time settings ask and compute its budget ([f352c7a](https://github.com/event4u-app/agent-config/commit/f352c7aea72beab330f1abd625041f7bcb46df3a))
+* **language-mirror:** fall back to the system locale on a terse first prompt ([784ee64](https://github.com/event4u-app/agent-config/commit/784ee64307086a28e9657b0a0ae5ae2fac94309a))
+* **gates:** fail the pre-push chain when the running hook bundle predates its sources ([a829a7c](https://github.com/event4u-app/agent-config/commit/a829a7cb50fac0fe02fc4af80c7083a890312913))
+* **review:** one findings schema both tracks validate against ([581dfa0](https://github.com/event4u-app/agent-config/commit/581dfa079ee333edcba920b464a19c11542db4c8))
+* **review:** make prompt provenance and author-vs-reviewer checkable ([cefcd37](https://github.com/event4u-app/agent-config/commit/cefcd37ae8a4b0ee5e42ee0514e9b09399f98870))
+* **gate:** enforce the corpus refresh cadence and open the CSVs nobody opened ([c946769](https://github.com/event4u-app/agent-config/commit/c9467697823b5a0b82d8f3e4b4d34c8bd8fe813f))
+* **rules:** close the write side of the UI loop ([a396442](https://github.com/event4u-app/agent-config/commit/a396442da455b6e02afddacc87c462f80b198499))
+* **hooks:** per-concern tools: filter, applied by the dispatcher ([28a8f96](https://github.com/event4u-app/agent-config/commit/28a8f96ee413083e3f451f1bf49b5588483ae9aa))
+* **gate:** ratchet gate_self_test adoption as a shrink-only non-adopter count ([99e3656](https://github.com/event4u-app/agent-config/commit/99e36560c208904510bc0525122ad2549d697bea))
+* **agents:** create agents/proposals — the directory seven artefacts pointed at ([64717a9](https://github.com/event4u-app/agent-config/commit/64717a96680cc70d3de7c4dd9a853d92952fbb53))
+* **design:** route a capability URL and a design-system dir to design-fidelity ([85b1562](https://github.com/event4u-app/agent-config/commit/85b1562c193f9eaf6ed63f8692f79e0b9d2eda3f))
+* **commands:** add /roadmap:next — screen, select, then ship a roadmap ([459211c](https://github.com/event4u-app/agent-config/commit/459211cadcc7682f26c8b081ac6c87c2a4712e46))
+
+### Bug Fixes
+
+* **release:** stop masking every push failure as a moved remote ref ([47faa19](https://github.com/event4u-app/agent-config/commit/47faa19e080bbe27c3cd8dfeb0bee67a10acfbf8))
+* **settings:** retract an overclaim and take the fork off the request path ([2139b17](https://github.com/event4u-app/agent-config/commit/2139b174c8e4afad3f7294bfc196ad0e79801cec))
+* **settings:** close the R2 review findings on the prefill and the pins ([fe35e63](https://github.com/event4u-app/agent-config/commit/fe35e63702661f34e55345c5c4fa7e2cd6b34fa4))
+* **tests:** narrow the ARMS lookup for noUncheckedIndexedAccess ([3b3e1b1](https://github.com/event4u-app/agent-config/commit/3b3e1b14ee8bb588004410d901835d35649b2544))
+* **roadmaps:** make solution-minimalism report its own spend gate ([3d9ceef](https://github.com/event4u-app/agent-config/commit/3d9ceef6153ed6df35292bf74d9a48b1e83dd982))
+* **cli:** both routing commands were dead through the shipped binary ([c2b38e2](https://github.com/event4u-app/agent-config/commit/c2b38e2263e9b27401ea38bb2782b0d7532c4527))
+* **gates:** emit the freshness verdict via stdout, not console.log ([fa06eea](https://github.com/event4u-app/agent-config/commit/fa06eea18620e671f3c09ac877cb094c6022c0aa))
+* **hooks:** design-slop read the tool fields where the dispatcher does not put them ([3ca190f](https://github.com/event4u-app/agent-config/commit/3ca190f0b2364c785f791dc106086209d86f1983))
+* **ci:** close the five surfaces this change reds, one of them a real gate gap ([c7c25ff](https://github.com/event4u-app/agent-config/commit/c7c25ffc1eac8f8b73776c5655f35af42f9eb9f7))
+* **conformance:** round 2 — the shipped gates did not fire, and four reasons were wrong ([8fdcc7b](https://github.com/event4u-app/agent-config/commit/8fdcc7b9d2de7c3239af7e809e86933e41cf44e2))
+* **gate:** close the word-form count hole in lint_abstraction_thresholds ([d5c294c](https://github.com/event4u-app/agent-config/commit/d5c294c4cf547696bf452a385ea0935b191283cd))
+* **video:** refuse --crossfade instead of silently delivering a hard cut ([6eea400](https://github.com/event4u-app/agent-config/commit/6eea4000146d1de2c8de703e046aa8072e9e4d96))
+* **ci:** close the two count-and-fixture surfaces a new sub-command reds ([f8d9566](https://github.com/event4u-app/agent-config/commit/f8d9566ca568c45c18cb2ec62d72492eaecf7570))
+
+### Reverts
+
+* **gates:** drop the skill-completeness check — its premise is false and it blocks the release ([5473a92](https://github.com/event4u-app/agent-config/commit/5473a925e13989fc6ba382145ab20c485dae2995))
+
+### Documentation
+
+* **roadmap:** reopen step 4.2 — the prefill shipped, the ask did not ([5fb6c05](https://github.com/event4u-app/agent-config/commit/5fb6c053a587440749af0b6d29b37c00fc1c03d1))
+* **roadmap:** close Phases 4 and 5 from evidence, re-encode the blocked steps ([2c70288](https://github.com/event4u-app/agent-config/commit/2c70288e372254be0cd0a23acfdd76f3b1318cb1))
+* **bench:** add the ab-v2 reproduce path and the Phase-3 pre-registration ([bb0ad48](https://github.com/event4u-app/agent-config/commit/bb0ad480deddf4ee3739d80d795a6c8546de9ffc))
+* cancel P1.2 on measurement, close the P2.1 null-scope check ([81fce51](https://github.com/event4u-app/agent-config/commit/81fce5189b88b9d64051cbf9d58e4322a783ca57))
+* **roadmap:** close P1.3 and P5.3 with their measured departures ([1c101db](https://github.com/event4u-app/agent-config/commit/1c101db9a045cc0b298927ef3d8d2622e8ec6625))
+* **roadmap:** close the four verified-fix steps of the inbox harvest ([b0cd2f4](https://github.com/event4u-app/agent-config/commit/b0cd2f4773b0f9a97135ecc5ff2432e0ae2513ab))
+
+### Refactoring
+
+* **settings:** point the four bespoke ask sites at the shared protocol ([17c3716](https://github.com/event4u-app/agent-config/commit/17c371647eddc5945dbbcc03e1cb2e698c63cf55))
+
+### Tests
+
+* **settings:** pin the ask-shaped settings migration ([3bae006](https://github.com/event4u-app/agent-config/commit/3bae00676daa7ae0e8c195fd2b6e00a2a25c60bb))
+
+### Chores
+
+* **ci:** retrigger pull_request event delivery ([a20088f](https://github.com/event4u-app/agent-config/commit/a20088f328d533827fac1de60273a3f206aceef1))
+* **roadmaps:** record the cost endpoint against the Endpoints step ([a3585ad](https://github.com/event4u-app/agent-config/commit/a3585ad7152b64fbe250ea294d242ab5a86a693b))
+* **roadmaps:** close the thresholds step, record the reproducibility residue ([39a93d3](https://github.com/event4u-app/agent-config/commit/39a93d33a3e69b132f643fe97380e2a7804d1acb))
+* **reports:** refresh the originality report round 2 left stale ([a65f929](https://github.com/event4u-app/agent-config/commit/a65f92939bae5b170a3cf58464579ccf774c5a9e))
+* regenerate router.json after the trunk merge ([0af3e84](https://github.com/event4u-app/agent-config/commit/0af3e8425106ccc395be79f66faacc3f8b45a5b1))
+* regenerate router.json and the routed-rule count for the new rule ([f262b83](https://github.com/event4u-app/agent-config/commit/f262b83fdba6b71905b03333fd93f657ae0905a3))
+* regenerate the tool trees and indices for the new rule ([2788940](https://github.com/event4u-app/agent-config/commit/2788940cc55326e125c2000ad3cf0e90fe2b5c51))
+* **router:** regenerate router.json for the two new design-fidelity triggers ([20aee52](https://github.com/event4u-app/agent-config/commit/20aee52cb1d440d77ec4b9e712164addfd0a83de))
+
+### Other
+
+* **settings:** record the R2 findings, and announce the Iron Law 3 recurrence ([63e2f09](https://github.com/event4u-app/agent-config/commit/63e2f094c57c77ec18ecf4cf449e7682597be29f))
+
+Tests: 11643 (+200 since 9.25.0)
+
 ## [9.25.0](https://github.com/event4u-app/agent-config/compare/9.24.0...9.25.0) (2026-08-06)
 
 ### Release highlights

package/README.md

@@ -4,7 +4,7 @@
 
 [![Smoke](https://github.com/event4u-app/agent-config/actions/workflows/smoke.yml/badge.svg)](https://github.com/event4u-app/agent-config/actions/workflows/smoke.yml) [![Public install smoke (3 OS × 2 Node)](https://github.com/event4u-app/agent-config/actions/workflows/smoke-public-install.yml/badge.svg)](https://github.com/event4u-app/agent-config/actions/workflows/smoke-public-install.yml) [![npm](https://img.shields.io/npm/v/@event4u/agent-config?style=flat-square&label=npm&color=orange)](https://www.npmjs.com/package/@event4u/agent-config) [![agent-config MCP server](https://glama.ai/mcp/servers/event4u-app/agent-config/badges/score.svg)](https://glama.ai/mcp/servers/event4u-app/agent-config) [![MCP Toplist](https://mcptoplist.com/badge/glama%2Fevent4u-app%2Fagent-config.svg)](https://mcptoplist.com/server/glama%2Fevent4u-app%2Fagent-config)
 
-[![Skills](https://img.shields.io/badge/Skills-288-orange?style=flat-square)](dist/agent-src/skills/) [![Rules](https://img.shields.io/badge/Rules-112-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-195-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-104-orange?style=flat-square)](docs/guidelines/) [![Personas](https://img.shields.io/badge/Personas-29-orange?style=flat-square)](dist/agent-src/personas/) [![Advisors](https://img.shields.io/badge/Advisors-5-orange?style=flat-square)](dist/agent-src/personas/advisors/)
+[![Skills](https://img.shields.io/badge/Skills-288-orange?style=flat-square)](dist/agent-src/skills/) [![Rules](https://img.shields.io/badge/Rules-114-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-196-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-104-orange?style=flat-square)](docs/guidelines/) [![Personas](https://img.shields.io/badge/Personas-29-orange?style=flat-square)](dist/agent-src/personas/) [![Advisors](https://img.shields.io/badge/Advisors-5-orange?style=flat-square)](dist/agent-src/personas/advisors/)
 
 **Try it in 30 seconds** — drop one read-only subagent into any repo and watch it gate "done": `@production-validator check this branch is actually done`. No wizard, no lock-in, nothing else installed — the [30-second wedge ↓](#quickstart) is the whole first step. Start at the proof, not the catalog: **[event4u-app.github.io/agent-config/proof/](https://event4u-app.github.io/agent-config/proof/)**.
 

package/dist/agent-src/commands/analyze/conformance.md

@@ -8,7 +8,7 @@ sub: conformance
 cluster: analyze
 skills: [roadmap-writing, decision-review, ai-council, subagent-orchestration]
 description: Audit recent local sessions for rule violations — deterministic scan plus subagent passes over the transcripts, root-cause each class, and emit a roadmap that mechanises what is mechanisable.
-argument-hint: "[--sessions N] [--scan-only] [--no-council] [--no-roadmap] [--worktree]"
+argument-hint: "[--limit N] [--scan-only] [--no-council] [--no-roadmap] [--worktree]"
 suggestion:
   eligible: false
   rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /analyze:conformance name; not independently suggested (surface-consolidation)."
@@ -155,7 +155,7 @@ Before the roadmap is believed, run every new detector and gate against:
 
 | Flag | Effect |
 |---|---|
-| `--sessions N` | How many recent sessions to read (default 30). |
+| `--limit N` | How many recent sessions to read (default 30). |
 | `--scan-only` | Step 1 only — the deterministic report, no subagents, no spend. |
 | `--no-council` | Skip step 4. Record that it was skipped. |
 | `--no-roadmap` | Findings only; no artefact authored. |

package/dist/agent-src/commands/review/changes.md

@@ -136,11 +136,12 @@ Read `subagents.adversarial_council` from `.agent-settings.yml` (default
 
 - `off` (default): skip silently.
 - `ask`: when the diff is explicitly high-risk (security, tenant, migration,
-  public API), offer it (in the user's language):
-
-  > 1. Run the adversarial verification council on this high-risk diff? (distinct-model skeptics red-team for finding coverage)
-  > 2. Skip — the five internal judges are enough
-
+  public API), offer it — in the shape
+  [`settings-ask-protocol`](../../../../rules/settings-ask-protocol.md) fixes,
+  which supplies the four slots, the one-question budget, and the storage line
+  (not persisted: `subagents.adversarial_council` is class C). What only this
+  command knows is *why now*: the diff is high-risk, and the offer is a paid
+  distinct-model red-team for finding coverage against the five internal judges.
 - `on`: run it automatically on a high-risk diff.
 
 When run, dispatch the

package/dist/agent-src/commands/roadmap/next.md

@@ -0,0 +1,194 @@
+---
+model_tier: medium
+name: roadmap-next
+pack: product-basic
+tier: 2
+visibility: internal
+cluster: roadmap
+sub: next
+skills: [roadmap-management, agent-docs-writing, ai-council, subagent-orchestration, worktree-lifecycle, git-workflow]
+description: Pick the next executable roadmap and carry it to a reviewable PR — live remote screen, five-disqualifier feasibility pass, council on the pick, process-full, chunked commits, PR, CI fix.
+argument-hint: "[--worktree] [roadmap]"
+suggestion:
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+---
+
+# /roadmap:next
+
+Selection + delivery scope of the [`/roadmap`](../roadmap.md) cluster.
+The three `process-*` subs take a roadmap **as given** and vary the
+scope inside it. `/roadmap:next` varies the **selection**: it screens
+what is actually executable right now, picks one, pins the scope to
+`full`, and carries the run to a PR that is ready for review.
+
+One invocation = one roadmap = one branch = one PR.
+
+## Instructions
+
+### 1. Live remote screen — before any selection reasoning
+
+Selection reads live state, never memory, a dashboard count, or an
+earlier fetch (per [`direct-answers`](../../rules/direct-answers.md)
+Iron Law 2 and [`roadmap-process-loop § 1`](../../contexts/execution/roadmap-process-loop.md#1-resolve-roadmap)).
+Run as ONE block:
+
+```bash
+git fetch origin --prune
+git ls-tree --name-only origin/main agents/roadmaps/          # still active?
+git ls-tree --name-only origin/main agents/roadmaps/archive/   # already closed?
+gh pr list --state open --json number,title,headRefName        # in flight?
+```
+
+Excluded from the candidate set: `template.md`, `archive/`,
+`skipped/`, `later/`, anything with `status: draft` whose promotion
+trigger has not fired, and any roadmap whose slug matches an **open
+PR's** branch — that one is taken.
+
+A roadmap completes by an archive move **inside its merging PR**, so a
+local checkout can show a closed roadmap as open. That is why this step
+precedes the screen instead of following it.
+
+### 2. Screen the survivors — five disqualifiers
+
+For each candidate read its frontmatter, its open-step count, and every
+`### blocker:` section. Disqualify on:
+
+1. **A blocker whose resolution is a human ACTION** — install a secret,
+   click a repo setting, recruit a participant, approve spend, let a
+   date pass. Apply the action-vs-judgement split: a blocker that is a
+   **judgement call** (which option, whether to reopen a recorded
+   decision, is the evidence sufficient) is **not** a disqualifier — it
+   is council-resolvable in step 3.
+2. **Spend** — paid bench or API runs, an npm publish, a public release.
+3. **A date that must pass.**
+4. **A kernel-rule edit** — [`scope-control`](../../rules/scope-control.md)
+   demands its own PR plus a ≥24 h soak, so it cannot close in this run
+   (kernel list: [`kernel-membership`](../../../docs/contracts/kernel-membership.md)).
+5. **Phases gated on a spike verdict** that may return FINDING.
+
+Also check the **family concurrency cap** (`lint_roadmap_family_cap`) —
+adding a third `road-to-<family>-*` roadmap without archiving one reds
+CI.
+
+Partial disqualification is normal and does **not** drop a candidate:
+record which phases the blocker actually blocks. A roadmap whose blocker
+touches one deferred step still has a full working set.
+
+Delegate the per-candidate reads to parallel subagents when more than
+three candidates survive step 1 (per
+[`delegation-policy`](../../rules/delegation-policy.md)); each returns
+`{slug, open_steps, blockers[], disqualifiers[], blocked_phases[]}` and
+nothing else.
+
+### 3. Rank, then let the council settle a genuine tie
+
+```
+RANK BY DEFECT SEVERITY, NEVER BY PERCENT-DONE OR STEP COUNT.
+A ROADMAP THAT REPAIRS A LIVE, USER-VISIBLE WRONGNESS OUTRANKS
+ONE THAT MOVES MORE CHECKBOXES. PICKING BY CHECKBOX COUNT IS THE
+GOODHART MOVE THIS PACKAGE'S OWN DISCIPLINE FORBIDS.
+```
+
+- **Exactly one survivor, or one that dominates** → take it, state the
+  one-line reason inline, proceed. Do not ask
+  ([`no-cheap-questions`](../../rules/no-cheap-questions.md)).
+- **Two or more with a real trade-off** → put the pick to the AI
+  council with the constraint set stated (survivors, open-step counts,
+  blocked phases, severity read) per
+  [`ai-council`](../../skills/ai-council/SKILL.md). Check the council's
+  decisive premise against the tree before adopting it — twice recorded,
+  the load-bearing claim was falsifiable in-repo.
+- **Zero survivors** → emit the screen table (candidate · open steps ·
+  disqualifier) and stop. Suggest
+  [`/roadmap:create`](create.md) or a blocker the user can clear. Do
+  not manufacture a pick.
+
+### 4. Workspace — branch by default, worktree on request
+
+Default: a feature branch in the current checkout, named
+`feat/<roadmap-slug>` per [`commit-conventions`](../../rules/commit-conventions.md).
+Propose the name once and proceed; no naming menu.
+
+`--worktree` — or the user saying "in a worktree" — routes through
+[`/worktree:create`](../../worktree/create.md) in full, including its
+[seeding allow/deny list](../../../skills/using-git-worktrees/SKILL.md#4b-seed-the-worktree--allow--deny-list).
+Two entries decide whether the run's gate results mean anything:
+dependencies are symlinked or installed **fully**, and
+`.agent-settings.yml` is **never** copied — absent IS the CI shape.
+
+### 5. Run it
+
+Hand off to [`/roadmap:process-full`](process-full.md) and follow it
+verbatim, including its Iron Law — full is full, and its five halt
+conditions are the only stops. The execution contract from
+[`roadmap-execution-contract`](../../contexts/execution/roadmap-execution-contract.md)
+is derived once; the user's single Accept covers branch, chunked
+commits, push to that branch, and the PR.
+
+### 6. Deliver
+
+Chunked commits (the agent picks the split — never ask how, per
+[`commit-policy`](../../rules/commit-policy.md)), then
+[`/create-pr`](../../git/pr/create.md): archival sweep, preflight,
+push, PR opened **ready for review** (not draft).
+
+### 7. CI — fix locally, honour the push gate
+
+Follow [`/create-pr` § 4d](../../git/pr/create.md): wait for the
+verdict in the background, never end the turn on "CI is running",
+diagnose and fix in the working tree on red, within the N=3 budget per
+[`autonomous-execution`](../../rules/autonomous-execution.md).
+
+```
+THE LOCAL FIX IS AUTONOMOUS. THE RE-PUSH IS NOT.
+git push IS A HARD-FLOOR TRIGGER AND THE FLOOR REFUSES A STANDING
+DIRECTIVE BY CONSTRUCTION. FIX, VERIFY, THEN SAY WHAT IS READY.
+NEVER INVENT A PER-PR "STANDING MANDATE" WORKAROUND.
+```
+
+The cheapest CI-fix loop is the one that never fires: run `task
+preflight` before the first push, which runs the same
+`skill_linter --changed` gate CI does.
+
+### 8. Report
+
+Roadmap picked + the screen result that picked it · steps closed /
+total · commits · PR URL as the literal last line (per
+[`direct-answers`](../../rules/direct-answers.md) reply-close) · CI
+verdict · anything left open with its reason.
+
+## Iron Law — screened, never guessed
+
+```
+NEVER PICK A ROADMAP FROM MEMORY, A DASHBOARD COUNT, OR AN EARLIER SESSION.
+THE THREE LIVE CHECKS RUN FIRST, EVERY INVOCATION.
+A ROADMAP CLAIMED "IN FLIGHT", "MERGED", OR "DONE" WITHOUT A LIVE CHECK
+AT THE MOMENT OF THE CLAIM IS AN UNVERIFIED CLAIM.
+```
+
+## Rules
+
+- **One roadmap per invocation.** Never chain a second pick after the
+  first closes — the user re-invokes.
+- **The screen is reported, not just used.** State which candidates were
+  disqualified and on what, so the pick is auditable.
+- **A judgement-call blocker goes to the council, not to the user.**
+  A human-ACTION blocker goes to neither — it disqualifies.
+- **No merge, ever.** The PR is opened for review; merging is
+  conversational ([`non-destructive-by-default`](../../rules/non-destructive-by-default.md)).
+- All rules from [`/roadmap:process-full`](process-full.md#rules) apply
+  unchanged to the execution half.
+
+## See also
+
+- [`/roadmap`](../roadmap.md) — cluster orchestrator
+- [`/roadmap:process-full`](process-full.md) — the execution half this wraps
+- [`/roadmap:ai-council`](ai-council.md) — challenge a roadmap before running it
+- [`/worktree:create`](../../worktree/create.md) — the `--worktree` path
+- [`/create-pr`](../../git/pr/create.md) — delivery + the CI wait contract
+- [`roadmap-process-loop`](../../contexts/execution/roadmap-process-loop.md) — canonical mechanics

package/dist/agent-src/commands/roadmap.md

@@ -2,14 +2,14 @@
 model_tier: medium
 name: roadmap
 disable-model-invocation: true
-argument-hint: "[create|ai-council|process-step|process-phase|process-full] [args]"
+argument-hint: "[create|ai-council|process-step|process-phase|process-full|next] [args]"
 pack: product-basic
-intent: "Roadmap dispatcher — create, process-step, process-phase, process-full, ai-council"
-routes_to: [roadmap-create, roadmap-ai-council, roadmap-materialize, roadmap-process-step, roadmap-process-phase, roadmap-process-full]
+intent: "Roadmap dispatcher — create, process-step, process-phase, process-full, next, ai-council"
+routes_to: [roadmap-create, roadmap-ai-council, roadmap-materialize, roadmap-process-step, roadmap-process-phase, roadmap-process-full, roadmap-next]
 replaces: []
 tier: 1
 visibility: advanced
-description: Roadmap orchestrator — routes to create (authoring) and process-step / process-phase / process-full (autonomous execution).
+description: Roadmap orchestrator — routes to create (authoring), process-step / process-phase / process-full (autonomous execution), and next (pick a roadmap and ship it).
 cluster: roadmap
 type: orchestrator
 suggestion:
@@ -40,6 +40,7 @@ paused for confirmation before every step) was removed —
 | `/roadmap:process-step` | `commands/roadmap/process-step.md` | Autonomously process the next open step, then stop |
 | `/roadmap:process-phase` (**default execution scope**) | `commands/roadmap/process-phase.md` | Autonomously process every open step in the current phase |
 | `/roadmap:process-full` | `commands/roadmap/process-full.md` | Autonomously process every open step across every phase |
+| `/roadmap:next` | `commands/roadmap/next.md` | Screen for the next executable roadmap, then carry it to a reviewable PR (selection + `process-full` + delivery) |
 
 Sub-command names match the locked contract in
 [`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
@@ -70,6 +71,7 @@ each only binds a scope delta.
    > 3. process-step — process the next open step, then stop
    > 4. process-phase — process the current phase (default)
    > 5. process-full — process every open step across every phase
+   > 6. next — pick the next executable roadmap and ship it to a PR
 
 ## Rules
 
@@ -84,3 +86,9 @@ each only binds a scope delta.
   *"finish this phase"*) default to
   [`/roadmap:process-phase`](roadmap/process-phase.md) unless the user
   named a different scope.
+- **Selection intents** (*"take the next sensible roadmap"*, *"nimm dir
+  die nächste Roadmap vor"*, *"pick a roadmap and ship it"*) — i.e. the
+  user has NOT named a roadmap and wants one chosen — route to
+  [`/roadmap:next`](roadmap/next.md), which is the only sub that
+  screens and selects. The three `process-*` subs never choose across
+  roadmaps.

package/dist/agent-src/contexts/execution/subagent-routing.md

@@ -48,7 +48,10 @@ THE SAME MINUS THE QUOTA WIN.
    tier <t>`); a 429/quota error trips `tripCooldown` for that tier and
    falls back per the relation — never a retry loop. Under
    `budget_routing: ask`, the FIRST budget-motivated downshift of a session
-   is confirmed once; `auto` proceeds silently. Every budget-routed
+   is confirmed once, in the shape
+   [`settings-ask-protocol`](../../rules/settings-ask-protocol.md) fixes and
+   without persisting the answer (`subagents.budget_routing` is class C);
+   `auto` proceeds silently. Every budget-routed
    dispatch emits one `orchestration_record` line (tier + provenance-tagged
    token delta) so realized savings are measured, not asserted.
 

package/dist/agent-src/rules/delegation-policy.md

@@ -50,8 +50,9 @@ clears — all of:
   [`auto-dispatch-classification`](../contexts/execution/auto-dispatch-classification.md)
   (≥1 independent, well-specified slice above the size floor).
 
-`subagents.auto: ask` → ask once before dispatching (per
-[`user-interaction`](user-interaction.md)); `auto: on` → surface the chosen mode
+`subagents.auto: ask` → ask once before dispatching, in the shape
+[`settings-ask-protocol`](settings-ask-protocol.md) fixes (the answer is not
+persisted — `subagents.auto` is class C); `auto: on` → surface the chosen mode
 + per-subtask tiers in one line. Any gate failing, or `auto: off`, or no host
 primitive → run in-session (clean no-op).
 

package/dist/agent-src/rules/design-fidelity.md

@@ -23,7 +23,9 @@ triggers:
   - phrase: "bau das nach"
   - phrase: "1:1 um"
   - phrase: "1:1 nach"
+  - phrase: "claude.site/artifacts"
   - file_pattern: "*design.html"
+  - path_prefix: ".claude/design-system/"
 applies_to_user_types:
   - "creator"
   - "developer"
@@ -96,13 +98,27 @@ artifact is simply attached. The last is covered by `file_pattern: *design.html`
 HTML edit in every project and be strictly worse than the gap it closes. A
 handover under some other filename needs one word in the prompt.
 
+Two further handover shapes carry the artifact without any of the above:
+
+- **A capability URL.** A published artifact is handed over as a link, not a
+  file — so `phrase: "claude.site/artifacts"` fires on the *published-artifact
+  path*, not on the host. `claude.ai` alone is a chat link and must stay quiet:
+  a keyword on the bare domain would fire on "I pasted this from claude.ai",
+  which is a conversation reference, not a spec.
+- **A design-system directory.** `path_prefix: ".claude/design-system/"` — the
+  conventional location for a handed-over token/component set. The prefix is the
+  vendor-scoped directory, never a bare `design-system/`, which is a normal
+  source folder in a large fraction of frontend repos.
+
 The trigger set is deliberately phrase-heavy on the German side and on
 `artifact`: a bare `artifact` keyword fires on "the CI build artifact is 40 MB".
 `ROUTING_MATRIX` in
 [`design_fidelity_routing.test.ts`](../../tests/scripts/design_fidelity_routing.test.ts)
 pins both halves — every class that must route, and the near-misses that must
 stay silent (fixture `daf-port-trigger-de`). Extending the set without adding a
-near-miss row there is how an over-broad trigger lands.
+near-miss row there is how an over-broad trigger lands: each of the two triggers
+above ships with its own near-miss row (`near-claude-ai-chat-link`,
+`near-generic-design-system-dir`).
 
 Body migrated to [`guideline:design-fidelity-mechanics`](../docs/guidelines/design-fidelity-mechanics.md) (per P4 of `road-to-kernel-and-router.md`) — surgical visual edits (targeted-edit vs redesign-trigger discipline, stable anchors), asset & imagery discipline (owned-asset path, third-party delivery is self-hosted by default, real-imagery-as-proof, iconography floor, no unrequested filler), deviation-surfacing shape, failure-mode catalog, `daf-*` fixtures.
 Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/design-review-after-ui-write.md

@@ -0,0 +1,116 @@
+---
+type: "auto"
+tier: "2b"
+alwaysApply: false
+description: "UI written or changed — review it against the design contract before calling it done; the write-side twin of ui-audit-gate"
+triggers:
+  - path_prefix: "resources/views/"
+  - path_prefix: "resources/js/"
+  - keyword: "component"
+  - keyword: "design token"
+routes_to:
+  - "skill:design-review"
+  - "skill:accessibility-auditor"
+workspaces: [agent-config-maintainer, engineering]
+packs: [frontend-design]
+collision_ok:
+  "component": "a written component is reviewed before it is called done — the write-side half"
+  "design token": "same surface, opposite side: ui-audit-gate inventories tokens before the write, this reviews what the write emitted"
+  "resources/views/": "both halves of one UI loop fire on the same path — audit before, review after; neither substitutes for the other"
+  "resources/js/": "both halves of one UI loop fire on the same path — audit before, review after; neither substitutes for the other"
+---
+
+# Design Review After UI Write
+
+The UI loop was closed on one side only. [`ui-audit-gate`](ui-audit-gate.md)
+covers the **read** side — inventory what exists before adding a component — and
+routes to `existing-ui-audit`. Nothing covered the **write** side: **zero rules
+routed to `skill:design-review`**, so a component could be written, declared
+done, and never looked at against the contract it was supposed to satisfy.
+
+This is that rule's twin, deliberately built to the same shape: same tier, same
+pack, same diff-decidable allow-list, and the same honest scope.
+
+## The Iron Law
+
+```
+UI WRITTEN OR CHANGED IS NOT DONE UNTIL IT IS REVIEWED.
+NEVER CLAIM A UI CHANGE IS COMPLETE ON "IT LOOKS RIGHT" — THAT IS A VERDICT
+WITHOUT EVIDENCE. NO RENDER CAPABILITY → SCOPE THE VERDICT TO WHAT WAS
+STATICALLY CHECKED AND SAY SO. NEVER "LOOKS GOOD" WITH NOTHING BEHIND IT.
+```
+
+## What "reviewed" means
+
+The verdict is gated on evidence, not on having run a skill:
+
+- **Render capability present** (Playwright MCP, Chrome DevTools, or a live
+  preview URL) → the [design-artifact verification checklist](../docs/contracts/design-artifact-verification.md#verification-checklist)
+  steps 1–5. A UI task does not pass without render evidence.
+- **Render capability absent** → the verdict is **scoped to the static checks
+  that actually ran** and says which those were. This is not a downgrade to be
+  hidden; `design-review` itself states it ("scope the verdict to what was
+  statically checked and say so"). An unscoped "looks good" is the failure.
+- **A provided artifact is the spec** → findings the artifact *covers* are
+  informational, not defects, per [`design-fidelity`](design-fidelity.md). The
+  review does not "improve" the user's own design.
+
+## Allow-list — `ui-trivial`, decidable from the diff alone
+
+Skip only when **all** hold:
+
+- ≤ 1 file, ≤ 5 changed lines, no new component, no new state, no new dependency.
+- Inside the work engine, `directive_set == "ui-trivial"` — the dispatcher states
+  it directly. Outside it, the same conditions are read **off the diff**, which
+  is observable without any dispatcher state.
+
+The list is deliberately the engine's five conditions, not the four its
+sibling rule's prose carries: `ui_trivial/apply.ts` enforces `new_dependency`
+too, and a twin that copied the shorter prose would inherit a gap the engine
+does not have.
+
+## Honest scope — what this rule does NOT enforce
+
+```
+THE REVIEW OBLIGATION IS MODEL-CARRIED. NEVER CLAIM THE REVIEW RAN
+AS IF IT WERE VERIFIED.
+```
+
+There is no artefact a chat session can point at to prove a design review
+happened — "I ran `design-review`" is self-report, and self-report is not
+enforcement. So this rule ships `enforced_by: none`, the same honesty boundary
+`ui-audit-gate`, `security-sensitive-stop`, and `untrusted-input-defense` state
+for their own obligations, rather than pretending a satisfiable-by-assertion
+condition is a gate.
+
+What that leaves, and it is the useful part: the write side now has a named
+obligation and a route to the skill that discharges it, where before it had
+neither. Full enforcement needs the work-engine `review`/`polish` gates (which
+already act on `a11y_violation` and `token_violation` findings) or pack-scoped
+rule projection — a maintainer decision, never an automated one.
+
+One asymmetry worth stating: `design-review` lives in `engineering-base` while
+this rule is scoped to `frontend-design`. The route still resolves — a rule may
+name a skill from another pack — but a consumer with `frontend-design` and
+without `engineering-base` gets the obligation without the skill. That is why
+`accessibility-auditor` is a second route: it is the part of the review that
+must not depend on the pairing.
+
+## Failure modes
+
+- Writing the component and calling it done because the tests pass — tests do not
+  look at it.
+- "Looks good" as a verdict with no render, no static check named, and no scope.
+- Running the review and acting on findings the provided artifact covers, i.e.
+  redesigning the user's spec under the banner of quality.
+- Treating the a11y half as optional because the visual half looked fine.
+- Skipping the review for "just one tile" — the same bypass `ui-audit-gate`
+  names on its own side.
+
+## See also
+
+- [`ui-audit-gate`](ui-audit-gate.md) — the read-side twin; audit before writing.
+- [`design-review`](../skills/design-review/SKILL.md) — the 7-phase review this routes to.
+- [`accessibility-auditor`](../skills/accessibility-auditor/SKILL.md) — the WCAG half.
+- [`design-fidelity`](design-fidelity.md) — a provided artifact is the spec; covered findings are informational.
+- [`verify-before-complete`](verify-before-complete.md) — the general no-claim-without-evidence gate this applies to UI.

package/dist/agent-src/rules/evaluator-independence.md

@@ -81,9 +81,15 @@ was manufactured anyway.
 
 [`evidence_independence.ts`](../scripts/hooks/evidence_independence.ts) is a
 `pre_tool_use` concern. It **blocks** a dispatch whose prompt carries a
-pre-loaded verdict, and **blocks** a second evaluation-shaped dispatch in the
-same turn; it **warns** on the first. It reads the prompt the agent is about to
-send, so items 1 and 4 above are mechanically enforced.
+pre-loaded verdict, and **blocks** a second *self-scoped* evaluation dispatch in
+the same turn; it **warns** on the first. It reads the prompt the agent is about
+to send, so items 1 and 4 above are mechanically enforced.
+
+Two limits, stated because round 2 measured them. The pre-loaded-verdict list is
+a **phrase list**, so a paraphrase evades it — it catches recurrences of known
+steering wording, not steering as such. And the turn boundary is the
+authorization ledger's `detected_at` stamp, because the envelope carries no turn
+id; with no ledger yet, the counter falls back to session scope.
 
 Items 2 and 3 — an honestly chosen scope, and recording the prompt with the
 verdict — are **not** enforced by anything. A narrowed scope is not decidable

package/dist/agent-src/rules/session-canary.md

@@ -12,6 +12,8 @@ workspaces: [agent-config-maintainer, construction, engineering, finance, founde
 packs: [meta]
 enforced_by:
   - "hook:session-canary"
+collision_ok:
+  "canary_name": "this rule owns what the NAME does once set and which of the three layers already supplies it; settings-ask-protocol owns how it is asked for and where the answer goes"
 ---
 
 # Session Canary