@event4u/agent-config 16.3.0 → 16.5.0

package/.augment-plugin/marketplace.json

@@ -1,20 +1,20 @@
 {
   "name": "event4u-agent-config",
   "description": "Governed agent system — skills, rules, commands, and guidelines for AI-assisted development.",
-  "version": "16.3.0",
+  "version": "16.5.0",
   "owner": {
     "name": "event4u",
     "email": "dev@event4u.app"
   },
   "metadata": {
     "description": "A policy-driven execution system that enforces quality, consistency, and developer-like behavior for AI agents.",
-    "version": "16.3.0"
+    "version": "16.5.0"
   },
   "plugins": [
     {
       "name": "agent-config",
       "description": "Full governed agent system — rules, skills, commands, guidelines, and runtime tooling.",
-      "version": "16.3.0",
+      "version": "16.5.0",
       "source": ".",
       "category": "governance",
       "tags": [

package/.augment-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "agent-config",
   "description": "A governed skill framework for AI agents — runtime execution, tooling, observability, feedback, and lifecycle management with policy-driven quality enforcement.",
-  "version": "16.3.0",
+  "version": "16.5.0",
   "author": {
     "name": "event4u",
     "email": "dev@event4u.app"

package/.claude-plugin/marketplace.json

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

package/CHANGELOG.md

@@ -32,6 +32,69 @@ Entry-shape contract: [`docs/contracts/CHANGELOG-conventions.md`](docs/contracts
 
 ### Changed
 
+- **46 settings keys are retired; an install that never changed them sees no
+  difference.** Each key's shipped default is now fixed behavior: every reader
+  of it — code, rule and command prose, the wizard — was rewritten to that
+  default in the same change. **If your `.agent-settings.yml` still sets one,
+  that value is ignored** and the loader prints one line per key —
+  `<key> was removed (<what decides instead>); ignored.` — so a non-default
+  value you chose is lost visibly, never silently. Delete the line to silence
+  it. The keys:
+  - Output and tone: `telegraph.speak`, `tokens.rich_skills`, `personal.minimal_output`, `personal.play_by_play`, `personal.pr_comment_bot_icon`, `verbosity.intent_announcements`, `verbosity.preview_artifacts`, `verbosity.routine_confirmations`, `verbosity.post_action_reports`.
+  - Reasoning protocol switches: `reasoning.auto_gate`, `reasoning.components.orchestrator`, `reasoning.components.notes_first`, `reasoning.components.grounding`, `reasoning.components.intent`, `reasoning.components.complexity_first`, `reasoning.components.verifier_default`, `reasoning.components.prediction_tracking`, `reasoning.components.decision_ledger`, `reasoning.components.uncertainty_budget`.
+  - Roadmap cadence: `roadmap.skip_pre_run_gate`, `roadmap.dashboard_regen_cadence`.
+  - Command suggestion and PR creation: `commands.auto_detect`, `commands.suggestion.enabled`, `commands.suggestion.confidence_floor`, `commands.suggestion.cooldown_seconds`, `commands.suggestion.max_options`, `commands.create_pr.api_examples`, `commands.create_pr.ui_paths`, `commands.create_pr.api_paths`.
+  - Memory and knowledge sharing: `memory.cadence`, `memory.review_threshold`, `knowledge.global_sharing.redaction.enabled`, `knowledge.global_sharing.redaction.halt_on_trigger`, `knowledge.global_sharing.auto_promote_threshold`, `knowledge.global_sharing.freshness.hypothesis_after_days`, `knowledge.global_sharing.freshness.stale_after_days`.
+  - Hooks and engine: `hooks.concern_budget.max_per_event`, `hooks.concern_budget.hard_fail`, `decision_engine.surface_traces`, `decision_engine.on_block_fallback`, `explain.enable_last`.
+  - Remaining: `project.pr_template`, `pipelines.skill_improvement`, `consistency.cross_source`, `subagents.downshift`, `ai_team.suppress_setup_hint`.
+  The reference page lists each key with the behavior that replaces it
+  (`templates/agent-settings.md` § Retired keys).
+
+- **A medium security finding now needs a disposition before a release
+  ships.** `check_finding_dispositions` treats `security × medium` as blocking
+  for every release after 16.3.0 (council 2026-10-07, 2/2). Such a row must
+  carry `fixed` (with its commit), `false_positive` or `accepted_risk`, each
+  with a rationale and a `verified_by`, like any blocking row, and
+  `still_open` keeps the release red with a message saying so. On a release
+  pull request (`--pr`), a medium security finding the self-review reported
+  but the ledger lacks is red too. Releases up to 16.3.0 are judged as they
+  shipped. The merge gate (`self_review_gate.classifyBlocking`) is unchanged,
+  so on every other pull request the finding only advises. `claim × medium`
+  stays advisory in both.
+- **No spend bound applies unless you set one.** Owner directive, 2026-10-05,
+  recorded as **ADR-279** and accepted on the owner's own answer (option (a))
+  on 2026-10-06. With nothing configured, no USD or token ceiling this package
+  defines stops a council run, a debate or a paid gate, and none of them asks —
+  because no ceiling exists to ask about. Every ceiling remains settable and
+  behaves exactly as its contract describes once set.
+  **Your own council file is not rewritten.** If you copied
+  `agents/templates/.ai-council.yml.example` before this release it carries
+  these lines explicitly, and they are your figures now:
+  `cost_budget.max_input_tokens: 500000`, `cost_budget.max_output_tokens:
+  200000`, `cost_budget.max_total_usd: 20.0` and `debate.max_cost_usd: 5.00`.
+  Delete them to become unbounded; keep them to stay bounded. The shipped
+  defaults behind an absent key moved to `0` in all three layers — the loader,
+  the command's own fallback for a file with no `cost_budget` block, and the
+  `CostBudget` constructor.
+  **`max_calls` and the debate round limits did not move**: they bound call
+  count per invocation, not money. Nor did any of the controls listed under
+  § What stays in ADR-279 — provider refusals, the per-day plan-quota guards,
+  the `--confirm` a class-1 gate asks for, the debate's between-round
+  confirmation, or the budget an unattended run must still be given.
+  **Two defects were repaired in the same change, and both could bite a
+  configured install.** `0` was documented as disabling a token cap and did
+  not — the two token comparisons carried no zero guard while the two USD
+  comparisons beside them did, so a budget with every cap at zero breached on
+  a ten-token estimate. And the class-1 gate's two caps had to BOTH be set
+  before EITHER applied, so setting one left you bounded by neither. Each cap
+  now bounds alone.
+  **One optional hard stop now works for the first time.** With
+  `cost.enforcement: hard-stop` and a budget configured, the cost preflight
+  resolved its budget script relative to the working directory, read the
+  resulting empty output as "no budget configured", and exited `0` on a spent
+  budget from every working directory. It now resolves the script from its own
+  location and exits non-zero as its contract always said it would.
+
 - **`agent-config init` no longer overwrites a managed file you have edited.**
   Owner ruling, 2026-09-21, taken after an AI council split 1/1 on it. Until
   now the installer's `_resolve_file_conflict` returned `write` for every
@@ -125,6 +188,79 @@ Entry-shape contract: [`docs/contracts/CHANGELOG-conventions.md`](docs/contracts
 
 ### Added
 
+- **An old project keeps its real commit format — `agent-config git:convention
+  measure`.** A repository with no declared convention and no approved card is
+  now measured instead of silently given Conventional Commits: the verb samples
+  the non-merge history of the default branch, resolved as the carrier resolves
+  it (the server's symref, then `refs/remotes/origin/HEAD`) — with no default
+  branch it says so and exits `1` rather than sampling `main`, `master` or the
+  current branch in its place — drops bots, automation and bulk imports, caps
+  each author per half, and names the established subject family or — below the
+  bar — the two strongest. It also proposes a `branch_pattern` from the remote
+  branch names (or reports no clear pattern) and shows the observed update style,
+  which it never adopts. The thresholds are constants of the module the verb
+  runs and are rendered into the commit-subject reference, not restated by hand.
+  `show` and `subject` print `no convention established — run git:convention
+  measure` in that state (`convention_established` under `--json`; exit codes
+  unchanged). An interactive `/commit` asks once — the established family or the
+  two strongest against Conventional Commits — and writes the answer to the
+  approved convention card, also when the answer is Conventional, so the question
+  is never repeated; `/commit:in-chunks` never asks and reports the measurement.
+  Where the choice maps to a setting, `measure` prints the ready-to-commit
+  `.git-convention.yml` (`commit_format`, `branch_pattern`, never
+  `update_strategy`); a human creates and commits it, the agent never writes it.
+
+- **A team's git convention can be declared instead of measured — the new
+  `git:` settings block.** Three Class-C keys, each defaulting to the
+  behaviour every install had before, so an install that sets nothing is
+  unchanged. `git.commit_format: ticket-conventional` writes
+  `DEV-1234 feat(exporter): …` instead of `feat(DEV-1234): …` and treats a
+  ticket in the scope as a wrong subject; `/commit` and `/commit:in-chunks`
+  validate against the regex for the configured format, and the
+  conventional-commits-writing classifier gains a `ticket-conventional` family
+  so such a history is no longer misread as free-text ticket prefixes.
+  `git.branch_pattern` (`{type}`, `{ticket}`, `{slug}`) shapes the branches
+  `/worktree:create` proposes; reading a ticket back out of a branch now takes
+  the first `[A-Z][A-Z0-9]+-[0-9]+` token that is not a standard name (`UTF`,
+  `ISO`, `SHA`, `RFC` prefixes), so `DEV-1234-device-export` yields its ticket.
+  Under `git.update_strategy: rebase`, `/create-pr` asks for
+  `git rebase origin/<base>` plus `--force-with-lease`, and `/pr:merge`,
+  `/prepare-for-review` and `/review:changes` report a behind branch instead of
+  updating it; none of them merges the base into a feature branch — one git-workflow reference
+  (`references/branch-update.md`) now owns that decision, and
+  `sync_pr_branch` exits `3` instead of merging when such a branch is behind
+  (a current branch still exits `0`). **What it does not do:** the setting picks the operation and never
+  authorises it; git-history-discipline still requires the user's request for
+  every rebase, fixup or autosquash. A team declares the keys in
+  `.git-convention.yml`, a tracked file at the repository root that overrides
+  every developer settings file and where either value is a declaration
+  (ADR-283): `git.update_strategy` is read from it at the commit a pull request
+  is judged against, so a worktree, a fresh clone and CI agree and a pull
+  request cannot change the strategy its own update is judged by;
+  `git.commit_format` and `git.branch_pattern` are read at `HEAD`. Without the
+  carrier the keys come from the project settings files as before; the
+  user-global file does not carry them, and the settings GUI no longer offers
+  them while it writes there. `agent-config git:convention show` prints the
+  value in force, the commit it was read at and a differing checkout value as
+  a candidate; `show --key` judges only the named keys. The commit is the
+  `--base` given — a pull request passes `--base origin/<its base>` — else the
+  default branch; nothing asks the forge. A carrier that does not parse makes
+  `sync_pr_branch` exit `4`, a target that names no commit exit `1`, and a named
+  commit that cannot be fetched is `unverified`; none of them merges. A target
+  that moves between the strategy read and the merge is read again at the
+  commit being merged, which is governed by the strategy it carries: the same
+  strategy goes on against it, another one exits `1` before anything is
+  merged. A blank `--base` is a usage error (exit `2`) in `sync_pr_branch`,
+  `git:convention show` and `sync`, and `check_branch_freshness`, never read
+  as no `--base`. A commit-linting config
+  in the repository still outranks `git.commit_format`. In a packed consumer
+  install `git:convention show` is the git surface that resolves, and the
+  consumer matrix proves it with a `git-convention` leg; `sync_pr_branch` and
+  `check_branch_freshness`, which `/pr:merge`, `/create-pr`, `/fix:ci` and
+  `/roadmap:next` run through `./scripts-run`, still need a source checkout of
+  this package.
+  The merge method is not a key: `/pr:merge` already reads it from the forge.
+
 - **A push no longer ships a branch whose tree contradicts its own commits.**
   `check_branch_work_committed` runs first in the pre-push hook, and it exists
   because this branch produced the defect it guards: a merge-reconciled baseline
@@ -735,109 +871,73 @@ Entry-shape contract: [`docs/contracts/CHANGELOG-conventions.md`](docs/contracts
 > keeps the active era under the 250-line drift cap enforced by
 > `tests/test_changelog_eras.py`.
 
-# Era: 16.3.x — current
+# Era: pre-16.5.0 — archived
 
-> Started at `16.3.0`. Full entries live inline below.
+> All entries before `16.5.0` live in
+> [`docs/archive/CHANGELOG-pre-16.5.0.md`](docs/archive/CHANGELOG-pre-16.5.0.md).
+> The archive is read-only; git tags remain the canonical
+> source for what shipped. Splitting them out of the main file
+> keeps the active era under the 250-line drift cap enforced by
+> `tests/test_changelog_eras.py`.
+
+# Era: 16.5.x — current
+
+> Started at `16.5.0`. Full entries live inline below.
 > The drift test caps this era at 250 lines of entry body; growth past
-> that forces a new era split (`# Era: 16.4.x`, etc.) — see
+> that forces a new era split (`# Era: 16.6.x`, etc.) — see
 > [`docs/contracts/CHANGELOG-conventions.md § Era splits`](docs/contracts/CHANGELOG-conventions.md).
 
-## [16.3.0](https://github.com/event4u-app/agent-config/compare/16.2.0...16.3.0) (2026-10-05)
+## [16.5.0](https://github.com/event4u-app/agent-config/compare/16.4.0...16.5.0) (2026-10-12)
 
 ### Release highlights
 
-- **Behaviour changes:** Rule links that name a path the repository actually has, and the blocker that held them (#2185) (8031e09); Rule laws that can stand, and the class whose law stands with them (#2177) (9e2fe18); 100 % roadmaps archive — bare deferrals carried, owner blockers ask step by step (#2167) (074eee6); make the two pack-boundary gates green on the trunk and run the workflow-security audit in CI (#2155) (90a0ad5); A release record that says what it reviewed, and an index with every major (#2157) (8e30a53).
+- **Behaviour changes:** give hand-authored SVG a witness, an owner, and five recorded runs (#2300) (bdeb65c).
 - **Default changes + migration:** _none_
-- **Security and correctness:** 100 % roadmaps archive — bare deferrals carried, owner blockers ask step by step (#2167) (074eee6); make the two pack-boundary gates green on the trunk and run the workflow-security audit in CI (#2155) (90a0ad5).
+- **Security and correctness:** close the two real findings of the third 16.5.0 review, plus road-to-svg-witness-provenance (#2309) (d1f7c3b); close the security findings from the 16.5.0 re-cut review (#2307) (9904258); close the five medium-security findings from the 16.5.0 release review (#2305) (5593838); close the sixth review round of #2302 (#2303) (c88865f); strip only generic glob classes from an inbox name (fda00b3); admit a date suffix only on the families that are dated (fd5be56); +3 more.
 - **Honest nulls:** _none_
-- **Known limitations:** An installed layer measured against its limit, and the consent an installer must have before thinning (#2201) (src/scripts/install.ts declares a residual) (df7ea79); Two Phase-0 instruments closed against measurement, and the third blocked by a record rather than a ceiling (#2198) (src/scripts/check_standing_rule_delivery.ts declares a residual) (92027a2); A rule carrier that delivers what the install carries, in the host's form, in a string the host keeps (#2182) (src/scripts/install.ts declares a residual) (7fdfd0a); Rule triggers and installed links that hold (#2174) (src/scripts/install.ts declares a residual) (328a21b); A tree that keeps its neighbours (#2161) (src/scripts/install.ts declares a residual) (4399b5a); make the two pack-boundary gates green on the trunk and run the workflow-security audit in CI (#2155) (90a0ad5); +2 more.
+- **Known limitations:** _none_
 
-> **Governance mix:** governance-only 23 vs consumer-only 1 (taxonomy 1.1.0).
+> **Governance mix:** governance-only 6 vs consumer-only 1 (taxonomy 1.1.0; range d411219277ce..d1f7c3b834bb).
 
 ### Features
 
-* **commands:** /roadmap:resolve-blockers — council first, owner one question at a time (#2204) ([5ddfc05](https://github.com/event4u-app/agent-config/commit/5ddfc05819a501b1066b713571e9073d1ce435c9))
-* **commands:** /roadmap:triage-parked — drain later/ and skipped/ (#2184) ([ab516fc](https://github.com/event4u-app/agent-config/commit/ab516fc19a420a7022eb7dc5f8b16f6d033fc6e8))
-* **evidence:** classify the evidence tree by reference, and rule out a cold location (#2153) ([590cebc](https://github.com/event4u-app/agent-config/commit/590cebc729a7a45fbe98e2ee55b8f231ac0329c2))
-* **hooks:** run the project's own quality tools over the files a turn edited (#2152) ([d4760bb](https://github.com/event4u-app/agent-config/commit/d4760bb4f47b7be902c9ec3b88c51d8aa818311e))
-* **memory-learn:** open the learning dogfood window and give it a screen (#2151) ([162889e](https://github.com/event4u-app/agent-config/commit/162889e8b16359904766927a7fbd896f961ed9b9))
-* **ui:** flip the carried-nothing shadow to a halt, closing road-to-a-ui-coverage-ledger-that-can-fail (#2149) ([cbd5d07](https://github.com/event4u-app/agent-config/commit/cbd5d07fe21af3a3de12e847b3b8da7f86f8bb81))
+* **svg:** close all three SVG roadmaps — routing, review follow-ups and the live-session findings (#2302) ([5098697](https://github.com/event4u-app/agent-config/commit/50986972088029db18a90c6f7d198c5ab0e26da5))
+* give hand-authored SVG a witness, an owner, and five recorded runs (#2300) ([bdeb65c](https://github.com/event4u-app/agent-config/commit/bdeb65c37533825c2a3061fb7a33ef5778454d11))
 
 ### Bug Fixes
 
-* **archival:** 100 % roadmaps archive — bare deferrals carried, owner blockers ask step by step (#2167) ([074eee6](https://github.com/event4u-app/agent-config/commit/074eee6881d19b5f6d7ec8574a83c26dffd25353))
-* **gates:** make the two pack-boundary gates green on the trunk and run the workflow-security audit in CI (#2155) ([90a0ad5](https://github.com/event4u-app/agent-config/commit/90a0ad522d49a853d30ffb6f1fec46e2b802ae35))
-* **hooks:** make the bundle ceiling describe the trunk it defends (#2165) ([c399d09](https://github.com/event4u-app/agent-config/commit/c399d097eea2f30676b36604a2514ff0e22cd46d))
+* **svg:** close the two real findings of the third 16.5.0 review, plus road-to-svg-witness-provenance (#2309) ([d1f7c3b](https://github.com/event4u-app/agent-config/commit/d1f7c3b834bb43b8937dee44b7e38733d5eb70f2))
+* **svg:** close the security findings from the 16.5.0 re-cut review (#2307) ([9904258](https://github.com/event4u-app/agent-config/commit/990425836285eded0a6cb4370f8ded95823dd6c8))
+* **svg:** close the five medium-security findings from the 16.5.0 release review (#2305) ([5593838](https://github.com/event4u-app/agent-config/commit/5593838c01fab686e0856fba227ae4f37cd7b8f0))
+* **svg-engine:** close the sixth review round of #2302 (#2303) ([c88865f](https://github.com/event4u-app/agent-config/commit/c88865fdc1aad9337b4f98a868483d571848d7ea))
+* **hooks:** strip only generic glob classes from an inbox name ([fda00b3](https://github.com/event4u-app/agent-config/commit/fda00b35ef5a0d2b603b56511a986081a261dc11))
+* **hooks:** admit a date suffix only on the families that are dated ([fd5be56](https://github.com/event4u-app/agent-config/commit/fd5be56f6f17ebe96b17579ffdd452cbef3dfc39))
+* **hooks:** accept only wildcard-suffixed family heads and keep bracket payloads ([8446cc0](https://github.com/event4u-app/agent-config/commit/8446cc05e322c6d084df502319daff8c1bc79e63))
+* **hooks:** let a glob over an opaque family prefix through block-speaking-inbox-dir ([22904a5](https://github.com/event4u-app/agent-config/commit/22904a51d58dd8d3bbed7a6db08b717b7336adb1))
+* **lineage:** count a present non-road-to parent as present ([4b40ab6](https://github.com/event4u-app/agent-config/commit/4b40ab692f85bbc2b642f98603a9d601879cd5a1))
 
 ### Documentation
 
-* **roadmaps:** drain road-to-leading-every-row — install above the fold, commit-mix baseline, seven owner questions put (#2148) ([8f32c31](https://github.com/event4u-app/agent-config/commit/8f32c316b489f6b8decfdacf57da72149e07dbd5))
-* **roadmaps:** land four roadmaps from inbox round inbox-2026-10-c (#2150) ([07f83a1](https://github.com/event4u-app/agent-config/commit/07f83a1f681869b9cea467f2ad88e5642ef55af9))
-* **roadmaps:** use the declared decision classes in the inbox-2026-10-a roadmaps ([ab5c92b](https://github.com/event4u-app/agent-config/commit/ab5c92b61936fdddfd5bb3e315d086b64bc1911e))
-* **roadmaps:** state the measured blocker growth in the round's claim ([2a52860](https://github.com/event4u-app/agent-config/commit/2a528602ea27b6407e9e999b8818f41ad1e9f0cb))
-* **evidence:** disposition for inbox round inbox-2026-10-a ([ea06fa1](https://github.com/event4u-app/agent-config/commit/ea06fa1fafe54db61b1313050c52d4c7497e799a))
-* **roadmaps:** record arrivals and owner questions on six held objects ([60f9e60](https://github.com/event4u-app/agent-config/commit/60f9e60f6d2940c49677479641a599d23cbd380b))
-* **roadmaps:** land eight roadmaps from inbox round inbox-2026-10-a ([2c34c3d](https://github.com/event4u-app/agent-config/commit/2c34c3d99b103bd704f917d1603e926f7dac3f0c))
-* **evidence:** declare the evidence type on the inbox-2026-10-b disposition ([8adf9ef](https://github.com/event4u-app/agent-config/commit/8adf9eff9b7908334ed29cb7ed4fbe48f2e05cda))
-* **evidence:** record the inbox-2026-10-b disposition ([a51740b](https://github.com/event4u-app/agent-config/commit/a51740b4b79d963af8ff2fd3551c26214430166e))
-* **stubs:** count the inbox-2026-10-b arrivals on four held stubs ([6f2bc0b](https://github.com/event4u-app/agent-config/commit/6f2bc0b116a78747bc98e1addfda25672ea76ed7))
-* **roadmaps:** land the leading-every-row programme and its lanes from inbox-2026-10-b ([6631412](https://github.com/event4u-app/agent-config/commit/6631412219157e4b26ee9f1eede6493ea38764c0))
+* **contracts:** point the hook-concern row at the manifest instead of a count ([3406ae5](https://github.com/event4u-app/agent-config/commit/3406ae53848f7cf2ca866c2d03d297ad549743d1))
+
+### Tests
+
+* **hooks:** table-drive the opaque-family glob cases over all five heads ([52c9e0e](https://github.com/event4u-app/agent-config/commit/52c9e0e40ebd736aadcf8f37831f994ba1fe0dc6))
 
 ### Chores
 
-* **deps:** bump the site group in /site with 4 updates (#2170) ([7464482](https://github.com/event4u-app/agent-config/commit/7464482550df64e24f101988086f9c6fb1bd7945))
-* **deps-dev:** bump the telemetry-worker group across 1 directory with 2 updates (#2163) ([11eb5d8](https://github.com/event4u-app/agent-config/commit/11eb5d813dc9057e9f475b7a827aa9730d688447))
+* **ratification:** record the council review of the inbox-name guard change ([a03c9e9](https://github.com/event4u-app/agent-config/commit/a03c9e95a6b7cb58065fd9e9c30b104ebcb4911b))
 
 ### Other
 
-* The intake rule was enforced and never written down, so git kept inviting the commit the gate refuses (#2206) ([975d03d](https://github.com/event4u-app/agent-config/commit/975d03d01cc549c297a7a8ea92134b08005eb333))
-* Two roadmaps that read finished, and the three gates that keep each of them where it is (#2205) ([df377ca](https://github.com/event4u-app/agent-config/commit/df377ca64d0333105ffd80813caa94e11805c30b))
-* An installed layer measured against its limit, and the consent an installer must have before thinning (#2201) ([df7ea79](https://github.com/event4u-app/agent-config/commit/df7ea7928c9d9fe5815978b689198b79fc8158d3))
-* Archive the kernel-plumbing roadmap, which finished and stayed in the active set (#2203) ([901e8bc](https://github.com/event4u-app/agent-config/commit/901e8bc4e848283327f5c6811e4e221246a41210))
-* A blocker citation pointing at a test fixture, and a step oracle that cannot reach its own exit (#2202) ([c04d74b](https://github.com/event4u-app/agent-config/commit/c04d74bea094071c72a1421fb013ee12e8200f2f))
-* The first observed structured-ask row, and the subagent leg the absent one was read from (#2199) ([f73e77d](https://github.com/event4u-app/agent-config/commit/f73e77d0f93f55ab76658d86b38dde00222d1246))
-* An acceptance criterion closed on measurement, a guard claim withdrawn, and the second obstacle under a blocked gate (#2200) ([e3e4774](https://github.com/event4u-app/agent-config/commit/e3e4774e2c6f6e2aa24d8720e6aff38c095d67f4))
-* A calendar hold whose date had already passed, and the gate standing behind the stamp (#2196) ([6aa3c36](https://github.com/event4u-app/agent-config/commit/6aa3c36f9cbd596a65cb5b2faafa71cdd240b8f5))
-* Two Phase-0 instruments closed against measurement, and the third blocked by a record rather than a ceiling (#2198) ([92027a2](https://github.com/event4u-app/agent-config/commit/92027a20c350f5b53625a1efbd3157aaf163b26b))
-* Two locks under one owner question, a bundle figure stale by 41 kB, and the oracle a blocked step is waiting for (#2197) ([24d6d5b](https://github.com/event4u-app/agent-config/commit/24d6d5b0d93852ee106dd1a1a7eda9bca9b2c249))
-* A blocker that held on its fourth reading, and the line it cited having moved (#2195) ([780c27e](https://github.com/event4u-app/agent-config/commit/780c27e1ed0f36edc6cd59883dce36230dfef9d4))
-* A payload total that drifted under a pin that never pinned it (#2194) ([e6b7193](https://github.com/event4u-app/agent-config/commit/e6b71933a84bb15e432e86aced4c848897498716))
-* A blocker that held on its sixth reading, and the four edits it is waiting on (#2193) ([fe0cff8](https://github.com/event4u-app/agent-config/commit/fe0cff8a558897a47caba9eb6d9dbe80e90e2d4b))
-* A blocker stated in prose, re-stated as the command that decides it (#2192) ([18ac6b2](https://github.com/event4u-app/agent-config/commit/18ac6b21ec35c4132958dc382349acc6af9a3b53))
-* A fifth reading of two blockers that held, and a second obstacle under the first (#2191) ([afad042](https://github.com/event4u-app/agent-config/commit/afad042bb39e24f3edf5dbbbfccabbda0f3ddb00))
-* A guard that permitted the call precisely when it broke, in six places and a seventh shape (#2189) ([51ee084](https://github.com/event4u-app/agent-config/commit/51ee0844b564f8863b753606f1758c9c0ef6dbd3))
-* An accrual figure that moved while the labelled corpus did not (#2190) ([30481f6](https://github.com/event4u-app/agent-config/commit/30481f6605ade9ff06bbc9ca300ab8614781321c))
-* A third reading of a blocker that has not moved, and a census nine units behind the tree (#2187) ([50bec97](https://github.com/event4u-app/agent-config/commit/50bec97430107d9fe73a6561a4fb986150c57ea8))
-* The fourth wake shape has no envelope tag, and the anchor is the whole guard (#2188) ([97a5a64](https://github.com/event4u-app/agent-config/commit/97a5a647412e376bf8ac12b9065706710c956831))
-* Rule links that name a path the repository actually has, and the blocker that held them (#2185) ([8031e09](https://github.com/event4u-app/agent-config/commit/8031e09d6ff6ecc61be329f2af4a904bcc7be18f))
-* The third wake shape: a subagent hand-back is a turn nobody typed, in two vocabularies that both missed it (#2186) ([0199fd0](https://github.com/event4u-app/agent-config/commit/0199fd0c0a448f3fdf262373cc30971213954168))
-* Twenty-eight boxes re-run rather than read, and the policy behind seven settled-looking cells (#2183) ([d6a2da7](https://github.com/event4u-app/agent-config/commit/d6a2da7bca601dbe9432b35c6fd76fddd63c80db))
-* A rule carrier that delivers what the install carries, in the host's form, in a string the host keeps (#2182) ([7fdfd0a](https://github.com/event4u-app/agent-config/commit/7fdfd0a4d59c616153ffaa283e265708b87b88ae))
-* A rule carrier that works outside the repo: resolution, one mode answer, and the matrix that proves both (#2181) ([95dc7bf](https://github.com/event4u-app/agent-config/commit/95dc7bfb1ba8c5dcb43ce7cfe3f8d271093eacf9))
-* The MCP recorder does not run, and what it would record was wrong in five ways (#2180) ([59824fd](https://github.com/event4u-app/agent-config/commit/59824fd95acfe5f6772f8da02e9f52a7896d593c))
-* Neighbours counted by use, and the link criterion measured rather than assumed (#2179) ([cd26c2e](https://github.com/event4u-app/agent-config/commit/cd26c2e177976d85644fbe8fd9c5a973418bfcdc))
-* Rule laws that can stand, and the class whose law stands with them (#2177) ([9e2fe18](https://github.com/event4u-app/agent-config/commit/9e2fe189e85d4b1feabb0bef55680e02097f0ac7))
-* A route line that says where the skill came from (#2178) ([6bdc2b2](https://github.com/event4u-app/agent-config/commit/6bdc2b25ba6c6d06b94a2137ccfd336efc8f60b0))
-* Stacks beyond PHP: the composition gate, the third binding site, and four resolver fixtures (#2173) ([a3c8393](https://github.com/event4u-app/agent-config/commit/a3c839340059ef68c8a37568685739bb9f8c7fe3))
-* Say which tree the reach numbers came from, and publish the per-prompt pair (#2176) ([4871260](https://github.com/event4u-app/agent-config/commit/48712607ad706c502cb44938a288a39b64d3f784))
-* Rule triggers and installed links that hold (#2174) ([328a21b](https://github.com/event4u-app/agent-config/commit/328a21bef2d8f6660227f4f9656d2043751ff7fc))
-* The stop gate records who set stop_hook_active, and the fingerprint store cannot be bound where its council chose (#2175) ([379cd53](https://github.com/event4u-app/agent-config/commit/379cd535c6618d8d514b78654eef8c59461dc0a1))
-* The advisories were already fixed; the record was not (#2171) ([30f7d21](https://github.com/event4u-app/agent-config/commit/30f7d21f65146fd348bc354b33093794ab500bcf))
-* Dispositions the carried roadmaps were missing (#2172) ([11726a9](https://github.com/event4u-app/agent-config/commit/11726a985ca8de0e183c14d643519d7aa5d77d0c))
-* archive the three roadmaps main still held at 100 % (#2168) ([21da719](https://github.com/event4u-app/agent-config/commit/21da71917d1ad685737b10196245c8d323bd21f4))
-* Let dependency PRs reach their required check (#2169) ([540ee7a](https://github.com/event4u-app/agent-config/commit/540ee7a0bed2bf327c971f204ab90a346a768250))
-* A tree that keeps its neighbours (#2161) ([4399b5a](https://github.com/event4u-app/agent-config/commit/4399b5a0d6395631d808f6bc5f75aaa7eed7e573))
-* A graph that reaches the search, sees the edit, and feeds the gate in shadow (#2159) ([4958809](https://github.com/event4u-app/agent-config/commit/495880908332d55c9a4069f7266dc19c99c83824))
-* A release record that says what it reviewed, and an index with every major (#2157) ([8e30a53](https://github.com/event4u-app/agent-config/commit/8e30a533124b1c85b011bb463a6bd63c3fc3c6e1))
-* Three claims a roadmap makes about itself, made checkable (#2156) ([3a8498c](https://github.com/event4u-app/agent-config/commit/3a8498c2c00fcff37970e2eeabd4ebe7b43f8b9e))
-* Blocking severities where a refusal can land (#2154) ([81d712f](https://github.com/event4u-app/agent-config/commit/81d712f2706ffe6fcdf98f2198a5607d7c6faf17))
-* Give the three spawn-bound test suites their own timeout (#2166) ([aead73d](https://github.com/event4u-app/agent-config/commit/aead73d280f8c61de7cf604ef39c06274fb6baf4))
-* A ranker that routes: the null, and the two premises it refuted (#2162) ([213d870](https://github.com/event4u-app/agent-config/commit/213d870558b7fbcdc033ac6f8f0ef4c1a43a5a80))
-* One YAML reader in the hook bundle, a ceiling on it, and a census that renders (#2158) ([22b19e5](https://github.com/event4u-app/agent-config/commit/22b19e520c198b6f0aec2cbf8cb2851818c11fcc))
-* Record a verification command that fails on claude (#2160) ([29b1832](https://github.com/event4u-app/agent-config/commit/29b183256155f9a3dea3d3351268b62b33628fde))
-* Three surfaces that said more than they did (#2144) ([00612c1](https://github.com/event4u-app/agent-config/commit/00612c1f27edafcfa6340b41c56a0da281d6ebc2))
-
-Tests: 25888 (+896 since 16.2.0)
+* add road-to-svg-from-a-live-session from the continued raster-to-SVG session (#2301) ([a17bd4a](https://github.com/event4u-app/agent-config/commit/a17bd4aa2bcca14cc787096be644647be6188f2e))
+* road-to-svg-review-followups from two reviews of the SVG roadmaps (#2299) ([b015b74](https://github.com/event4u-app/agent-config/commit/b015b747f7c2eea4a8206aba846b82dcc6e84f40))
+* add two ready SVG roadmaps from inbox-2026-10-l (#2298) ([fd02787](https://github.com/event4u-app/agent-config/commit/fd02787ef8e0e9eb21e9a0256e5f3ea9bca21492))
+* give six added verify clauses an expectation that can fail ([9a5338a](https://github.com/event4u-app/agent-config/commit/9a5338aebd49923a894e803b7e21f0d5dbb5d7d3))
+* add thirteen ready roadmaps from inbox-2026-10-g..k ([d8a9e43](https://github.com/event4u-app/agent-config/commit/d8a9e43a881bcf6ad9a8a96c83a4e4958f321098))
+* record inbox-2026-10-g..k arrivals on held stubs and parked roadmaps ([243b6f3](https://github.com/event4u-app/agent-config/commit/243b6f30251da478e03a5f9aa3d60636a14ea0e1))
+
+Tests: 27325 (+127 since 16.4.0)
 
 # Era: pre-4.0.0 — archived
 

package/README.md

@@ -4,9 +4,9 @@
 
 [![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-121-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-205-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-121-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 -->
+[![Skills](https://img.shields.io/badge/Skills-300-orange?style=flat-square)](dist/agent-src/skills/) [![Rules](https://img.shields.io/badge/Rules-122-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-205-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-121-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 121** counts the **source** rules while the linked projection holds 120 — 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>
+<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 205** counts every command file **recursively** (the linked directory holds 60 at its top level), and **Rules 121** counts the **source** rules while the linked projection holds 120 — 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/)**.
 

package/agents/templates/.ai-council.yml.example

@@ -29,9 +29,14 @@
 # `api` rung. A vendor CLI under your subscription is preferred whenever one
 # resolves, so the common case costs nothing per token — run
 # `agent-config council status` to see the resolved transport and billing class
-# per member before invoking. The autonomy directive does NOT silently spend
-# tokens — the /council command always asks before invoking, even under
-# autonomy: on.
+# per member before invoking.
+#
+# This block used to end "the /council command always asks before invoking,
+# even under autonomy: on". That was already untrue when ADR-230 replaced the
+# unconditional ask with a three-case bound, and ADR-279 has since removed the
+# last case that asked. The command does not ask; it shows the estimate as
+# information. What bounds a billable run is a ceiling you set below — and
+# with nothing set, nothing bounds it.
 
 # Master switch (true, false). REQUIRED — the loader has no default for it,
 # so this file's value is the only value.
@@ -138,11 +143,21 @@ defaults:
 # Prices come from agents/.agent-prices.md (gitignored, refreshed weekly
 # by `python3 scripts/update_prices.py`; bootstrapped from
 # scripts/ai_council/_default_prices.py on first run).
+#
+# These ship at 0 — no ceiling on tokens or money unless you set one
+# (ADR-279). `max_calls` is NOT a ceiling on money: it bounds fan-out per
+# invocation, so it keeps its value. To get a bound back, replace a 0 with the
+# figure you want; the units are TOKENS for the first two and US DOLLARS for
+# `max_total_usd`.
+#
+# If you copied this file before 2026-10-06 it carries 500000 / 200000 / 20.0
+# explicitly. Those are YOUR figures now and nothing rewrites them — delete the
+# lines to become unbounded, or keep them to stay bounded.
 cost_budget:
-  max_input_tokens: 500000
-  max_output_tokens: 200000
+  max_input_tokens: 0
+  max_output_tokens: 0
   max_calls: 50
-  max_total_usd: 20.0
+  max_total_usd: 0.0
 
 # Phase 8 — Debate cost-visibility + hard refusal cap.
 #
@@ -150,7 +165,10 @@ cost_budget:
 # high-end estimate (expected × 1.20 over-run buffer) exceeds the cap,
 # `/council debate` refuses to start — the user must lower `--rounds`,
 # drop members, or raise the cap explicitly. No --proceed-anyway override.
-# Set to 0 to disable the cap (not recommended).
+#
+# It ships at 0 — disabled, per ADR-279. Set a USD figure to get the refusal
+# back. The between-round confirmation below is a separate control and is NOT
+# a money ceiling: it stays on whatever this is set to.
 #
 # `cost_disclosure.mode` ∈ {"always", "above_threshold", "off"}:
 #   always           — emit the disclosure block before every debate.
@@ -165,7 +183,7 @@ cost_budget:
 #         mode: above_threshold
 #         threshold_usd: 0.50
 debate:
-  max_cost_usd: 5.00
+  max_cost_usd: 0.00
   cost_disclosure:
     mode: always
     threshold_usd: 1.00

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

@@ -672,13 +672,16 @@ attempt. At the third, write the row with what was observed and move on.
 
 This cap is **this phase's own**, and the divergence from
 [`autonomous-execution`](../../../../rules/autonomous-execution.md)
-§ Validation-loop budget is deliberate rather than an oversight: that rule's N=3
-governs a *validation target* it defines as "a single identifiable artefact (file
-path, lint rule ID, test name)", explicitly excluding natural-language clusters —
-and a verbatim step out of a prose file is exactly such a cluster. Its remedy is
-also different (STOP and ask the user). Borrowing the number while failing the
-definition, and then citing the rule as authority, would weaken the rule it
-claims to obey. So: same number, stated here, for a reason stated here.
+§ Validation-loop budget is deliberate rather than an oversight: that rule's
+`execution.fix_loop_max` budget (default 10, with a strategy-shift ladder)
+governs a *validation target* it defines as "a single identifiable artefact
+(file path, lint rule ID, test name)", explicitly excluding natural-language
+clusters — and a verbatim step out of a prose file is exactly such a cluster.
+This phase's own remedy is also different: STOP and ask the user, where the
+rule's remedy at the same count is a mandatory strategy shift, never a stop.
+Borrowing the number while failing the definition, and then citing the rule
+as authority, would weaken the rule it claims to obey. So: same number,
+stated here, for a reason stated here.
 
 One row per selected step:
 

package/dist/agent-src/commands/bug/investigate.md

@@ -26,7 +26,7 @@ packs:
 
 Run `git branch --show-current` and extract ticket IDs:
 
-- Match pattern: `[A-Z]+-[0-9]+` (e.g., `DEV-1234`, `PROJ-567`)
+- Read it with `agent-config git:convention ticket` ([`commit-subject`](../../../../skills/git-workflow/references/commit-subject.md) § Reading the ticket; e.g. `DEV-1234`, `PROJ-567`)
 - Common branch formats: `fix/DEV-1234/description`, `hotfix/DEV-999`, `fix/bug-description`
 
 If a ticket ID is found:

package/dist/agent-src/commands/commit/in-chunks.md

@@ -43,10 +43,16 @@ If there are no uncommitted changes (staged or unstaged), report
 
 ### 2. Determine the ticket number
 
-- Extract the ticket ID from the current branch name (e.g. `feat/DEV-1234/...`
-  → `DEV-1234`).
-- If no ticket ID is found, omit the scope from the messages — write
-  `chore: ...` not `chore(): ...`. Do **not** ask the user for one.
+- Read the ticket exactly as [`/commit`](../commit.md) step 2 does
+  (`agent-config git:convention ticket`, with the card's `ticket_keys` line as
+  `--keys`) and place it per the convention in force —
+  [`commit-subject`](../../../../skills/git-workflow/references/commit-subject.md),
+  including its area-scope clause. A candidate marked `unknown-key` is omitted,
+  never asked about.
+- If no ticket ID is found, omit it — write `chore: ...` not `chore(): ...`.
+  Do **not** ask the user for one.
+  Under an approved convention card this is never a stop: the family's form
+  without the ticket part is valid (`commit-subject` § Placing the ticket).
 
 ### 3. Analyze and split
 
@@ -69,6 +75,12 @@ Splitting rules:
 
 Generate commit messages per [`commit-conventions`](../../rules/commit-conventions.md).
 
+**No convention established — never ask.** When `agent-config git:convention
+show --key commit_format` prints `no convention established`, run
+`agent-config git:convention measure`, carry its `verdict` line into the summary,
+and generate under the convention in force (the default). Asking and writing the
+card belong to the interactive [`/commit`](../commit.md) step 3c only.
+
 ### 3b. Secret-leak pre-flight — MANDATORY, not autonomy-lifted
 
 Run `./scripts-run src/scripts/check_secret_leak`. A high-confidence hit is a
@@ -79,14 +91,22 @@ strip one.
 
 ### 4. Validate, then commit immediately
 
-Before staging anything, run the same `preview-on-error` validator as
-[`/commit`](../commit.md) step 5. Each generated message must match
-`^(feat|fix|chore|docs|refactor|test|perf|style|build|ci|revert)(\([^)]+\))?!?: .+`.
+Before staging anything, pipe every generated subject through
+`agent-config git:convention subject`, as [`/commit`](../commit.md) step 5 does.
+
+- **Exit `0`** → proceed silently; a `note:` line naming a `commit-msg` hook
+  or a commitlint config is not a stop — that validator runs at commit, and a
+  rejection there stops the run like any failed commit.
+- **Exit `1`** → stop, print the verb's output (each failed subject and its
+  rule, or the format it could not read), hand back to the user.
+  Do **not** auto-commit broken messages even though confirmation is
+  otherwise suppressed.
 
-- **All valid** → proceed silently.
-- **Any invalid** → stop, print the failed message(s) + the regex,
-  hand back to the user. Do **not** auto-commit broken messages even
-  though confirmation is otherwise suppressed.
+An approved convention card an earlier [`/commit`](../commit.md) wrote and left
+uncommitted (`agents/memory/curated/conventions/approved/commit-subject.md`,
+unstaged or untracked) rides in the first chunk: add it with that chunk's files
+(`git add -- agents/memory/curated/conventions/approved/commit-subject.md`), so
+every worktree and clone reads the convention it was approved under.
 
 For each planned commit in order:
 
@@ -98,29 +118,18 @@ git commit -m "{message}"
 No "looks good?" prompt. No confirmation step. The user invoked this
 command knowing the plan would be executed.
 
-### 5. Report (verbosity-gated)
-
-Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
-`minimal`). Same contract as [`/commit`](../commit.md) step 7.
-
-- `off` → emit nothing (still run `git log --oneline -N` silently for
-  the agent's own verification).
-- `minimal` (default) → one line:
+### 5. Report
 
-  ```
-  → N commits created
-  ```
+Same contract as [`/commit`](../commit.md) step 7 — one line (run
+`git log --oneline -N` silently for the agent's own verification):
 
-- `full` → full summary:
-
-  ```
-  Created N commits:
-  1. {sha1}  feat(DEV-1234): {summary}
-  2. {sha2}  test(DEV-1234): {summary}
-  3. {sha3}  chore: {summary}
-  ```
+```
+→ N commits created
+```
 
-  Include `git log --oneline -N` output for verification.
+A run that measured because no convention was
+established adds the verb's `verdict` line and `→ run /commit once to choose and
+record the convention`.
 
 ## Rules