session-orchestrator 5.0.0 → 5.2.0

package/scripts/lib/instruction-budget-guard.mjs

@@ -255,17 +255,17 @@ export const DEFAULT_BYTE_CEILING = 121000;
  *      → rulesDir extracted from `c73c094f`: { bytes: 76114, files: 8 }
  *      → rulesDir extracted from `e4674109`: { bytes: 89763, files: 43 }
  *
- * The CONCLUSION stands, on a wider base: firing rate is 0 of 3, not 0 of 2 —
- * the guard would not have fired at any of the three states this repo has
- * recorded. What does NOT stand is the headroom claim it rested on. The live
- * corpus is **2,427 B** below the historical peak, not 13,649 B: a single
- * /reconcile wave of the size this one just absorbed puts the generated corpus
- * back at its worst recorded state, and the ceiling still would not notice.
- * "Decorative" is therefore an understatement of the gap, not an overstatement
- * — which strengthens the case for the operator decision this block defers,
- * and changes none of its terms. Still tracked rather than silently patched:
- * raising OR lowering a threshold inside a population fix is exactly the
- * conflation this comment exists to end.
+ * HISTORY as of 2026-09-16 — every number in this paragraph described the
+ * 124,000 ceiling, which no longer exists on this axis. It read, correctly for
+ * 2026-09-11: firing rate 0 of 3, not 0 of 2; the generated corpus then sat
+ * **2,427 B** below the peak known at that time (87,336 of 89,763 B), not
+ * 13,649 B, so one /reconcile wave of the size that session absorbed would have
+ * restored its worst recorded state with the ceiling still silent. Superseded
+ * on BOTH terms by the RE-CALIBRATED block below (ceiling 95,000, true peak
+ * 99,774 B, live distance to the peak 29,833 B measured 2026-09-16). Kept
+ * because it records the rule that produced the eventual fix: raising OR
+ * lowering a threshold inside a population fix is exactly the conflation this
+ * comment exists to end.
  *
  * FIRING-RATE AUDIT — widened from 3 states to 89 (#1308, 2026-09-11T17:26Z,
  * clean tree @ `4a49adc6`). HR-105 forbids a rule nothing records; "0 of 3"
@@ -273,35 +273,63 @@ export const DEFAULT_BYTE_CEILING = 121000;
  * guard was replayed over EVERY commit that touched `.claude/rules/`:
  * `git log --format=%h -- .claude/rules/` → 89 commits, each extracted with
  * `git archive <sha> .claude/rules | tar -x -C <tmp>` and fed to
- * `computeInstructionBudget({rulesDir})`:
+ * `computeInstructionBudget({rulesDir})`. Firing rates only — the headroom
+ * annotations this table used to carry are deliberately gone, because an
+ * absolute headroom rots between two edits of the corpus; read the live one
+ * from the axis itself (command in the RE-MEASURED block below):
  *
  *   directive axis  (480)      → fires  4/89 =  4.5 %   rare, healthy
- *   byte axis       (121,000)  → fires  0/89 =  0.0 %   live: 586 B headroom
- *   generated axis  (124,000)  → fires  0/89 =  0.0 %   peak ever 89,763 B
- *   pathScoped axis (124,000)  → fires  4/89 =  4.5 %   falsifiable
- *
- * "Silently broken" is now RULED OUT: `pathScoped` runs the same code path off
- * the same walk and fires on 4 of the same 89 states. What remains is the
- * calibration gap — the all-time peak of this population is 89,763 B, i.e.
- * 72.4 % of the ceiling, so no state this repo has ever recorded could have
- * breached it, and none plausibly will before the corpus grows ~38 %.
- * A falsifiable ceiling for this axis would sit just above the recorded peak
- * (≈ 92,000 B, peak + 2.5 %); this module does NOT move it, because
- * `.claude/rules/development.md` § Guard & Threshold Design makes re-aiming a
- * threshold an operator decision, separate from measuring it. Revisit trigger:
- * re-run the 89-state replay above whenever the generated corpus passes
- * 92,000 B, or when this axis first fires (then it is calibrated, not
- * decorative).
- *
- * That trigger FIRED: the generated corpus stood at 99,774 B at `c16fb518`
- * (2026-09-12), past 92,000. It was answered by consolidation rather than by
- * a replay of this axis — the 8 generated files were merged down (prose only,
- * provenance unchanged) to 75,130 B / 8 files on the 2026-09-12 working tree
- * (#1316), back under the 92,000 mark. This ceiling is unchanged and the
- * 89-state replay of THIS axis was not re-run; the trigger stays armed for the
- * next pass of 92,000 B.
+ *   byte axis       (121,000)  → fires  0/89 =  0.0 %
+ *   generated axis  (124,000)  → fires  0/91 =  0.0 %   → superseded, see below
+ *   pathScoped axis (124,000)  → fires  5/91 =  5.5 %   → calibrated
+ *
+ * RE-CALIBRATED 2026-09-16 (#1308). The replay was re-run over the FULL
+ * recorded history of this directory, not the 89-state subset:
+ *
+ *   `git log --format=%h -- ./.claude/rules/` → 91 states; each materialized
+ *   with `git archive <sha> .claude/rules | tar -x -C <tmp>` and fed to
+ *   `computeInstructionBudget({ rulesDir })`.
+ *
+ * True peak of the generated axis: **99,774 B @ `2ae08fe0`** — which CORRECTS
+ * the "peak ever 89,763 B" this docblock carried until now (that number came
+ * from a single replayed commit, not from the population). Median state:
+ * 4,802 B. Firing table over the same 91 states:
+ *
+ *   124,000            → 0/91 = 0.0 %   (the standing, unfalsifiable value)
+ *   102,268 (peak+2.5%)→ 0/91 = 0.0 %   (a ceiling above the peak never fires)
+ *    95,000            → 1/91 = 1.1 %   ← chosen
+ *    88,000            → 3/91 = 3.3 %
+ *    80,000            → 5/91 = 5.5 %
+ *
+ * Why 95,000: it FIRES on recorded history (HR-105 — a rule you cannot falsify
+ * is not a rule), at 1.1 % it sits in HR-101's rare band (a class above ~10 %
+ * is a broken instrument), and it stays silent on the corpus it lands on, so it
+ * does not go red before the #1367 consolidation has been committed. "Peak +
+ * 2.5 %" is REJECTED here for the reason the old text recommended it: above the
+ * peak, the axis is decorative by construction.
+ *
+ * RE-MEASURED 2026-09-16 @ `ca214376`, after the #1367 consolidation landed in
+ * the working tree (the state this ceiling was calibrated for is the state it
+ * now judges):
+ *
+ *   node --input-type=module -e "const m = await import('./scripts/lib/instruction-budget-guard.mjs'); \
+ *     console.log(JSON.stringify(m.computeInstructionBudget({ repoRoot: process.cwd() }).bySurface))"
+ *   → generated  { bytes: 69941, files: 7 }   ×1.36 under 95,000
+ *     pathScoped { bytes: 109932, files: 10 }
+ *
+ * Read the headroom off that command, never off a sentence in this block: the
+ * two numbers a verdict needs are the AXIS and its CEILING, and the distance
+ * between them changes with every rule edit. For the record at that SHA the
+ * generated axis sat 25,059 B under its ceiling and 29,833 B under the 99,774 B
+ * peak — i.e. one /reconcile wave the size of the largest recorded one would
+ * still not reach the peak, but a repeat of the growth that produced it would
+ * cross 95,000 first. That is the intended, rare signal: a cue to consolidate.
+ *
+ * BV-004 revisit trigger: re-run the 91-state replay when the generated corpus
+ * passes 90,000 B, or on this ceiling's FIRST fire — at which point it is
+ * calibrated by a real event rather than by a replay.
  */
-export const DEFAULT_GENERATED_BYTE_CEILING = 124000;
+export const DEFAULT_GENERATED_BYTE_CEILING = 95000;
 
 /**
  * Default byte ceiling for the PATH-SCOPED rule surface — the fourth axis,
@@ -353,11 +381,14 @@ export const DEFAULT_GENERATED_BYTE_CEILING = 124000;
  *   working tree (2026-09-11):       134,969 B / 11 files → FIRES
  *
  * Firing rate 2 of 3, falsifiable in both directions — the condition
- * {@link DEFAULT_GENERATED_BYTE_CEILING} does NOT currently meet (0 of 3).
- * Confirmed on a wider base (#1308, 2026-09-11T17:26Z @ `4a49adc6`): replayed
- * over all 89 commits that touched `.claude/rules/`, this axis fires 4/89
- * (4.5 %) against the generated axis's 0/89 — inside HR-101's rare band, and
- * falsifiable, which is exactly the property the sibling ceiling lacks.
+ * {@link DEFAULT_GENERATED_BYTE_CEILING} did not meet while it stood at
+ * 124,000 (0 of 3). Confirmed on a wider base (#1308, 2026-09-11T17:26Z @
+ * `4a49adc6`): replayed over all 89 commits that touched `.claude/rules/`, this
+ * axis fires 4/89 (4.5 %) — inside HR-101's rare band, and falsifiable.
+ * SUPERSEDED as a CONTRAST 2026-09-16: the sibling ceiling was re-calibrated to
+ * 95,000 in the same #1308 replay and now fires 1/91 (1.1 %) on recorded
+ * history, so "the property the sibling ceiling lacks" is no longer true of it —
+ * both axes are falsifiable, and this one is simply the looser of the two.
  * This is also why it is not re-derived upward off the live number: a ceiling
  * placed above 134,969 would be silent on all three states, i.e. the same
  * unfalsifiable shape, obtained by the threshold-patch move
@@ -385,9 +416,14 @@ export const DEFAULT_GENERATED_BYTE_CEILING = 124000;
  * the threshold-patch move `development.md` § Guard & Threshold Design
  * forbids.
  *
- * Headroom is 1,237 B. The next `/reconcile` rule (~2.5 KB written
- * standalone) trips this axis unless it is absorbed into a thematic file in
- * the SAME write step — an obligation written in the /reconcile-overshoot
+ * Headroom moves with every rule edit, so it is measured, never quoted from
+ * here: `computeInstructionBudget({ repoRoot }).bySurface.pathScoped` against
+ * this constant. At 2026-09-16 @ `ca214376` that was 109,932 B / 10 files —
+ * 14,068 B under the ceiling, after the #1367 consolidation; on 2026-09-12 it
+ * was 1,237 B, which is how narrow this axis can get. The next `/reconcile`
+ * rule (~2.5 KB written standalone) trips it from a margin like that one
+ * unless it is absorbed into a thematic file in the SAME write step — an
+ * obligation written in the /reconcile-overshoot
  * learning of `.claude/rules/measurement-discipline.md` and checked by the
  * reconcile writer's budget pre-flight (`scripts/lib/reconcile/writer.mjs`).
  * A breach sets `overBudget` AND turns `tests/rules/receiving-review.test.mjs`
@@ -749,7 +785,7 @@ function sumBytes(entries) {
  * @param {Record<string, unknown>} meta
  * @returns {boolean}
  */
-function isMachineGeneratedRule(meta) {
+export function isMachineGeneratedRule(meta) {
   if (!meta || typeof meta !== 'object') return false;
   return (
     meta['auto-generated'] === true ||
@@ -758,6 +794,110 @@ function isMachineGeneratedRule(meta) {
   );
 }
 
+/** One day in milliseconds — local to this module, as in every other lib here. */
+const MS_PER_DAY = 86_400_000;
+
+/**
+ * Whole days from `now` until this rule's `expires-at`, or `null` when the rule
+ * declares no expiry or an unparseable one.
+ *
+ * Negative ⇒ already expired. The comparison basis is deliberately the SAME one
+ * `rule-loader.mjs` `applyGates` uses — `Date.parse(expires-at) < now`, i.e. a
+ * bare `YYYY-MM-DD` is UTC midnight — so "expired" here means exactly "the
+ * loader already filters it out of every wave's rule set", never a second
+ * definition of the same word. `Math.floor` therefore returns `-1` for a rule
+ * that expired at midnight today: past, but by less than a day.
+ *
+ * An unparseable date returns `null` (fail-OPEN, matching the loader, which
+ * warns and ignores the expiry rather than excluding the file) — the malformed
+ * value is a separate finding, not an expiry verdict.
+ *
+ * @param {{ meta?: Record<string, unknown>, now?: Date|number|string }} [opts]
+ * @returns {number|null}
+ */
+export function daysUntilGeneratedRuleExpiry(opts = {}) {
+  const meta = opts.meta;
+  if (!meta || typeof meta !== 'object') return null;
+  if (!Object.prototype.hasOwnProperty.call(meta, 'expires-at')) return null;
+  const expiresAt = Date.parse(String(meta['expires-at']));
+  if (!Number.isFinite(expiresAt)) return null;
+
+  const raw = opts.now;
+  let now;
+  if (raw instanceof Date) now = raw.getTime();
+  else if (typeof raw === 'number' && Number.isFinite(raw)) now = raw;
+  else if (typeof raw === 'string' && Number.isFinite(Date.parse(raw))) now = Date.parse(raw);
+  else now = Date.now();
+
+  return Math.floor((expiresAt - now) / MS_PER_DAY);
+}
+
+/**
+ * Is this generated rule's `expires-at` already in the past?
+ *
+ * The defect it names (#1372): `rule-loader.mjs` filters an expired rule out at
+ * READ time, but nothing DELETES it — so the file keeps being counted by every
+ * byte ceiling above and keeps being loaded verbatim by Claude Code, which has
+ * no notion of `expires-at`.
+ *
+ * @param {{ meta?: Record<string, unknown>, now?: Date|number|string }} [opts]
+ * @returns {boolean}
+ */
+export function isExpiredGeneratedRule(opts = {}) {
+  const days = daysUntilGeneratedRuleExpiry(opts);
+  return days !== null && days < 0;
+}
+
+/**
+ * Enumerate the machine-generated rule files in `rulesDir`.
+ *
+ * Same population, same filter and same frontmatter parser as
+ * {@link measureRuleCorpora}'s `generated` surface — that is the point of
+ * exporting it: a consumer that needs the FILES rather than the BYTES (the
+ * expiry test, the session-start maintenance probe) must not mirror the
+ * predicate, because a mirror agrees only until one side is edited.
+ *
+ * Three-state, like every reader in the banner family: `ok: false` means the
+ * directory exists but could not be enumerated, which a caller must record as
+ * "undeterminable" and never as "no generated rules". A MISSING directory is
+ * `ok: true` with an empty list — a repo without `.claude/rules/` genuinely has
+ * none.
+ *
+ * @param {{ rulesDir?: string, repoRoot?: string }} [opts]
+ * @returns {{ ok: boolean, rules: Array<{ file: string, meta: Record<string, unknown>, expiresAt: string|null }> }}
+ */
+export function listMachineGeneratedRules(opts = {}) {
+  const dir =
+    typeof opts.rulesDir === 'string' && opts.rulesDir.length > 0
+      ? opts.rulesDir
+      : join(opts.repoRoot ?? process.cwd(), '.claude', 'rules');
+
+  /** @type {Array<{ file: string, meta: Record<string, unknown>, expiresAt: string|null }>} */
+  const rules = [];
+  let names;
+  try {
+    names = readdirSync(dir);
+  } catch (err) {
+    // ENOENT is an answer ("no generated rules"); anything else is not knowing.
+    return { ok: err?.code === 'ENOENT', rules };
+  }
+
+  for (const file of names) {
+    if (!file.endsWith('.md')) continue;
+    let meta;
+    try {
+      ({ meta } = parseGlobsFrontmatter(readFileSync(join(dir, file), 'utf8')));
+    } catch {
+      continue; // unreadable or unparseable — skip, never throw
+    }
+    if (!isMachineGeneratedRule(meta)) continue;
+    const raw = meta?.['expires-at'];
+    rules.push({ file, meta, expiresAt: typeof raw === 'string' ? raw : null });
+  }
+
+  return { ok: true, rules };
+}
+
 /**
  * Single-pass scan of `.claude/rules/*.md` producing the TWO corpus measures
  * this guard's third axis needs, which #1297 proved are NOT the same set:

package/scripts/lib/is-main-module.mjs

@@ -0,0 +1,82 @@
+/**
+ * is-main-module.mjs — the one entry-guard predicate, symlink-safe.
+ *
+ * ## The incident class
+ *
+ * An ESM module that wants to run `main()` only when invoked as a CLI has to
+ * compare "the module I am" against "the script Node was told to run". The two
+ * sides are NOT the same kind of path:
+ *
+ *   - `import.meta.url` is resolved by Node to the module's **realpath**.
+ *   - `process.argv[1]` is the path **as typed on the command line**.
+ *
+ * With a symlink anywhere in the invocation path — a `node_modules/.bin/` shim,
+ * a `~/bin/foo -> /repo/scripts/foo.mjs` convenience link, a plugin directory
+ * symlinked into `~/.claude/plugins/`, or `/tmp` itself (on macOS `/tmp` is a
+ * symlink to `/private/tmp`) — the two strings differ and the guard is FALSE.
+ *
+ * The failure is silent and total: `main()` never runs, nothing is printed, and
+ * the process exits 0. Every caller — a hook, a CI job, an npm script, an
+ * operator — reads that as success. This is the single worst shape a defect can
+ * have in this repo, which is why the predicate is centralised here instead of
+ * being re-typed per file.
+ *
+ * ## The textual variants this replaces
+ *
+ * Measured 2026-09-16 @ ca214376 over the 50 files swept for #1371, the guard
+ * had been hand-written in 15 distinct textual forms (measured by extracting the
+ * guard expression from every file at HEAD), collapsing into four
+ * semantic variants — all four wrong in the same way:
+ *
+ *   V1  import.meta.url === `file://${process.argv[1]}`
+ *       (also breaks on any space or non-ASCII char in the path — no escaping)
+ *   V2  import.meta.url === pathToFileURL(process.argv[1] ?? '').href
+ *   V3  resolve(process.argv[1]) === resolve(fileURLToPath(import.meta.url))
+ *       / resolve(process.argv[1]) === resolve(__filename)
+ *   V4  fileURLToPath(import.meta.url) === process.argv[1]
+ *
+ * V2/V3 fix the `undefined`-argv and relative-path cases; none of them resolve
+ * symlinks, because only `realpath` does.
+ *
+ * ## Non-goal: Windows drive-letter / case folding
+ *
+ * `realpathSync.native` delegates to the OS, so on NTFS it canonicalises the
+ * stored casing of every path component and the two sides agree. Where the
+ * realpath call FAILS (deleted path, permission error) the fallback is a raw
+ * string compare, which on Windows can be case-sensitive against a
+ * case-insensitive filesystem. That residual case is deliberately out of scope:
+ * this repo runs on macOS and Linux CI, and a case-only mismatch degrades to
+ * today's behaviour rather than to something worse.
+ *
+ * @module scripts/lib/is-main-module
+ */
+
+import { realpathSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+
+/**
+ * Whether the module identified by `importMetaUrl` is the script Node was
+ * invoked with.
+ *
+ * Symlink-safe: both sides are canonicalised via `realpathSync.native` before
+ * comparison, so an invocation through a symlink (shim, `~/bin` link, `/tmp` on
+ * macOS) still matches. When either path cannot be realpath'd — it was deleted
+ * between spawn and this call, or is unreadable — the comparison degrades to a
+ * raw string compare rather than throwing, because an entry guard must never be
+ * the thing that crashes an import.
+ *
+ * @param {string} importMetaUrl the calling module's `import.meta.url`
+ * @param {string | undefined} [argv1] the invoked script path; defaults to
+ *   `process.argv[1]`, which is `undefined` under `node -e`, the REPL and some
+ *   dynamic-import contexts — those return `false`
+ * @returns {boolean} true when this module IS the entrypoint
+ */
+export function isMainModule(importMetaUrl, argv1 = process.argv[1]) {
+  if (!argv1) return false;
+  const self = fileURLToPath(importMetaUrl);
+  try {
+    return realpathSync.native(argv1) === realpathSync.native(self);
+  } catch {
+    return argv1 === self;
+  }
+}

package/scripts/lib/locks/index.mjs

@@ -1,31 +1,38 @@
 /**
- * locks/index.mjs — convenience barrel for the short-lived lock protocols split
- * out of session-lock.mjs in #630 (A1 barrel-preserving split).
+ * locks/index.mjs — DEPRECATED convenience barrel for the lock protocols
+ * split out of session-lock.mjs in #630 (A1 barrel-preserving split).
  *
- * Re-exports both protocol modules so a consumer can `import { withStateMdLock,
- * withStagingFenceLock } from '@lib/locks/index.mjs'` in one statement. This is
- * a nice-to-have: session-lock.mjs remains the canonical barrel that preserves
- * the original 22-symbol import surface, and the two protocol modules are also
- * importable directly.
+ * @deprecated since 5.2.0, removed in 6.0.0. Import directly from
+ * `./state-md-lock.mjs` / `./staging-fence-lock.mjs`, or from
+ * `scripts/lib/session-lock.mjs` for the canonical 22-symbol barrel that
+ * preserves the original import surface for all its importers.
  *
- * Pure re-export leaf — imports only the two sibling modules, never
- * session-lock.mjs, so there is no import cycle.
+ * This file shipped in 5.1.0 with zero in-repo importers and was deleted in
+ * dd05e0f8 (`check-unwired-features` S4: no hook, npm script, CI job or husky
+ * stage reached it, and it named symbols — not modules — so it did not qualify
+ * for the pure `export *` exemption that shape gets). Restored here as a
+ * one-cycle deprecation shim (`.claude/rules/development.md` § Package Lifecycle
+ * & Versioning) because `package.json` carries no `exports` map: every packed
+ * file under `scripts/lib/` is public, so a consumer that deep-imported this
+ * path before the deletion has no compile error to warn it, only a runtime
+ * "module not found" — a shim buys that consumer one minor cycle to migrate
+ * before 6.0.0 removes the path outright.
+ *
+ * Deliberately the `export *` form with ZERO named exports (matches the
+ * `scripts/lib/autopilot-telemetry.mjs` precedent): a named-export re-export
+ * barrel is exactly the shape `check-unwired-features.mjs` S4 flags as an
+ * unreachable library module (condition 4 in `collectUnreachableLibraryModules`
+ * requires named exports before a re-export shim over live code enters that
+ * census) — that flag is what got this file deleted the first time. A star
+ * re-export names no symbol, so the shim reads as `exports: []` and stays
+ * invisible to that census while its target modules stay reachable through it.
  */
 
-export {
-  STATE_LOCK_PATH,
-  DEFAULT_STATE_LOCK_TIMEOUT_MS,
-  STATE_LOCK_POLL_MS,
-  acquireStateLock,
-  releaseStateLock,
-  withStateMdLock,
-} from './state-md-lock.mjs';
+console.warn(
+  '[deprecated] scripts/lib/locks/index.mjs is deprecated since 5.2.0 and will be removed in 6.0.0 — ' +
+    "import from './state-md-lock.mjs' / './staging-fence-lock.mjs' directly, or from " +
+    'scripts/lib/session-lock.mjs for the canonical surface.',
+);
 
-export {
-  STAGING_FENCE_LOCK_PATH,
-  DEFAULT_STAGING_FENCE_LOCK_TIMEOUT_MS,
-  STAGING_FENCE_LOCK_POLL_MS,
-  acquireStagingFenceLock,
-  releaseStagingFenceLock,
-  withStagingFenceLock,
-} from './staging-fence-lock.mjs';
+export * from './state-md-lock.mjs';
+export * from './staging-fence-lock.mjs';

package/scripts/lib/maintenance-due-banner.mjs

@@ -20,7 +20,7 @@
  * ## Design constraints it is written against
  *
  * - **HR-101 (a signal may only warn if it is rare).** Nothing is due ⇒ the
- *   probe is SILENT. Six independent signals are ANDed with a cooldown, not
+ *   probe is SILENT. Seven independent signals are ANDed with a cooldown, not
  *   ORed into a permanent warning: a repo that ran `/session housekeeping`
  *   within the last {@link HOUSEKEEPING_COOLDOWN_DAYS} days says nothing at
  *   all, because the operator already did the thing the banner would ask for.
@@ -33,7 +33,7 @@
  *   an existing module constant. Same posture as `reconcile-nudge-banner.mjs`
  *   and `loop-readiness-banner.mjs`: an advisory banner needs no switch.
  *
- * ## The six signals
+ * ## The seven signals
  *
  * | id                | due when                                                              | source |
  * |-------------------|-----------------------------------------------------------------------|--------|
@@ -43,6 +43,20 @@
  * | `dialectic`       | `shouldDispatchAutoDialectic().trigger === true`                      | `auto-dialectic.mjs` |
  * | `memory-cleanup`  | `shouldDispatchAutoDream().trigger === true`                          | `auto-dream.mjs` |
  * | `pending-sidecar` | a pending dream/dialectic proposal younger than 14 days is unapplied   | `.orchestrator/*-pending*.md` |
+ * | `generated-rules-expiring` | a machine-generated rule is expired or expires within {@link GENERATED_RULE_EXPIRY_HORIZON_DAYS} days | `instruction-budget-guard.mjs` |
+ *
+ * ### Why the expiry alarm is HERE and not in the test suite (#1372 follow-up)
+ *
+ * The invariant "no generated rule file sits expired in `.claude/rules/`" was
+ * first written as a vitest case comparing `expires-at` against TODAY. That is
+ * a calendar time-bomb in a BLOCKING gate: with nothing committed and nothing
+ * broken, `npm test` — pre-push hook and CI alike — turns red on the morning
+ * after the earliest date and blocks every unrelated hotfix, while the repair
+ * (consolidate the file, move its provenance pairs, delete it) is a human
+ * decision no test run can take. HR-101/HR-105: a signal must fire when
+ * something CHANGED, at a moment the operator can act, and be repairable by the
+ * thing that fires it. Session start, recommending `/session housekeeping`, is
+ * that moment; the predicate itself is still tested, against an INJECTED clock.
  *
  * Only SIDE-EFFECT-FREE signal functions are called — never a variant that
  * advances `.orchestrator/dialectic-last-run`, because a probe that writes the
@@ -66,13 +80,32 @@ import { shouldDispatchAutoDream } from './auto-dream.mjs';
 import { resolveMemoryDir } from './memory-paths.mjs';
 import { readCanonicalSessions } from './sessions-canonical.mjs';
 import { filterRealSessions } from './session-schema.mjs';
+import {
+  daysUntilGeneratedRuleExpiry,
+  listMachineGeneratedRules,
+} from './instruction-budget-guard.mjs';
 
 /**
  * How many signals this probe knows about. The banner denominator is this
  * number MINUS the signals a kill-switch skipped on this host — see the
  * `skipped` array in {@link computeMaintenanceDue}'s result.
  */
-export const MAINTENANCE_TOTAL_SIGNALS = 6;
+export const MAINTENANCE_TOTAL_SIGNALS = 7;
+
+/**
+ * How far ahead the `generated-rules-expiring` signal looks.
+ *
+ * NAMED CEILING (BV-004): 7 days is one week of sessions — long enough that the
+ * operator meets the warning before the loader silently starts dropping the
+ * rule, short enough that it is not standing noise (HR-104: a signal that is
+ * essentially always present is no signal). On this repo's corpus at
+ * 2026-09-16 the earliest `expires-at` was 14 days out, so the row is silent.
+ *
+ * REVISIT TRIGGER: if the row is due on more than ~1 session start in 10, the
+ * horizon is measuring the reconcile engine's 30-day default TTL rather than an
+ * overdue consolidation — re-aim it (HR-101), never widen it.
+ */
+export const GENERATED_RULE_EXPIRY_HORIZON_DAYS = 7;
 
 /**
  * Active-learning floor for the `evolve` signal. Deliberately the SAME number
@@ -391,6 +424,39 @@ export async function computeMaintenanceDue(opts = {}) {
     undeterminable.push('pending-sidecar');
   }
 
+  // --- generated-rules-expiring (S7) ---------------------------------------
+  // The predicate and the population both come from `instruction-budget-guard`,
+  // which is where the generated corpus is DEFINED (its byte ceiling judges the
+  // same set). A local re-implementation would be a second definition of
+  // "machine-generated" that agrees only until one of the two is edited.
+  try {
+    const listed = listMachineGeneratedRules({ repoRoot });
+    if (!listed.ok) {
+      // The directory is there but unreadable — not knowing is not clean.
+      undeterminable.push('generated-rules-expiring');
+    } else {
+      const expiring = listed.rules
+        .map((r) => ({ ...r, days: daysUntilGeneratedRuleExpiry({ meta: r.meta, now }) }))
+        .filter((r) => r.days !== null && r.days <= GENERATED_RULE_EXPIRY_HORIZON_DAYS)
+        .sort((a, b) => a.days - b.days);
+      if (expiring.length > 0) {
+        // HR-106: name the files and the dates the verdict was computed from —
+        // the operator has to open exactly those files to repair this.
+        // HR-106 again, one step further: name the REPAIR, not only the
+        // finding. The sweep (#1377) is the mechanical half — prose out, the
+        // provenance pair kept as `markers only` — and an operator who is told
+        // only which files expired has to rediscover that the command exists.
+        markDue(
+          'generated-rules-expiring',
+          `${expiring.map((r) => `${r.file} ${r.expiresAt}`).join(', ')} → ` +
+            'node scripts/sweep-expired-rules.mjs (dry-run first)',
+        );
+      }
+    }
+  } catch {
+    undeterminable.push('generated-rules-expiring');
+  }
+
   return {
     due,
     // HR-106: the denominator counts the signals this host actually EVALUATED.

package/scripts/lib/peer-discovery.mjs

@@ -68,6 +68,7 @@ import { readLock, isLockLive, LOCK_PATH } from './session-lock.mjs';
 import { checkPeerStateMd } from './state-md-peer-guard.mjs';
 import { listWorktreesChecked } from './worktree/listing.mjs';
 import { parseSessionId } from './session-id.mjs';
+import { isMainModule } from './is-main-module.mjs';
 
 /** Closed enum of provenance sources. */
 const SOURCE_DISCOVERED = 'discovered'; // lock + registry unified (irreversibly merged upstream)
@@ -901,11 +902,7 @@ async function _cliMain(argv) {
 }
 
 const __filename = fileURLToPath(import.meta.url);
-const _isCliMain =
-  typeof process !== 'undefined'
-  && process.argv[1] !== null
-  && process.argv[1] !== undefined
-  && path.resolve(process.argv[1]) === path.resolve(__filename);
+const _isCliMain =isMainModule(import.meta.url);
 
 // Called WITHOUT `await` on purpose: a top-level await would make this module
 // async for every importer, and `_cliMain` cannot reject (all paths are caught