v5.42.0 — the receipts release
·
319 commits
to master
since this release
v5.42.0 — the receipts release
The front door works, the receipts stopped lying, and won latency is now pinned.
The P0, closed on the live seat
memory_writeno longer dies with WinError 5 on a fresh unsaved scene — scene
memory resolves a writable address, discovery still reads the raw$JOBroot
(G1a + followup), verified over raw WS against the captured cold-boot baseline
(scripts/live_probes/probe_g1_acceptance_ws.py).doctor's permanently-red install-stamp false alarm fixed for repo-direct
installs (G1c).
Four honest-receipt fixes — same family: a green light that couldn't say no
healthnow carrieswrite_plane(and its probe can no longer hang ~43 hours
on an ACL-denied dir — one non-retrying syscall, pinned by a real icacls test).composition_validcarries a real verdict (it had ZERO assignment sites — an
anchor that could never fail). Failed compositions now read fidelity 0.0.- Ops that fail BEFORE validation record
composition_applicable=falseinstead
of inheriting "ran and passed" (K4). - Reduced-mode hashing is now COUNTED:
operation_stats()lifetime counters +
the session tracker'sunobservable_deltas(R306). Fidelity semantics
deliberately untouched.
Latency: measured, fixed, and pinned
- The agent loop stamps an incremental prompt-cache breakpoint each iteration
(kills the O(K^2) re-prefill) and captures real usage vialast_usage— the
producer that can finally price it. - The stage-hash gate re-keyed on AUTHORED ARRAY VOLUME: a 4-prim/2M-instance
stage that slipped a 16,677x miss past the prim gate now takes the reduced
path (~55,000x cheaper, measured on two machines). - Non-saturating T4 phase timers (
synapse_composition_ms,
synapse_stage_touch_ms) — a 7 s event lands in a real bucket instead of
vanishing at the old 4–5 s ceiling. - One stage walk per op instead of two (
_stage_exceedsper-op cache),
independently confirmed by the perf ratchet's own counters. - The perf ratchet is ARMED: counted-proxy floor, read at
merge-base(origin/master) so a PR cannot gate against its own doctored floor,
CI-runnable with zero pxr. Counts fall freely; rises need a human-promoted
floor. - The scale bench sweeps the axis: prims held at 4, the gate flips on
volume alone between 500k and 1M authored elements. Offline tier emits
COUNTS ONLY — enforced in code, not prose. - Latency board:
harness/latency/— 8 PASS / 0 FAIL / 0 PENDING.
Suite hygiene
- The module-planting class (synthetic packages in
sys.moduleswithout
parent-attribute binding) fixed at 26 files;tests/pkgbootstrap.pyis the
one sanctioned way to plant. - Refuted and recorded so nobody re-litigates: extending declarative coverage
(would ADD a round-trip), H1 topo-hash cost (cookCount never cooks), H2
blast-radius cost (0.039 ms at N=500).
Suite at tag: 5540+ passed / 0 failed (main checkout). Producer paths for every
number: harness/latency/LEDGER.md + LOG.md.
Same-day additions (post-tag, on master)
The tag is fada390; the release day kept going. Three more merges, each
crucible-verified, all on master:
- First live-tier bench rows ever (
b7d2d14). Two wire-contract defects
surfaced on the bench's first contact with a real bridge and were fixed
client-side: the arm dialed the bare root (the WS handler mounts at
/synapse), and liveexecute_pythonresults arrive stringified (parse
ast.literal_eval). The measurement: live-path cost is flat across
100k -> 4M authored elements (ping ~0.4 ms, set_parm ~3.7 ms) — confirming
the live envelope skips the stage term by construction, so only the audited
path ever needed the volume gate. - The suite flake is dead, and it was a production bug (
6daac63). A test
built the process-wide FreezeChain at production thresholds and nothing
could stop it —shutdown_freeze_chain()did not exist. Its 30-second
escalation timer fired into whichever test was running, which is why the
victim differed every time. The fix is production-shaped: the shutdown
counterpart now exists and the panel'scloseEventcalls it, so closing the
panel no longer leaves a timer that force-opens the breaker against a live
bridge 30 seconds later. Plus the module-planting sweep: 9 sys.modules /
parent-attribute divergences -> 0, including the newly named
restore-without-rebind shape. - README refresh (
5e8973f): the volume-axis story, the receipts, the
measured two-path cost asymmetry, and current figures — every number with
its producer.
Suite at head of release day: 5,551 passed / 0 failed — the first
zero-failure full run with the flake mechanism removed rather than dodged.