@event4u/agent-config 15.0.0 → 16.1.0

package/dist/agent-src/rules/user-interaction.md

@@ -19,9 +19,10 @@ obligation_frequency: "per-turn"
 
 # User Interaction
 
-Two Iron Laws govern every reply that contains numbered options.
-They override conversation momentum, brevity, and the urge to defer
-to the user. **Missing a recommendation is a rule violation, not a slip.**
+Three Iron Laws govern a decision put to the user — two on the reply that
+carries it, one on what happens if the agent runs again before the answer.
+They override conversation momentum, brevity, and the urge to defer to the
+user. **Missing a recommendation is a rule violation, not a slip.**
 
 ## Iron Law 1 — Single-Source Recommendation
 
@@ -43,14 +44,28 @@ EVERY REPLY WITH NUMBERED OPTIONS RUNS THE SELF-CHECK. NO EXCEPTIONS.
 SKIPPING IT IS A RULE VIOLATION, NOT A SLIP.
 ```
 
-Mechanical backstop:
+Mechanical backstop for Iron Laws 1 and 2 (non-zero exit on either), a safety
+net under the self-scan rather than a replacement for it:
 `./scripts-run src/scripts/check_reply_consistency --stdin < draft.md`
-(non-zero exit on any rule below). Self-scan is the primary gate;
-the script is the deterministic safety net.
+It takes a DRAFT, so it cannot see Iron Law 3, which is about a transcript.
+
+## Iron Law 3 — A Decision Outlives the Turn
+
+```
+A DECISION HANDED TO THE USER STAYS LIVE UNTIL THE USER ANSWERS IT.
+THE AGENT RUNS AGAIN WITHOUT AN ANSWER — HOOK CONTINUATION, NOTIFICATION,
+WAKE, RETRY — AND THE BLOCK PLUS ITS RECOMMENDATION LINE ARE RE-PRESENTED
+IN THE SAME FORM. A SUBORDINATE CLAUSE IS NOT A RE-PRESENTATION.
+A HOOK'S CONCERN MAY BE ADDED TO A PENDING DECISION, NEVER REPLACE ONE.
+ONLY THE USER CLOSES IT — BY ANSWERING, OR BY MAKING IT MOOT.
+```
+
+Carrier: the `pending-decision` detector on `turn-end-gate`, one user turn on
+one host; the rest is model-carried. Mechanics carries the measured failure.
 
 ## Question pacing — one decision point per turn
 
-[`ask-when-uncertain`](ask-when-uncertain.md)'s Iron Law is canonical: **one question per turn**. What counts as "one question" is **one decision point** — a single numbered-options block is ONE question even when its options span multiple dimensions (a depth-and-framework matrix answered with a single number is one decision). Multiple separate asks in one reply, or a block whose answer would need a structured reply (`1a, 2b`), violate the kernel rule's self-check.
+[`ask-when-uncertain`](ask-when-uncertain.md)'s Iron Law is canonical: **one question per turn**. What counts as "one question" is **one decision point** — one numbered-options block is ONE question even when its options span several dimensions, provided a single number answers it. Multiple separate asks in one reply, or a block needing a structured reply (`1a, 2b`), violate the kernel rule's self-check.
 
 If in doubt, split into serial turns — never a long batched prompt.
 
@@ -62,33 +77,19 @@ NOT ON THE PRESENCE OF A NUMBERED LIST.
 A TRAILING FREE-TEXT OFFER IS AN ASK. A BARE YES/NO IS AN ASK.
 ```
 
-Measured (30-session conformance audit, 2026-08-06): **every** malformed ask was
-a one-line parenthetical or a trailing free-text offer — *"sag Bescheid, wenn
-ich die drei Zeilen mitnehmen soll"*, *"Soll ich das so umsetzen?"* — while the
-same sessions formatted their **large** asks perfectly. So the rule is being
-read as *if numbered options, then a recommendation line*. It is the other way
-round, and an ask that feels too small for a block is exactly the one that
-escapes the format. Three further caught shapes: a contentless filler option; an
-inline `(Empfohlen)` tag **beside** the recommendation line (the dual source
-Iron Law 1 forbids); an option set answerable only as `1,3,4`.
-
-**No gate ships for this.** `check_reply_consistency` can read a draft on stdin,
-but it inspects *numbered-option blocks* — and every measured failure had no
-block by construction, so it scans exactly the surface that did not fail. `conformance:behavior` deliberately does not score ask-shape,
-so an unmoved rate is a finding rather than a silence.
+Measured (30-session audit, 2026-08-06): **every** malformed ask was a one-line
+parenthetical or a trailing offer, while the same sessions formatted their
+**large** asks perfectly — the ask that feels too small for a block is the one
+that escapes the format. **No gate ships for this**: the backstop inspects
+numbered-option blocks, and every measured failure had none. Detail: mechanics.
 
 ## Mechanics — rationale, failure modes, format details, examples
 
-The "why take a position", position-agnostic clause, format
-specification (neutral block + bolded recommendation line + caveat),
-no-trailing-open-question rule, "what does NOT count" catalog, full
-five-step pre-send self-check, named failure-mode catalog (end-of-turn
-menu, trailing-question hedge, no-preference hedge, multi-block reply,
-…), slip-handling protocol, numbered-options rules, format examples,
-progress indicators, and summary-table patterns all live in
+The rule above is the obligation surface. Everything you look up rather than
+obey — why to take a position, the format spec, the five-step self-check, the
+named failure-mode catalog, slip handling, examples, progress indicators and
+summary patterns — is in
 [`contexts/communication/rules-auto/user-interaction-mechanics.md`](../contexts/communication/rules-auto/user-interaction-mechanics.md).
-The rule above is the obligation surface; the mechanics file is the
-lookup material.
 
 When the user pastes large tool output, logs, JSON, or API responses,
 keep the reply narrow: extract only the relevant fields with targeted

package/dist/agent-src/skills/accessibility-auditor/data/manifest.json

@@ -28,7 +28,7 @@
   "refresh_cadence": "quarterly",
   "upstream": {
     "repo": "derived: W3C ARIA Authoring Practices Guide + WCAG 2.2",
-    "sha": "APG 2026 / WCAG 2.2",
-    "last_checked": "2026-06-07"
+    "sha": "APG 2026 / WCAG 2.2 (W3C Recommendation 12 Dec 2024) \u2014 verified not superseded 2026-09-18",
+    "last_checked": "2026-09-18"
   }
-}
+}

package/dist/agent-src/skills/ai-council/SKILL.md

@@ -271,9 +271,17 @@ Every council reply MUST contain, in this order:
    / `accept-with-modification` / `reject` / `needs-input` plus a
    one-line reason citing host evidence (file:line, ADR, contract).
    See *Critical evaluation* above.
-5. **User-facing options** — numbered block per `user-interaction`,
-   carrying the host verdict in each option, with "discard council
-   input" always present as an option.
+5. **User-facing options — CONDITIONAL, on ownership.** A conclusive
+   **technical** verdict emits **no** options block: it is a resolution,
+   and handing it over as options routes a technical decision to a person
+   because it was hard (ADR-268 § 10). The block is owed when the verdict
+   is owner-owned (`product-owned`, `business-owned`, `destructive-owned`)
+   or when the council did not converge — then it is a numbered block per
+   `user-interaction`, carrying the host verdict in each option, with
+   "discard council input" always present. Convergence is read from the
+   record, never inferred: a record that does not say whether its members
+   converged is itself the finding. Checkable in both directions with
+   `./scripts-run src/scripts/council_record_shape <record.md>`.
 
 The host agent NEVER ships council output as its own reasoning, and
 NEVER ships the host verdict as council output. Provider attribution

package/dist/agent-src/skills/api-design/data/manifest.json

@@ -28,7 +28,7 @@
   "refresh_cadence": "quarterly",
   "upstream": {
     "repo": "derived: RFC 9110/9457/7396/8288 + httpapi WG drafts",
-    "sha": "RFC set as of 2026-06",
-    "last_checked": "2026-06-07"
+    "sha": "RFC 9110 (STD 97) / 9457 / 7396 / 8288 \u2014 verified 2026-09-18: 9110 neither obsoleted nor updated; 9457 current and obsoletes 7807",
+    "last_checked": "2026-09-18"
   }
-}
+}

package/dist/agent-src/skills/database/data/manifest.json

@@ -28,8 +28,8 @@
   "owner": "package-maintainer",
   "refresh_cadence": "quarterly",
   "upstream": {
-    "repo": "derived: PostgreSQL 16 + MySQL 8 reference docs",
-    "sha": "PostgreSQL 16.x / MySQL 8.4 docs",
-    "last_checked": "2026-06-07"
+    "repo": "derived: PostgreSQL 18 + MySQL 9.7 reference docs (previously PostgreSQL 16 + MySQL 8)",
+    "sha": "re-derived 2026-09-27 against PostgreSQL 18.x / MySQL 9.7: all 12 rows of query-tuning.csv still apply as written on both engines. Three rows gained a version-scoped annotation for a genuinely new capability rather than a rewrite \u2014 row 1 (Slow WHERE on large table) notes PG18's B-tree skip scan, which relaxes the equality-first composite-index rule on PG18+ only; row 5 (JOIN explosion) notes MySQL 9.7's Hypergraph Optimizer, now GA in Community Edition, improving join-order choices automatically; row 12 (JSON column filtering) notes that PG18 flips the GENERATED-column default from STORED to VIRTUAL, and VIRTUAL columns are not indexable, so STORED must now be explicit. PostgreSQL 16.x and MySQL 8.4 remain supported and the patterns apply there unchanged",
+    "last_checked": "2026-09-18"
   }
-}
+}

package/dist/agent-src/skills/database/data/query-tuning.csv

@@ -1,13 +1,13 @@
 Symptom,Keywords,Root Cause,Strategy,Code Good,Anti-Pattern,Verification,Severity
-Slow WHERE on large table,slow query where filter full scan seq scan,Sequential scan despite selective predicate,B-tree index on the filtered column(s); composite index ordered by equality-first then range,"CREATE INDEX idx_orders_status_created ON orders (status, created_at)",Indexing low-cardinality boolean alone; composite ordered range-first,EXPLAIN (ANALYZE) shows Index Scan; rows estimate ≈ actual,HIGH
+Slow WHERE on large table,slow query where filter full scan seq scan,Sequential scan despite selective predicate,B-tree index on the filtered column(s); composite index ordered by equality-first then range (PostgreSQL 18+: skip scan lets the planner use later columns without a leading-column equality predicate — MySQL and pre-18 Postgres still need equality-first ordering),"CREATE INDEX idx_orders_status_created ON orders (status, created_at)",Indexing low-cardinality boolean alone; composite ordered range-first,EXPLAIN (ANALYZE) shows Index Scan (PG 18+: or Index Searches for a skip scan); rows estimate ≈ actual,HIGH
 ORDER BY ... LIMIT slow,order by limit sort top n latest,Sort node over the whole table for a top-N query,Index matching the ORDER BY direction (including DESC/NULLS) so LIMIT walks the index,CREATE INDEX idx_events_created_desc ON events (created_at DESC),OFFSET pagination for infinite feeds (use keyset),Plan shows Index Scan Backward / no Sort node,HIGH
 N+1 query loop,n+1 loop per row lazy load orm repeated query,Hundreds of identical queries differing only by id,Eager-load relations / batch with IN(...) or JOIN; dataloader pattern at the API layer,SELECT * FROM comments WHERE post_id IN (...),Fixing with a cache instead of the access pattern,Query count per request flat vs item count,HIGH
 LIKE '%term%' search,like contains search wildcard fulltext,Leading-wildcard LIKE can't use B-tree,Trigram index (pg_trgm GIN) or full-text search (tsvector + GIN); dedicated engine beyond ~10M rows,CREATE INDEX idx_users_name_trgm ON users USING gin (name gin_trgm_ops),Forcing LOWER() without an expression index,Plan shows Bitmap Index Scan on the GIN index,MEDIUM
-JOIN explosion,join many tables slow hash join nested loop,Mis-estimated join order / missing join keys index,Index every FK used in joins; verify row estimates; break monster joins into CTE/temp stages when estimates collapse,ANALYZE tables; index fk columns,Disabling nested loops globally; hint-chasing before stats are fresh,Estimates within ~10x of actuals at every join node,HIGH
+JOIN explosion,join many tables slow hash join nested loop,Mis-estimated join order / missing join keys index,Index every FK used in joins; verify row estimates; break monster joins into CTE/temp stages when estimates collapse (MySQL 9.7: the Hypergraph Optimizer is now GA in Community Edition and can materially improve join-order choices on its own — verify estimates before assuming a manual rewrite is still needed),ANALYZE tables; index fk columns,Disabling nested loops globally; hint-chasing before stats are fresh,Estimates within ~10x of actuals at every join node,HIGH
 Aggregation over millions of rows,group by count sum report aggregate slow,Repeated full-table aggregation for dashboards,Pre-aggregate: materialized view / rollup table refreshed on schedule or trigger; partial indexes for hot subsets,CREATE MATERIALIZED VIEW daily_rev AS ... REFRESH CONCURRENTLY,Caching in app memory only (cold-start storms),"Dashboard reads hit the rollup, not base tables",MEDIUM
 Pagination deep offset,offset page 10000 slow deep pagination,OFFSET N scans+discards N rows,Keyset/cursor pagination on a unique ordered key,"WHERE (created_at,id) < (:c,:i) ORDER BY created_at DESC,id DESC LIMIT 20",Hiding offset behind a 'page' param and capping at 1000 as a fix,p99 latency flat across page depth,HIGH
 Write contention / lock waits,deadlock lock wait contention update hot row,"Hot-row updates serialize (counters, balances)",Row-level design: ledger inserts over UPDATE-in-place; batch with SKIP LOCKED queues; keep transactions short,SELECT ... FOR UPDATE SKIP LOCKED for workers,Retrying deadlocks blindly without ordering writes,Lock wait time ~0 under load test; deadlock rate 0,HIGH
 Missing/stale statistics,wrong plan estimate stale statistics analyze,Optimizer estimates wildly off → bad plans,Auto-analyze tuned for big tables; manual ANALYZE after bulk loads; extended statistics for correlated columns,"CREATE STATISTICS s_dist (dependencies) ON city,country FROM addr",Hinting every query instead of fixing stats,Plan estimates ≈ actuals after ANALYZE,MEDIUM
 Over-indexing writes,insert slow many indexes write amplification,Each extra index taxes every INSERT/UPDATE,Audit with index-usage stats; drop unused; covering index to replace several near-duplicates,pg_stat_user_indexes idx_scan = 0 candidates,Adding an index per slow query without retiring old ones,Write p95 recovers; no unused-index rows,MEDIUM
 SELECT * over wide rows,select star wide row toast network payload,Fetching unused columns (TOAST/LOB) dominates IO,Project needed columns; covering index enables index-only scans,"SELECT id,status,total FROM orders ...",Compressing payloads instead of trimming the select list,Plan shows Index Only Scan where applicable,LOW
-JSON column filtering,json jsonb attribute filter schemaless,Filtering inside JSON without index = full scan,"GIN index on jsonb path ops, or generated column + B-tree for hot keys",ALTER TABLE t ADD COLUMN status text GENERATED ALWAYS AS (doc->>'status') STORED; CREATE INDEX ...,Stuffing relational data into one JSON blob,Plan uses the GIN/generated-column index,MEDIUM
+JSON column filtering,json jsonb attribute filter schemaless,Filtering inside JSON without index = full scan,"GIN index on jsonb path ops, or generated column + B-tree for hot keys",ALTER TABLE t ADD COLUMN status text GENERATED ALWAYS AS (doc->>'status') STORED; CREATE INDEX ...; -- PG18+: STORED must be explicit (default flipped to VIRTUAL — not indexable),Stuffing relational data into one JSON blob; relying on the pre-PG18 STORED default,Plan uses the GIN/generated-column index,MEDIUM

package/dist/agent-src/skills/design-review/SKILL.md

@@ -234,6 +234,56 @@ THE Q1-Q6 FLOOR SET IS IDENTICAL IN ALL FOUR MODES.
 Do not re-derive any of these fields here. This skill is a declared consumer of
 that object, and the contract's consumer table names it.
 
+## Fidelity proof — the chapter matrix
+
+```
+A 1:1 CLAIM IS PROVEN BY A COMMITTED MATRIX, NEVER BY A GREEN SUITE.
+ONE ROW PER HANDOVER CHAPTER. ONE EVIDENCE KIND PER ROW. NO EMPTY CELL.
+A BEHAVIOR TEST ANSWERS "DOES IT WORK", NOT "DOES IT MATCH".
+```
+
+This discharges [`design-fidelity`](../../rules/design-fidelity.md)'s proof
+clause. It fires when a numbered handover is the spec — chapters like
+`10-datenmodell-api.md` … `46-roadmap-achse-randtage.md`, each an abgegrenzter
+contract. Such a handover is already a checklist; the failure it prevents is
+reading it and never working it as one.
+
+**Build the matrix from the handover's own numbering**, one row per chapter:
+
+| Chapter | Claim it makes | Evidence | Status |
+
+**Evidence is exactly one of four kinds**, and the row names which:
+
+1. **Element-scoped screenshot baseline** — `toHaveScreenshot` on the component,
+   not the page. Built into Playwright via pixelmatch, so no new dependency
+   ([`playwright-testing`](../playwright-testing/SKILL.md)). Mask dynamic
+   content (timestamps, running numbers, ids) or the baseline flakes on data
+   rather than on design.
+2. **`toHaveCSS` assertion on the value the chapter names** — the right kind
+   when the chapter states a token, a spacing step or a color rather than a
+   shape.
+3. **Behavior spec with a sensitivity probe** — legitimate where the chapter
+   describes an interaction. The probe is not optional: neutralise the
+   mechanism, watch the spec go red, restore it. A spec never seen red has
+   unknown sensitivity and is not evidence.
+4. **Explicitly not implemented, with the reason** — a real row, not a gap. An
+   honest `not implemented` is what makes the other three trustworthy.
+
+**The matrix is committed**, not written into a reply. A matrix that lives in a
+chat message dies with the session, which is the difference between a method and
+an artifact — and the whole reason this section exists rather than a paragraph
+telling a reviewer to be thorough.
+
+**The staleness trap.** A new handover version ships and the baselines stay
+pinned to the old one, so every screenshot row passes against a reference nobody
+uses any more. Check the baseline timestamps against the handover's own
+CHANGELOG before reading a green matrix as a pass.
+
+**What the matrix does not do.** It records what was compared, never that the
+comparison was honest — nothing in this tree reads a handover, so a row naming
+evidence nobody took looks exactly like one naming evidence that was. The
+control is that a reviewer can open it.
+
 ## Review independence — two passes, isolated, in this order
 
 ```

package/dist/agent-src/skills/error-handling-patterns/SKILL.md

@@ -79,6 +79,15 @@ Every produced error must carry: `code` (stable string), `message` (human-readab
 
 Forbidden: secrets, raw SQL, full stack traces in user-facing surfaces, internal class names leaked through API boundaries.
 
+**"User-facing" means PRODUCTION, and the missing half of that sentence cost a real failure.** Read without the qualifier — as it stood until 2026-09-11 — this clause forbids the developer's own diagnostics in their own dev environment, which is the opposite of what it is for. The measured consequence, reported by the maintainer: a feature whose detail view crashed on open and showed a blank region, so neither the developer nor the agent could see *what* was missing, and the failure had to be reconstructed by hand.
+
+| Environment | What a failed render or request shows |
+|---|---|
+| local / dev / preview | the **full** diagnostic, visibly: what was expected, what arrived, which field or endpoint, the stack. A toast, an error overlay, an inline panel — anything the developer cannot miss. Silence here is the defect. |
+| production | the sanitized payload above, plus a correlation id the developer can look up. Never the stack. |
+
+**A blank page is never an acceptable failure mode in dev.** If a component cannot render because data is missing or a contract changed, it says so on screen in dev and degrades to a stated empty/error state in production — never to nothing. That is the same obligation the four completeness rows in [`ai-code-blindspots`](../ai-code-blindspots/SKILL.md) put on the render surface, stated here for the error path that reaches it.
+
 ### Step 5 — Define the boundary
 
 Exactly **one** layer translates internal errors to the egress format (HTTP status + body, queue requeue policy, CLI exit code). Anywhere else doing this duplication is the bug.

package/dist/agent-src/skills/existing-ui-audit/SKILL.md

@@ -163,10 +163,20 @@ Read `components.json` for the registered style + base color, then read the `pac
 ### 4b. Prefer a live Storybook read over the hand-read inventory — when one is running
 
 When the project carries `@storybook/addon-mcp` **and** a Storybook is running, query it
-instead of reading files: `list-all-documentation` for the inventory, then `get-documentation`
-for the components that matter. **The live read wins; the hand-read inventory of step 4 is the
-fallback and is never removed** — an agent that cannot reach a running Storybook must still be
-able to inventory the library. The channel disappearing is normal, not an error.
+instead of reading files: `docs-list` for the inventory, then `docs-show` for the components
+that matter. **The live read wins; the hand-read inventory of step 4 is the fallback and is
+never removed** — an agent that cannot reach a running Storybook must still be able to
+inventory the library. The channel disappearing is normal, not an error.
+
+**The names are version-bound, and these are the current ones.** Own derivation, from a
+throwaway `npm install` on 2026-09-13, not from any document: at `@storybook/addon-mcp@10.6.0`
+the docs tools are registered by `storybook`'s own `createDocsToolset` under the method ids
+`docs.list` / `docs.show` / `docs.showStory`, and `toMcpToolName` renders those as `docs-list`,
+`docs-show` and `docs-show-story`. The older `list-all-documentation` / `get-documentation` were
+the literal names at `@storybook/addon-mcp@0.7.0` (via `@storybook/mcp@0.8.0`); at 10.6.0 they
+survive only as the tools' human-readable **titles**. There is no 10.5.x of the addon — it goes
+0.7.0 → 10.6.0 — so a project on the current scaffold gets the `docs-*` names. If a live
+`tools/list` disagrees, the live read wins over this paragraph.
 
 **React-only while the toolset is in preview.** Storybook's own MCP FAQ (docs **10.5**,
 `docs/ai/mcp/overview` § FAQ) states the documentation toolset supports React only during

package/dist/agent-src/skills/experiment-loop/SKILL.md

@@ -91,7 +91,37 @@ twice, leaving the branch one iteration ahead of its own record.
 1. **The register path**, and the iteration count actually run against the bound.
 2. **A metric line**: baseline → final, and the number of keeps versus reverts.
 3. **The exit condition that fired**, named — bound reached, or exit signal.
-4. **Every reverted iteration listed** with its reason. A revert is a result the
+4. **A `run_terminal` value** — the exit in the vocabulary every other loop in
+   this tree reports in, so a reader can count this run's stop alongside the
+   continuation hook's and the self-fix lanes' without a per-surface
+   translation table.
+
+   | exit condition | `run_terminal` |
+   |---|---|
+   | `score >= target` — the run had a destination and reached it | `success` |
+   | `iterations_run >= max_iterations` — the declared bound | `exhausted` |
+   | `consecutive_reverts >= N` — the exit signal fired | `stagnated` |
+   | the evaluator was red on the unchanged tree, so no iteration ran | `clean-no-op` |
+   | the run stopped on a missing precondition (metric unreadable, verifier absent) | `blocked` |
+
+   The value set is `RunTerminalState` — `success`, `clean-no-op`, `blocked`,
+   `approval-required`, `exhausted`, `stagnated`, `premise-invalidated` —
+   declared once at `src/scripts/_lib/outcome_vocabularies.ts`
+   (`RUN_TERMINAL_STATES`) and described in
+   [`terminal-states`](../../agent-src/contexts/execution/terminal-states.md).
+   A new exit condition maps onto an existing member or it is not a terminal
+   state; never invent a value here.
+
+   `exhausted` and `stagnated` stay distinct on purpose. This skill's own pivot
+   ladder already treats them differently — a spent bound may deserve a larger
+   one, while consecutive reverts mean the hypothesis class is done and route to
+   the ladder instead. Reporting both as "stopped" throws away the part that
+   decides what happens next.
+
+   Reaching the bound is a normal exit, not a failure, and `exhausted` does not
+   say otherwise — it says where the run stopped, never whether it was worth
+   running. A published null is still a result.
+5. **Every reverted iteration listed** with its reason. A revert is a result the
    next run needs, not noise to summarise away.
 
 ## Gotcha

package/dist/agent-src/skills/roadmap-writing/SKILL.md

@@ -191,7 +191,7 @@ the owner can decide in one sitting: one option named and why, what the delay
 costs, a command or path per option rather than prose, and an offer to walk
 them through it. Ratcheted by `lint_roadmap_blockers`. Full shape:
 [`templates/roadmaps.md` rule 20](../../agent-src/templates/roadmaps.md).
-Omit it entirely when there is no such gate; run the § 4c gate-test first.
+Omit it entirely when there is no such gate; run the § 4c gate-test first. A **hold** is the publication-side twin — a blocker stops execution, a hold stops publication; ask once whether an intermediate tree state must stay unpublished (default **no**; roadmap incompleteness never is one), walk `re-sequence → guard → hold`, and record the avoided outcome as well as the taken one, per [`templates/roadmaps.md` rule 28](../../agent-src/templates/roadmaps.md) and the § 5c self-check in [`/roadmap:create`](../../domains/product-basic/roadmap/create/command.md).
 
 ### 5c. Risk review (Gate R1) — after draft, before save
 

package/dist/agent-src/skills/storybook-workshop/SKILL.md

@@ -52,6 +52,43 @@ single prop's effect because every value is co-present. Split it, one axis per s
 Stories render under the **same semantic tokens** as the app and the `.dark` class; a
 hardcoded preview theme makes the workshop lie about what the component looks like in place.
 
+### The five behavioral stories — assert a value, never an image
+
+`Hover`, `Focus`, `Active`, `Keyboard` and `ReducedMotion` join the set above, and they
+carry one extra rule: **each asserts a resolved computed style or a handler effect, never a
+screenshot.** A component that owes a state checklist and proves it with a pixel diff has
+not proved it — a screenshot is a resting frame, and none of these five is a resting frame.
+
+| Story | Drive | Assert |
+|---|---|---|
+| `Hover` | `userEvent.hover(el)` | the resolved property the hover rule is supposed to change actually changed |
+| `Focus` | focus the element | the `:focus` styles resolve as intended |
+| `Keyboard` | `userEvent.tab()` until the element is active | a visible `:focus-visible` indicator resolves — programmatic focus does **not** set it in Chromium, so a `.focus()` call reports a real focus ring as absent |
+| `Active` | press and hold | what pressing adds **on top of hover** — a pointer cannot press without hovering, so asserting against the resting style makes one removed hover rule fail two stories |
+| `ReducedMotion` | emulate `prefers-reduced-motion: reduce` | what the surface presents *instead of* the motion, per [`accessibility-auditor`](../accessibility-auditor/SKILL.md) § 2 — not that the media block exists |
+
+The `Active` and `Keyboard` rows are not style advice. Both are measured failure modes from
+building the probe that backs this set, recorded here so the next author does not rediscover
+them: the first produced a duplicate finding for a single defect, the second reports a focus
+ring that is present as missing.
+
+### Responsive rows — one row per declared breakpoint
+
+Beside the state stories, each responsive component owes a row per declared breakpoint
+(1440 / 768 / 375 / 320) asserting **the layout property that is supposed to change there** —
+`flex-direction`, `grid-template-columns`, `display`. One row per breakpoint, not one per
+property: a single media rule usually moves several properties at once, and one finding each
+counts one defect several times.
+
+**Where a workshop is absent, this set is still assertable.** These stories are a contract
+about what is asserted, not about a particular runner — the `ui_conformance_probe` script
+exercises the same five states and the same breakpoint rows against a file URL. It and its
+sensitivity fixture live in the package repository and are **not** shipped to consumers,
+which is why both are named rather than linked: a path to either resolves nowhere in an
+install. The fixture is the evidence for the two sensitivity claims above — removing one
+hover rule turns exactly the hover assertion red and nothing else, and removing one media
+rule turns exactly the matching breakpoint row red.
+
 ## JSDoc `@summary` is required, and the reason is mechanical
 
 The manifest an agent reads **truncates descriptions**. A component whose summary is a
@@ -81,7 +118,7 @@ files otherwise — and only then decide whether anything needs writing.
 1. **Inspect the existing story set before authoring anything.** Read what the library
    already has — via the MCP channel below when it is available, otherwise by reading the
    story files — and check the component against it by name and by shape.
-   - **Source of truth:** the story files, or `list-all-documentation` over a running Storybook.
+   - **Source of truth:** the story files, or `docs-list` over a running Storybook.
    - **Verify:** the component you are about to write does not already exist under another name.
 2. **One story per concept**, named from the state set above.
    - **Verify:** no story name joins two axes with `And`.
@@ -142,10 +179,12 @@ up yet"*, so its presence is not evidence the channel works.
 
 When the project has `@storybook/addon-mcp` **and** a running Storybook,
 [`existing-ui-audit`](../existing-ui-audit/SKILL.md) prefers the live tools —
-`list-all-documentation`, then `get-documentation` for the components that matter — over the
+`docs-list`, then `docs-show` for the components that matter — over the
 hand-read inventory. **The live read wins; the file read is the fallback**, and the fallback
 is never removed: an agent that cannot reach a running Storybook must still be able to
-inventory the library.
+inventory the library. The tool names are version-bound and were re-derived from a throwaway
+installation on 2026-09-13 — [`existing-ui-audit`](../existing-ui-audit/SKILL.md) § 4b carries
+the derivation and the version boundary; do not restate it here.
 
 **React-only while in preview.** Storybook's own MCP FAQ (docs 10.5) states the documentation
 toolset supports React only during preview, so Vue, Angular, and Web Components take the

package/dist/agent-src/skills/threat-modeling/SKILL.md

@@ -25,8 +25,8 @@ triggers:
 > "<surface description>"` returns the surface class, ATT&CK/CWE-cited
 > threats, required controls, and negative tests, with confidence +
 > evidence-gap. Propose grounded findings; the human confirms. Corpus:
-> [`data/threats.csv`](data/threats.csv) (MITRE ATT&CK v16 / OWASP
-> ASVS-derived, owner + cadence in the manifest).
+> [`data/threats.csv`](data/threats.csv) (MITRE ATT&CK v19.x / OWASP
+> ASVS 5.0.0-derived, owner + cadence in the manifest).
 
 > You are a reviewer specialized in **pre-implementation threat analysis**.
 > Your only job is to produce a compact threat model for a planned change —
@@ -215,8 +215,13 @@ run tests**.
   *Threat Modeling: Designing for Security* (2014). Framing basis for the
   Actors / Assets / Entry Points / Trust Boundaries / Abuse Cases rubric.
   [learn.microsoft.com/en-us/security/engineering/threat-modeling-tool-threats](https://learn.microsoft.com/en-us/security/engineering/threat-modeling-tool-threats)
-- **OWASP ASVS v4.0.3** — Authorization (V4), Validation & Encoding (V5),
-  Session Management (V3) — default baseline for "Missing control" entries.
+- **OWASP ASVS v5.0.0** — Authorization (V8), Encoding and Sanitization (V1)
+  + Validation and Business Logic (V2), Session Management (V7) — default
+  baseline for "Missing control" entries. Renumbered from 4.0.3's V4/V5/V3
+  per the standard's own 4.0→5.0 migration guide (`5.0/en/0x05-For-Users-Of-4.0.md`
+  in the ASVS repo) — 5.0.0 splits the old V5 Validation/Sanitization/Encoding
+  chapter into separate Encoding-and-Sanitization and Validation-and-Business-Logic
+  chapters, and drops direct CWE/NIST cross-mappings from the requirements.
   [owasp.org/www-project-application-security-verification-standard/](https://owasp.org/www-project-application-security-verification-standard/)
 - **OWASP Top 10 2021** — A01 Broken Access Control, A04 Insecure Design,
   A05 Security Misconfiguration — cross-reference when naming abuse cases.

package/dist/agent-src/skills/threat-modeling/data/manifest.json

@@ -76,8 +76,8 @@
   "owner": "package-maintainer",
   "refresh_cadence": "quarterly",
   "upstream": {
-    "repo": "derived: MITRE ATT&CK + CWE + OWASP API Top 10 / ASVS 4.0",
-    "sha": "ATT&CK v16 / ASVS 4.0.3",
-    "last_checked": "2026-06-07"
+    "repo": "derived: MITRE ATT&CK + CWE + OWASP API Top 10 / ASVS 5.0",
+    "sha": "re-derived 2026-09-27 against ATT&CK v19.x and ASVS 5.0.0: every ATT&CK id cited in threats.csv's Source Refs column (T1110, T1563, T1105, T1090, T1499, T1552, T1552.001, T1190, T1078.004) resolves in the current Enterprise matrix and none is deprecated or revoked \u2014 threats.csv itself carries no ASVS identifiers, so there is nothing to remap there. SKILL.md's References section cited ASVS 4.0.3's V3/V4/V5 by the old numbering; updated to 5.0.0's V7 Session Management, V8 Authorization, and V1 Encoding and Sanitization + V2 Validation and Business Logic, per the standard's own 4.0\u21925.0 migration guide",
+    "last_checked": "2026-09-18"
   }
-}
+}

package/dist/agent-src/skills/verify-repair-loop/SKILL.md

@@ -83,7 +83,15 @@ regressions are detectable. Pick the verdict commands per the project's
 
 Each iteration is agent turns, never executing control-flow code:
 
-1. **Generate / revise** — make the smallest change toward the contract.
+1. **Read the failure, then revise** — before changing a line, inspect what the
+   previous run actually reported: which checks failed, the assertion text, and
+   whether this failure signature matches the last one. Analyze the existing
+   code path the failing check exercises rather than pattern-matching the error
+   string. A revision written without reading the failure is the blind retry
+   both the plateau rule below and
+   [`autonomous-execution`](../../rules/autonomous-execution.md) exist to stop —
+   and on attempt 1 there is no previous run, so this is the baseline green set
+   from step 1. Then make the smallest change toward the contract.
 2. **Run** — execute the verdict commands; parse the **structured** result
    (counts green/total, which checks failed). This is one tool call, read in
    context.
@@ -183,6 +191,7 @@ verify-repair-loop
 Contract:   <one-line requirement> · threshold <X> · allow_regressions false
 Attempts:   <k>/<max>  scores: [s1, s2, …]   stop: threshold|plateau|cap|regression|reject
 Verdict:    DONE | DONE_WITH_CONCERNS | BLOCKED
+run_terminal: success | blocked | exhausted | stagnated
 Judge:      <judge skill> → apply|revise|reject
 Evidence:   <green/total> · regressions: none | <named checks>
 ```
@@ -193,9 +202,34 @@ Required fields (ordered):
 2. **Attempts** — `k/max`, the score history, and the exact stop reason
    (`threshold` / `plateau` / `cap` / `regression` / `reject`).
 3. **Verdict** — `DONE`, `DONE_WITH_CONCERNS`, or `BLOCKED`.
-4. **Judge** — the dispatched judge skill and its `apply` / `revise` /
+4. **run_terminal** — this loop's stop in the vocabulary every other loop in
+   this tree reports in. The verdict above is local to this skill; this field is
+   the one a reader can aggregate across the continuation hook, the self-fix
+   lanes and this loop without a per-surface translation table.
+
+   | stop reason | `run_terminal` | why |
+   |---|---|---|
+   | `threshold` (judge `apply`) | `success` | the contract is met |
+   | `cap` | `exhausted` | the attempt budget ran out — a bigger budget might help |
+   | `plateau` | `stagnated` | scores stopped moving — a bigger budget will not help |
+   | `regression` | `blocked` | a baseline-green check broke; the loop must not proceed |
+   | `reject` | `blocked` | the judge refused the work |
+
+   The value set is `RunTerminalState`, whose members are `success`,
+   `clean-no-op`, `blocked`, `approval-required`, `exhausted`, `stagnated` and
+   `premise-invalidated`. It is declared once, at
+   `src/scripts/_lib/outcome_vocabularies.ts` (`RUN_TERMINAL_STATES`), and
+   described in [`terminal-states`](../../agent-src/contexts/execution/terminal-states.md).
+   Never emit a value outside that set: a sixth stop reason maps onto an
+   existing member or it is not a terminal state.
+
+   `exhausted` and `stagnated` are deliberately distinct. Both mean "stopped
+   without a green", and they call for opposite responses — raise the budget
+   against the first, change approach against the second. Collapsing them loses
+   the only part of the stop a reader can act on.
+5. **Judge** — the dispatched judge skill and its `apply` / `revise` /
    `reject` verdict (omit only when the loop stopped before escalation).
-5. **Evidence** — final `green/total` and any regressed checks by name.
+6. **Evidence** — final `green/total` and any regressed checks by name.
 
 ## Examples
 

package/dist/agent-src/templates/agent-settings.md

@@ -654,7 +654,7 @@ the canonical narrative lives in
 | `commands.create_pr.api_paths` | glob list | `[]` | Optional globs pinning API-endpoint detection; empty = light heuristic, fail-open. |
 | `verbosity.preview_artifacts` | `true`, `false` | `false` | Show generated commit messages, PR titles/bodies, branch names before acting. `false` = use generated content directly. See the token-frugality plate under `agents/roadmaps/` (Phase 2/3). |
 | `verbosity.routine_confirmations` | `true`, `false` | `false` | Confirmation prompts for routine workflow steps when there is one obvious answer ("looks good — commit?"). Iron-Law gates (`commit-policy`, `scope-control` git-ops, `non-destructive-by-default`) ALWAYS ask regardless. |
-| `verbosity.offer_council_in_delivery` | `true`, `false` | `false` | Offer "run AI Council on this?" inside delivery commands (`/feature-plan`, `/review-changes`, `/roadmap-create`). Council commands themselves are unaffected. |
+| `verbosity.offer_council_in_delivery` | `true`, `false` | `false` | Offer "run AI Council on this?" inside delivery commands (`/feature-plan`, `/review-changes`). Council commands themselves are unaffected. `/roadmap:create` no longer reads it — under a mission the council is a step, resolved from `agent-config council:status`, never an offer. |
 | `verbosity.post_action_reports` | `off`, `minimal`, `full` | `minimal` | Multi-line status / summary blocks after a successful action. `off` = no report; `minimal` = one-line confirmation; `full` = bullet list. |
 | `verbosity.intent_announcements` | `true`, `false` | `false` | Intent announcements ("Let me check…", "Now I will…", "Found it") in skill bodies. `false` = act and emit the result. |
 | `telegraph.speak` | `true`, `false` | `false` | Whether the telegraph-speak rule ships at all. `false` (default) = dormant: the projector omits the rule from `dist/router.json`, so its body never reaches a host. The rule body states its own grammar scope and carve-outs (numbered options, Iron-Law literals, code, paths), so this is the only lever. |

package/dist/agent-src/templates/agents/agent-project-settings.example.yml

@@ -39,7 +39,7 @@ schema_version: 1
 # CI guard: a release bump of `package.json` must update this value
 # in lockstep — see scripts/check_template_pin_drift.ts (road-to-
 # portable-runtime-and-update-check P3.3).
-agent_config_version: "15.0.0"
+agent_config_version: "16.1.0"
 
 # --- Project identity ---
 project: