This repository was archived by the owner on Oct 28, 2026. It is now read-only.
Repository navigation
fix: recover a missing startup entry script once - #339
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A cold production visit received a 404 for the initial fingerprinted boot script, leaving the app unable to start its existing recovery. A CSP-hashed inline guard now retries that exact same-origin entry once only after Resource Timing confirms 404/410. Successful startup adds no requests; persistent or unknown failures show an accessible Reload button without changing the page URL, drafts or session storage. A delayed Home response cannot cover the error panel.
Validation: pinned production/static builds and CSP metadata check passed; all 14 boot regressions passed with zero retries, including six new desktop/phone recovery cases. The unchanged deployment/early-paint cases passed (44 cases); static checks passed (18 passed, 19 existing skips). The strict local interaction run retained one failed 51 ms long task against the unchanged 50 ms limit (40 passed, 31 not run) on a busy Mac with overlapping local browser work; it receives no acceptance credit. The normal PR CI must pass every original strict check before merge. No changes to performance tests, retries, deployment readiness or asset warming.
The production trace shows the same entry URL returning 404 and then 200; the underlying CDN cause is not established. This change adds bounded client recovery, with a manual option on browsers that do not expose response status. SpacetimeDB and private mute/block behavior are unchanged.