Diagnostic only · 2026-08-07
Dark Factory: contained route-health diagnostic
- Stopped at
- review
- Reason category
- technical
Executive summary
The promoted Lantern Index route returned HTTP 500. Containment rolled production back to the recorded pre-promotion Worker version, restored core routes, and left the game route withdrawn; no candidate is published by this record.
Context considered
Lantern Index was shaped by the sanitized 2026-08-07 theme-selection evidence: an underground archive, route restoration, and linked rooms. The committed sanitized trend longlist preserves source signal ids and topic labels but not public article metadata, so this backfill does not publish article titles, URLs, or quotes.
Selected frame: The Lantern Archive · Action-adventure / Metroidvania
The factory story
The brief
The scheduled run completed controlled design, local validation and review work before its production route-health check.
What was researched
Only sanitised research and controlled handoffs informed the candidate work; this diagnostic exposes no raw research or candidate source.
What was decided
A production HTTP 500 overrides local readiness evidence, so the promoted version was withdrawn rather than repaired in place.
What was built
The candidate isn't made playable or linked by this report.
How it was validated
Rollback deployment c88876b5-88b1-452d-a13f-bd123c1a339d restored the recorded pre-promotion Worker version. The homepage, Dark Factory landing route and an existing report route returned HTTP 200 after rollback.
Independent review
A new immutable candidate must repeat the invalidated review, preview, blind-playtest, assurance and release gates before a future promotion.
What happened at release
No candidate is merged, deployed, catalogued, linked or made playable by this diagnostic-only record.
Outcome
The failing game route remains withdrawn after containment; the next scheduled run remains enabled.
What we learned
A locally reviewed candidate isn't release-ready until its exact production route is healthy, and missing telemetry remains null rather than estimated.
Run timing and token use
Step timing and token telemetry was introduced after this historical run, so no figures are available to publish.
Checks completed
- The promoted game route failure was identified as HTTP 500.
- Rollback restored the recorded pre-promotion Worker version.
- Core routes were verified healthy after rollback while the game route remained withdrawn.
- The terminal diagnostic names the invalidated gates and required remediation.
What happens next
The next calendar day’s run remains scheduled.