@event4u/agent-config 14.14.1 → 14.15.0

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

@@ -34,10 +34,10 @@
       "note": "The nine active non-draft roadmaps that predate the `relates:` requirement (road-to-agentic-engineering-assurance, road-to-component-library-lifecycle, road-to-council-evidence-integrity, road-to-frontend-fidelity-calibration, road-to-monorepo-scope-and-detection, road-to-observability-plate, road-to-role-scoped-spawn-profiles, road-to-skill-delivery-over-mcp, road-to-standing-payload-diet). This is a NEW obligation rather than a repaired scan root, and the ratchet is the point: `depends:` shipped in the template with nothing requiring it and measured 0 adoption, so requiring `relates:` retroactively across the estate would be an owner-reserved write with no analysis behind the edges it would have to invent (held as step 4.3, deferred). Clearing an entry here is one roadmap at a time: run `agent-config roadmap:context` on it, write the rows the probe surfaces, and lower the count."
     },
     "check_source_size_budget": {
-      "count": 18205,
+      "count": 18193,
       "landed": "2026-09-03",
       "note": "Lowered 18,245 -> 18,230 on 2026-09-02 by drain/publication-integrity-option-a. Phase 2 Option A moved the authoring instruction out of the generator: release.ts, which sits ~530 lines PAST the 1500 cap so every line there costs one excess, loses the comment emission, a 16-line HEAD_DEFAULT doc block and its alias const, and gains a shorter writer docstring. The doc block moved to _lib/release_material.ts, which is 289 lines and therefore UNDER the cap, so the same prose now costs nothing. Net -15. The branch first came in at +8 and paid its own way down rather than raising the baseline.",
-      "reason": "Lowered 18,230 -> 18,209 on 2026-09-03 by drain/artifact-location. `doctor --strict` needed 16 lines of integration wiring in cmd_doctor.ts, which sits ~2,100 lines PAST the 1500 cap so every line there costs one excess. The branch first came in at +137 and paid its own way down rather than raising the baseline: the strict semantics, threshold, kill switch, payload helper and argv fragments moved to _cli/_doctor_strict.ts (~160 lines, under the cap, costs nothing), taking it to +15; then the 37-line drift renderer moved to _cli/_doctor_emit.ts. Net -21. The renderer was chosen deliberately: pure rendering, two dependencies, no argparse involvement and therefore none of the byte-parity risk the parser surface carries against the retired Python implementation; nothing outside cmd_doctor.ts imported it. An AI council on the residual split (a: raise by 15 / d: descope the feature); neither was taken, because a parallel branch demonstrated the same day that paying down is achievable in this codebase, which is the evidence the split lacked. This gate's own test comment prescribes it: a commit that splits a god-file lowers the excess and must carry the lowered baseline. MERGE RECONCILIATION 2026-09-03, 18,209 -> 18,205: drain/wired-instruments and drain/artifact-location each lowered from the SAME 18,230 base in parallel -- the branch to 18,226 (net -4, run_continuation_hook.ts's termination ladder moved to _lib/continuation_ladder.ts and runtime_journal.ts's prose to _lib/outcome_vocabularies.ts, both under the cap) and main to 18,209 (net -21, the doctor --strict split above). Taking either side alone is wrong in a different direction: main's value silently discards the branch's earned -4, and the branch's value RAISES the baseline against main and weakens the gate. The committed number is neither -- it is the gate's own output on the merged tree, where both reductions apply. THIS LOCAL READING IS ADMISSIBLE HERE, and the discriminator matters because this file's ci-parity:local-only entry records a 165 -> 164 lowering that was reverted for exactly the opposite case: that count depends on how the environment resolves the projection surface, whereas this gate walks only SOURCE_ROOTS = ['src'] (check_source_size_budget.ts:88) counting excess lines over the 1500 ceiling, and `git status --porcelain -uall -- src/` reported ZERO untracked files, so a clean CI checkout of this commit measures the same 18,205. If CI reads anything else, CI's number is the correct one and this note is the record of why."
+      "reason": "Lowered 18,230 -> 18,209 on 2026-09-03 by drain/artifact-location. `doctor --strict` needed 16 lines of integration wiring in cmd_doctor.ts, which sits ~2,100 lines PAST the 1500 cap so every line there costs one excess. The branch first came in at +137 and paid its own way down rather than raising the baseline: the strict semantics, threshold, kill switch, payload helper and argv fragments moved to _cli/_doctor_strict.ts (~160 lines, under the cap, costs nothing), taking it to +15; then the 37-line drift renderer moved to _cli/_doctor_emit.ts. Net -21. The renderer was chosen deliberately: pure rendering, two dependencies, no argparse involvement and therefore none of the byte-parity risk the parser surface carries against the retired Python implementation; nothing outside cmd_doctor.ts imported it. An AI council on the residual split (a: raise by 15 / d: descope the feature); neither was taken, because a parallel branch demonstrated the same day that paying down is achievable in this codebase, which is the evidence the split lacked. This gate's own test comment prescribes it: a commit that splits a god-file lowers the excess and must carry the lowered baseline. MERGE RECONCILIATION 2026-09-03, 18,209 -> 18,205: drain/wired-instruments and drain/artifact-location each lowered from the SAME 18,230 base in parallel -- the branch to 18,226 (net -4, run_continuation_hook.ts's termination ladder moved to _lib/continuation_ladder.ts and runtime_journal.ts's prose to _lib/outcome_vocabularies.ts, both under the cap) and main to 18,209 (net -21, the doctor --strict split above). Taking either side alone is wrong in a different direction: main's value silently discards the branch's earned -4, and the branch's value RAISES the baseline against main and weakens the gate. The committed number is neither -- it is the gate's own output on the merged tree, where both reductions apply. THIS LOCAL READING IS ADMISSIBLE HERE, and the discriminator matters because this file's ci-parity:local-only entry records a 165 -> 164 lowering that was reverted for exactly the opposite case: that count depends on how the environment resolves the projection surface, whereas this gate walks only SOURCE_ROOTS = ['src'] (check_source_size_budget.ts:88) counting excess lines over the 1500 ceiling, and `git status --porcelain -uall -- src/` reported ZERO untracked files, so a clean CI checkout of this commit measures the same 18,205. If CI reads anything else, CI's number is the correct one and this note is the record of why. LOWERED 18,205 -> 18,193 on 2026-09-03 by fix/release-curation-ask. The change adds a fifth publication guard, and its own additions landed at +10 excess: release.ts 2,008 -> 2,018, every line of which is past the 1500 cap. Paid down rather than baselined, in the two ways this gate's doctrine prescribes. The guard's rationale (~13 lines of docstring, including why prMerged is a parameter rather than a call-site if) lives in release_publication.ts, 915 lines and therefore UNDER the cap, so the prose costs nothing; and the two pure text helpers _splitlines and _rstrip moved out of release.ts into release_env.ts (333 lines, also under the cap), taking release.ts to 1,996 -- 12 BELOW where it started. The branch came in at +10 and leaves at -12. Recorded while moving them: _splitlines is duplicated a third and fourth time at adoption_report.ts:106 and readme_linter.ts:418; collapsing all three onto one definition touches three modules and was left out of this change rather than done silently."
     },
     "ci-parity:local-only": {
       "count": 165,

package/src/config/rule-enforcement-baseline.json

@@ -11,7 +11,6 @@
   "brand-source-of-truth.md",
   "broken-access-control.md",
   "cli-output-handling.md",
-  "code-comment-discipline.md",
   "command-suggestion-policy.md",
   "commit-conventions.md",
   "commit-policy.md",

package/src/scripts/_lib/release_highlights.ts

@@ -279,9 +279,57 @@ export function derive_categories(commits: readonly SpanCommit[]): Record<string
  *
  * A label with no evidence is omitted, so the caller's `_none_` default still
  * applies where `_none_` is the true answer. One line per label keeps the
- * rendered head inside its cap; SHA citations are capped at `DERIVED_SHA_CAP`
- * with an explicit remainder count rather than a silent truncation.
+ * rendered head inside its cap; citations are capped at `DERIVED_SHA_CAP` with
+ * an explicit remainder count rather than a silent truncation.
+ *
+ * **PUBLISHABLE BY DEFAULT since 2026-09-03, and this is the third position
+ * this line has held.** It shipped `DERIVED_MARKER` plus a CATEGORY
+ * DESCRIPTION — "rule/schema diffs, breaking commits or removed public surface
+ * in 5a3b7c5". The 2026-09-01 flip then made that marker a hard refusal, and
+ * the combination had a consequence nobody priced: every release of this
+ * package touches `src/rules/` or `src/scripts/schemas/`, so **Behaviour
+ * changes** is always substantiated, so the generator always wrote a line the
+ * gate always refused. Every release halted, by construction. That was
+ * recorded as "the cadence the flip chose"; the maintainer's instruction of
+ * 2026-09-03 — *"fix the bug so this stops happening"* — is the authority for
+ * removing it.
+ *
+ * The fix is not a weaker gate, and it is not the marker moving somewhere
+ * cheaper (that was 2026-09-03's first attempt, `guard_release_curation`,
+ * which relocated the halt without removing it). It is the writer no longer
+ * emitting text that cannot ship. Two changes, and the first is what makes the
+ * second honest:
+ *
+ * 1. The line now states the COMMIT SUBJECTS behind each category, not the
+ *    name of the category's own detection rule. "hooks:effect reports whether
+ *    a bound concern fires (b0a03a7)" is a claim a reader can use; "rule/schema
+ *    diffs in b0a03a7" is a restatement of why the classifier fired.
+ * 2. `DERIVED_MARKER` is gone from the emission, so nothing unpublishable is
+ *    ever written and no release halts on the writer's own output.
+ *
+ * What is deliberately NOT relaxed: `highlight_contradictions` still refuses a
+ * human editing a substantiated line down to `_none_`, which is the failure the
+ * false 9.13.0 and 9.14.0 heads actually were; and the marker constant and its
+ * four guard sites stay, now covering only a marker somebody writes BY HAND.
+ * The honest cost of this change, stated rather than left to be discovered: the
+ * head is a categorised view of the span rather than curated prose, and it
+ * ships without a human having read it. An operator who wants better prose
+ * still edits it — they are no longer STOPPED until they do.
  */
+/**
+ * A commit subject reduced to the claim inside it.
+ *
+ * Drops the conventional-commit `type(scope):` prefix, because "feat(hooks):"
+ * is metadata about the commit and the changelog's own commit lists already
+ * carry it — what a highlight line needs is the sentence after the colon. Keeps
+ * the subject otherwise verbatim: rewording it here would make the head a
+ * paraphrase of the span rather than a citation of it, and the whole point of
+ * this module is that the two cannot disagree.
+ */
+function _claim_text(subject: string): string {
+    return subject.replace(/^[a-z]+(?:\([^)]*\))?!?:\s*/u, '').trim();
+}
+
 export function render_derived_head_values(
     hits: Readonly<Record<string, readonly CategoryHit[]>>,
 ): Record<string, string> {
@@ -292,11 +340,19 @@ export function render_derived_head_values(
         if (!reason || ev.length === 0) {
             continue;
         }
-        const shas = ev.map((h) => h.sha.slice(0, 7));
-        const shown = shas.slice(0, DERIVED_SHA_CAP);
-        const remainder = shas.length - shown.length;
-        const more = remainder > 0 ? ` +${remainder} more` : '';
-        out[label] = `${DERIVED_MARKER} ${reason} in ${shown.join(', ')}${more}.`;
+        const shown = ev.slice(0, DERIVED_SHA_CAP);
+        const remainder = ev.length - shown.length;
+        const more = remainder > 0 ? `; +${String(remainder)} more` : '';
+        const cited = shown
+            .map((h) => `${_claim_text(h.text)} (${h.sha.slice(0, 7)})`)
+            .join('; ');
+        // `reason` still names the classifier that fired, kept as the fallback
+        // for a hit whose subject renders empty after trimming — a subject that
+        // is nothing but a conventional-commit prefix. Without it the line
+        // would read "( b0a03a7)".
+        out[label] = cited ? `${cited}${more}.` : `${reason} in ${shown
+            .map((h) => h.sha.slice(0, 7))
+            .join(', ')}${more}.`;
     }
     return out;
 }