@event4u/agent-config 14.12.0 → 14.14.0

package/CREDITS.md

@@ -0,0 +1,135 @@
+# Credits
+
+Attribution for derived work and external contributions. Two kinds of entries
+live here: **license-required attribution** for vendored/derived material
+(Apache-2.0 / MIT obligations) and **community credit** for external
+contributors whose skills, rules or commands were merged.
+
+## License-required attribution (vendored / derived material)
+
+| Artefact | Upstream | License | Detail |
+|---|---|---|---|
+| `design-intelligence` (corpus + grounding engine) | Next Level Builder — `ui-ux-pro-max-skill` | MIT | [`src/skills/design-intelligence/ATTRIBUTION.md`](src/skills/design-intelligence/ATTRIBUTION.md) |
+| `design-intelligence` (`ui-styling`-derived assets) | "claudekit" | Apache-2.0 | [`LICENSE.apache-2.0.txt`](src/skills/design-intelligence/LICENSE.apache-2.0.txt) + modified-file markers per §4b |
+| `corpus-grounding`, `design-tokens`, `react-shadcn-ui`, `tailwind-engineer` (derived slices) | see per-skill notices | MIT / Apache-2.0 | ADR-061 — the per-skill attribution notice is authoritative |
+| `src/scripts/cost/budget.mjs`, `src/scripts/cost/track.mjs` | ruvnet/ruflo — `plugins/ruflo-cost-tracker` | MIT | full notice below; transformation record in [`provenance/borrows.jsonl`](provenance/borrows.jsonl) and [`docs/THIRD-PARTY-NOTICES.md`](docs/THIRD-PARTY-NOTICES.md) |
+
+#### MIT notice — ruvnet/ruflo
+
+Reproduced in full rather than by reference, because MIT requires the copyright
+notice AND the permission notice to travel with copies or substantial portions
+of the Software. This file ships in the npm package (`package.json` → `files`),
+which is what discharges the obligation for a consumer who receives
+`src/scripts/cost/` from the registry — the source files themselves carry no
+in-file source name, per
+[`source-confidentiality`](src/rules/source-confidentiality.md), and MIT does not
+require one.
+
+```
+Copyright (c) 2024-2026 ruvnet
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+```
+
+### Comparators (benchmark baselines, no vendored material)
+
+| Comparator | Pinned at | License | Where it is used |
+|---|---|---|---|
+| `Source A` — an external agent-instruction suite | `2ed6c52c` | MIT | benchmark comparator arm: [`agents/roadmaps/stubs/road-to-solution-minimalism-full-tier-run.md`](agents/roadmaps/stubs/road-to-solution-minimalism-full-tier-run.md) § The published comparator |
+
+Nothing is vendored from it — no code, no oracle text, no prose. What is used is
+its **published baseline numbers** as the external column of a two-arm report,
+and four mechanism ideas folded (never copied) into
+`road-to-trigger-delivered-rule-bodies`. It is credited under an anonymised label
+because [`source-confidentiality`](src/rules/source-confidentiality.md) forbids
+the tracked tree recording which third-party package seeded an idea; the real
+identifier resolves from the encrypted token in that roadmap's § Provenance.
+
+Per [ADR-061](docs/decisions/ADR-061-corpus-grounding-layer.md), vendored
+material keeps its upstream notice inside the skill directory; this table is
+the aggregate pointer, never a replacement for the per-skill notice.
+
+### Runtime dependencies — code-graph engine (ADR-124)
+
+**No longer shipped to consumers.** The native code-graph engine
+(`src/scripts/code_graph/`, Class-A per
+[ADR-124](docs/decisions/ADR-124-embedded-engine-doctrine.md)) once added two
+exact-pinned *runtime* dependencies. The engine returned an honest null (recall
+0.365 vs grep 0.797) and is permanently `enabled: false`, so the pair moved out
+of `dependencies` rather than shipping to every consumer for a path none of them
+can reach — ~51 MB unpacked, the largest single install item in the set.
+
+They are now `devDependencies`: npm does not install those for consumers, so a
+consumer install resolves neither, while the engine's own test suite still runs
+in CI. The exact pins live there, which keeps the ABI lock machine-checked (the
+dependency-floor gate scans only `dependencies` and no longer sees the pair):
+
+| Dependency | Version | License | Role |
+|---|---|---|---|
+| `web-tree-sitter` | 0.24.7 (exact) | MIT | WASM tree-sitter runtime — parses PHP/TS/JS with no native toolchain |
+| `tree-sitter-wasms` | 0.1.13 (exact) | Unlicense | prebuilt grammar `.wasm` (ABI 14; the pair is ABI-locked and must move together) |
+
+Re-enabling as a consumer means installing them yourself:
+`npm i web-tree-sitter@0.24.7 tree-sitter-wasms@0.1.13`.
+
+## Method lineage — inspiration, not incorporated material
+
+Three external sources shaped the *method* behind this package's AI-council
+topology: how a multi-model council is staged, how its advisor personas frame a
+question, and how the CLI is packaged. **No code or text from any of them is
+incorporated**, which is why they appear here rather than in the
+license-required section above — nothing about them is license-required, and
+recording them anyway is an epistemic obligation rather than a legal one
+(`code-provenance` § the knowledge layer: an artefact asserting an
+externally-sourced claim either cites a harvest id or labels the statement as
+own analysis).
+
+They are named **anonymously**, per `source-confidentiality`: a shipped artifact
+in this tree does not carry derivation attribution to a named external project.
+The maintainer-side record holds the real identities; the links are retained as
+`ENC1:` tokens, which are opaque here and decryptable only with the key in the
+maintainer's user-global settings.
+
+| Label | What it contributed | Link |
+|---|---|---|
+| **Source A** <!-- harvest:council-topology-three-stage-shape --> | The three-stage method shape: independent generation → blind peer evaluation → synthesis. | `ENC1:` (pending maintainer encryption) |
+| **Source B** <!-- harvest:council-advisor-lens-framing --> | The thinking-lens framing that informed the shipped advisor personas. | `ENC1:` (pending maintainer encryption) |
+| **Source C** <!-- harvest:council-cli-first-packaging --> | CLI-first / fallback packaging ergonomics. | `ENC1:` (pending maintainer encryption) |
+
+**What the `ENC1:` placeholder means, stated rather than left to look like a
+finished token.** The real links are held maintainer-side and are not encrypted
+into this file yet; `src/scripts/_lib/link_crypto.ts` needs
+`secrets.link_encryption_key`, which is deliberately absent from any tracked
+tree and from an agent's reach. The rows in `provenance/harvests.jsonl` carry
+`source_ref: opaque:…` instead, which is that ledger's own sanctioned form for a
+source that cannot be pinned to a public revision — so the record is complete on
+the ledger's terms while this column stays a placeholder.
+
+## Community contributions
+
+External contributions merged into the catalog are credited here and carry
+`provenance: community` in their frontmatter — the public catalog
+([`docs/catalog.md`](docs/catalog.md)) renders that as `community` in the
+`source` column.
+
+| Artefact | Contributor | Merged in |
+|---|---|---|
+| _none yet — yours could be the first_ | | |
+
+If your work appears in this package unattributed, please open an issue —
+attribution gaps are treated as bugs.

package/NOTICE

@@ -0,0 +1,13 @@
+event4u/agent-config
+Copyright (c) 2026 event4u
+
+This product includes material derived from the following third-party
+projects:
+
+openai/codex-plugin-cc (https://github.com/openai/codex-plugin-cc)
+Copyright OpenAI
+Licensed under the Apache License, Version 2.0
+(http://www.apache.org/licenses/LICENSE-2.0)
+  - The team-review system prompt and findings shape in
+    src/scripts/ai_team/team_dispatch.ts are derived from the plugin's
+    adversarial-review findings shape.

package/README.md

@@ -1,10 +1,12 @@
 <p align="center"><a href="https://event4u.app"><img alt="event4u Agent Config" src=".github/assets/banner.png"></a></p>
 
-# Agent Config — every claim machine-checked, including "zero runtime daemon"
+# Agent Config — every claim machine-checked, including the counts in these badges
 
 [![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-299-orange?style=flat-square)](dist/agent-src/skills/) [![Rules](https://img.shields.io/badge/Rules-120-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-202-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-114-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-299-orange?style=flat-square)](dist/agent-src/skills/) [![Rules](https://img.shields.io/badge/Rules-120-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-202-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-118-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/) <!-- claim:published-artifact-counts -->
+
+<sub>**How these are counted** — one canonical counter, `agent-config` → `update_counts --check`, re-derives all six from the tree and fails CI on a drift of one. Two bases are not what the linked directory shows, so they are stated here rather than left to be inferred: **Commands 202** counts every command file **recursively** (the linked directory holds 61 at its top level), and **Rules 120** counts the **source** rules while the linked projection holds 119 — one rule is dormant and is not projected. **Personas 29** excludes the directory README. Counts are of files and directories: none of them measures quality, activation, or adoption. <!-- claim:published-artifact-counts --></sub>
 
 **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/)**.
 
@@ -14,7 +16,7 @@
 
 > **Choose your experience — developer · founder · content · agency · finance · ops. Add packs. Get a focused command set, not a 500-artefact dump.** Bring your own AI provider.
 
-**A deep library of skills, commands and governed rules** — plus a capability router that loads the right skill on intent and multi-agent orchestration with consensus review. The whole layer is compiled into **20 host agents** — of 23 detected, 3 being export-only<!-- claim:host-agent-count --> (Claude Code, Cursor, Augment, Cline, Windsurf, Copilot, Gemini CLI, Codex, Continue, Zed, JetBrains, Aider and more) — with **zero runtime daemon**.<!-- claim:no-runtime-daemon --> Six role-shaped entry paths sit on top, so any host becomes a reliable team member — without locking you to a single model or vendor.
+**A deep library of skills, commands and governed rules** — plus a capability router that loads the right skill on intent and multi-agent orchestration with consensus review. The whole layer is compiled into **20 host agents** — of 23 detected, 3 being export-only<!-- claim:host-agent-count --> (Claude Code, Cursor, Augment, Cline, Windsurf, Copilot, Gemini CLI, Codex, Continue, Zed, JetBrains, Aider and more). **Resident processes are permitted only under the supervision contract ADR-249 establishes** — a policy this repository adopted on 2026-08-27, not a description of anything running today. Six role-shaped entry paths sit on top, so any host becomes a reliable team member — without locking you to a single model or vendor.
 
 ### What's different
 
@@ -86,7 +88,7 @@ is platform operation, not a user-work flow.)
 
 <p align="center">
   <a href="CHANGELOG.md">CHANGELOG</a> ·
-  <a href="MIGRATION.md">Upgrade to 6.0</a> ·
+  <a href="MIGRATION.md">Upgrade to 14.x</a> ·
   <a href="CHANGELOG.md#breaking--v400-unified-setup-road-to-unified-setup">Breaking changes</a> ·
   <a href="https://github.com/event4u-app/agent-config/releases/latest">Latest release</a> ·
   <a href="https://github.com/event4u-app/agent-config/discussions">Discussions</a>
@@ -324,7 +326,7 @@ task mcp:cloud:secret-put    # opt in to bearer-auth (recommended for private de
 
 → Operator walkthrough: [`mcp-cloud-setup`](docs/setup/mcp-cloud-setup.md) · Per-client config: [`mcp-client-config`](docs/setup/mcp-client-config.md) · Endpoints: [`mcp-cloud-endpoints`](docs/setup/mcp-cloud-endpoints.md).
 
-> **Scope — Lite, not Full.** The Worker serves read-only governance (skills · commands · rules · guidelines · contexts) as MCP prompts and resources, plus small read-only tools (`memory_lookup`, `chat_history_read`, `list_*`). It does **not** execute the ~112 Python scripts (linters, audits, `task ci`, work-engine hooks) — those require local install per [Quickstart](#quickstart).
+> **Scope — Lite, not Full.** The Worker serves read-only governance (skills · commands · rules · guidelines · contexts) as MCP prompts and resources, plus small read-only tools (`memory_lookup`, `chat_history_read`, `list_*`). It does **not** execute the repository's local scripts (linters, audits, `task ci`, work-engine hooks) — those require local install per [Quickstart](#quickstart).
 
 > The built-in **local stdio** server is listed for discovery in the [Glama MCP Registry](https://glama.ai/mcp/servers/event4u-app/agent-config) (agent developers / contributors; requires a local checkout, not a turnkey install — see [ADR-067](docs/decisions/ADR-067-glama-registry-listing.md)).
 
@@ -597,7 +599,7 @@ task dev:setup        # boot the onboarding wizard against the working tree
 
 **Invoking the CLI from a source checkout:** `./agent-config <command>` (the maintainer shim at the repo root → `scripts/agent-config` → `dist/cli/agent-config.js`). `npx @event4u/agent-config` doesn't resolve in the source repo without a prior `npm link`, since there's no `node_modules/.bin/agent-config` symlink — use `./agent-config` instead. Build the TS binary with `npm run build:cli` if `dist/cli/agent-config.js` is missing.
 
-→ Full project structure and commands: [**docs/development.md**](docs/development.md) · [CONTRIBUTING.md](CONTRIBUTING.md). Stack: **TypeScript** CLI/UI + **Python 3.10+** build/lint scripts. MCP registry payloads render under `dist/mcp/` ([submission checklist](docs/distribution/mcp-submission-checklist.md)).
+→ Full project structure and commands: [**docs/development.md**](docs/development.md) · [CONTRIBUTING.md](CONTRIBUTING.md). Stack: **TypeScript** throughout — CLI, UI, and the build / lint scripts. MCP registry payloads render under `dist/mcp/` ([submission checklist](docs/distribution/mcp-submission-checklist.md)).
 
 ---
 

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

@@ -121,11 +121,75 @@ Resolve the argument. Directory mode: list files with size and line count, and
 say up front how many there are. **A large inbox is a triage problem, not a
 throughput problem** — never open ten files at full depth in one pass.
 
+#### The inbox directory name is opaque, or the whole chain leaks
+
+```
+AN INBOX DIRECTORY UNDER agents/tmp/ CARRIES AN OPAQUE ROUND IDENTIFIER.
+NEVER NAME IT AFTER THE SOURCE. THE TRUE SOURCE IS RECORDED ONCE, `ENC1:`
+ENCRYPTED, IN THE ROUND'S OWN INTAKE NOTE. ROADMAP `Source:` LINES CITE THE
+CODENAME ONLY.
+```
+
+`agents/tmp/` is gitignored, so a speaking directory name looks free. It is not:
+the name gets **quoted** into a tracked roadmap `Source:` header, into an
+evidence artefact, into a review-snapshot filename and into a PR body, and each
+quote republishes it in a public repository. Measured at
+`road-to-source-silence` Phase 0: 190 block-tier occurrences of quoted
+non-opaque `agents/tmp(.old)/<name>/` paths across the tracked tree, plus one
+tracked findings file named after a round. **The directory name is the root of
+the leak chain — if it is opaque, nothing readable exists to be quoted.**
+
+Accepted forms — `isOpaqueRoundId` in `src/scripts/_lib/source_shape.ts` is the
+authority, and the gate enforces the same predicate:
+
+| Form | Example |
+|---|---|
+| round-dated, optional 1-3 char disambiguator | `inbox-2026-08-h` |
+| content-free hex | `round-a91f3c`, `set-a91f3c` |
+| set number | `S17` |
+
+Anything that reads is speaking by construction. If a round arrives under a
+speaking name, **rename the directory before Phase 2** and record the mapping as
+below; renaming after the first quote lands means chasing the quotes.
+
+**Record the true source exactly once, encrypted.** In the round's intake note
+(`agents/tmp/<round-id>/intake.md`):
+
+```bash
+printf '%s' '<the real source, url or description>' \
+  | ./scripts-run src/scripts/_lib/link_crypto encrypt
+```
+
+Paste the `ENC1:` token into the intake note. That token, and the codename map at
+`agents/evidence/reports/source-codename-map.md`, are the only places the
+correspondence may exist. Never a second plaintext copy — not in the roadmap, not
+in the PR body, not in a commit message.
+
 ### Phase 2 — Triage (cheap, all files)
 
 One pass per file, shallow, producing a table before any deep read:
 
-| file | genre | age | drafted-against | recurrence | first-impression disposition |
+| file | genre | age | drafted-against | recurrence | lineage | first-impression disposition |
+
+`lineage` is `n/a` for a file that claims no consolidation, `complete` for one
+whose declared parent set matches the siblings present, or `omits: <names>` /
+`ghost: <name>` / `undeclared`. Fill it from one command over the folder, not by
+reading:
+
+```bash
+./scripts-run src/scripts/lint_consolidation_lineage --root <the inbox folder>
+```
+
+The column exists because a consolidating artifact is the one genre that reads
+as *finished* while being incomplete: it presents its content as adjudicated —
+parents named, conflicts resolved, a kill register for what was rejected — so a
+parent missing from that list is not *killed*, it is *undiscussed*, and nothing
+in the artifact distinguishes those two states. Measured over four inbox folders
+carrying a declared consolidation, four had an incomplete lineage
+(`agents/evidence/analysis/consolidation-lineage-census-2026-08-26.md`). It sits
+in the triage table rather than in a deep read for the same reason `recurrence`
+does: it is one command, and by the time a deep read starts the artifact has
+already been believed.
 
 `recurrence` is `first-seen` or a pointer to the earlier artifact — the marker in
 the file's own words, or a hit in `agents/tmp.old/` on the same subject (Phase
@@ -400,6 +464,16 @@ visibly not a new one, and the resulting learning is emitted as an artefact in
 Phase 5 like any other survivor — never as a line in the reply that nothing reads
 again.
 
+**A status-update prediction naming a concrete mechanism becomes a stub or a
+roadmap in the SAME run, never a line in a file about to be consumed.** That is
+the "right, never recorded" outcome caught at its source: the round before
+`inbox-2026-08-g` already named the hook-concern axis as the next ratchet
+candidate at 68→69, the sentence sat in an untracked inbox file, the file was
+consumed, and nothing under `agents/roadmaps/` inherited it — so the same
+recommendation arrived again a round later, correct both times and durable
+neither. A prediction that names a mechanism is already an artefact; the only
+question is whether anyone writes it down before its carrier disappears.
+
 ### Phase 5 — Map survivors onto this suite's artefact types
 
 The question is never "what does the file say" but **"what does it become here"**:
@@ -413,6 +487,65 @@ The question is never "what does the file say" but **"what does it become here"*
 | reference material read on demand | a `guideline` or `context` |
 | a measured finding | a `decision-record`/ADR, not a rule |
 | a defect claim | a roadmap item, once verified |
+| a claim that maps onto an existing stub | **not a fresh artifact — a stub-blocked finding, see below** |
+| a consolidation omitting a parent | **not an artifact — a discharge, see below** |
+
+**An omitted parent is discharged, never left silent.** When Phase 2's `lineage`
+column read anything but `n/a` or `complete`, this phase says what happened to
+each omitted parent. Exactly three discharges are legal, and the choice is the
+operator's:
+
+1. **Fold it in** — read the omitted parent and carry its surviving items into
+   the consolidation, marking them as coming from it.
+2. **Record a kill ID for it** — the consolidation's kill register gains a row
+   naming the parent and why its content does not survive.
+3. **State that it was read and adds nothing** — one sentence, in the artifact,
+   naming the parent.
+
+**Silence is the failure mode; any of the three is a complete discharge.** The
+obligation is to *name* it, never to consolidate it — whether the omission was
+correct is a judgement the operator makes and this command does not. A finding
+that is usually wrong gets ignored, which is why a false positive costs one
+sentence (discharge 3) rather than a re-run.
+
+A `ghost:` reading — a declared parent with no matching file — has the same three
+discharges plus a fourth that is really a correction: fix the name. A lineage
+naming a plan nobody can open is the cheaper half of the same defect.
+
+**A survivor that maps onto an existing stub is never resolved into a verdict
+line.** When a verified claim lands on something `agents/roadmaps/stubs/` already
+holds, the mapping is neither "a defect claim → a roadmap item" nor "nothing to
+do": the plan exists, and something is holding it. Before this row the table had
+no entry for that state, so a run that found one had no prescribed output and
+wrote a summary sentence instead. The round that produced this row closed exactly
+so — *"Not a neglected guard: the cost of an unmade owner decision. On the owner's
+desk."* That sentence is accurate, and it is why nine feedback rounds on one guard
+produced no executable item: it names a state and hands nobody anything to do.
+
+The run's output MUST carry all four of these, per stub matched. Three of them
+are the difference between a finding and a shrug, and the fourth is already
+computed upstream:
+
+1. **The stub path** — `agents/roadmaps/stubs/<slug>.md`, so a reader opens it
+   instead of searching for it.
+2. **Its blocker slug** — the `### blocker: <slug>` holding it, named. Where the
+   hold is recorded outside any blocker section, say so in those words and name
+   the section; "waiting on a decision" with nothing named is the verdict line
+   again, one word longer.
+3. **Its age in days** — days since the file first appeared under
+   `agents/roadmaps/stubs/`, from
+   `git log --diff-filter=A --format=%ad --date=short -- <path> | tail -1`. A
+   stub parked eleven days and one parked two hundred are different findings and
+   a reader cannot tell them apart from the path.
+4. **The recurrence count from Phase 4c** — how many earlier rounds raised the
+   same subject. A first arrival and a ninth are different findings, 4c has
+   already counted it, and dropping it here is what let one subject arrive nine
+   times as if each were new.
+
+Missing any of the four leaves the survivor undischarged. This row does not
+decide what happens to the stub — promotion is the estate's question and this
+command does not answer it — it only forbids resolving the survivor into prose
+that names no artifact.
 
 Three hard defaults, from this repo's own scar tissue:
 
@@ -449,10 +582,20 @@ transcription. Phase 4b states this obligation for Phases 5 and 6 both; it is
 repeated here because this is the phase that writes the artefact, and an
 obligation named only upstream is one a Phase-6 executor never sees.
 
+**The `Source:` line carries the codename, never the source.** Per Phase 1's
+naming rule the round directory is already opaque, so
+`> **Source:** \`agents/tmp.old/inbox-2026-08-h/\`` is a compliant header and a
+speaking one is not. The gate's `source-header` and `tmp-quote` classes both
+block inside `agents/**`, so a speaking value fails CI rather than merely
+reading badly. If the roadmap needs to say *what kind* of source it was, describe
+the class ("an external acceptance-pipeline reference") and put the identity in
+the encrypted intake note.
+
 Then the inbox contract from
 [`agents-layout`](../../../../docs/contracts/agents-layout.md), in the **same
 reply**: `mv` the consumed file to `agents/tmp.old/`, point the roadmap's
-`Source:` line at its new path, and regenerate the dashboard. A consumed file
+`Source:` line at its new path — still the codename — and regenerate the
+dashboard. A consumed file
 left in `agents/tmp/` is a rule violation, not untidiness. Move only the files
 actually processed — never sweep the rest of the inbox.
 

package/dist/agent-src/commands/feature/dev.md

@@ -7,7 +7,7 @@ cluster: feature
 sub: dev
 description: Full 7-phase feature development workflow for complex features.
 argument-hint: "[description]"
-skills: [laravel, php-coder]
+skills: [laravel, php-coder, test-driven-development]
 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)."
@@ -88,7 +88,12 @@ Do NOT use for single-line fixes, trivial changes, or urgent hotfixes.
 3. Follow chosen architecture from Phase 4.
 4. Follow codebase conventions strictly (read guidelines).
 5. Update task list as progress is made.
-6. Write tests alongside the implementation.
+6. Work **one behavior at a time**: write the failing test for that behavior,
+   observe it fail, write the minimum code that makes that one behavior pass,
+   then take the next behavior. A test phase followed by a code phase is
+   batch-TDD, not test-first — it buys the ordering and loses the feedback.
+   The only exceptions are the Do-NOT list in the `test-driven-development`
+   skill; a skipped test-first cycle is recorded in the decision log, never silent.
 
 ### Phase 6: Quality Review
 

package/dist/agent-src/commands/ghostwriter/write.md

@@ -81,7 +81,11 @@ Style fidelity may be lower."* Non-blocking.
 Per [`write-engine § 2`](../../../docs/contracts/write-engine.md).
 Flag form: `--tone=<formal|casual|neutral>`,
 `--length=<words>`, `--channel=<linkedin-post|tweet|blog|freeform>`,
-`--audience=<text>`. Missing flags → interactive prompt, **one
+`--audience=<text>`. The channel values and their length defaults are
+the schema-validated set in `src/config/drafting-channels.yml` — edit
+that file and `write-engine.md` together, never one alone;
+`tests/scripts/drafting_channels_schema.test.ts` fails on drift, and on
+the short form `linkedin`, which is not a value. Missing flags → interactive prompt, **one
 question per turn**, in the order Topic → Tone → Length → Channel →
 Audience. Tone / length defaults derive from the per-channel table
 and the vocab-register → tone mapping in the engine contract.

package/dist/agent-src/commands/implement-ticket.md

@@ -7,7 +7,7 @@ routes_to: [refine-ticket, feature-planning]
 replaces: []
 visibility: visible
 skills: [refine-ticket, feature-planning]
-description: Drive a ticket end-to-end through refine → memory → analyze → plan → implement → test → verify → report — Option-A loop over the `work_engine` engine, block-on-ambiguity, no auto-git.
+description: Drive a ticket end-to-end through refine → memory → analyze → plan → implement → test → verify → report — Option-A loop over `work_engine`, block-on-ambiguity, no auto-git, test-first enforced.
 argument-hint: "[ticket-key | url | bundle-path | pasted-text]"
 suggestion:
   eligible: true

package/dist/agent-src/commands/mission/upgrade.md

@@ -122,7 +122,7 @@ catalog fixes are test-driven — a bounded generate→run→revise→re-run loo
 a numeric threshold (then a judge confirms), reusing the same N=3 cap. Use
 test/quality verdicts only; the live-app Playwright verdict stays deferred. The
 loop is multi-turn reasoning, not a runtime — it honors
-[`no-runtime-boundary`](../../docs/contracts/no-runtime-boundary.md) exactly as
+[`resident-process-governance`](../../docs/contracts/resident-process-governance.md) exactly as
 the mission does.
 
 Handle exit codes per the `/work` contract:

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

@@ -5,7 +5,7 @@ pack: meta
 visibility: internal
 cluster: orchestrate
 skills: [subagent-orchestration]
-description: Run a YAML pipeline defined under `.agent-config/orchestrations/` — chains personas / skills / commands / sub-agents per the orchestration-dsl-v1 contract
+description: Run a YAML pipeline defined under `.agent-config/orchestrations/` — chains personas / skills / commands / subagents per the orchestration-dsl-v1 contract
 argument-hint: "<pipeline-name | path> [key=value ...]"
 suggestion:
   eligible: true
@@ -23,7 +23,7 @@ packs:
 
 Execute a YAML pipeline file from `.agent-config/orchestrations/`
 against the current workspace. Pipelines are deterministic chains of
-personas, skills, commands, and sub-agents pinned by the
+personas, skills, commands, and subagents pinned by the
 [`orchestration-dsl-v1`](../docs/contracts/orchestration-dsl-v1.md)
 contract.
 

package/dist/agent-src/commands/post-as/me.md

@@ -75,7 +75,11 @@ operator notes, not voice signal.
 Per [`write-engine § 2`](../../../docs/contracts/write-engine.md).
 Flag form: `--tone=<formal|casual|neutral>`,
 `--length=<words>`, `--channel=<linkedin-post|tweet|blog|freeform>`,
-`--audience=<text>`. Missing flags → interactive prompt, **one
+`--audience=<text>`. The channel values and their length defaults are
+the schema-validated set in `src/config/drafting-channels.yml` — edit
+that file and `write-engine.md` together, never one alone;
+`tests/scripts/drafting_channels_schema.test.ts` fails on drift, and on
+the short form `linkedin`, which is not a value. Missing flags → interactive prompt, **one
 question per turn**, in the order Topic → Tone → Length → Channel →
 Audience. Defaults inherit from the engine's per-channel table and
 the pace mapping above.

package/dist/agent-src/commands/pr/merge.md

@@ -287,9 +287,9 @@ built bundle.
 ## 7. Expiry is a reported state, never a stall
 
 ```
-WHEN THE AUTHORIZATION WINDOW CLOSES WITH WORK LEFT, THE RUN STOPS CLEANLY
-AND REPORTS. IT NEVER RETRIES THE GUARD, AND IT NEVER EDITS THE GUARD,
-ITS SOURCE, OR ITS BUNDLES — READ-ONLY VERIFICATION ONLY.
+WHEN THE AUTHORIZATION WINDOW CLOSES WITH WORK LEFT, THE RUN PAUSES, REPORTS,
+AND ASKS FOR RE-AUTHORIZATION. IT NEVER RETRIES THE GUARD, AND IT NEVER EDITS
+THE GUARD, ITS SOURCE, OR ITS BUNDLES — READ-ONLY VERIFICATION ONLY.
 ```
 
 **Unreachable while the merge step is gated**, and stated rather than left for
@@ -298,9 +298,22 @@ operation (`push` and `commit` are `WARN_OPS`), so the window governs nothing
 it does. This section is the contract for when the gate opens.
 
 Write the summary as-is with a `window-expired` disposition per unprocessed PR
-and name the exact re-authorization needed. Widening `LEDGER_MAX_AGE_MS` is
-forbidden practice: on 2026-08-21 it was patched to six hours for a drain run
-and the widening reached the trunk.
+and name the exact re-authorization needed. Then STOP and wait — do not end the
+run, and do not proceed to the next PR. ADR-251 (2026-08-30) decided this
+shape: expiry is a pause, not a termination.
+
+**The operator's reply is what resumes it, and it renews the window through the
+path that already exists.** `git_authorization_hook.ts` rewrites this session's
+ledger with a fresh `detected_at` on every human-typed prompt, so a reply
+carrying the re-authorization you named resets the age the guard compares
+against — no new mechanism, and the signal still comes from text the user typed.
+Re-verify the manifest entry (number and head SHA) before resuming, exactly as
+§ 8 requires: the pause is a window in which the world can move.
+
+Widening `LEDGER_MAX_AGE_MS` is still forbidden practice, and ADR-251 kept the
+30-minute value deliberately rather than by omission: on 2026-08-21 it was
+patched to six hours for a drain run and the widening reached the trunk. The run proposes no value for it, edits neither it nor its bundles,
+and treats a refusal as the answer.
 
 ## 8. Kill switches, and what happens after a merge
 

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

@@ -313,11 +313,25 @@ branch setting, push, open a PR, re-run CI, update a merge base, fix a failing
 test, authorise spend inside a budget — is machine-executable by the agent, and
 is therefore remediation work rather than a blocker.
 
-| Outcome | When | Success? |
-|---|---|---|
-| `complete` | `count_open == 0` and the PR is open | yes — archival check runs |
-| `blocked` | every remaining open step is **externally impossible** for the agent | **no** — partial progress, labelled as such |
-| a halt | one of the five conditions fired | **no** — the halt is reported |
+| Outcome | When | Success? | terminal state |
+|---|---|---|---|
+| `complete` | `count_open == 0` and the PR is open | yes — archival check runs | `success` |
+| `blocked` | every remaining open step is **externally impossible** for the agent | **no** — partial progress, labelled as such | `blocked`, or `approval-required` where the work is finished and waiting on a human |
+| a halt | one of the five conditions fired | **no** — the halt is reported | `exhausted` when a declared budget ran out; `stagnated` when the same failure signature repeated with budget left |
+
+**The closing report names the terminal state by word**, from
+[`terminal-states`](../../../../src/agent-src/contexts/execution/terminal-states.md).
+The reason is the failure that vocabulary exists to stop: a run that stopped at
+its iteration cap and one that finished both leave the roadmap looking the same,
+because the checkbox glyphs cannot express `exhausted`, `stagnated` or
+`approval-required` — they collapse into `[ ]` and `[~]`. Three of the six states
+are therefore invisible in the dashboard and visible only in the report, which is
+why the report has to say the word.
+
+`exhausted` and `stagnated` are **never** reported as `complete`, whatever
+partial progress exists, and they are kept apart on purpose: `exhausted` says the
+budget may have been too small and raising it is a legitimate response;
+`stagnated` says more of the same will not help and raising it is the wrong one.
 
 `blocked-preflight` no longer exists. A run always starts.
 

package/dist/agent-src/commands/tdd/red.md

@@ -6,7 +6,7 @@ visibility: internal
 cluster: tdd
 sub: red
 skills: [test-driven-development]
-description: TDD red phase — enumerate cases, write ONE failing test, watch it fail at an assertion (not an import error)
+description: TDD red phase — enumerate cases, write ONE failing test, watch it fail for a reason that is about the behaviour under test
 argument-hint: "[behavior to test]"
 suggestion:
   eligible: false
@@ -26,6 +26,16 @@ Drives the **Design → Test-Red** phases of
 
 1. State the behavior in one sentence; enumerate the cases (happy / boundary / error).
 2. Write ONE failing test for the first case.
-3. Run it; confirm it fails at an **assertion**, not an import/collection error.
+3. Run it; confirm the failure is **about the behavior under test**. Valid:
+   a failing **assertion** · a **missing target** (class-not-found, or a
+   compile/type error naming the unimplemented symbol) · a **contract
+   failure**. Invalid: a broken **fixture** · a **syntax error** in the test ·
+   a missing **unrelated dependency** · a **runner or environment** fault —
+   those would fail identically with the behavior fully implemented, so they
+   measure nothing. A symbol that does not exist yet can only fail at load;
+   demanding an assertion there would force a production stub first, which is
+   what this phase exists to prevent. Taxonomy owner:
+   [`test-driven-development`](../../../skills/test-driven-development/SKILL.md)
+   § What makes a RED valid.
 4. Honor the Test-Red Forbidden block: **no production edits** (diff = `tests/**` only).
 5. Output: the failing test + its observed failure reason. Hand to `/tdd green`.

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

@@ -7,7 +7,7 @@ routes_to: [refine-prompt, command-routing]
 replaces: []
 visibility: visible
 skills: [refine-prompt, command-routing]
-description: Drive a free-form prompt end-to-end through refine → score → plan → implement → test → verify → report — Option-A loop over the `work_engine` engine, confidence-band gated, no auto-git.
+description: Drive a free-form prompt end-to-end through refine → score → plan → implement → test → verify → report — Option-A loop over `work_engine`, confidence-band gated, no auto-git, test-first.
 argument-hint: "[prompt]"
 suggestion:
   eligible: true

package/dist/agent-src/contexts/communication/rules-auto/token-efficiency-mechanics.md

@@ -115,3 +115,43 @@ the enumerated-set carve-out.
 - User explicitly asks for full output — show it.
 
 → Detailed patterns: `docs/guidelines/agent-infra/output-patterns.md`
+
+## Independent calls go in ONE block — the evidence
+
+```
+CALLS WITH NO DEPENDENCY BETWEEN THEM GO IN THE SAME BLOCK.
+A SECOND CALL THAT DOES NOT READ THE FIRST ONE'S RESULT IS NOT A SECOND TURN.
+BEFORE EMITTING A SINGLE CALL, ASK WHAT ELSE IS ALREADY KNOWN TO BE NEEDED.
+```
+
+The ceiling above forbids repetition; this forbids the opposite failure —
+splitting work that had no reason to be split. It is stated because it is
+**measured, not suspected**: over ten sessions of this package,
+`probe_turnaround` reports a mean tool-call batch size of **1.01**, with 27 of
+2,889 tool-using requests (0.93 %) carrying more than one call. At a 4.7 s
+median generation latency, a request that fans out to 42 calls spends about five
+minutes on serialization before a single tool runs.
+
+**Nothing in this package caused that, and nothing in it can fix it.** The cause
+was looked for and is recorded as absent
+(`agents/evidence/analysis/agent-turnaround-2026-08-30.md` § E2): no rule, skill
+or template forbids parallel calls, and parallel calls do occur — so 1.01 is a
+tendency, not a floor with a mechanism behind it.
+
+**The discriminator is the dependency, never the count.** Two greps over
+different files, a status and a log, three independent reads named before the
+first one runs — one block. A read whose path comes out of the previous result —
+two blocks, and batching them would be guessing.
+
+**Do not read this as "write shorter commands".** In the same corpus, 98.1 % of
+`Bash` calls are already compound or heredoc, and the 18 % that exceed 1,500
+characters carry 75 % of all command bytes — those are one-shot scripts that each
+replace three to six round-trips. Splitting them trades one expensive call for
+several cheap ones and makes the number worse while looking like a fix.
+
+**Honest enforcement — `instruction-only`.** No gate can observe a call that was
+not batched: a transcript records the calls that happened, never the block they
+could have shared. `probe_turnaround` reports the rate afterwards and refuses to
+gate on a store CI does not have. This paragraph is the whole mechanism, and the
+roadmap that added it pre-committed to recording a null if the rate does not
+move rather than repeating the reminder more loudly.