@event4u/agent-config 9.18.0 → 9.19.0

package/.claude-plugin/marketplace.json

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

package/CHANGELOG.md

@@ -82,6 +82,29 @@ Entry-shape contract: [`docs/contracts/CHANGELOG-conventions.md`](docs/contracts
 
 ### Fixed
 
+- **Every release PR was red on its first run — the generator and the
+  highlight gate contradicted each other.** `release.ts` wrote `_none_` into
+  all five curated-head fields; `check_release_highlights` (added 2026-08-03)
+  fails a `_none_` the release span contradicts. Because every release of this
+  package touches `src/rules/` or `src/scripts/schemas/`, "Behaviour changes"
+  is *always* substantiated, so the gate reliably red-flagged the generator's
+  own default — 9.17.0 (run 30871194277) and 9.18.0 (run 30909511315) both
+  failed on that one step, and each release had to be unblocked by hand.
+  - The span → category classifier now lives once, in
+    `src/scripts/_lib/release_highlights.ts`, and is shared by the generator
+    and the gate; the two duplicated label lists are gone with it.
+  - `release.ts` **pre-fills** each substantiated label with the deriving
+    reason plus its citing SHAs (capped at 6, remainder stated, never silently
+    truncated). `_none_` is now a fallback for labels the span does not
+    substantiate, not a blanket default — so the tool no longer asserts five
+    things it never checked.
+  - The gate keeps full teeth for the failure it was actually built for: a
+    **human** editing a substantiated line back down to `_none_`, which is what
+    produced the false 9.13.0 and 9.14.0 heads. An unrewritten auto-derived
+    line is advisory (a prose gap, not a false claim) and never blocks.
+  - Derivation is best-effort in the generator: a git failure degrades to the
+    `_none_` skeleton with a warning instead of aborting a release.
+
 - **`/team delegate` double gate is now enforced in code, not only in prose**
   (team mode stays default-off; closing `road-to-team-mode`). The gate on the
   only write-access wrapper existed as agent-followed instructions in the
@@ -271,6 +294,72 @@ Entry-shape contract: [`docs/contracts/CHANGELOG-conventions.md`](docs/contracts
 > that forces a new era split (`# Era: 9.19.x`, etc.) — see
 > [`docs/contracts/CHANGELOG-conventions.md § Era splits`](docs/contracts/CHANGELOG-conventions.md).
 
+## [9.19.0](https://github.com/event4u-app/agent-config/compare/9.18.1...9.19.0) (2026-08-04)
+
+### Release highlights
+
+<!-- Curated head: fill before merge, keep it under 10 lines, and leave `_none_` where it is genuinely the answer. The generated log below is unchanged. -->
+- **Behaviour changes:** _none_
+- **Default changes + migration:** _none_
+- **Security and correctness:** _none_
+- **Honest nulls:** _auto-derived, rewrite before merge:_ commits carrying an honest-null marker in 1c744c3.
+- **Known limitations:** _none_
+
+### Features
+
+* **gate-coverage:** ratchet the unhardened-gate count, armed at 189 and able to fail ([5d1564f](https://github.com/event4u-app/agent-config/commit/5d1564fe0dcbeb340c97f33a29245a54c43a8591))
+* **gate-coverage:** publish the asserted count from five gates, 17 -> 22 covered ([d228aa5](https://github.com/event4u-app/agent-config/commit/d228aa5cb5019dffe11c0e4606644630450d0816))
+
+### Bug Fixes
+
+* **roadmap:** repair the archived roadmap's own relative link ([ac85f3a](https://github.com/event4u-app/agent-config/commit/ac85f3a0fdefbbed74c50cc7049c5ffc72b408a8))
+* **census:** make the scan-scope census reproducible, and regenerate it ([1e539ee](https://github.com/event4u-app/agent-config/commit/1e539ee96efc1807663342e084c2a0e666eaf9bc))
+* **lint_handoffs:** stop the CI invocation resolving --quiet as the scan root ([6994781](https://github.com/event4u-app/agent-config/commit/6994781875f8d1d2feab6012ac7704e04232447e))
+* **gates:** name the fence hole, drop the dead sort ([16dace4](https://github.com/event4u-app/agent-config/commit/16dace44b7d468aaba95abf16ec79d65d9862db8))
+
+### Documentation
+
+* **roadmap:** close road-to-gates-that-can-fail, re-charter the adoption gap ([34ff10c](https://github.com/event4u-app/agent-config/commit/34ff10c0748ea7e1c4cfdb99f423c35bba1c9a98))
+* **claims:** register the exit-2 rate alarm in the Stage-A protocol ([4653841](https://github.com/event4u-app/agent-config/commit/46538415f7a59993aef7575f32cc84582a03126f))
+* **review:** unsteered post-merge blind pass — 5 findings, 1 critical ([1c744c3](https://github.com/event4u-app/agent-config/commit/1c744c395f8d1bb727be946f459ce5a498320b5d))
+
+### Chores
+
+* **census:** regenerate after merging origin/main ([239f141](https://github.com/event4u-app/agent-config/commit/239f1413b950455efbe379976ea34a67ff02d380))
+
+Tests: 10972 (+9 since 9.18.1)
+
+## [9.18.1](https://github.com/event4u-app/agent-config/compare/9.18.0...9.18.1) (2026-08-04)
+
+### Release highlights
+
+<!-- Curated head: fill before merge, keep it under 10 lines, and leave `_none_` where it is genuinely the answer. The generated log below is unchanged. -->
+- **Behaviour changes:** the release generator pre-fills the curated head from the release span instead of writing `_none_` into all five fields (8fe60e9, 2f23d6b) — `_none_` now means "the span substantiates nothing", so a reader can trust it; review-gate scope classification changed, with IaC and extensionless build files counting as code and a findings row required to be exactly six cells (6c5f0f5).
+- **Default changes + migration:** _none_
+- **Security and correctness:** two more fail-open routes in the review-gate fence parser are closed — an unterminated fence no longer swallows the rest of a findings artefact (55dc01d) and a bare fence never delimits a region (9937ad9, the fourth such route); both previously let a truncated artefact read as clean.
+- **Honest nulls:** the honest-null recorded against 6c6fc15a9 in the 9.18.0 notes was **false** — the real binding review is restored (d56c0be), so treat that 9.18.0 line as withdrawn. Rounds 6 to 8 of the R2 review closed 7 findings and deferred 10, with 0 critical or high (7a0f7b3, 39f071f, 70bb89f).
+- **Known limitations:** the head pre-fill matches an `honest-null` literal anywhere in a commit body, so a commit *about* the mechanism gets cited as one — it did here, for 2f23d6b, and a human dropped it. The derived line is a draft, never a claim; the gate blocks only a `_none_` the span contradicts and never judges a filled field.
+
+### Bug Fixes
+
+* **release:** derive the head in --dry-run too, so the preview matches ([2f23d6b](https://github.com/event4u-app/agent-config/commit/2f23d6bb963577af5741951962b48e556e5a3e97))
+* **release:** stop the generator writing a `_none_` the gate rejects ([8fe60e9](https://github.com/event4u-app/agent-config/commit/8fe60e9aba5192c07f8e33bc6ce1747a77e82922))
+* **gates:** a bare fence never delimits a region — close the fourth fail-open route ([9937ad9](https://github.com/event4u-app/agent-config/commit/9937ad9b75f60bffd4ad42f2a830589bd4be7e5c))
+* **gates:** an unterminated fence must not swallow the rest of a findings artefact ([55dc01d](https://github.com/event4u-app/agent-config/commit/55dc01d1fd3c8dbf44dd04fa7b3f41e3f4bc39bb))
+* **gates:** IaC and extensionless build files are code; a row is exactly six cells ([6c5f0f5](https://github.com/event4u-app/agent-config/commit/6c5f0f5999b8a421cf765269a8da8b780465dc98))
+
+### Documentation
+
+* **review:** close round 8 — 1 fixed, 4 deferred, 0 critical ([70bb89f](https://github.com/event4u-app/agent-config/commit/70bb89f2820f4c5a5a26cd25f5db2daa53b08e5e))
+* **review:** close round 7 — 2 fixed, 3 deferred, 0 critical/high ([39f071f](https://github.com/event4u-app/agent-config/commit/39f071fad58dc2c5cb9e6ec87e8e37b79085db2f))
+* **gates:** in-place re-binding is the normal fix-pass path (2.1/2.5/2.7) ([1f7d140](https://github.com/event4u-app/agent-config/commit/1f7d1404c4bc63e87d4b46f91d52f81f2ae51f7b))
+* **review:** round-7 R2 findings — 2 medium, 3 low, 0 critical/high ([2bd3eda](https://github.com/event4u-app/agent-config/commit/2bd3edad82ff69700f62c4d16c93f38a484e5e08))
+* **review:** close round 6 — 4 fixed, 3 deferred, 0 critical/high ([7a0f7b3](https://github.com/event4u-app/agent-config/commit/7a0f7b33aed30921f2404ae1955a8e5aa76dde9b))
+* **gates:** two claims corrected to match the code (round-6 lows) ([0f5d43a](https://github.com/event4u-app/agent-config/commit/0f5d43a17be245b034287b0f486839fb156f8b86))
+* **review:** restore the real binding review — 6c6fc15a9's honest-null was false ([d56c0be](https://github.com/event4u-app/agent-config/commit/d56c0be63f6782183737ab50256401ab52a1f38f))
+
+Tests: 10963 (+19 since 9.18.0)
+
 ## [9.18.0](https://github.com/event4u-app/agent-config/compare/9.17.0...9.18.0) (2026-08-04)
 
 ### Release highlights

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

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

package/dist/discovery/deprecation-report.md

@@ -1,6 +1,6 @@
 # Discovery — Deprecation Report
 
-- Generated: `2026-08-04T14:13:41Z`
+- Generated: `2026-08-04T16:08:00Z`
 - Deprecated artefacts: **0**
 
 _None. Tree is clean._

package/dist/discovery/discovery-manifest.json

@@ -14402,7 +14402,7 @@
       "reason": "scaffold template for ticket-bundle tickets (ADR-101); carries no runtime frontmatter — emit-tickets fills it in per ticket"
     }
   ],
-  "generated_at": "2026-08-04T14:13:41Z",
+  "generated_at": "2026-08-04T16:08:00Z",
   "packs": [
     {
       "artefact_count": 117,

package/dist/discovery/discovery-manifest.json.sha256

@@ -1 +1 @@
-4a7dadd2d33fe1127bfd31cb3bdf58c83d3609c17b740e06e8666569b760cf65  discovery-manifest.json
+771e350a2329d84c1a47378ed09ebeed75e5ada993d722cfc079b3f5befec595  discovery-manifest.json

package/dist/discovery/discovery-manifest.summary.md

@@ -1,6 +1,6 @@
 # Discovery Manifest — Summary
 
-- Generated: `2026-08-04T14:13:41Z`
+- Generated: `2026-08-04T16:08:00Z`
 - Scanner: `c24312e116f8`
 - Artefacts: **594**
 - Unassigned: **0**

package/dist/discovery/orphan-report.md

@@ -1,6 +1,6 @@
 # Discovery — Orphan Report
 
-- Generated: `2026-08-04T14:13:41Z`
+- Generated: `2026-08-04T16:08:00Z`
 - Orphan artefacts: **0**
 
 > An orphan is an artefact whose declared pack has no other members.

package/dist/discovery/packs.json

@@ -1,6 +1,6 @@
 {
   "checksum": "sha256:d766f7f17140ce6b648e68821c9403c0bf478609a1ea925e85501c5994002a05",
-  "generated_at": "2026-08-04T14:13:41Z",
+  "generated_at": "2026-08-04T16:08:00Z",
   "packs": [
     {
       "always_on": false,

package/dist/discovery/trust-report.md

@@ -1,6 +1,6 @@
 # Discovery — Trust Report
 
-- Generated: `2026-08-04T14:13:41Z`
+- Generated: `2026-08-04T16:08:00Z`
 - Workspaces tracked: **10**
 - Human-review-required artefacts: **3**
 

package/dist/discovery/workspaces.json

@@ -1,6 +1,6 @@
 {
   "checksum": "sha256:d766f7f17140ce6b648e68821c9403c0bf478609a1ea925e85501c5994002a05",
-  "generated_at": "2026-08-04T14:13:41Z",
+  "generated_at": "2026-08-04T16:08:00Z",
   "scanner_version": "c24312e116f8",
   "workspaces": [
     {

package/dist/mcp/registry-manifest.json

@@ -9,7 +9,7 @@
     "homepage": "https://event4u-app.github.io/agent-config",
     "name": "@event4u/agent-config",
     "repository": "https://github.com/event4u-app/agent-config",
-    "version": "9.18.0"
+    "version": "9.19.0"
   },
   "registries": [
     {

package/dist/mcp/server.json

@@ -9,12 +9,12 @@
       "transport": {
         "type": "stdio"
       },
-      "version": "9.18.0"
+      "version": "9.19.0"
     }
   ],
   "repository": {
     "source": "github",
     "url": "https://github.com/event4u-app/agent-config"
   },
-  "version": "9.18.0"
+  "version": "9.19.0"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@event4u/agent-config",
     "mcpName": "io.github.event4u-app/agent-config",
-    "version": "9.18.0",
+    "version": "9.19.0",
     "description": "Governed skills, rules and commands for AI coding tools (Claude Code, Cursor, Windsurf, Copilot) — every claim machine-checked, including \"zero runtime daemon\".",
     "license": "MIT",
     "private": false,

package/src/config/gate-coverage.yml

@@ -40,25 +40,43 @@
 #                visible, or it repeats the sin it exists to catch.
 #   canary       optional mutation recipe (Phase 7) — see CANARY below
 #
-# COVERAGE — THE HONEST DENOMINATOR (measured 2026-08-02)
-# ------------------------------------------------------
-# 211 `lint_*` / `check_*` / `audit_*` scripts live under `src/scripts/`.
-# **8 of them emit the machine-readable `scanned: <N>` line under their
-# CI-identical argv, and all 8 are listed below.** The manifest is therefore
-# complete with respect to its own contract, and covers ~4 % of the gate
-# population.
+# COVERAGE — THE HONEST DENOMINATOR (re-measured 2026-08-04)
+# ----------------------------------------------------------
+# 223 `lint_*` / `check_*` / `audit_*` scripts live under `src/scripts/`
+# (the count is computed, not asserted — `check_gate_coverage.count_gate_scripts`).
+# **22 of them emit the machine-readable `scanned: <N>` line under their
+# CI-identical argv, and all 22 are listed below.** The manifest is therefore
+# complete with respect to its own contract, and covers ~10 % of the population.
 #
-# The other ~203 are NOT covered, for one reason: rule 1. They print their count
+# The previous revision of this header claimed "8 of 211". Both halves had
+# drifted: entries were added without the header following, and the population
+# grew by 12. Numbers written in prose beside a mechanism that can compute them
+# is how a denominator goes stale — the population figure now comes from the
+# function, and the honest-denominator test bounds the drift.
+#
+# The other ~201 are NOT covered, for one reason: rule 1. They print their count
 # in prose ("111 file(s) scanned", "0 declarer(s)") or not at all, and a guard
 # that parses prose is the fragile thing being replaced. Padding this list with
 # them would manufacture exactly the false green the file exists to prevent.
 #
-# Closing the gap is one line per gate, not a new mechanism: a gate that already
-# computes its count for `_lib/scan_scope.assertScanned` need only also write
-# `scanned: <N>`. Seven gates are one line away today — they call `assertScanned`
-# / `assertWatchlistResolves` with a real count in hand: `audit_skill_overlap`,
-# `check_iron_law_prominence`, `check_safety_floor_untouched`, `lint_handoffs`,
-# `lint_namespace`, `lint_artefact_frontmatter`, `skill_linter` (listed).
+# THE "SEVEN GATES ONE LINE AWAY" NOTE IS DISCHARGED (2026-08-04). It named
+# `audit_skill_overlap`, `check_iron_law_prominence`, `check_safety_floor_untouched`,
+# `lint_handoffs`, `lint_namespace`, `lint_artefact_frontmatter`, `skill_linter`.
+# Five are now converted and listed below; `skill_linter` was already listed when
+# the note was written. `check_safety_floor_untouched` is deliberately NOT
+# converted: it is the one watch-list gate, so its "count" is the size of a fixed
+# guard list (4), not a corpus. A floor under a constant can never trip — that is
+# the false-count shape Phase 2 of the roadmap repaired, and re-introducing it
+# here to raise a coverage number would be the manufactured green this file
+# exists to prevent. It stays unlisted, named, with the reason.
+#
+# What remains is NOT one line per gate. For the ~201 the count would have to be
+# INVENTED (what is this gate's unit?) rather than published, and that judgement
+# is per-gate. It is tracked as a vulnerability ratchet — `gate-hardening:
+# unhardened-scan-scope` in src/config/gate-violation-baselines.json, which fails
+# on a RISE and targets 0 — and charter-owned by
+# `agents/roadmaps/road-to-gate-hardening-adoption.md`.
+#
 # `tests/scripts/check_gate_coverage.test.ts` fails the build the moment a gate
 # starts emitting the line without being registered here, so the list cannot
 # silently fall behind again (that omission is exactly how `check_site_links`
@@ -329,8 +347,12 @@ gates:
       Gate R2 (docs/contracts/plan-review-gates.md § 2). HONEST LIMIT, stated
       because a floor that cannot fail is exactly the false green this file
       exists to prevent: scanned = artefacts inspected + 1 for the diff
-      evaluation, so it is >= 1 by construction and `min_scanned: 1` can never
-      trip. NOTHING ELSE TRIPS EITHER DURING THE ADVISORY WINDOW. The argv above
+      evaluation, so on any run that REACHES the count `min_scanned: 1` cannot
+      trip. It is not unreachable in principle — a moved reviews root exits
+      before the inventory and reports `scanned: 0`, which the guard does read —
+      but that path is the dead-scope violation below, so the floor never adds
+      anything the assertion does not already catch.
+      NOTHING TRIPS AT ALL DURING THE ADVISORY WINDOW. The argv above
       mirrors the CI invocation, and under `--advisory` every violation kind —
       dead-scan-scope included — is printed as a warning and the exit code is 0.
       So for the duration of the Stage-A window this entry proves only that the
@@ -342,3 +364,64 @@ gates:
       from the CI invocation; nothing else changes at that switch. The entry
       stays registered so the guard reports this gate rather than skipping it
       silently.
+
+  # ---------------------------------------------------------------------------
+  # The five below close the gap this header named: they already called
+  # `_lib/scan_scope.assertScanned` with a real count and only had to PRINT it.
+  # The published number is not agent-derived — it is byte-identical to the value
+  # the gate's own dead-scope assertion already gates a red exit on, so there is
+  # no fresh judgement about "what a unit is" and no room for a count that drifts
+  # from what the gate inspected. That property is what made them convertible
+  # without per-gate adjudication; gates whose count would have to be INVENTED
+  # are deliberately NOT in this batch — see road-to-gate-hardening-adoption.
+  # Floors are ~87 % of the measured baseline: room for legitimate deletions,
+  # far above a collapse (rule 3).
+  # ---------------------------------------------------------------------------
+
+  - id: lint_handoffs
+    argv: ["--quiet"]
+    min_scanned: 250
+    corpus: "src/skills/*/SKILL.md (288 at baseline)"
+    status: enforced
+    note: >
+      The argv here is load-bearing, not decoration. Taskfile injects `--quiet`
+      (QUIET_FLAG) and this gate read `args[0]` as a positional path, so the CI
+      invocation resolved `--quiet` as its skills root, scanned 0 and exited 2 —
+      red in `task lint-handoffs`, green when probed bare. Fixed by filtering
+      flag-shaped args before the positional read. Registering it under the REAL
+      argv is what keeps that regression caught: a bare-probe entry would have
+      gone on passing over the broken invocation.
+
+  - id: lint_namespace
+    argv: ["--quiet"]
+    min_scanned: 540
+    corpus: "names across src/rules + src/skills + src/agent-src + src/domains/**/command.md (621 at baseline)"
+    status: enforced
+    note: >
+      Counts NAMES, not files — the scan-scope census counts files under the same
+      roots, so the two artefacts legitimately report different numbers here.
+
+  - id: lint_artefact_frontmatter
+    argv: ["--quiet"]
+    min_scanned: 540
+    corpus: "artefacts carrying frontmatter across the discovery roots (619 at baseline)"
+    status: enforced
+
+  - id: audit_skill_overlap
+    argv: ["--quiet", "--print-table", "--strict"]
+    min_scanned: 250
+    corpus: "src/skills/*/SKILL.md compared pairwise (288 at baseline)"
+    status: enforced
+    note: >
+      `--strict` is part of the CI invocation and can exit non-zero on a real
+      overlap finding. The guard reads the count independently of the exit code —
+      coverage and verdict are different questions.
+
+  - id: check_iron_law_prominence
+    argv: ["--quiet"]
+    min_scanned: 90
+    corpus: "src/rules/*.md (111 at baseline)"
+    status: enforced
+    note: >
+      Emits on stderr, not stdout: `--format json` owns this gate's stdout and a
+      count written there would corrupt the payload. The guard reads both streams.

package/src/config/gate-violation-baselines.json

@@ -1,6 +1,11 @@
 {
   "$comment": "Violation ratchet for gates whose dead scan root was repaired. A repair REVEALS pre-existing debt; it does not create it. Each entry records the count revealed at repair time — the gate fails only when its count RISES. Lowering a count is a normal commit; raising one is a defect. Entries expire: a baseline that has not dropped within 56 days of `landed` (or of `reaffirmed.date`) fails its gate, because a number that never moves is suppression with extra steps. Mechanism + rationale: src/scripts/_lib/gate_baseline.ts. Decision: AI council 2026-08-02, roadmap road-to-gates-that-can-fail blocker `dead-gate-finding-triage`.",
   "gates": {
+    "gate-hardening:unhardened-scan-scope": {
+      "count": 189,
+      "landed": "2026-08-04",
+      "note": "Gate scripts under src/scripts (population 223, the lint_/check_/audit_ prefix set) that neither route through _lib/scan_scope nor emit the machine-readable 'scanned:' line — the gates that can still report success over a moved or empty root without saying so. This is a VULNERABILITY count, not a coverage percentage: it measures how much of the original defect class is still reachable, it RISES whenever a new gate is written without a scope assertion, and its target is 0. That direction is the whole point — an adoption-reach metric ('hardened gates must increase') can never regress and would be threshold-lowering wearing a ratchet's clothes (AI council 2026-08-04, anthropic/claude-sonnet-4-5 + openai/gpt-4o, convergent on scope decomposition plus this discriminator). Clearing it is the charter of road-to-gate-hardening-adoption; the 56-day non-stagnation clause applies unchanged, so a number that never drops fails this gate rather than hardening into configuration. NEW ENTRY, not a raised threshold: this records newly-measured pre-existing exposure at first measurement — nothing was loosened."
+    },
     "check_no_new_legacy_path:hardcoded-scan-roots": {
       "count": 51,
       "landed": "2026-08-02",