Repository navigation
Fix Site archive checks for current Cloudflare JSD wrapper - #82
Merged
Merged
Conversation
ELRdn
changed the title
This branch was successfully deployed
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
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.
Site deployment rejects unchanged public HTML when Cloudflare emits its newer parent-location JSD wrapper. The existing normalizer recognizes only the older script wrapper, so request-specific ray IDs and timestamps falsely appear to be release changes.
Normalize the observed ID/time fields and request ID query. Cloudflare alternates two loader bodies on consecutive requests; canonicalize only the exact two observed bodies. Any other script or HTML change, malformed metadata, missing asset or checksum mismatch still fails verification. Retirement windows and previous-shell evidence remain enforced. Also report the concrete failure reason.
The failures were reproduced using public responses observed from a read-only GitHub runner. All 12 archive safety tests pass, covering all four old/new loader combinations and rejection of changed scripts, changed app entries, invalid timestamps/queries and unsafe archives. Three consecutive source/probe comparisons match on a GitHub runner. The temporary diagnostic workflow was restored exactly; no workflow change remains in the final diff. This unblocks production deployment of the Agent avatar fix in #81.