Close the service-worker drift left unresolved by observation 0001 - #13
Merged
Conversation
Observation 0001 recorded repository aaig-v85 against production aaig-v84 and deferred. The pin has since advanced to aaig-v87 and no later receipt had re-observed the deployed file, so an unresolved finding was aging out of view rather than being closed. Fetched sw.js from production and compared it to the committed bytes. They are byte identical, and both name cache aaig-v87. The receipt closes the current-state question only. It records that the v85 and v86 generations were never observed in production and cannot be reconstructed from it, that one edge was sampled, and that installed client caches were not inspected. Checkpoint 000013 seals the new event. The projection root is unchanged at 22852b5a3025, because an OBSERVE decision with effect NONE must not advance accepted state. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying resilience-eval-ai with
|
| Latest commit: |
826b1c0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fb844630.resilience-eval-ai.pages.dev |
| Branch Preview URL: | https://receipt-close-sw-drift.resilience-eval-ai.pages.dev |
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.
What this closes
Deployment observation
0001recorded repositoryaaig-v85against productionaaig-v84and returnedDEFER. The runtime pin has since advanced toaaig-v87and no later receipt re-observed the deployed file, so an unresolved finding was aging out of view rather than being closed.What was observed
Fetched
sw.jsfromhttps://resilience-eval-ai.pages.dev/sw.jsand compared it to the committed bytes.fa01638d7399…fa01638d7399…aaig-v87What the receipt does not claim
It records that the
aaig-v85andaaig-v86generations were never observed in production and cannot be reconstructed from it, that one edge was sampled, and that installed client service-worker caches were not inspected. The claim ceiling is stated in the payload.Chain state
000003-service-worker-drift-closed.jsonappends to thedeploymentstream at sequence 3,prev_event_hashbound to000002.checkpoint-000013.jsonseals the resulting 17-event inventory.governance/ledger/lib.js, not by hand.22852b5a3025. AnOBSERVEdecision witheffect.kind: NONEmust not advance accepted state, so this is the expected result rather than an oversight.Verification
node governance/harnesses/run-all.jspasses, 34/34 holds across 12 suites.🤖 Generated with Claude Code