[PavelMakarchuk]

Stacked on #197. GitHub retargets it to main once #197 merges.

Summary

The Build progress tab now reads the process telemetry that PolicyEngine/microcosm#1082's follow-up adds to US release builds, branch staging-telemetry-p0. Runs that don't report it look exactly as before.

• Cores and memory per stage. Cores are CPU seconds divided by wall seconds between the stage's start and end resources. Memory is the larger resident set at either end. Both appear on timeline rows, and as medians and maxima in "Where build time goes". The overview adds a line for the running stage: "1.0 of 18 cores busy in Target compilation · memory 62 GB of 128 GB · peak 81 GB · commit …".
• Heartbeat. A run that sends heartbeats is marked stalled after five minutes without one (HEARTBEAT_STALE_MS), not six hours. That makes an out-of-memory or SIGKILL death visible quickly.
• Measured batch progress. work in the progress document gives batches done, the total and the time spent so far.
  • The current stage's remaining time follows that measured rate once 3 units are done.
  • History still forecasts what comes after the stage.
  • Calibration's epoch rate stays a floor only, because size search repeats passes.
• Failure classes. A failed run shows its class (gate refused, terminated, interrupted, out of memory, refused, error). A new "Why runs stop" table counts runs by class, together with the median compute already spent. Blocked runs count as gate refusals and silent runs as "stopped without a final event".
• Identity. The run manifest's commit, runtime versions, CPU count and memory are shown.

Testing

• bun test: 529 pass, including new tests for cores from resources, measured batch rate with and without history, heartbeat staleness, failure-class counts and identity parsing. tsc --noEmit passes.
• End to end: I drove microcosm's real StagingTelemetry from the staging-telemetry-p0 branch through a simulated US release, local only with no uploads, and watched it on the local tab.
  • Batch progress appeared, and the remaining time followed the measured rate.
  • Cores and memory appeared per stage, along with the heartbeat age, the host and the commit.
  • The run ended in a classed gate refusal with its failure lines.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
calibration-diagnostics	Ready	Preview	Oct 1, 2026 8:09pm UTC