fix(mapgen-studio): run-in-game proof matches again — turbo passes SWOOPER_STUDIO_RUN_ID through the cached build + fail-fast bundle guard#1659
Merged
Conversation
This was referenced Jun 12, 2026
Merged
Owner
Author
This was referenced Jun 12, 2026
Owner
Author
Merge activity
|
mateicanavra
changed the base branch from
design/effect-substrate-spike
to
graphite-base/1659
June 12, 2026 22:50
…OOPER_STUDIO_RUN_ID through the cached build + fail-fast bundle guard
Root cause of the 'Waiting for Proof' zombie: gen:maps runs inside turbo's
CACHED build task and SWOOPER_STUDIO_RUN_ID was never declared in
turbo.json — strict env mode stripped it (and the cache could replay a
stale bundle), so the deployed map script logged [mapgen-proof]
{"requestId":null,…} (observed live in Scripting.log) and the ordered
marker waiter could never match. Every Run in Game sat the full 90s log
timeout in waiting-for-proof while the game reached turn green.
- turbo.json: build.env [SWOOPER_STUDIO_RUN_ID] — env-visible AND
cache-correct (verified both directions: with env the id lands in the
generated source + bundle; without, it drops).
- engines.ts: post-deploy guard via mapScriptEmbedsRequestId — a bundle
that does not embed the request id fails immediately with
run-request-id-not-materialized + recovery hint instead of zombying.
Verified live end-to-end: Run in Game → materializing → … →
waiting-for-proof → Complete; proof line carries the request id; chip
shows Complete · Current.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mateicanavra
force-pushed
the
design/y1-run-proof-request-id
branch
from
June 12, 2026 22:52
7d4d183 to
a718bc0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause of the 'Waiting for Proof' zombie: gen:maps runs inside turbo's
CACHED build task and SWOOPER_STUDIO_RUN_ID was never declared in
turbo.json — strict env mode stripped it (and the cache could replay a
stale bundle), so the deployed map script logged [mapgen-proof]
{"requestId":null,…} (observed live in Scripting.log) and the ordered
marker waiter could never match. Every Run in Game sat the full 90s log
timeout in waiting-for-proof while the game reached turn green.
cache-correct (verified both directions: with env the id lands in the
generated source + bundle; without, it drops).
that does not embed the request id fails immediately with
run-request-id-not-materialized + recovery hint instead of zombying.
Verified live end-to-end: Run in Game → materializing → … →
waiting-for-proof → Complete; proof line carries the request id; chip
shows Complete · Current.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com