@event4u/agent-config 14.16.0 → 14.18.0

package/src/scripts/check_installed_hooks_fresh.ts

@@ -0,0 +1,381 @@
+#!/usr/bin/env tsx
+/**
+ * Is the INSTALLED copy of this repository's git hooks still what the installer
+ * would write?
+ *
+ * WHY. `src/scripts/install-hooks.sh` writes six hooks into the shared
+ * `.git/hooks` directory. Afterwards it runs only on the package manager's
+ * `prepare` lifecycle step (git clones only) or when a human runs
+ * `task install-hooks`. Between those two events the installed copy drifts from
+ * the source that writes it, silently and without bound. Measured in this
+ * repository on 2026-09-05, before this gate existed: the installed `pre-push`
+ * was 146 lines against a 189-line source body, and the 43 missing lines were
+ * the entire base-freshness gate merged five days earlier. In the source, in
+ * CI, and in the skill documenting it, that gate read as live. On the checkout
+ * that actually runs it, it did not exist.
+ *
+ * That is the general shape of an INSTALLED copy of a generated file: the
+ * source is gated, the copy is not, and the copy is what runs.
+ *
+ * HOW. Not by re-parsing the heredocs. `install-hooks.sh` writes `post-merge`
+ * and `post-checkout` as a heredoc PLUS an appended auto-sync block, and it
+ * interpolates the hook name into both — so no slice of the source file equals
+ * a hook body, and a comparison built on slicing would be wrong for two of six
+ * hooks and brittle for the rest. Instead the gate runs the real installer with
+ * `AGENT_CONFIG_HOOKS_DIR` pointed at a scratch directory and byte-compares
+ * what it produced against what is installed. Anything the installer does
+ * deterministically — interpolation, appends, future additions — compares equal
+ * by construction, which is what keeps this from being the too-strict check its
+ * roadmap's risk register warned about.
+ *
+ * WHERE IT IS BOUND. Two carriers, and NEITHER REFUSES. The pre-push hook body
+ * calls it after the base-freshness gate, advisory (silence it with
+ * `AGENT_CONFIG_SKIP_PREPUSH_HOOKFRESH=1`); the `post-merge` / `post-checkout`
+ * auto-sync block calls it at the event that CAUSES the staleness. The
+ * predicate is "installed == what THIS checkout renders", and `.git/hooks` is
+ * shared by every linked worktree, so it has no unique referent and a refusal
+ * would fire on ordinary parallel work — council 2026-09-05, 2 of 2 seats.
+ *
+ * WHAT THE EVENT CARRIER DOES NOT REACH. `git pull --rebase` fires neither
+ * `post-merge` nor `post-checkout` — it fires `post-rewrite`, which carries no
+ * detector. A rebase-pull that moves the installer is therefore reported at the
+ * next push and not before. Named rather than closed: `post-rewrite` also fires
+ * on every `git commit --amend`, so wiring it there trades a real gap for a
+ * notice on an operation that cannot have moved the installer.
+ *
+ * WHY NOT IN CI. Deliberately NOT in `task ci` or `task preflight`: CI cannot
+ * observe a contributor's `.git/hooks`, so a CI-registered run would scan
+ * nothing and report a green that means "no data" — the vacuous-pass class this
+ * repository audited in 2026-07. Its correctness is covered by
+ * `tests/scripts/check_installed_hooks_fresh.test.ts`, which does run in CI,
+ * and which asserts BOTH directions.
+ *
+ * EMPTY IS A REAL STATE. A checkout that never ran the installer has no managed
+ * hook to compare. That exits 0 and says so in one line, rather than pretending
+ * to have checked something.
+ *
+ * CLI contract: exit 0 = every installed managed hook matches, or none is
+ * installed; 1 = at least one is missing or differs; 2 = the installer could
+ * not be rendered (usage error, or the installer itself failed).
+ *
+ * Usage:
+ *     ./scripts-run src/scripts/check_installed_hooks_fresh
+ *     ./scripts-run src/scripts/check_installed_hooks_fresh --quiet
+ *     ./scripts-run src/scripts/check_installed_hooks_fresh --hooks-dir <path>
+ */
+// ledger-exempt: this gate has one target — the installed hook set — and it
+// reports every managed hook by name with a fingerprint on both the clean and
+// the failing path, so per-target accounting is already the whole output.
+
+import { spawnSync } from 'node:child_process';
+import * as crypto from 'node:crypto';
+import * as fs from 'node:fs';
+import * as os from 'node:os';
+import * as path from 'node:path';
+import process from 'node:process';
+import { fileURLToPath, pathToFileURL } from 'node:url';
+
+import { DeadScopeError, reportScanned } from './_lib/scan_scope.js';
+
+const _HERE = fileURLToPath(import.meta.url);
+const REPO = path.resolve(path.dirname(_HERE), '..', '..');
+const INSTALLER_REL = 'src/scripts/install-hooks.sh';
+const FIX = 'task install-hooks';
+const SKIP_ENV = 'AGENT_CONFIG_SKIP_PREPUSH_HOOKFRESH';
+// Both child processes run on the push path. Unbounded, a wedged `git` or an
+// unwritable TMPDIR leaves the push hanging with no diagnostic, and the
+// "could not render" branch is only reached if the child returns at all.
+const GIT_TIMEOUT_MS = 5_000;
+const INSTALLER_TIMEOUT_MS = 30_000;
+
+export interface HookVerdict {
+    name: string;
+    /**
+     * `not-executable` is its own state rather than a flavour of `differs`:
+     * git SKIPS a hook without the executable bit, so a byte-identical file
+     * that lost +x is exactly the installed-but-inert case this gate exists
+     * to find, and it needs a different sentence than "the content drifted".
+     * `unreadable` is separated from `missing` for the same reason — EACCES
+     * and ENOENT need different fixes (#7).
+     */
+    state: 'match' | 'differs' | 'missing' | 'not-executable' | 'unreadable';
+    expectedSha: string;
+    installedSha: string | null;
+    /** Error code when `state` is `unreadable`. */
+    readError?: string;
+}
+
+export interface FreshnessReport {
+    hooksDir: string;
+    /** Managed hooks the installer would write. */
+    verdicts: HookVerdict[];
+    /** True when NONE of the managed hooks is installed — a fresh clone. */
+    neverInstalled: boolean;
+}
+
+function sha(buf: Buffer): string {
+    return crypto.createHash('sha256').update(buf).digest('hex').slice(0, 12);
+}
+
+/**
+ * The hooks directory git will actually execute from.
+ *
+ * `--git-path hooks` rather than `--git-common-dir` + "/hooks": the two agree
+ * on the ordinary case AND on a linked worktree (verified here — from a
+ * worktree both resolve to the SHARED common-dir hooks, which is the property
+ * the whole shared-state argument rests on), and they diverge when
+ * `core.hooksPath` is set, where only `--git-path` follows it. Composing the
+ * path by hand would compare a directory git never runs and report a match over
+ * hooks that are unrelated — the vacuous green this gate exists to refuse.
+ *
+ * Honest limit: the `core.hooksPath` branch is git-documented and NOT exercised
+ * here. This repository's own `block-no-verify` guard refuses any command
+ * carrying `core.hooksPath`, read-only probes included, so it cannot be tested
+ * from inside a session. The worktree and default cases are verified.
+ */
+export function resolveHooksDir(repoRoot: string): string {
+    const res = spawnSync('git', ['-C', repoRoot, 'rev-parse', '--git-path', 'hooks'], {
+        encoding: 'utf-8',
+        timeout: GIT_TIMEOUT_MS,
+    });
+    const out = (res.stdout ?? '').trim();
+    if (res.status !== 0 || out === '') return path.join(repoRoot, '.git', 'hooks');
+    return path.isAbsolute(out) ? out : path.join(repoRoot, out);
+}
+
+/**
+ * Render every hook the installer would write, into a scratch directory.
+ *
+ * Shells out to the real installer rather than reimplementing it: an
+ * independent renderer would be a second source of truth, and the drift between
+ * the two would be invisible in exactly the way this gate exists to catch.
+ */
+export function renderExpected(repoRoot: string): Map<string, Buffer> {
+    const stage = fs.mkdtempSync(path.join(os.tmpdir(), 'hookfresh-'));
+    // The seam FAILS OPEN by construction: install-hooks.sh treats an empty or
+    // absent AGENT_CONFIG_HOOKS_DIR as "install normally", so a redirect that
+    // does not take effect turns this read-only inspection into a real install
+    // over the pre-push that is currently executing it.
+    //
+    // THIS CHECK IS THE WEAKER HALF, and saying so matters on a path whose
+    // stated risk is that overwrite. It inspects `stage` — a value mkdtempSync
+    // produced two lines up — and therefore catches a caller that supplies an
+    // unusable path. It CANNOT observe whether the variable reached the child.
+    // The defence that can is the installer's own refusal of a set-but-empty
+    // value (install-hooks.sh), which is where the fall-through happens.
+    if (!path.isAbsolute(stage) || stage.trim() === '') {
+        throw new Error(
+            `refusing to run the installer: scratch dir ${JSON.stringify(stage)} is not an absolute path, ` +
+                'and an unredirected run would overwrite the real .git/hooks.',
+        );
+    }
+    try {
+        const res = spawnSync('bash', [path.join(repoRoot, INSTALLER_REL)], {
+            cwd: repoRoot,
+            encoding: 'buffer',
+            timeout: INSTALLER_TIMEOUT_MS,
+            env: { ...process.env, AGENT_CONFIG_HOOKS_DIR: stage },
+        });
+        if (res.error !== undefined) {
+            throw new Error(`${INSTALLER_REL} did not complete: ${res.error.message}`);
+        }
+        if (res.status !== 0) {
+            const err = res.stderr ? res.stderr.toString('utf-8') : '';
+            throw new Error(`${INSTALLER_REL} exited ${String(res.status)}\n${err}`);
+        }
+        const out = new Map<string, Buffer>();
+        for (const name of fs.readdirSync(stage).sort()) {
+            out.set(name, fs.readFileSync(path.join(stage, name)));
+        }
+        return out;
+    } finally {
+        fs.rmSync(stage, { recursive: true, force: true });
+    }
+}
+
+export function inspect(repoRoot: string, hooksDirOverride?: string): FreshnessReport {
+    const hooksDir = hooksDirOverride ?? resolveHooksDir(repoRoot);
+    const expected = renderExpected(repoRoot);
+    if (expected.size === 0) {
+        // The installer produced nothing — it cannot have been read correctly.
+        throw new DeadScopeError(
+            'check_installed_hooks_fresh',
+            `${INSTALLER_REL} wrote no hooks — the installer, not the installed copy, is the problem.`,
+        );
+    }
+    const verdicts: HookVerdict[] = [];
+    for (const [name, body] of expected) {
+        const target = path.join(hooksDir, name);
+        let installed: Buffer | null = null;
+        let executable = false;
+        let readError: string | undefined;
+        try {
+            installed = fs.readFileSync(target);
+            // The installer chmod +x's every hook. Git silently skips one that
+            // is not executable, so mode is part of what "installed" means.
+            //
+            // POSIX only. Windows reports 0o666 / 0o444 and has no executable
+            // bit, so every hook would resolve `not-executable` and the gate
+            // would exit 1 forever — a permanent false red on the platform the
+            // test suite explicitly accommodates.
+            executable =
+                process.platform === 'win32' || (fs.statSync(target).mode & 0o111) !== 0;
+        } catch (e) {
+            const code = (e as NodeJS.ErrnoException).code ?? 'UNKNOWN';
+            installed = null;
+            // ENOENT is absence; anything else is a file that exists and could
+            // not be read, which a re-install will not fix on its own.
+            if (code !== 'ENOENT') readError = code;
+        }
+        const state: HookVerdict['state'] =
+            installed === null
+                ? readError === undefined
+                    ? 'missing'
+                    : 'unreadable'
+                : !installed.equals(body)
+                  ? 'differs'
+                  : executable
+                    ? 'match'
+                    : 'not-executable';
+        verdicts.push({
+            name,
+            state,
+            expectedSha: sha(body),
+            installedSha: installed === null ? null : sha(installed),
+            ...(readError === undefined ? {} : { readError }),
+        });
+    }
+    return {
+        hooksDir,
+        verdicts,
+        // "Never installed" means nothing is THERE. An unreadable hook is
+        // there, so it must not be swallowed by the fresh-clone branch.
+        neverInstalled: verdicts.every((v) => v.state === 'missing'),
+    };
+}
+
+function render(report: FreshnessReport, quiet: boolean, write: (s: string) => void): number {
+    // Outside the quiet guard on purpose: CI-shaped callers pass --quiet, and a
+    // gate that reports no count there reads as silent.
+    const collect = ((chunk: string | Uint8Array): boolean => {
+        write(typeof chunk === 'string' ? chunk : Buffer.from(chunk).toString('utf-8'));
+        return true;
+    }) as typeof process.stdout.write;
+    reportScanned(
+        {
+            gate: 'check_installed_hooks_fresh',
+            scanned: report.verdicts.length,
+            units: 'managed hook(s)',
+            roots: [INSTALLER_REL],
+        },
+        collect,
+    );
+
+    if (report.neverInstalled) {
+        write(
+            `✅  check_installed_hooks_fresh: no managed hook is installed at ${report.hooksDir} — ` +
+                `nothing to compare. Run '${FIX}' to install them.\n`,
+        );
+        return 0;
+    }
+
+    const stale = report.verdicts.filter((v) => v.state !== 'match');
+    if (stale.length === 0) {
+        if (!quiet) {
+            for (const v of report.verdicts) {
+                write(`    ${v.name}  ${v.expectedSha}\n`);
+            }
+        }
+        write(
+            `✅  check_installed_hooks_fresh: ${String(report.verdicts.length)} installed hook(s) match ${INSTALLER_REL}.\n`,
+        );
+        return 0;
+    }
+
+    write(`⚠️  check_installed_hooks_fresh: .git/hooks does not match this checkout.\n`);
+    write(`    hooks dir: ${report.hooksDir}   (shared by every linked worktree)\n`);
+    write(`    worktree:  ${REPO}\n`);
+    for (const v of stale) {
+        switch (v.state) {
+            case 'missing':
+                write(`    ${v.name}  MISSING                 (this checkout renders ${v.expectedSha})\n`);
+                break;
+            case 'unreadable':
+                write(`    ${v.name}  UNREADABLE (${String(v.readError)})   — exists but cannot be read\n`);
+                break;
+            case 'not-executable':
+                write(`    ${v.name}  NOT EXECUTABLE          — byte-identical, and git skips it\n`);
+                break;
+            default:
+                write(
+                    `    ${v.name}  installed ${String(v.installedSha)}  ≠  this checkout ${v.expectedSha}\n`,
+                );
+        }
+    }
+    // Deliberately NOT "run the installer". A mismatch proves difference, never
+    // that THIS checkout is the newer side: linked worktrees share one hooks
+    // directory, so on a sibling-worktree mismatch a re-install only moves the
+    // mismatch to the other worktree, and on a behind-base checkout it writes
+    // the OLDER hook set over the shared one.
+    write(`\n    A mismatch does not by itself say which side is newer.\n`);
+    write(`    · behind the base?      merge it first — the installer moves with it\n`);
+    write(`    · sibling worktree on a different branch?  re-installing only moves the mismatch\n`);
+    write(`    · otherwise             ${FIX}\n`);
+    write(`    Gates the installed hooks are missing are inert on this checkout.\n`);
+    write(`    Silence this notice with ${SKIP_ENV}=1.\n`);
+    return 1;
+}
+
+export function main(argv: readonly string[] = process.argv.slice(2)): number {
+    let quiet = false;
+    let hooksDir: string | undefined;
+    for (let i = 0; i < argv.length; i += 1) {
+        const a = argv[i];
+        if (a === '--quiet') quiet = true;
+        else if (a === '-h' || a === '--help') {
+            process.stdout.write(
+                'usage: check_installed_hooks_fresh [--quiet] [--hooks-dir PATH]\n',
+            );
+            return 0;
+        } else if (a === '--hooks-dir') {
+            i += 1;
+            const next = argv[i];
+            // `--hooks-dir --quiet` must be a usage error, not a hooks
+            // directory literally named "--quiet" — which would report every
+            // managed hook missing and exit 1 with a staleness verdict, the
+            // exact misdiagnosis the undefined check below was written against.
+            if (next === undefined || next.startsWith('--')) {
+                process.stderr.write(
+                    'check_installed_hooks_fresh: --hooks-dir needs a path, got ' +
+                        `${next === undefined ? 'nothing' : JSON.stringify(next)}\n`,
+                );
+                return 2;
+            }
+            hooksDir = next;
+        } else {
+            process.stderr.write(`check_installed_hooks_fresh: unknown argument ${a}\n`);
+            return 2;
+        }
+    }
+
+    let report: FreshnessReport;
+    try {
+        report = inspect(REPO, hooksDir);
+    } catch (e) {
+        process.stderr.write(
+            `❌  check_installed_hooks_fresh: ${e instanceof Error ? e.message : String(e)}\n`,
+        );
+        return 2;
+    }
+
+    const chunks: string[] = [];
+    const code = render(report, quiet, (s) => chunks.push(s));
+    const text = chunks.join('');
+    if (code === 0) process.stdout.write(text);
+    else process.stderr.write(text);
+    return code;
+}
+
+if (process.argv[1] !== undefined && import.meta.url === pathToFileURL(process.argv[1]).href) {
+    process.exit(main());
+}

package/src/scripts/check_release_highlights.ts

@@ -2,12 +2,12 @@
  * Highlight plausibility gate (release-truth Phase 2).
  *
  * The recorded failure: the curated release head said `_none_` twice while
- * false — 9.13.0 shipped behaviour changes, a removed public trigger type, a
+ * false — 9.13.0 shipped behavior changes, a removed public trigger type, a
  * security fix, and honest nulls; the head claimed none of it. Same at
  * 9.14.0.
  *
  * This gate derives GENERATED evidence categories from the release span
- * (security-tagged commits, behaviour/default changes from conventional
+ * (security-tagged commits, behavior/default changes from conventional
  * commit types + rule/schema diffs, honest-null markers, removed public
  * surface) and FAILS when a populated generated category meets a `_none_`
  * curated field. It blocks the contradiction only — a human still writes the
@@ -23,7 +23,7 @@
  * ## REVERSED 2026-09-01 — an unrewritten derived line now BLOCKS
  *
  * This header used to end the paragraph above with *"An unrewritten derived
- * line warns; it never blocks."* That is no longer the behaviour, and the
+ * line warns; it never blocks."* That is no longer the behavior, and the
  * sentence is replaced rather than deleted so the reversal is legible.
  *
  * **The premise was never wrong; the conclusion drawn from it was.** A derived
@@ -71,9 +71,11 @@ import {
     collect_span_commits,
     derive_categories,
     parse_git_log,
+    mix_response_blockers,
     previous_release_tag,
     stale_draft_labels,
 } from './_lib/release_highlights.js';
+import { loadTaxonomy, measureRange } from './measure_release_mix.js';
 import {
     CURATED_HEAD_INSTRUCTION,
     extract_changelog_section,
@@ -149,7 +151,7 @@ export function highlight_contradictions(
  * Exported so the advisory-vs-blocking decision is a fixture, not a claim.
  *
  * CORRECTED 2026-09-01 with the reversal. This comment used to say that
- * `stale_draft_labels` firing while the exit code stays 0 is the behaviour the
+ * `stale_draft_labels` firing while the exit code stays 0 is the behavior the
  * cadence blocker adjudicates. That is no longer what happens — the branch at
  * the call site returns 1 — and the sentence is replaced rather than deleted
  * because it was the load-bearing claim on the other side.
@@ -237,6 +239,18 @@ export function main(argv: readonly string[]): number {
         );
         return 1;
     }
+    // Hoisted above the curated-head branches on purpose. It used to sit inside
+    // `contradictions.length === 0`, so CI reached it only for a section that
+    // HAS a head, carries no unrewritten draft and contradicts nothing — while
+    // the local guards call the same predicate unconditionally. A section
+    // without a curated head was therefore refused locally and waved through by
+    // CI: one predicate, two different gatekeepers, which is the drift this
+    // change exists to remove.
+    const mix = check_governance_mix_response(section.body, from, to, version);
+    if (mix !== 0) {
+        return mix;
+    }
+
     const curated = parse_curated_head(section.body);
     if (!curated) {
         process.stdout.write(`ℹ️  no curated head in the ${version} section — nothing to check\n`);
@@ -332,6 +346,77 @@ export function main(argv: readonly string[]): number {
     return 1;
 }
 
+/**
+ * The governance-versus-product response, checked for PRESENCE, never for the
+ * ratio (ADR-253).
+ *
+ * `measure_release_mix` publishes a level. This is the one place that level has
+ * a consequence, and the consequence is deliberately about completeness of the
+ * written answer: when governance-only commits strictly outnumber consumer-only
+ * commits over the release span, the section under release must carry a written
+ * response naming either the next cycle's consumer work or a maintainer
+ * justification. No number is enforced, and no number can be — both council
+ * seats refused a threshold on fewer than two readings, and a gate with no
+ * threshold that blocks on the ratio is a smuggled threshold.
+ *
+ * The response lives OUTSIDE the curated head, as its own `> **Governance
+ * mix:**` line, so it does not consume the head's ten-line cap and does not
+ * become a sixth label every historical section would suddenly lack.
+ *
+ * Scope matches every other check here: only the section under release is read.
+ *
+ * A measurement failure DEGRADES to a printed warning rather than to a refusal.
+ * This is a governance signal, not a correctness or security control, and a
+ * shallow clone or a missing tag on the release path would otherwise turn an
+ * unrelated environment fact into a blocked release.
+ */
+export function check_governance_mix_response(
+    body: string,
+    from: string,
+    to: string,
+    version: string,
+): number {
+    let reading;
+    try {
+        reading = measureRange(from, to, loadTaxonomy(), version, REPO_ROOT);
+    } catch (err) {
+        process.stdout.write(
+            `⚠️   governance mix not measured for ${version}: ${(err as Error).message}\n`,
+        );
+        return 0;
+    }
+    const o = reading.response_obligation;
+    const level = `governance-only ${o.governance_only} vs consumer-only ${o.consumer_only} (taxonomy ${reading.taxonomy_version})`;
+    if (!o.triggered) {
+        process.stdout.write(`✅  governance mix for ${version}: ${level} — no response owed\n`);
+        return 0;
+    }
+    // ONE predicate, shared with `guard_release_branch_push` — see
+    // `mix_response_blockers`. This side prints and exits; the local side dies
+    // before anything leaves the machine. Neither owns the rule.
+    const blockers = mix_response_blockers(body, version, `\`release/${version}\``, {
+        triggered: true,
+        level,
+    });
+    if (blockers.length === 0) {
+        process.stdout.write(`✅  governance mix for ${version}: ${level} — response present\n`);
+        return 0;
+    }
+    process.stderr.write(
+        `❌  the ${version} section owes a governance-versus-product response: ${level}.\n` +
+            blockers.map((b) => `    - ${b}\n`).join('') +
+            '    Governance-only commits outnumber consumer-only commits over the release span, so\n' +
+            '    the section carries a written response naming either the next cycle\'s consumer work\n' +
+            '    or a maintainer justification (docs/contracts/CHANGELOG-conventions.md § Governance-\n' +
+            '    versus-product response; the decline this replaces is ADR-253).\n' +
+            '    Only that section is read; historical sections are out of scope. No ratio is\n' +
+            '    enforced — this blocks a MISSING answer, never a particular number.\n' +
+            '    Reproduce locally, before any push:\n' +
+            `        ./scripts-run src/scripts/check_release_highlights --version ${version}\n`,
+    );
+    return 1;
+}
+
 const _isMain = (() => {
     const entry = process.argv[1];
     if (!entry) return false;

package/src/scripts/check_suppression_hygiene.ts

@@ -260,6 +260,17 @@ export const SUPPRESSION_INVENTORY: readonly SuppressionSpec[] = [
         // mistyped path as a fresh baseline.
         what: 'review prompts whose recorded prompt_hash does not re-derive',
     },
+    {
+        file: 'src/config/conformance-claim-baseline.json',
+        listKey: 'undeclared',
+        tier: 'string_list',
+        // Absent at the base ref because this change introduces it. Remove the
+        // flag on the next change once the introducing commit is an ancestor of
+        // main — the scan below fails while it is set and the file resolves,
+        // so the flag closes itself rather than needing to be remembered.
+        newInThisChange: true,
+        what: 'skill and rule artefacts carrying a standard-conformance claim with no enforced_by declaration',
+    },
 ];
 
 export interface SuppressionFinding {