@event4u/agent-config 14.6.0 → 14.8.0

package/dist/agent-src/scripts/archival_sweep.ts

@@ -0,0 +1,117 @@
+/**
+ * Archival-sweep spawner for the roadmap dashboard.
+ *
+ * Split out of `update_roadmap_progress.ts` rather than authored there: that
+ * file sits at the 1500-line source ceiling `check_source_size_budget`
+ * ratchets, and the sweep plus its contract is the newest and most separable
+ * thing in it. The contract below is that text, moved intact.
+ *
+ * `--archive` (opt-in; wired into `task roadmap-progress` and
+ * `agent-config roadmap:progress`) runs the archival sweep before rendering
+ * instead of printing "Completed roadmaps not yet archived" and leaving the
+ * work to a human who has been ignoring the line for weeks. It is a flag rather
+ * than the default because the PostToolUse hook re-runs the WRITE path once per
+ * turn on every roadmap edit, and a hook that silently `git mv`s files mid-work
+ * is a bigger problem than the warning it would remove. `--check` never
+ * archives — see `run_archival_sweep`.
+ *
+ * WHY the warning existed at all, since this is the one place a reader of the
+ * flag will look: the sweep's own default is `--changed-only`, so a PR archives
+ * exactly the roadmaps it completed. A roadmap completed by a PR whose sweep did
+ * not run is then complete, on the trunk, and OUTSIDE every later branch's
+ * history — no `--changed-only` sweep finds it again. Measured 2026-08-20: six
+ * such roadmaps, with every regen reprinting the warning at whoever ran it.
+ * `/create-pr` § 1c keeps `--changed-only`; repo-wide reconciliation is this
+ * flag's job and nothing else's.
+ *
+ * This layout is deliberate rather than convenient: the prose homes for it are
+ * both at their ceilings (`roadmap-progress-mechanics.md` sits 122 chars under
+ * the 16,000-char depth ceiling, and `roadmap-management/SKILL.md` tips
+ * `skill_too_large` on any prose block), so the contract lives with the code it
+ * governs. Moving it out means making room first.
+ *
+ * AI council 2026-08-20 (anthropic + openai, blind peer review): both seats
+ * converged on explicit opt-in + `--all` scope + hook archival-free, and both
+ * independently required the `--check` exclusion, the archive-before-render
+ * order, and that a failed sweep must not render. RECORDED DISSENT: one seat
+ * argued for flipping the sweep's own default to `--all` instead. Rejected —
+ * that makes every PR a potential estate-wide cleanup, which is exactly what
+ * `--changed-only` exists to prevent.
+ */
+
+import { spawnSync } from 'node:child_process';
+import * as fs from 'node:fs';
+import * as path from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+// Same directory as `update_roadmap_progress.ts`, so the `path.dirname` below
+// resolves the sweep script exactly as it did before the split.
+const _HERE = fileURLToPath(import.meta.url);
+
+function _isFile(p: string): boolean {
+    try {
+        return fs.statSync(p).isFile();
+    } catch {
+        return false;
+    }
+}
+
+/**
+ * Run the archival sweep for every complete roadmap, in-place.
+ *
+ * Spawned rather than imported: `archive_completed_roadmaps.ts` imports
+ * `collect` from `update_roadmap_progress.ts`, so a static import back would close a cycle, and
+ * `main()` is synchronous so a dynamic `await import()` is not available either.
+ * The sweep is the same twin `_regen_dashboard` already spawns in the other
+ * direction, so the spawn shape is the established one in this pair.
+ *
+ * No recursion: the sweep re-runs this script with NO flags, so its inner
+ * dashboard pass has archival off and terminates at depth 2.
+ *
+ * `--all`, not the sweep's `--changed-only` default. The default exists so a PR
+ * archives exactly the roadmaps it completed; here the caller asked the
+ * repo-wide dashboard to reconcile the estate, and the roadmaps that leak are
+ * by construction the ones NOT in this branch's history — six had accumulated
+ * on the trunk while the warning printed every regen. A roadmap the sweep
+ * refuses (open blockers) stays put and is still reported below.
+ */
+export function run_archival_sweep(root: string): SweepResult {
+    const script = path.join(path.dirname(_HERE), 'archive_completed_roadmaps.ts');
+    if (!_isFile(script)) {
+        // A consumer install without the sweep script: nothing to run, and that
+        // is a normal state — the warning below still reports the roadmaps.
+        return { ran: false, ok: true, stdout: '', stderr: '' };
+    }
+    const argv = [script, '--all', '--repo-root', root];
+    const binName = process.platform === 'win32' ? 'tsx.cmd' : 'tsx';
+    let dir = path.dirname(_HERE);
+    for (;;) {
+        const candidate = path.join(dir, 'node_modules', '.bin', binName);
+        if (fs.existsSync(candidate)) {
+            return _sweepResult(spawnSync(candidate, argv, { cwd: root, encoding: 'utf-8' }));
+        }
+        const parent = path.dirname(dir);
+        if (parent === dir) {
+            break;
+        }
+        dir = parent;
+    }
+    return _sweepResult(spawnSync('npx', ['tsx', ...argv], { cwd: root, encoding: 'utf-8' }));
+}
+
+export interface SweepResult {
+    ran: boolean;
+    ok: boolean;
+    stdout: string;
+    stderr: string;
+}
+
+function _sweepResult(r: ReturnType<typeof spawnSync>): SweepResult {
+    return {
+        ran: true,
+        ok: r.status === 0,
+        stdout: String(r.stdout ?? ''),
+        stderr: String(r.stderr ?? ''),
+    };
+}
+

package/dist/agent-src/scripts/archive_completed_roadmaps.ts

@@ -31,6 +31,7 @@
  *     ./scripts-run src/scripts/archive_completed_roadmaps            # --changed-only (default)
  *     ./scripts-run src/scripts/archive_completed_roadmaps --all
  *     ./scripts-run src/scripts/archive_completed_roadmaps --base origin/main --dry-run
+ *     ./scripts-run src/scripts/archive_completed_roadmaps --repo-root /path/to/proj
  *
  * --- Parity notes (ADR-200) ---
  *
@@ -397,10 +398,13 @@ function _regen_dashboard(root: string, dry_run: boolean): void {
     // Python: `_run([sys.executable, str(script)], root)`; the twin spawns the
     // dashboard generator twin through the same `tsx` runtime, cwd=root.
     _runTwin(root, script);
-    const dash = path.join(root, 'agents', 'roadmaps-progress.md');
-    if (_isFile(dash)) {
-        _run(['git', 'add', '--', 'agents/roadmaps-progress.md'], root);
-    }
+    // The dashboard is NOT staged. It is gitignored in this repository, and
+    // `git add -- <ignored-path>` exits 1 with "The following paths are ignored"
+    // -- a code `_run` returns and this call site discarded, so the previous
+    // `git add` here was a silent no-op from the moment the file was untracked
+    // (2026-08-21) and nothing objected. Regenerating it is still correct; the
+    // developer reads it on disk, and `task roadmap-progress-check` compares a
+    // present copy against a fresh render.
 }
 
 /**
@@ -462,19 +466,21 @@ function _runTwin(root: string, script: string): void {
 const _PROG = 'archive_completed_roadmaps.py';
 
 function _usage(): string {
-    return `usage: ${_PROG} [-h] [--all] [--base BASE] [--dry-run]\n`;
+    return `usage: ${_PROG} [-h] [--all] [--base BASE] [--dry-run] [--repo-root REPO_ROOT]\n`;
 }
 
 interface Args {
     all: boolean;
     base: string;
     dry_run: boolean;
+    repo_root: string | null;
 }
 
 function _parseArgs(argv: readonly string[]): Args {
     let all = false;
     let base = 'origin/main';
     let dry_run = false;
+    let repo_root: string | null = null;
     const emitError = (msg: string): never => {
         process.stderr.write(_usage());
         process.stderr.write(`${_PROG}: error: ${msg}\n`);
@@ -502,17 +508,30 @@ function _parseArgs(argv: readonly string[]): Args {
         } else if (tok.startsWith('--base=')) {
             base = tok.slice('--base='.length);
             i += 1;
+        } else if (tok === '--repo-root') {
+            const val = argv[i + 1];
+            if (val === undefined) {
+                emitError('argument --repo-root: expected one argument');
+            }
+            repo_root = val as string;
+            i += 2;
+        } else if (tok.startsWith('--repo-root=')) {
+            repo_root = tok.slice('--repo-root='.length);
+            i += 1;
         } else {
             emitError(`unrecognized arguments: ${tok}`);
         }
     }
-    return { all, base, dry_run };
+    return { all, base, dry_run, repo_root };
 }
 
 function main(argv?: readonly string[]): number {
     const ns = _parseArgs(argv ?? process.argv.slice(2));
 
-    const root = _repo_root();
+    // An explicit `--repo-root` wins over the `git rev-parse` resolution. The
+    // dashboard generator passes it so a monorepo sub-project sweep cannot walk
+    // up to the enclosing repo and archive the PARENT's roadmaps.
+    const root = ns.repo_root ?? _repo_root();
     const archived = archive_completed(root, {
         changed_only: !ns.all,
         base: ns.base,

package/dist/agent-src/scripts/dashboard_mode.ts

@@ -0,0 +1,212 @@
+// The `--check` tracked/untracked mode table for the roadmap dashboard.
+//
+// Extracted from `update_roadmap_progress.ts` so the verdict is a pure function
+// over observable state — the generator does the I/O, this decides. It also
+// keeps that script under its per-file size cap.
+
+import { spawnSync } from 'node:child_process';
+import * as fs from 'node:fs';
+
+/**
+ * Is the dashboard expected to be a committed artefact? Explicit, never
+ * inferred from git state — an unconditional "absent means pass" cannot tell a
+ * correctly-untracked repo from a generator that silently stopped producing
+ * output. `tracked` is the default and the historical behaviour.
+ */
+export type DashboardMode = 'tracked' | 'untracked';
+
+/**
+ * Is `abs` in the git index? Used only by `--check --untracked-mode`, to tell
+ * "correctly absent" from "still committed". No git at all answers `false`,
+ * which is correct: nothing is tracked there.
+ */
+export function isTrackedInGit(abs: string, repo_root: string): boolean {
+    const r = spawnSync('git', ['ls-files', '--error-unmatch', '--', abs], {
+        cwd: repo_root,
+        encoding: 'utf-8',
+        timeout: 10_000,
+    });
+    return r.status === 0;
+}
+
+export interface DashboardStateInput {
+    mode: DashboardMode;
+    /** Is the file on disk? */
+    present: boolean;
+    /** Is the file in the git index? Only consulted in `untracked` mode. */
+    trackedInGit: boolean;
+    /** Does the on-disk content equal a fresh render? Only meaningful if present. */
+    current: boolean;
+    /** Repo-relative path, for the messages. */
+    rel: string;
+    /**
+     * How to regenerate, for the stale/missing messages. Defaults to the
+     * dashboard's own command. A second caller — `build_archive_index --check`
+     * — reuses this table for a different generated artefact, and a message
+     * telling that reader to run the dashboard generator would be wrong.
+     */
+    regen?: string;
+    /**
+     * What the artefact is called in the "deliberately does not commit the X"
+     * hint. Defaults to `dashboard` so every existing message is byte-identical.
+     */
+    noun?: string;
+}
+
+export interface DashboardStateVerdict {
+    /** True when the dashboard half of `--check` fails. */
+    stale: boolean;
+    /** Diagnostic for stderr, or null. */
+    error: string | null;
+    /** Success line for stdout, or null when `stale`. */
+    ok: string | null;
+}
+
+// The SOURCE path, not `.augment/scripts/…`: that tree is a gitignored
+// projection built by `task sync`, so the advice failed outright in a fresh
+// worktree and in any CI step ordered before the sync.
+const REGEN =
+    'Run `./scripts-run src/agent-src/scripts/update_roadmap_progress` ' +
+    'to regenerate (or `task roadmap-progress` in Taskfile projects).';
+
+/**
+ * The mode table:
+ *
+ *   tracked:   absent -> fail | present+stale -> fail | present+current -> pass
+ *   untracked: in-index -> fail | absent -> pass | present+stale -> fail
+ *              | present+current -> pass
+ *
+ * Absence is distinguished ONLY in untracked mode; a present file is
+ * freshness-checked in both, so untracked never means unchecked.
+ */
+export function evaluateDashboardState(inp: DashboardStateInput): DashboardStateVerdict {
+    const { mode, present, trackedInGit, current, rel } = inp;
+    const regen = inp.regen ?? REGEN;
+    const noun = inp.noun ?? 'dashboard';
+
+    if (mode === 'untracked' && trackedInGit) {
+        // Migration incomplete: declared untracked, still carried by git.
+        // Print the fix; never run it — git-index ops are the user's.
+        return {
+            stale: true,
+            error:
+                `❌  ${rel} is still tracked by git, but this repository runs ` +
+                '`--untracked-mode`. Untrack it, keeping the working-tree file:\n' +
+                `      git rm --cached ${rel}\n`,
+            ok: null,
+        };
+    }
+
+    if (!present) {
+        if (mode === 'tracked') {
+            return {
+                stale: true,
+                error:
+                    `❌  ${rel} is missing. ` +
+                    regen.replace('to regenerate', 'to generate it') +
+                    ' If this repository deliberately does not commit the ' +
+                    `${noun}, pass \`--untracked-mode\`.\n`,
+                ok: null,
+            };
+        }
+        // untracked + absent: the declared state. "up to date" would mislead.
+        return {
+            stale: false,
+            error: null,
+            ok: `✅  ${rel} is not committed here (--untracked-mode) and no stale copy is on disk.\n`,
+        };
+    }
+
+    if (!current) {
+        return { stale: true, error: `❌  ${rel} is stale. ${regen}\n`, ok: null };
+    }
+    return { stale: false, error: null, ok: `✅  ${rel} is up to date.\n` };
+}
+
+/**
+ * `evaluateDashboardState` against the real filesystem and git index. The
+ * generator hands over the paths; every read the verdict needs happens here, so
+ * the caller's check branch stays three lines.
+ */
+export function evaluateDashboardOnDisk(opts: {
+    mode: DashboardMode;
+    target: string;
+    repo_root: string;
+    rendered: string;
+    rel: string;
+    regen?: string;
+    noun?: string;
+}): DashboardStateVerdict {
+    const present = fs.existsSync(opts.target);
+    return evaluateDashboardState({
+        mode: opts.mode,
+        present,
+        trackedInGit: opts.mode === 'untracked' && isTrackedInGit(opts.target, opts.repo_root),
+        current: present && fs.readFileSync(opts.target, { encoding: 'utf-8' }) === opts.rendered,
+        rel: opts.rel,
+        ...(opts.regen === undefined ? {} : { regen: opts.regen }),
+        ...(opts.noun === undefined ? {} : { noun: opts.noun }),
+    });
+}
+
+/** One roadmap row, as far as the estate report below needs it. */
+export interface EstateRow {
+    rel: string;
+    done: number;
+    total_active: number;
+    deferred: number;
+}
+
+/**
+ * The `--check` report: the artefact's own verdict, then the estate-wide
+ * conditions — completed-but-unarchived, and Iron Law 3 deferred items.
+ *
+ * `dashboardOnly` drops the estate half. Two obligations with two blast radii:
+ * the artefact verdict is about ONE file and is safe behind a required status
+ * check, while the estate conditions are about roadmaps an unrelated change
+ * never touched, so requiring them turns any pre-existing estate defect into a
+ * merge block on every PR. It did, on 2026-08-22.
+ *
+ * Extracted from the generator so the report is a pure function of the verdict
+ * and two lists — and because the generator sits exactly on its 1500-line
+ * source ceiling, where the honest way to add a feature is to take lines out.
+ */
+export function reportCheckVerdict(inp: {
+    verdict: DashboardStateVerdict;
+    complete: readonly EstateRow[];
+    pending: readonly EstateRow[];
+    dashboardOnly: boolean;
+    warnMergeGated: () => void;
+    gatedCount: number;
+}): { rc: number; stdout: string; stderr: string } {
+    const { verdict, dashboardOnly } = inp;
+    const complete = dashboardOnly ? [] : inp.complete;
+    const pending = dashboardOnly ? [] : inp.pending;
+    let err = verdict.error ?? '';
+    if (complete.length) {
+        err +=
+            '❌  Completed roadmaps are still in `agents/roadmaps/` — ' +
+            'move them to `agents/roadmaps/archive/` (per the ' +
+            '`roadmap-progress-sync` rule):\n';
+        for (const r of complete) err += `      - ${r.rel}  (${r.done}/${r.total_active} done)\n`;
+    }
+    if (pending.length) {
+        err +=
+            '❌  Iron Law 3 — roadmaps with unresolved `[~]` deferred ' +
+            'items must NOT auto-archive. Resolve via `roadmap-management § 4b` ' +
+            '(spawn follow-up, restore, or cancel):\n';
+        for (const r of pending) {
+            err += `      - ${r.rel}  (${r.done}/${r.total_active} done · ${r.deferred} deferred)\n`;
+        }
+    }
+    if (!dashboardOnly && inp.gatedCount > 0) inp.warnMergeGated();
+    const rc = verdict.stale || complete.length > 0 || pending.length > 0 ? 1 : 0;
+    return { rc, stdout: rc === 0 ? (verdict.ok ?? '') : '', stderr: err };
+}
+
+/** `--tracked-mode` / `--untracked-mode` → the mode, or null for any other token. */
+export function parseModeToken(tok: string): DashboardMode | null {
+    if (tok === '--tracked-mode') return 'tracked';
+    if (tok === '--untracked-mode') return 'untracked';
+    return null;
+}

package/dist/agent-src/scripts/gate_budget.ts

@@ -0,0 +1,282 @@
+/**
+ * gate_budget — the class-1 spend bound and its append-only receipt ledger
+ * (`road-to-gate-autonomy` Phase 2, blocker `b-gate-budget-preauth`).
+ *
+ * WHY THIS EXISTS. Class 1 of the gate taxonomy is "billable or long-running
+ * but reversible; the human ingredient is *spend consent*, not judgment".
+ * `gate_execute.ts` shipped without it on purpose — "no invented ledger",
+ * because the budget SHAPE was an open maintainer decision. That decision is
+ * now taken (option (a): a per-run cap AND a rolling-window cap, with an
+ * append-only receipt ledger as the audit surface), so this module supplies
+ * exactly the shape that was decided and nothing more.
+ *
+ * WHAT THIS IS NOT. It is **not** a consent bypass. `gates --execute` still
+ * requires `--confirm` on every class-1 run, so the this-turn,
+ * names-the-exact-object confirmation `non-destructive-by-default` asks for is
+ * unchanged. The caps bound the SIZE of an authorised spend; they never
+ * manufacture the authorisation. A ledger under `agents/runtime/state/` is
+ * agent-writable, so a mechanism that read an "authorisation" out of it would
+ * be an agent consenting on the user's behalf — which is precisely the threat
+ * model the live-trigger-eval terminal abort exists for. That is why the
+ * receipt records CONSUMPTION only, and why step 2.3's bypass flag is not
+ * built on top of this file.
+ *
+ * A per-run cap alone is not a spend bound — it bounds one mistake, not a week
+ * of them — which is the whole reason the decision carries two numbers.
+ */
+import * as fs from 'node:fs';
+import * as path from 'node:path';
+
+/**
+ * Ledger location, relative to the workspace root.
+ *
+ * The name is the one already present in `gate_execute.ts` as the
+ * absent-ledger placeholder, kept verbatim so the path a class-1 entry has
+ * been REPORTING since Phase 2 is the path it now reads. `agents/runtime/state/`
+ * is this tree's state convention (`run_checkpoint`, `unattended_guard`,
+ * `recycle_envelope_paths` all live there); a bare `agents/state/` is not.
+ */
+export const GATE_BUDGET_LEDGER_REL = path.join(
+    'agents',
+    'runtime',
+    'state',
+    'gate-budget-ledger.jsonl',
+);
+
+/**
+ * Build the absolute ledger path.
+ *
+ * Callers import THIS rather than joining {@link GATE_BUDGET_LEDGER_REL}
+ * themselves: a bare relative constant is the shape that goes silently dead
+ * when the location moves, because nothing joins it any more and nothing
+ * complains.
+ */
+export function gateBudgetLedgerPath(workspaceRoot: string): string {
+    return path.join(workspaceRoot, GATE_BUDGET_LEDGER_REL);
+}
+
+/** The two caps decided by option (a). Both are USD. */
+export interface GateBudgetCaps {
+    maxCostPerRunUsd: number;
+    maxCostPerRolling7dUsd: number;
+}
+
+/**
+ * One append-only ledger line.
+ *
+ * The five fields the decision names — blocker, authorization, estimated and
+ * actual cost, timestamp — plus the single-use marker. `authorization` records
+ * HOW the spend was consented to; today the only value a run can honestly
+ * write is `confirm-flag`, because `--confirm` is the consent. A future
+ * human-only authorisation surface would add its own value here rather than
+ * reinterpreting this one.
+ */
+export interface GateBudgetReceipt {
+    kind: 'consumption';
+    blocker: string;
+    authorization: 'confirm-flag';
+    estimated_usd: number;
+    actual_usd: number | null;
+    at: string;
+    single_use: true;
+}
+
+/** Rolling window, in days, that `maxCostPerRolling7dUsd` bounds. */
+export const ROLLING_WINDOW_DAYS = 7;
+
+function _num(value: unknown): number | null {
+    if (typeof value === 'number' && Number.isFinite(value)) {
+        return value;
+    }
+    return null;
+}
+
+function _dig(settings: unknown, keys: readonly string[]): unknown {
+    let cursor: unknown = settings;
+    for (const k of keys) {
+        if (cursor === null || typeof cursor !== 'object' || Array.isArray(cursor)) {
+            return undefined;
+        }
+        cursor = (cursor as Record<string, unknown>)[k];
+    }
+    return cursor;
+}
+
+/**
+ * Read the caps out of an already-merged settings dict.
+ *
+ * Returns `null` when either cap is absent or non-numeric — deliberately NOT a
+ * fallback to the template numbers. An install whose settings do not carry the
+ * caps has not authorised a standing budget, and inventing one from the
+ * template default would authorise spend nobody configured. The caller renders
+ * the consent line instead.
+ */
+export function readGateBudgetCaps(settings: unknown): GateBudgetCaps | null {
+    const perRun = _num(_dig(settings, ['roadmap', 'gate_budget', 'max_cost_per_run_usd']));
+    const rolling = _num(
+        _dig(settings, ['roadmap', 'gate_budget', 'max_cost_per_rolling_7d_usd']),
+    );
+    if (perRun === null || rolling === null) {
+        return null;
+    }
+    return { maxCostPerRunUsd: perRun, maxCostPerRolling7dUsd: rolling };
+}
+
+/**
+ * Parse a USD figure out of a blocker's `Budget:` field.
+ *
+ * An explicit currency marker (`$` or `USD`) is REQUIRED. Without it a field
+ * like "~50 queries per run" would be read as fifty dollars, and a spend bound
+ * derived from a misread is worse than no bound: it would let a large run
+ * through under a small number. Returns `null` when no USD figure is stated.
+ */
+export function parseBudgetUsd(field: string): number | null {
+    const text = field.trim();
+    if (text === '') {
+        return null;
+    }
+    const dollar = /\$\s*([0-9]+(?:[.,][0-9]+)?)/.exec(text);
+    if (dollar) {
+        return Number.parseFloat(dollar[1]!.replace(',', '.'));
+    }
+    const usd = /([0-9]+(?:[.,][0-9]+)?)\s*(?:usd|dollars?)\b/i.exec(text);
+    if (usd) {
+        return Number.parseFloat(usd[1]!.replace(',', '.'));
+    }
+    return null;
+}
+
+/** Read every well-formed receipt. A malformed line is skipped, never fatal. */
+export function readGateBudgetLedger(workspaceRoot: string): GateBudgetReceipt[] {
+    const file = gateBudgetLedgerPath(workspaceRoot);
+    if (!fs.existsSync(file)) {
+        return [];
+    }
+    const out: GateBudgetReceipt[] = [];
+    for (const line of fs.readFileSync(file, 'utf-8').split('\n')) {
+        const trimmed = line.trim();
+        if (trimmed === '') {
+            continue;
+        }
+        let parsed: unknown;
+        try {
+            parsed = JSON.parse(trimmed);
+        } catch {
+            continue;
+        }
+        if (parsed === null || typeof parsed !== 'object') {
+            continue;
+        }
+        const rec = parsed as Record<string, unknown>;
+        if (rec['kind'] !== 'consumption' || typeof rec['blocker'] !== 'string') {
+            continue;
+        }
+        out.push({
+            kind: 'consumption',
+            blocker: rec['blocker'],
+            authorization: 'confirm-flag',
+            estimated_usd: _num(rec['estimated_usd']) ?? 0,
+            actual_usd: _num(rec['actual_usd']),
+            at: typeof rec['at'] === 'string' ? rec['at'] : '',
+            single_use: true,
+        });
+    }
+    return out;
+}
+
+/** Append one receipt. Append-only by construction — nothing here rewrites. */
+export function appendGateBudgetReceipt(
+    workspaceRoot: string,
+    receipt: GateBudgetReceipt,
+): void {
+    const file = gateBudgetLedgerPath(workspaceRoot);
+    fs.mkdirSync(path.dirname(file), { recursive: true });
+    fs.appendFileSync(file, `${JSON.stringify(receipt)}\n`, 'utf-8');
+}
+
+/**
+ * Spend inside the rolling window.
+ *
+ * `actual_usd` when the run reported one, the estimate otherwise — an
+ * unreported actual must not read as zero spend. A receipt with an unparseable
+ * timestamp counts as IN the window, because dropping it would understate the
+ * total and the cap is meant to fail closed.
+ */
+export function rollingSpendUsd(records: readonly GateBudgetReceipt[], now: Date): number {
+    const cutoff = now.getTime() - ROLLING_WINDOW_DAYS * 24 * 60 * 60 * 1000;
+    let total = 0;
+    for (const r of records) {
+        const stamp = Date.parse(r.at);
+        if (Number.isFinite(stamp) && stamp < cutoff) {
+            continue;
+        }
+        total += r.actual_usd ?? r.estimated_usd;
+    }
+    return total;
+}
+
+export type GateBudgetRefusal =
+    | 'no_caps'
+    | 'no_estimate'
+    | 'over_per_run'
+    | 'over_rolling_7d';
+
+export type GateBudgetVerdict =
+    | { ok: true; estimateUsd: number; rollingUsd: number }
+    | { ok: false; reason: GateBudgetRefusal; detail: string };
+
+/**
+ * Decide whether a class-1 run fits inside the standing budget.
+ *
+ * Every refusal path renders rather than runs — the blocker's own prescription
+ * for a missing ledger, generalised to every way the budget can say no.
+ */
+export function evaluateGateBudget(opts: {
+    caps: GateBudgetCaps | null;
+    records: readonly GateBudgetReceipt[];
+    estimateUsd: number | null;
+    now: Date;
+}): GateBudgetVerdict {
+    const { caps, records, estimateUsd, now } = opts;
+    if (caps === null) {
+        return {
+            ok: false,
+            reason: 'no_caps',
+            detail:
+                'no standing class-1 budget is configured ' +
+                '(`roadmap.gate_budget.max_cost_per_run_usd` and ' +
+                '`roadmap.gate_budget.max_cost_per_rolling_7d_usd`)',
+        };
+    }
+    if (estimateUsd === null) {
+        return {
+            ok: false,
+            reason: 'no_estimate',
+            detail:
+                'the entry states no USD estimate in its **Budget:** field, so no cap ' +
+                'can be compared against it',
+        };
+    }
+    if (estimateUsd > caps.maxCostPerRunUsd) {
+        return {
+            ok: false,
+            reason: 'over_per_run',
+            detail:
+                `the estimate ($${estimateUsd.toFixed(2)}) exceeds the per-run cap ` +
+                `($${caps.maxCostPerRunUsd.toFixed(2)})`,
+        };
+    }
+    const spent = rollingSpendUsd(records, now);
+    if (spent + estimateUsd > caps.maxCostPerRolling7dUsd) {
+        return {
+            ok: false,
+            reason: 'over_rolling_7d',
+            detail:
+                `$${spent.toFixed(2)} is already receipted in the last ` +
+                `${String(ROLLING_WINDOW_DAYS)} days and this run would add ` +
+                `$${estimateUsd.toFixed(2)}, over the rolling cap ` +
+                `($${caps.maxCostPerRolling7dUsd.toFixed(2)})`,
+        };
+    }
+    return { ok: true, estimateUsd, rollingUsd: spent };
+}