Backfilled from the 2026-05-25 nightly fire — the nightly PM silently missed 5/24 (noLAUNCHEDline innightly-startup.log; the log jumps 5/23 23:16 DONE → tonight 5/25 23:05). That's the documented machine-sleep / WTS-launch failure mode again — another data point for the opennightly-pm-silent-gapdecision.
(unchanged from 5/23 — same three items carried forward; see today's 5/25 writeup for the refreshed list)
/trading/dev/ams/_auth/, /cockpit/, /_api/cockpit/, /app/, /scorecards/ — and book_health_v1.json in /_api/cockpit/cache/ was regenerated. Pattern matches the prior AMS smoke-test passes during the Phase 3a integration window; no production AMS push, dev-tree only.p0-freshness-dashboard — ~10 days deferred./z/trading/dev/ams/_auth/error_log, /cockpit/error_log, /_api/cockpit/error_log, /app/error_log, /scorecards/error_log — AMS smoke testing (19:20–19:21 ET)/z/trading/dev/ams/_api/cockpit/cache/book_health_v1.json — cache regen during AMS test/z/public_html/scorecards/trade_scorecard_2026-05-24.html — auto-pipeline 16:30