@event4u/agent-config 9.2.0 → 9.4.0

package/docs/command-flows.md

@@ -7,7 +7,7 @@
 
 > Every command is classified in `src/flows/surface-map.yaml` (coverage enforced by `scripts/lint_command_flow_coverage.py`). The four user-work flows carry rich definitions in `src/flows/<flow>.yaml`.
 
-**184 commands** across **10 surfaces** (4 user-work flows + 6 platform/domain surfaces).
+**190 commands** across **10 surfaces** (4 user-work flows + 6 platform/domain surfaces).
 
 ## User-work flows
 
@@ -56,6 +56,10 @@ _Build it. The core "make the change" front — drive a prompt, ticket, or featu
 - `jira-ticket` — Read Jira ticket from branch name, analyze linked Sentry issues, implement feature or fix bug
 - `mission-upgrade` — Gated Laravel major-version upgrade mission — provisional branch, breaking-change catalog, size-tier surfac…
 - `module-create` — Create a new module from .module-template with interactive setup
+- `tdd` — TDD orchestrator — routes to red (failing test), green (minimum code), refactor (clean while green)
+- `tdd-green` — TDD green phase — write the minimum production code to make the failing test pass; no test edits
+- `tdd-red` — TDD red phase — enumerate cases, write ONE failing test, watch it fail at an assertion (not an import error)
+- `tdd-refactor` — TDD refactor phase — clean up (rename, deduplicate) while keeping the test green
 - `tests` — Tests orchestrator — routes to create, execute, e2e-plan, e2e-heal
 - `tests-create` — Write meaningful tests for the current branch — stack-adaptive (pest / phpunit / vitest / jest / pytest / …)
 - `tests-e2e-heal` — Find, debug, and fix failing Playwright E2E tests
@@ -79,6 +83,7 @@ _Check it. Self-review, judge, fix/quality, and threat-model a change before it
 
 - `fix-ci` — Fetch CI errors from GitHub Actions and fix them
 - `fix-quality` — Run quality pipeline (PHP and/or JS/TS) and fix all errors — auto-detects language from changed files
+- `fix-route` — Classify a vaguely-described problem and dispatch to the right fix sub-command (or name the specialist skil…
 - `judge` — Judge orchestrator — routes to solo, steps, on-diff
 - `judge-on-diff` — Run a single change through an implementer→judge loop with a two-revision ceiling, then hand back to the user
 - `judge-solo` — Run a standalone judge on an existing diff or code change — no implementer, no revision loop, verdict only
@@ -135,11 +140,11 @@ _Deliberately-started features — not daily flow members, never buried as skill
 - `roadmap-process-full` — Autonomously process every open step across every phase of a roadmap until the file is fully closed. Larges…
 - `roadmap-process-phase` — Autonomously process every open step in the next or current phase of a roadmap, then stop. Default executio…
 - `roadmap-process-step` — Autonomously process the single next open step of a roadmap and stop. Smallest execution scope of the /road…
-- `team` — Team orchestrator — cross-model depth review (one strong model builds, a second reviews the real diff); rou…
+- `team` — Team orchestrator — governed cross-model access layer (a second strong model reviews the real diff; read-on…
 - `team-adversarial` — Thin wrapper — adversarial cross-model review on a named focus via the official plugin (/codex:adversarial-…
 - `team-delegate` — Thin wrapper — hand a task to the second model as a native worker via the official plugin (/codex:rescue).…
 - `team-review` — Thin wrapper — cross-model review of the current diff via the official plugin (/codex:review). Gated on ai_…
-- `team-status` — Thin wrapper — plugin job status via /codex:status plus a ledger line with today's cli_call_budget openai c…
+- `team-status` — Thin wrapper — plugin job status via /codex:status plus a quota block (shared openai counter vs team + coun…
 
 ### Platform surface — `agent-admin`
 
@@ -165,9 +170,11 @@ _The system/admin surface (NOT a flow): memory · analytics · governance · con
 - `context` — Context orchestrator — routes to create, refactor
 - `context-create` — Analyze a codebase area and create a structured context document
 - `context-refactor` — Analyze, update, and extend an existing context document
+- `contribution-precheck` — Contributor self-service precheck — run the PR-relevant lint subset (skill linter, originality gate, frontm…
 - `cost` — Cost orchestrator — routes to report (session token cost + budget ladder) and profile (change the rule_load…
 - `cost-profile` — Change the rule_loading_tier in .agent-settings.yml — shows each profile's meaning and applies the selection
 - `cost-report` — Capture token cost from the active Claude Code session, append to the local sessions store, and surface the…
+- `explain-run` — Read-only 'why did that happen' run report — resolved rule set, rules fired, artefact engagement, subagent…
 - `knowledge` — Knowledge orchestrator — routes to ingest, list, forget. Local-only file ingestion into the agent memory na…
 - `knowledge-cross-repo` — Targeted, read-only retrieval over opted-in linked-project siblings (ADR-032 Option A). Pulls a shared type…
 - `knowledge-forget` — Drop a knowledge ingest from `agents/memory/knowledge/` by id prefix. Atomic, no partial state. Pinning pro…

package/docs/comparison.yaml

@@ -33,3 +33,13 @@ rows:
     our_evidence: "tests/scripts/witness/check_refs_relative_gap.test.ts"
     their_evidence: "Published known-limitation surfaces backed by reproducing tests are not a standard artifact in this category."
     checkable: true
+
+  - claim: "A 30-second single-file wedge exists — one read-only subagent, one command, verdict with file:line — and its promise is a scoped, published eval, not a feature list."
+    our_evidence: "internal/bench/orchestration/pv-a3-results.md#token_delta_provenance: measured"
+    their_evidence: "Category entry points typically install the full platform (profiles, packs, runtime) before the first felt win; single-artifact entries with a published eval behind the promise are not a standard artifact."
+    checkable: true
+
+  - claim: "The persona-identity question was tested and published as an honest null (identity swap ~zero effect, provider choice ~15x larger) instead of being shipped as theater."
+    our_evidence: "internal/bench/reports/persona-placebo.json#honest-null"
+    their_evidence: "Named-persona prompts are shipped as a feature across the category without a published A/B separating identity from method."
+    checkable: true

package/docs/contracts/adoption-signal-floor.md

@@ -84,6 +84,23 @@ must clear before the code lands:
 Until all four gates are written and reviewed, consumer-side
 telemetry is **forbidden** even as a discussion item in roadmaps.
 
+## Extraction demand gate — lint_originality standalone probe
+
+Added 2026-07-20 (road-to-originality-gate-and-contributor-funnel Phase 3,
+council 2026-07-20: extraction is demand-gated; the floor IS the demand gate,
+applied post-probe). Uses **allowed public signals only** — inbound GitHub
+issues/PRs and their authors; no consumer telemetry, consistent with the Iron
+Law above.
+
+| Field | Value |
+|---|---|
+| **Probe surface** | [`docs/anti-reskin-gate.md`](../anti-reskin-gate.md) — run-from-clone recipe + signal instructions |
+| **Signal definition** | A distinct external (non-maintainer) GitHub account opening an issue titled `anti-reskin gate: standalone request`, or referencing `lint_originality` in an inbound issue/PR about their own catalog |
+| **Floor** | ≥ 3 distinct external signals |
+| **Window** | 90 days from the probe page landing on `main` |
+| **Floor met** | Extract `lint_originality` as a standalone zero-config npx package (`--changed` mode, no repo coupling, regression suite included); npm publish remains a maintainer decision (name, scope, moment) |
+| **Floor missed** | Extraction **cancelled** — recorded via decision-record; not relitigated without new evidence |
+
 ## Re-audit cadence
 
 Re-audit on each of:

package/docs/contracts/ai-council-config.md

@@ -679,6 +679,31 @@ regression breaks `task consistency`, never the live council.
 `parse_corpus_strict` (Markdown). It runs **before** `task sync`
 rebuilds the lockfile, so it must read whatever the user just edited.
 
+## `model_downgrade` — auto-tiering + the A1↔A3 cache coupling
+
+Since the A3 slice of `road-to-api-cost-optimization` (2026-07-20):
+
+```yaml
+model_downgrade:
+  enabled: true        # default; false disables the size-fit gate entirely
+  auto_apply: true     # DEFAULT since A3 — auto-downgrade is opt-OUT
+  model_tier_override: # per-run escape hatch: member -> pinned model id
+    anthropic: claude-sonnet-4-5
+```
+
+- Small / low-complexity artefacts (per `necessity.classify_size_fit`,
+  character-based) auto-downgrade one ladder rung; the `debate` lens never
+  downgrades.
+- **Cache coupling:** a downgrade is applied only when the model saving beats
+  the forfeited model-scoped prompt-cache reads
+  (`pricing.downgrade_coupling`: `downgrade_savings > lost_cache_savings`,
+  expected reads = rounds − 1). One-shot paths (the low-impact fast-path)
+  have no reads to lose and downgrade to the CHEAPEST ladder rung outright.
+- `model_tier_override` pins a member to a model for the run — classifier and
+  coupling both skipped. Set it per artefact when a specific tier is needed.
+- Requires `model_ladder` on the member (smallest → largest, must include the
+  active `model`).
+
 ## `api_key_ref` forms
 
 Exactly two forms. Raw keys in the yml are a hard validation error.

package/docs/contracts/command-clusters.md

@@ -28,7 +28,7 @@ column 1 of this table.
 
 | Cluster | Phase | Sub-commands | Replaces |
 |---|:-:|---|---|
-| `fix` | 1 | `ci` · `pr-comments` · `pr-bot-comments` · `pr-developer-comments` · `portability` · `refs` · `seeder` · `comments` · `quality` | `fix-ci` · `fix-pr-comments` · `fix-pr-bot-comments` · `fix-pr-developer-comments` · `fix-portability` · `fix-references` · `fix-seeder`; `comments` added 2026-06-22 — audits the **code comments** in the current branch's diff (simplify / shorten / remove), distinct from the PR-review-thread `pr-comments` sub; `quality` added 2026-07-08 — replaces `quality-fix` (slug reorder, `replaces:` alias) |
+| `fix` | 1 | `ci` · `pr-comments` · `pr-bot-comments` · `pr-developer-comments` · `portability` · `refs` · `seeder` · `comments` · `quality` · `route` | `fix-ci` · `fix-pr-comments` · `fix-pr-bot-comments` · `fix-pr-developer-comments` · `fix-portability` · `fix-references` · `fix-seeder`; `comments` added 2026-06-22 — audits the **code comments** in the current branch's diff (simplify / shorten / remove), distinct from the PR-review-thread `pr-comments` sub; `quality` added 2026-07-08 — replaces `quality-fix` (slug reorder, `replaces:` alias); `route` added 2026-07-15 (ecosystem-harvest ergonomics U1) — the classify-and-dispatch entry (adapted from the source's `/smart-fix`; folded into the `fix` verb family to satisfy the ADR-041 controlled-verb vocabulary without a new verb) |
 | `optimize` | 1 | `agents-dir` · `augmentignore` · `rtk` · `skills` · `project` · `prompt` | `optimize-augmentignore` · `optimize-rtk-filters` · `optimize-skills` · former `/optimize agents` and `/optimize agents-md` moved to the `/agents` file-family cluster 2026-05-09; `/agents prepare/audit/cleanup` collapsed into the single `/optimize agents-dir` (flags or wizard) per the agent-doc consolidation; `project` (slug-neutral nest of `optimize-project`, pack move engineering-base → meta) + `prompt` (slug-neutral nest of `optimize-prompt`) added 2026-07-08 — the head now spans agent-layer / project-wide / prompt scopes with a disambiguating menu |
 | `feature` | 1 | `explore` · `plan` · `refactor` · `roadmap` · `dev` | `feature-explore` · `feature-plan` · `feature-refactor` · `feature-roadmap` · `feature-dev` |
 | `chat-history` | 2 | `show` · `import` · `learn` | `chat-history` (legacy status) — `resume` / `clear` / `checkpoint` removed in `road-to-chat-history-hook-only` (auto-adopt + structural hooks); `import` (verbatim cross-session render) and `learn` (project-improving learning extraction) added in the v4 stateless schema |
@@ -37,6 +37,7 @@ column 1 of this table.
 | `roadmap` | 2 | `create` · `ai-council` · `process-step` · `process-phase` · `process-full` | `roadmap-create` · `roadmap-execute` (replaced — autonomous, no per-step gate; `process-phase` is the default execution scope); `ai-council` added 2026-05-07 — wraps `/council default` with `--input-mode roadmap --depth deep` |
 | `module` | 2 | `create` · `explore` | `module-create` · `module-explore` |
 | `tests` | 2 | `create` · `execute` · `e2e-plan` · `e2e-heal` | `tests-create` · `tests-execute`; `e2e-plan` / `e2e-heal` added 2026-07-08 — replace the flat `e2e-plan` / `e2e-heal` (slug reorders, `replaces:` aliases; composite sub-names per ADR-003 §2) |
+| `tdd` | 2 | `red` · `green` · `refactor` | new cluster 2026-07-15 (ecosystem-harvest ergonomics U2) — thin per-phase ergonomic split over the `test-driven-development` skill; each sub drives one TDD phase, no logic duplication. Internal visibility. Bare `/tdd` shows the menu. |
 | `context` | 2 | `create` · `refactor` | `context-create` · `context-refactor` |
 | `override` | 2 | `create` · `manage` | `override-create` · `override-manage` |
 | `judge` | 2 | `solo` · `on-diff` · `steps` | `judge` (legacy standalone) · `do-and-judge` · `do-in-steps` |

package/docs/contracts/mcp-tool-inventory.md

@@ -14,22 +14,22 @@ keep-beta-until: 2026-08-14
 
 ## Summary
 
-- **Total tools:** 28
+- **Total tools:** 31
 - **By transport:** stdio=19
-- **By side-effect:** fs-write=8, ro=17, shell=3
-- **Discovery-only stubs (no implementation):** 9
+- **By side-effect:** fs-write=8, ro=20, shell=3
+- **Discovery-only stubs (no implementation):** 12
 
 ## Tools
 
 | Tool | Side-effect | Transports | Catalog | Handler |
 |---|---|---|---|---|
-| `lint_skills` | `ro` | stdio | [`consumer_tool_catalog.json:7`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L7) | [`tools.ts:1200`](../../src/scripts/mcp_server/tools.ts#L1200) |
-| `chat_history_append` | `fs-write` | stdio | [`consumer_tool_catalog.json:24`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L24) | [`tools.ts:1228`](../../src/scripts/mcp_server/tools.ts#L1228) |
-| `chat_history_read` | `ro` | stdio | [`consumer_tool_catalog.json:43`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L43) | [`tools.ts:1289`](../../src/scripts/mcp_server/tools.ts#L1289) |
-| `memory_lookup` | `ro` | stdio | [`consumer_tool_catalog.json:63`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L63) | [`tools.ts:1365`](../../src/scripts/mcp_server/tools.ts#L1365) |
-| `memory_get` | `ro` | stdio | [`consumer_tool_catalog.json:81`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L81) | [`tools.ts:1432`](../../src/scripts/mcp_server/tools.ts#L1432) |
-| `memory_signal` | `fs-write` | stdio | [`consumer_tool_catalog.json:95`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L95) | [`tools.ts:1541`](../../src/scripts/mcp_server/tools.ts#L1541) |
-| `memory_status` | `ro` | stdio | [`consumer_tool_catalog.json:111`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L111) | [`tools.ts:1456`](../../src/scripts/mcp_server/tools.ts#L1456) |
+| `lint_skills` | `ro` | stdio | [`consumer_tool_catalog.json:7`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L7) | [`tools.ts:1198`](../../src/scripts/mcp_server/tools.ts#L1198) |
+| `chat_history_append` | `fs-write` | stdio | [`consumer_tool_catalog.json:24`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L24) | [`tools.ts:1226`](../../src/scripts/mcp_server/tools.ts#L1226) |
+| `chat_history_read` | `ro` | stdio | [`consumer_tool_catalog.json:43`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L43) | [`tools.ts:1287`](../../src/scripts/mcp_server/tools.ts#L1287) |
+| `memory_lookup` | `ro` | stdio | [`consumer_tool_catalog.json:63`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L63) | [`tools.ts:1363`](../../src/scripts/mcp_server/tools.ts#L1363) |
+| `memory_get` | `ro` | stdio | [`consumer_tool_catalog.json:81`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L81) | [`tools.ts:1430`](../../src/scripts/mcp_server/tools.ts#L1430) |
+| `memory_signal` | `fs-write` | stdio | [`consumer_tool_catalog.json:95`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L95) | [`tools.ts:1539`](../../src/scripts/mcp_server/tools.ts#L1539) |
+| `memory_status` | `ro` | stdio | [`consumer_tool_catalog.json:111`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L111) | [`tools.ts:1454`](../../src/scripts/mcp_server/tools.ts#L1454) |
 | `skill_trigger_eval` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:118`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L118) | _stub-only_ |
 | `suggest_command` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:134`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L134) | _stub-only_ |
 | `suggest_skill_for_task` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:149`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L149) | _stub-only_ |
@@ -37,20 +37,23 @@ keep-beta-until: 2026-08-14
 | `update_form_request_messages` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:178`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L178) | _stub-only_ |
 | `sync_gitignore` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:193`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L193) | _stub-only_ |
 | `sync_agent_settings` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:206`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L206) | _stub-only_ |
-| `run_tests` | `shell` | stdio | [`consumer_tool_catalog.json:220`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L220) | [`tools.ts:1716`](../../src/scripts/mcp_server/tools.ts#L1716) |
+| `run_tests` | `shell` | stdio | [`consumer_tool_catalog.json:220`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L220) | [`tools.ts:1714`](../../src/scripts/mcp_server/tools.ts#L1714) |
 | `run_quality_checks` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:234`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L234) | _stub-only_ |
-| `list_skills` | `ro` | stdio | [`consumer_tool_catalog.json:247`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L247) | [`tools.ts:1470`](../../src/scripts/mcp_server/tools.ts#L1470) |
-| `list_commands` | `ro` | stdio | [`consumer_tool_catalog.json:254`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L254) | [`tools.ts:1485`](../../src/scripts/mcp_server/tools.ts#L1485) |
-| `list_rules` | `ro` | stdio | [`consumer_tool_catalog.json:261`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L261) | [`tools.ts:1500`](../../src/scripts/mcp_server/tools.ts#L1500) |
+| `list_skills` | `ro` | stdio | [`consumer_tool_catalog.json:247`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L247) | [`tools.ts:1468`](../../src/scripts/mcp_server/tools.ts#L1468) |
+| `list_commands` | `ro` | stdio | [`consumer_tool_catalog.json:254`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L254) | [`tools.ts:1483`](../../src/scripts/mcp_server/tools.ts#L1483) |
+| `list_rules` | `ro` | stdio | [`consumer_tool_catalog.json:261`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L261) | [`tools.ts:1498`](../../src/scripts/mcp_server/tools.ts#L1498) |
 | `compile_router` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:268`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L268) | _stub-only_ |
-| `read_resource_body` | `ro` | stdio | [`consumer_tool_catalog.json:281`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L281) | [`tools.ts:1516`](../../src/scripts/mcp_server/tools.ts#L1516) |
-| `roadmap_progress` | `fs-write` | stdio | [`consumer_tool_catalog.json:295`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L295) | [`tools.ts:1575`](../../src/scripts/mcp_server/tools.ts#L1575) |
-| `roadmap_archive` | `fs-write` | stdio | [`consumer_tool_catalog.json:308`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L308) | [`tools.ts:1598`](../../src/scripts/mcp_server/tools.ts#L1598) |
-| `capabilities_index` | `fs-write` | stdio | [`consumer_tool_catalog.json:315`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L315) | [`tools.ts:1614`](../../src/scripts/mcp_server/tools.ts#L1614) |
-| `doctor_report` | `ro` | stdio | [`consumer_tool_catalog.json:328`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L328) | [`tools.ts:1637`](../../src/scripts/mcp_server/tools.ts#L1637) |
-| `conformance_check` | `ro` | stdio | [`consumer_tool_catalog.json:335`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L335) | [`tools.ts:1651`](../../src/scripts/mcp_server/tools.ts#L1651) |
-| `telemetry_report` | `ro` | stdio | [`consumer_tool_catalog.json:342`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L342) | [`tools.ts:1665`](../../src/scripts/mcp_server/tools.ts#L1665) |
-| `council_estimate` | `ro` | stdio | [`consumer_tool_catalog.json:355`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L355) | [`tools.ts:1687`](../../src/scripts/mcp_server/tools.ts#L1687) |
+| `read_resource_body` | `ro` | stdio | [`consumer_tool_catalog.json:281`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L281) | [`tools.ts:1514`](../../src/scripts/mcp_server/tools.ts#L1514) |
+| `roadmap_progress` | `fs-write` | stdio | [`consumer_tool_catalog.json:295`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L295) | [`tools.ts:1573`](../../src/scripts/mcp_server/tools.ts#L1573) |
+| `roadmap_archive` | `fs-write` | stdio | [`consumer_tool_catalog.json:308`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L308) | [`tools.ts:1596`](../../src/scripts/mcp_server/tools.ts#L1596) |
+| `capabilities_index` | `fs-write` | stdio | [`consumer_tool_catalog.json:315`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L315) | [`tools.ts:1612`](../../src/scripts/mcp_server/tools.ts#L1612) |
+| `doctor_report` | `ro` | stdio | [`consumer_tool_catalog.json:328`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L328) | [`tools.ts:1635`](../../src/scripts/mcp_server/tools.ts#L1635) |
+| `conformance_check` | `ro` | stdio | [`consumer_tool_catalog.json:335`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L335) | [`tools.ts:1649`](../../src/scripts/mcp_server/tools.ts#L1649) |
+| `telemetry_report` | `ro` | stdio | [`consumer_tool_catalog.json:342`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L342) | [`tools.ts:1663`](../../src/scripts/mcp_server/tools.ts#L1663) |
+| `catalog_search` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:355`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L355) | _stub-only_ |
+| `catalog_inspect` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:372`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L372) | _stub-only_ |
+| `catalog_load` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:387`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L387) | _stub-only_ |
+| `council_estimate` | `ro` | stdio | [`consumer_tool_catalog.json:401`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L401) | [`tools.ts:1685`](../../src/scripts/mcp_server/tools.ts#L1685) |
 
 ## Glossary
 

package/docs/contracts/tier-3-contrib-plugin.md

@@ -16,7 +16,7 @@ promotion path from Tier-3 → Tier-2, and the non-implementation
 guarantee. Does **not** ship code: `agents/manifests/contrib/` is
 unmanifested until a user asks for an entry by name.
 
-Last refreshed: 2026-05-12.
+Last refreshed: 2026-07-16.
 
 ## Tier definitions
 
@@ -35,8 +35,16 @@ Tier-3 is the explicit overflow bucket.
 The following surfaces are Tier-3 candidates as of 2026-05-12. They
 were surfaced during the
 [`2026-05-12-installer-expansion`](../../agents/runtime/council/sessions/2026-05-12-installer-expansion/synthesis.md)
-council round and have **no entries** in `_VALID_TOOLS`,
-`USER_SCOPE_PATHS`, `SCOPE_SUPPORT`, or the bash `VALID_TOOLS` set.
+council round and had **no entries** in `_VALID_TOOLS`,
+`USER_SCOPE_PATHS`, `SCOPE_SUPPORT` or the bash `VALID_TOOLS` set at
+proposal time.
+
+**Status update (2026-07-16):** the candidates below have since been
+promoted to shipped hosts — each now has entries in `_VALID_TOOLS`,
+`USER_SCOPE_PATHS` and `SCOPE_SUPPORT`, deployed as the universal
+global skill bundle. The bullets are kept as the frozen proposal-time
+record; their rationales describe the pre-promotion state and no
+longer reflect current shipping status.
 
 - `qoder` — community fork, no public adoption signal
 - `trae` — ByteDance IDE, behind login wall
@@ -44,7 +52,7 @@ council round and have **no entries** in `_VALID_TOOLS`,
 - `codebuddy` — Tencent-internal, no public install path
 - `droid` — proposed CLI agent, alpha
 - `warp` — terminal-with-AI; integration shape unclear (PTY vs file marker)
-- `antigravity` — Google research project, no shipping surface
+- `antigravity` — Google's agentic IDE (public since 2026); shipped as a global bundle host (see status update above)
 
 Inclusion in this list is **not** a commitment to ship. Promotion
 requires a real user asking by name (issue, PR, council session, or

package/docs/decisions/ADR-122-adversarial-verification-council.md

@@ -129,7 +129,7 @@ Each settled decision this roadmap does NOT touch:
 
 ## References
 
-- `agents/roadmaps/road-to-adversarial-verification-council.md` — the roadmap.
+- `agents/roadmaps/archive/road-to-adversarial-verification-council.md` — the roadmap.
 - ADR-106 (recursive-verification honest-null), ADR-117 (subagents.auto flip),
   ADR-120 (council chairman mode), ADR-109 (subagent-v1 contract).
 - `docs/CLAIMS.md#adversarial-council-finding-coverage` — the pre-registered claim.

package/docs/development.md

@@ -112,9 +112,18 @@ task tool-validate             # Validate tool declarations
 
 ```bash
 task install -- --target <dir> # Run the installer orchestrator on a target
-task install-hooks             # Install git hooks (pre-commit marketplace lint, pre-push sync check, chat-history bridges)
+task install-hooks             # Install git hooks (pre-commit marketplace lint, pre-push consistency gate, chat-history bridges)
 ```
 
+The **pre-push hook runs `task consistency`** — the exact local mirror of the CI
+"Sync + Generate Tools Consistency" gate (sync + hashes + generate-tools +
+router + corpus + `git diff --quiet`). Any derived-output drift (counts, dist,
+generated tool trees) is blocked **before** the push instead of failing remote
+CI; the fix is `task consistency-fix`, stage, re-push. The hook auto-installs on
+`npm install` in a git clone (the `prepare` script); run `task install-hooks`
+manually if you skipped install scripts. Bypass a genuine WIP push with
+`git push --no-verify`.
+
 ### Local dev install (no release)
 
 Use these tasks to run the working tree as if it were a published

package/docs/featured-skills.md

@@ -1,6 +1,6 @@
 # Featured Skills
 
-A curated subset of the 275 skills. Three tiers, one per primary audience. Full catalog lives in [`dist/agent-src/skills/`](../dist/agent-src/skills/); see also [`docs/catalog.md`](catalog.md) for the complete index and [`docs/featured-commands.md`](featured-commands.md) for command-level highlights.
+A curated subset of the 278 skills. Three tiers, one per primary audience. Full catalog lives in [`dist/agent-src/skills/`](../dist/agent-src/skills/); see also [`docs/catalog.md`](catalog.md) for the complete index and [`docs/featured-commands.md`](featured-commands.md) for command-level highlights.
 
 > **Eval-gated messaging note.** Until `task bench --corpus non-dev` reports `selection_accuracy >= 0.60` (see `road-to-product-adoption.md` Phase 1), this page is documentation, not marketing. The entries below are the candidates the corpus tests against; their description quality is what the eval validates.
 
@@ -92,4 +92,4 @@ task lint-featured-skills
 
 CI runs this in `taskfiles/ci-fast.yml`. Stale entries (renamed / removed skill or command) fail the build. See [`scripts/lint_featured_skills.py`](../src/scripts/lint_featured_skills.py) for the matcher.
 
-→ Browse all 275 skills: [`dist/agent-src/skills/`](../dist/agent-src/skills/) · all 184 commands: [`dist/agent-src/commands/`](../dist/agent-src/commands/)
+→ Browse all 278 skills: [`dist/agent-src/skills/`](../dist/agent-src/skills/) · all 190 commands: [`dist/agent-src/commands/`](../dist/agent-src/commands/)

package/docs/getting-started-by-role.md

@@ -2,7 +2,7 @@
 
 > Pick the entry that matches what you do day-to-day. Each section names the three skills you will reach for first and shows whether MCP (no terminal) or CLI (terminal) is the simpler install path for that role.
 
-`agent-config` ships 275 skills, 105 governed rules, and 184 commands. You do not need all of them. Each role below filters to the slice that pays back in week one; the rest stays available and shows up on demand when a task references it.
+`agent-config` ships 278 skills, 105 governed rules, and 190 commands. You do not need all of them. Each role below filters to the slice that pays back in week one; the rest stays available and shows up on demand when a task references it.
 
 > **Taglines at a glance →** [`docs/role-experiences.md`](role-experiences.md) — the one-line pitch per role experience, in one table.
 

package/docs/getting-started.md

@@ -174,7 +174,7 @@ Your agent now understands slash commands:
 | `/fix quality` | Run and fix all quality checks |
 | `/chat-history import` | Pull a prior session into the current chat (resume) |
 
-→ [Browse all 184 active commands](../dist/agent-src/commands/)
+→ [Browse all 190 active commands](../dist/agent-src/commands/)
 
 ---
 

package/docs/governance-advantage.md

@@ -33,7 +33,7 @@ the host lacks (a static host gives it no runtime attention guarantee, but a
 runtime-only system gives it nothing at all here). A runtime-only system contributes *nothing* on these hosts.
 
 ### 2. Intent routing, not a 500-artefact dump
-A prompt does not load all 275 skills. `dist/router.json` (101 routed rules, intent →
+A prompt does not load all 278 skills. `dist/router.json` (101 routed rules, intent →
 skill, keyword/phrase/path triggers) carries the right skill on intent. The
 governance value is *selection discipline* — the host gets the relevant rule
 set, not the whole catalogue as context ballast.

package/docs/guidelines/component-oriented-and-oop-development.md

@@ -0,0 +1,181 @@
+# Component-Oriented & Object-Oriented Development
+
+> Cross-cutting development standard: **think in reusable units, and — in an
+> object-oriented / class-based codebase — treat object-oriented design as a
+> high-priority default where it reduces complexity.** Split by surface below
+> (frontend / backend), each pointing to the stack-specific carve-outs rather
+> than restating them. Framework-neutral by construction — React / Storybook /
+> Laravel / Symfony specifics live in their own skills, never here.
+
+## Paradigm-appropriate first — detect, then apply
+
+**Reuse is universal; OOP is paradigm-scoped.** Detect the codebase's paradigm
+before applying the object-oriented half: class-based / OO code (PHP, Java, C#,
+typical TS/React service layers) → this standard's OOP guidance is the
+high-priority default. A **functional / pipeline / actor-model** codebase
+(Elixir/Phoenix, Clojure, Haskell, Go-idiomatic, heavy FP-in-TS) → apply *that*
+paradigm's principles (immutability, pure functions, pattern-matching,
+composition of functions), and read the OOP bullets as "the same rigor, its
+paradigm's shape." **Never impose classes on functional code to satisfy this
+standard** — consistency with the codebase's chosen paradigm wins over OOP
+advocacy, always.
+
+## The standard, in one breath
+
+- **Reuse before you build** (every paradigm). Compose from units that already
+  exist — audit first, reuse the design system / shared abstractions, extract a
+  new unit only when the same shape repeats.
+- **Object-oriented where it fits** (in an OO codebase). Encapsulation, single
+  responsibility, composition over inheritance, and behavior-rich objects are
+  the high-priority default *when they reduce complexity* — not a quota to hit,
+  and not imposed on a codebase that has chosen a different paradigm.
+
+## The load-bearing caveat — reuse/OOP is a tool, never a mandate to abstract
+
+This standard **never** authorizes speculative abstraction. It is bounded by the
+package's restraint posture and defers to it on every conflict:
+
+- [`minimal-safe-diff`](../../src/rules/minimal-safe-diff.md) (+ its
+  anti-over-engineering mechanics) — smallest change; no premature abstraction,
+  no speculative feature, no rewrite for taste.
+- [`senior-engineering-discipline`](../../src/rules/senior-engineering-discipline.md)
+  — reuse the *existing* abstraction; generalize, don't overfit; never invent an
+  API to look object-oriented.
+- [`improve-before-implement`](../../src/rules/improve-before-implement.md) —
+  "does it fit the existing architecture?" before adding structure.
+- **When NOT to use a pattern** ([`php/patterns.md`](php/patterns.md) §) — KISS &
+  YAGNI trump pattern purity: no interface for a single implementation, no
+  pattern for a five-line function, no class where a function is clearer.
+
+Rule of thumb: **two real repetitions (or a genuine second axis of change)
+before you extract.** One occurrence is not a component; one branch is not a
+Strategy. A reviewer should be able to name the concrete duplication or the
+concrete change-axis the abstraction removes.
+
+**Precedence (explicit): `minimal-safe-diff` / YAGNI always trump OOP
+advocacy.** When "prefer OO shape" and "smallest change" conflict, the smallest
+change wins — this standard adds a *consideration*, never a competing objective
+that pressures preemptive abstraction. The review lens (below) may flag OO shape
+only where the duplication or the growing branch is **already present in the
+diff**, never as "this could grow later."
+
+## Frontend — think in reusable components
+
+Component-first is the default mindset, not an afterthought: decompose a screen
+into composable units, reuse the project's primitives, and extract shared shells
+when they repeat. Depth and mechanics already live in dedicated skills — consult
+them, don't duplicate:
+
+- [`fe-design`](../../src/skills/fe-design/SKILL.md) § Component Architecture —
+  the stack-agnostic "kind, not framework" taxonomy, granularity, extract-on-3+.
+- [`ui-component-architect`](../../src/skills/ui-component-architect/SKILL.md) —
+  how to *shape* a reusable component: composition over inheritance, slot
+  contracts, prop-API caps, controlled/uncontrolled, the componentization
+  threshold (repeat **and** real state).
+- [`existing-ui-audit`](../../src/skills/existing-ui-audit/SKILL.md) — the
+  reuse-before-invent gate: inventory existing components/tokens/primitives
+  first (enforced by [`ui-audit-gate`](../../src/rules/ui-audit-gate.md)).
+- [`design-tokens`](../../src/skills/design-tokens/SKILL.md) /
+  [`design-system-capture`](../../src/skills/design-system-capture/SKILL.md) —
+  the shared token/design-system layer components draw from.
+
+**Component workshop (Storybook et al.) — when the project is large enough.**
+For a project with a real, growing shared-component library, isolating and
+documenting each reusable component in a component workshop (Storybook or the
+ecosystem equivalent) pays for itself — it makes components discoverable,
+reviewable in isolation, and reused instead of re-invented. It is **not** worth
+the setup for a small surface with a handful of one-off components. The
+framework-specific setup is a carve-out, not a generic mandate — React /
+Storybook specifics: [`react-shadcn-ui`](../../src/skills/react-shadcn-ui/SKILL.md)
+§ Component workshop.
+
+Framework carve-outs (never restated here): React →
+[`react-shadcn-ui`](../../src/skills/react-shadcn-ui/SKILL.md); Next.js
+server/client component boundary →
+[`nextjs-patterns`](../../src/skills/nextjs-patterns/SKILL.md); Laravel FE →
+[`blade-ui`](../../src/skills/blade-ui/SKILL.md) /
+[`livewire`](../../src/skills/livewire/SKILL.md) /
+[`flux`](../../src/skills/flux/SKILL.md); styling →
+[`tailwind-engineer`](../../src/skills/tailwind-engineer/SKILL.md).
+
+## Backend — object-oriented where it reduces complexity
+
+The structural half — thin handlers, business logic in services / use-cases,
+behavior-rich domain models, validation at the boundary — is owned by
+[`architecture`](../../src/rules/architecture.md) and holds across paradigms. In
+an **object-oriented / class-based** service layer, layer the OO principles below
+on top of it, each applied only where it earns its place. In a **functional /
+pipeline** codebase, apply that paradigm's equivalent (pure functions +
+composition instead of behavior-rich objects; a dispatch map / pattern-match
+instead of a Strategy class) — the goal (encapsulate change, one responsibility,
+compose don't duplicate) is paradigm-independent; only its *shape* is OO here:
+
+- **Encapsulation** — objects own their data + the behavior over it; no anemic
+  bags mutated from the outside.
+- **Single responsibility** — one class, one reason to change; no god services.
+- **Composition over inheritance** — inject collaborators; reach for a base
+  class only for genuine is-a substitutability, not code sharing.
+- **Behavior-rich domain objects** — push rules into the model, keep services
+  orchestration-thin.
+- **Patterns where they earn their place** — a Strategy when a branch on a
+  discriminator will grow (`if-else` chain → polymorphism); a Factory when
+  construction is non-trivial; DI on an abstraction when there is a *real*
+  second implementation. Not before.
+
+Language / framework carve-outs (never restated here): PHP →
+[`php-coding-patterns`](php/php-coding-patterns.md) +
+[`patterns.md`](php/patterns.md) (+ `patterns/strategy.md`,
+`patterns/dependency-injection.md`, `patterns/factory.md`, `patterns/service-layer.md`)
++ skills [`php-coder`](../../src/skills/php-coder/SKILL.md) /
+[`php-service`](../../src/skills/php-service/SKILL.md); Laravel →
+[`laravel`](../../src/skills/laravel/SKILL.md); Symfony →
+[`symfony-workflow`](../../src/skills/symfony-workflow/SKILL.md); Next.js / TS →
+[`nextjs-patterns`](../../src/skills/nextjs-patterns/SKILL.md); cross-language
+clean-code baseline → [`code-clarity`](code-clarity.md).
+
+## Enums over scattered literals
+
+A field with two or more non-boolean states is an enum, not a bare string /
+magic number — the small OO move that keeps a codebase greppable and safe to
+change. Full rule + the defer-and-ask flow for pre-existing literals:
+[`prefer-enums-over-literals`](../../src/rules/prefer-enums-over-literals.md).
+
+## How this is reviewed
+
+"Reuse existing components + object-oriented shape (where it reduces
+complexity)" is a check on the code-quality review lens
+([`judge-code-quality`](../../src/skills/judge-code-quality/SKILL.md)), so it
+reaches `/review-changes`, `/judge`, the subagent judge modes, and team-mode's
+fallback review frame. It fires **only where the duplication or the growing
+branch is already present in the diff** — never "this could grow later" — and
+in the **codebase's own paradigm** (it will not tell a functional service to
+grow a class). It stays a human-judgment call that defers to the codebase's own
+conventions — never a generic SOLID dogma imposed over a project that has chosen
+differently.
+
+## Council review (2026-07-15)
+
+Deep debate, 3 rounds, cross-vendor (`anthropic/claude-sonnet-4-5` +
+`openai/gpt-4o`), $0.16. Split verdict; the load-bearing (anthropic) critique —
+that an "OOP-supreme default" over-indexes on OOP for a multi-paradigm consumer
+base and can conflict with `minimal-safe-diff` — was applied, bounded by this
+standard's stated purpose (OOP *is* a deliberate high priority for the operator):
+
+- **Paradigm-appropriate framing** — OOP is the high-priority default *within an
+  OO / class-based codebase*; detect and defer to a functional / pipeline /
+  actor paradigm; never impose classes on functional code (§ Paradigm-appropriate).
+- **Explicit precedence** — `minimal-safe-diff` / YAGNI win on conflict; the
+  review lens flags only *already-present* duplication / complexity, never
+  preemptive (§ caveat, § How this is reviewed).
+
+Divergence held: the frontend section stays (an intentional FE / backend
+entry-point + carve-out index, per the operator's explicit "split by FE /
+backend" ask) — against the anthropic "delete as redundant"; it is a cohesive
+index of the existing FE surfaces, not a claim of novel guidance. Trace:
+`agents/runtime/council/responses/component-oop-standard.json/` (gitignored, local-only).
+
+## See also
+
+- [`architecture`](../../src/rules/architecture.md) — the structural home this layers onto.
+- [`code-clarity`](code-clarity.md) — the cross-language clean-code baseline.
+- [`minimal-safe-diff`](../../src/rules/minimal-safe-diff.md) · [`senior-engineering-discipline`](../../src/rules/senior-engineering-discipline.md) — the restraint anchors this standard is bounded by.

package/docs/proof.md

@@ -27,7 +27,7 @@ evidence pointer, or `task check-claims` fails the build.
 | Claim | Kind | Evidence | Resolves |
 |---|---|---|---|
 | The release process is documented as an inheritable runbook + succession doc, and the project's bus-factor (trailing-90-day distinct human reviewers) is tracked and reported truthfully — currently 1, not implied to be more. | qual | `docs/succession.md#trailing 90 days` | ✅ |
-| 184 commands. | quant | `src/scripts/check_artefact_count_messaging.ts#Artefact-count messaging gate` | ✅ |
+| 190 commands. | quant | `src/scripts/check_artefact_count_messaging.ts#Artefact-count messaging gate` | ✅ |
 | A MEASURED-BUT-NOT-SHIPPED experiment — the thin rule projection reduced eager rule load 78,513 → 13,881 GPT-tokens (whole always-loaded projection 98,529 → 33,897, ~65.6%), but FAILED the quality gate (thin win-rate 36.2% vs required 48%) and does not ship; it un-defers only behind `discipline_profile: essential`. Shipped behavior does NOT include this reduction. Method: `agent-config benchmark` over the pinned token baseline; the baseline is the honest "what the user pays if everything loads eagerly", NOT a synthetic full-corpus strawman (council Q4); quality gate per the Phase-0 paired judge run. | quant | `internal/bench/reports/token-baseline.json#eager_rule_load` | ✅ |
 | The first cross-vendor parity pass (5 orchestration-corpus tasks × 2 vendors × 3 repeats, identical prompts via the council transport, $0.16) measured real per-host finding-count differences — claude-sonnet-4-5 surfaced ~2× the findings of gpt-4o on the multi-file analysis task (median 11 vs 5) while both vendors were identical on the planted hollow-implementation task (2 vs 2) and perfectly silent on the clean-code negative control (0 vs 0, no spurious findings). The per-task `finding_floor` values are calibrated from the cross-host lower envelope and the gate is armed. | quant | `internal/bench/reports/parity-count.json#min over hosts of median` | ✅ |
 | On a weak host (claude-haiku-4-5) the package produces a significant, placebo-controlled discipline lift on scope/downstream traps; on a strong host the same measurement is a published null — the package transplants discipline a weak model lacks, not model intelligence. | quant | `docs/benchmark.md#weak-host-specific` | ✅ |
@@ -40,15 +40,17 @@ evidence pointer, or `task check-claims` fails the build.
 | A hand-rolled, dependency-free BM25 + trigram lexical index resolves the "recalls but does not rank" gap: on the retrieval-precision corpus (9 keyword-overlapping-confuser tasks) it drives the mean top tie-set from 3.333 (the `_score` bucket scorer) to 1.0 — every needed decision uniquely top-ranked — with precision@1 and precision@5 unchanged at 1.0. Method: deterministic, model-free re-ranking of the SAME retrieved entry set; both scorers measured over the identical store via `measure_lexical_ranking.ts`. | quant | `internal/bench/reports/lexical-ranking.json` | ✅ |
 | The whole layer is compiled into host agents with zero runtime daemon. | qual | `docs/contracts/no-runtime-boundary.md#file-first, no-runtime suite` | ✅ |
 | On a 12-fixture option-decision corpus (3 arms × 2 providers, blind rubric judge claude-opus-4-8, pre-registered hypotheses), famous-figure identity framing added nothing beyond the underlying method text (method 5.04 vs figure 4.88, Δ=0.17, sign-test p=0.607), and provider diversity moved judged quality ~15× more than persona identity (provider Δ=2.58 vs identity Δ=0.17); the whole persona layer lifted only +0.08 over bare prompts. Honest null — persona panel-mode stays CUT, evidence-closed. | quant | `internal/bench/reports/persona-placebo.json#honest-null` | ✅ |
+| The only agent layer that publishes the runs where it changed nothing. Deliberately falsifiable — if a reader finds a comparable agent layer publishing its own honest-null benchmark runs, this line updates; that is the point. | comparative | `docs/benchmark.md#honest` | ✅ |
 | On the live end-to-end retrieval benchmark (9 tasks × 3 arms × 3 seeds on claude-haiku, fixture store with keyword-overlapping confusers), the memory retrieval substrate scored precision@5 = 100% (9/9) with 100% poisoned-entry rejection, and the retrieval-on arm passed 27/27 model-scored tasks vs 2/27 with retrieval off and 4/27 with a placebo injection. Known limit stays published: mean tie-set 4.1 means top-k ties break by store order, not relevance (the ADR-116/FTS5 signal). | quant | `internal/bench/reports/second-brain-retrieval.json#retrieval-on` | ✅ |
 | 105 governed rules. | quant | `src/scripts/check_artefact_count_messaging.ts#Artefact-count messaging gate` | ✅ |
 | On a deterministic multi-session recall corpus, the memory substrate produces a measured, placebo-controlled recall lift — memory-on 27/27 vs no-memory 10/27 and vs equal-byte placebo 9/27 (claude-haiku-4-5, n=9 tasks x 3 seeds, sign test p=0.031 for BOTH pairings). Scoped honestly: this is the context-value upper bound (perfect retrieval on a one-fact-per-task corpus), not retrieval precision under a large store. | quant | `internal/bench/reports/second-brain-delta.json` | ✅ |
 | Removing the perfect-retrieval assumption, the substrate's REAL keyword retrieval recalls the needed decision into the top-5 under keyword-overlapping confusers (precision@5 9/9) and the model disambiguates it from the co-injected confusers — retrieval-on 27/27 vs no-memory 5/27 and vs equal-count placebo 5/27 (claude-haiku-4-5, 9 tasks x 3 seeds, sign test p=0.008 both). Named limit: retrieval RECALLS but does not RANK (mean tie-set 3.3, ties broken by store order, not relevance) — the discrimination gap that motivates the SQLite-FTS5 activation path (ADR-116) at larger scale. | quant | `internal/bench/reports/second-brain-retrieval.json` | ✅ |
 | Every artifact the package ships — source AND the condensed projection that reaches consumers — is machine-scanned in CI for hidden-Unicode, mixed-script-confusable, and instruction-smuggling payloads (the rules-file-backdoor class); a finding blocks the release before `npm publish`, not just the merge. | qual | `.github/workflows/publish-npm.yml#lint_agent_security` | ✅ |
-| 275 skills. | quant | `src/scripts/check_artefact_count_messaging.ts#Artefact-count messaging gate` | ✅ |
+| 278 skills. | quant | `src/scripts/check_artefact_count_messaging.ts#Artefact-count messaging gate` | ✅ |
 | Removes only its own keys from a shared host config (matched by JSON-pointer + SHA-256), never a neighbour tool's entries. | qual | `docs/contracts/install-layout.md#JSON-pointer` | ✅ |
+| On the A3 orchestration eval (deterministic verify, measured token deltas), the production-validator subagent returned the correct verdict on both fixtures — NOT READY with the exact `file:line` citation on a planted hollow implementation, READY with zero spurious findings on the clean control — while consuming ~45k fewer tokens than the inline-host baseline on each task. Scope: two planted fixtures on a Claude Code host, not a broad hit-rate. | quant | `internal/bench/orchestration/pv-a3-results.md#token_delta_provenance: measured` | ✅ |
 
-**21 backed claim(s)** — all evidence pointers resolve in CI.
+**23 backed claim(s)** — all evidence pointers resolve in CI.
 
 Artefact counts in public prose (skills, commands, governed rules,
 guidelines, personas) are **generated from source and CI-drift-checked**:
@@ -77,11 +79,11 @@ shipping theater; the full per-cell data is committed at
 `internal/bench/reports/persona-placebo.json`.
 
 **Behavioural-eval coverage — the honest baseline.** Skill *quality* is only
-as good as its measurement. Today **42 of 275** skills carry a behavioural
+as good as its measurement. Today **42 of 278** skills carry a behavioural
 `evals.json`; the highest-traffic / highest-cost tiers (default-surface +
 `rich` + routers) are **fully covered (35 of 35)**, the long tail
-(7 of 240) is not. We publish that gap rather than imply
-"275 evaluated skills": coverage is measured per tier
+(7 of 243) is not. We publish that gap rather than imply
+"278 evaluated skills": coverage is measured per tier
 (`./scripts-run src/scripts/skill_eval_coverage`), **CI-ratcheted so it can
 only rise**, and the priority tiers carry a hard **tier floor**: every
 rich / default-surface / router skill MUST have a behavioural eval or an
@@ -152,6 +154,8 @@ that (`task check-comparison`), so this column can never lie.
 | Capability/benchmark results are published — including the runs where the package changed nothing. | [`docs/benchmark.md`](../docs/benchmark.md) | A category headline figure (e.g. an '84.8%' score) appears across marketing surfaces with no reproducible methodology published — so it cannot be verified either way. | ✅ |
 | Every public claim binds to machine-checked evidence. | [`docs/CLAIMS.md`](../docs/CLAIMS.md) | Marketing claims in this category are not bound to a machine-checked ledger a reader can reproduce. | ✅ |
 | Skills publish their own known limits, each with a witness test. | [`tests/scripts/witness/check_refs_relative_gap.test.ts`](../tests/scripts/witness/check_refs_relative_gap.test.ts) | Published known-limitation surfaces backed by reproducing tests are not a standard artifact in this category. | ✅ |
+| A 30-second single-file wedge exists — one read-only subagent, one command, verdict with file:line — and its promise is a scoped, published eval, not a feature list. | [`internal/bench/orchestration/pv-a3-results.md#token_delta_provenance: measured`](../internal/bench/orchestration/pv-a3-results.md) | Category entry points typically install the full platform (profiles, packs, runtime) before the first felt win; single-artifact entries with a published eval behind the promise are not a standard artifact. | ✅ |
+| The persona-identity question was tested and published as an honest null (identity swap ~zero effect, provider choice ~15x larger) instead of being shipped as theater. | [`internal/bench/reports/persona-placebo.json#honest-null`](../internal/bench/reports/persona-placebo.json) | Named-persona prompts are shipped as a feature across the category without a published A/B separating identity from method. | ✅ |
 
 ## 5. Verify it yourself
 

package/docs/self-review-gate.md

@@ -37,6 +37,20 @@ no-op** (never a failing check) — exactly the `cross-model-canary.yml` pattern
   `enforce: false` (advisory always returns `0` and reports the would-block
   set).
 
+## Escalation on large / claim-affecting diffs
+
+The two in-session lenses are a floor. A **large** diff (≥ 400 changed lines
+across reviewable files) or one that touches a **claim-affecting surface**
+(`docs/CLAIMS.md`, `docs/proof.md`, `docs/comparison.yaml`, or `README.md`)
+warrants the full `ai-council` advisor panel — a spend-bearing multi-model run.
+
+Per blocker `self-review-gate-cost`, the paid council stays governed by the
+standing spend-authorization discipline **at run time**. So the gate does not
+fire council calls itself: `escalationReasons(files, changedLines)` (pure,
+unit-tested) DETECTS the condition, the dry-run plan prints it, and the posted
+review RECOMMENDS a maintainer `/council:pr` run. Detection is deterministic
+and zero-spend; the multi-model run is the maintainer's run-time act.
+
 ## Arming it (maintainer, one flip)
 
 1. Add the `ANTHROPIC_API_KEY` repo secret (per-PR budget sign-off) — turns