The pipeline warm pass held a 10 s budget and timed out 5.2 s in, leaving
pipelines to compile live — a visible stall each. `Time<Real>` is sampled at the
top of the frame, and the frame the menagerie spawns in is the frame that loads
the in-game UI: his login's 3.9 s (4.8 s the day before) came out of the budget
before the first rig was ever revealed.
His own log says so without a bisect: "2069 rigs drained in 9.75s" printed 5.84 s
after "menagerie up", and 9.75 - 5.84 = 3.91 s, exactly that session's
`in-game UI up in 3907 ms`. It cleared the timeout by a quarter of a second.
The stamp is now an `Instant` read in the system, taken *after* `spawn_menagerie`:
building the rigs is the frame's own cost, which no timeout can cut short, so
charging it to the reveal only shortens the reveal. The spawn line prints that
build cost and the timeout line prints how far it got, so the next failure reads
as "too slow" or "budget stolen" with no further instrumenting.
And a live compile now names the near miss instead of just its own identity:
every variant that compiled behind a cover is kept as a `Variant`, and an
uncovered one logs the warm variant it is closest to and the single field that
differs — `cull=None (warm Some(Back))`, `vs_defs +WOW_RIG_SKIN` — or says no warm
variant carries its label at all, which is a missing menagerie arm rather than a
missing variant. One field is an edit; a 900-character pipeline identity is a
research project.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SgstFWtn1RxEJ5kVrpgYwn
gromandClaude Opus 5
c13c85615c