garrytan 36a97ceed3 A3: a JUnit case's recorded wall is capped by its shard's wall ...

junitCensus summed a case's JUnit test times as duration_ms; for
plan-mode-no-op's concurrent PTY tests that is 346 s inside a 176 s shard
(the "432-613 s" history). The case wall headroom shows is now
min(sum, shard elapsed), a true upper bound. Session headroom already
used the ledger's per-session clocks.

2026-10-04 18:44:34 +00:00

..

eval-history.ts

0.3: published lines cannot break a fixed fence

2026-10-04 18:02:05 +00:00

free-home-guard.ts

v1.91.16.0 fix: safe installs and upgrades, skills start everywhere, truthful completion (parallel wave) (#3014)

2026-10-03 07:54:09 -07:00

paid-cases.ts

v1.91.19.0 fix: severe fix wave (truthful gates, no lost memory, every host finds gstack) (#3025)

2026-10-04 07:58:41 -07:00

paid-plan.ts

v1.91.19.0 fix: severe fix wave (truthful gates, no lost memory, every host finds gstack) (#3025)

2026-10-04 07:58:41 -07:00

paid-report.ts

A3: a JUnit case's recorded wall is capped by its shard's wall

2026-10-04 18:44:34 +00:00

published-text.ts

0.3: published lines cannot break a fixed fence

2026-10-04 18:02:05 +00:00

shard-engine.ts

v1.91.16.0 fix: safe installs and upgrades, skills start everywhere, truthful completion (parallel wave) (#3014)

2026-10-03 07:54:09 -07:00