Repository navigation
Distinguish unavailable delivery checks from application failures - #25
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 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.
Delivery timeouts previously appeared as application failures and recommended repairing D1, missing assets or the public method guard without a returned response. The diagnostic now records unavailable response/body reads as blocked, retains failed outcomes for returned status/JSON/integrity defects, and emits per-check progress separately from the final JSON. Both blocked and failed results continue to prevent certification.
The cloud browser now opens the previously timed-out compliance page and switches its Public Sector tab. Fresh delivery checks verified the bundle, query bounds, POST rejection and all fallback assets; the health request still timed out. The audit separates this recovery from unknown internal cause and the held Machine Data Lake candidate's outstanding report checks.
Validation: all four generation gates, 161/161 tests and 53-asset build passed. The rebuilt Worker is byte-for-byte identical to the deployed source build. This change affects maintenance tooling and operational records; product facts, visitor behavior, storage, active-delivery flag and schedules are unchanged.