fix: stream FableLoom editorial and production progress - #8568
Merged
Merged
Conversation
atomantic
force-pushed
the
claim/issue-8544
branch
from
September 26, 2026 01:08
4c02776 to
0c94373
Compare
atomantic
force-pushed
the
claim/issue-8544
branch
from
September 26, 2026 01:10
0c94373 to
8f712c7
Compare
4 tasks
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.
FableLoom editorial autopilot and episode production now update from scoped run snapshots instead of two-second polls. Both views reattach on entry, reconnect, and tab show; revision and identity guards discard stale reads and mutation responses. Terminal refreshes happen once per run attempt, including resumed production.
The server emits snapshots at authoritative transitions, declares the socket payloads, and offers a read-only latest-production-run endpoint. Snapshots stay on the FableLoom subscriber channel and omit runtime handles.
Validation: 44 client tests and 135 server tests passed, covering rendered event updates, no timer reads, recovery, stale identities, terminal deduplication, service transitions, routes, and socket delivery. Post-rebase
npm run pregatepassed. CI will validate the remaining build, database, Windows, and smoke gates.Closes #8544
Part of #8534