@feigi/fleet-ctl 3.68.0 → 3.68.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@feigi/fleet-ctl",
3
- "version": "3.68.0",
3
+ "version": "3.68.1",
4
4
  "description": "Agent fleet: run-team controller, merge bot, PR reviewer, and the ticket pipeline they share",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -1288,6 +1288,19 @@ export function noTranscriptLines({ live, seen, stems, session, after, now }) {
1288
1288
  return out;
1289
1289
  }
1290
1290
 
1291
+ // The age-based checks this tick would run: CHECK-LIVENESS on
1292
+ // a live name of a known family, NO-TRANSCRIPT on a live member token with no
1293
+ // transcript among `stems` (null when the session was not listed). main()
1294
+ // names them on stderr when the state file is degraded: its `seen` stamps
1295
+ // cannot be read, so every token reads as first seen now and neither fires.
1296
+ export function ageChecks({ live, stems }) {
1297
+ const has = new Set(stems);
1298
+ return [
1299
+ ...(live.some((name) => livenessFamily(name) !== null) ? ["CHECK-LIVENESS"] : []),
1300
+ ...(stems !== null && live.some((name) => parseMember(name) !== null && !has.has(name)) ? ["NO-TRANSCRIPT"] : []),
1301
+ ];
1302
+ }
1303
+
1291
1304
  // --apply's pure half. The merge-bot numbers `applied.reapAfter` names for
1292
1305
  // THIS run: none when its `run` is not the controller record's `at`, since
1293
1306
  // merge-bot numbering restarts with a run and the state file outlives it
@@ -2087,6 +2100,8 @@ function main() {
2087
2100
  // registry census. It is not a row — it resets no `quiet`, moves no count
2088
2101
  // and frees no slot — and nothing here settles, kills or writes the ledger.
2089
2102
  const seen = stampSeen({ live: run.live, prev: prev.seen, controller: prev.controller, now });
2103
+ const ageless = prev.degraded ? ageChecks({ live: run.live, stems }) : [];
2104
+ if (ageless.length) console.error(`${NAME}: ${ageless.join(" and ")} not checked — ${path} ${prev.degraded}, so first-seen ages are unavailable`);
2090
2105
  const stale = livenessLines({ live: run.live, seen, thresholds: liveness, now });
2091
2106
  // Advisory the same way: a report on disk prints the settle it is for, and
2092
2107
  // nothing here runs it.
@@ -1304,7 +1304,14 @@ depth** guard table applied in code. Act on each line as it reads:
1304
1304
  `task` call, or settle the token `killed`. Advice the same way, folded as
1305
1305
  `…; NO-TRANSCRIPT <member> persists — …`. Both lines read the session
1306
1306
  directory this run's phase-0 receipt names, else `--session <dir>`; with
1307
- neither the tick skips them with one stderr line.
1307
+ neither the tick skips them with one stderr line. A heartbeat state file
1308
+ that exists but cannot be used — unreadable, not JSON, not a JSON object,
1309
+ or holding a `controller` that cannot be judged — holds no first-seen
1310
+ ages, and the tick never rewrites it, so every live token reads as first
1311
+ seen that tick and neither `CHECK-LIVENESS` nor `NO-TRANSCRIPT` can fire.
1312
+ The tick says so with one stderr line, `fleet-tick: CHECK-LIVENESS and
1313
+ NO-TRANSCRIPT not checked — <file> <cause>, so first-seen ages are
1314
+ unavailable`, naming only the checks that would have run that tick.
1308
1315
 
1309
1316
  **Tier guards under Pull.** The per-dispatch `tier-check.mjs --batch` is
1310
1317
  phase 2's own step, run by `tick --apply`: a mismatch it finds is the