Repository navigation
fix(ceremony): align CCDP catalogs, Worker selection and trust boundaries - #80
Merged
Merged
Conversation
Wondertan
force-pushed
the
fix/ccdp-conformance
branch
from
October 2, 2026 02:34
b7cb6df to
6ac469a
Compare
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
Wondertan
force-pushed
the
refactor/notarized-layering
branch
from
October 2, 2026 13:03
6fbc40d to
d6f0e25
Compare
Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Report authorization observations from a Bridge-origin Callback in the development application fixtures. Pin the documentation to the reviewed specification revision and record the added conformance checks. Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com> Assisted-by: Claude Opus 5.5
Recognize older content-addressed CCDP scripts when retiring the known nested scope, so it cannot prevent the root Worker from claiming Prover. Preserve unrelated registrations and exercise an older script in the browser regression. Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Retire only /ccdp/v1/worker.js at the old nested scope. Content-addressed scripts have only been registered at root scope, so remove the speculative matcher and make regression fixtures use the actual legacy path. Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Registration needs no popup connection, yet Prefetch started it only after authenticated readiness. It now starts at entry for a supported profile, so installing the pinned Worker overlaps the handshake, which matters most when the handshake is slow. Dispatch still waits for both readiness and that Worker. worker-ready-ms now measures only the part the handshake did not hide. Assisted-by: Claude Opus 5.5 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Wondertan
force-pushed
the
fix/ccdp-conformance
branch
from
October 2, 2026 13:16
a2e127a to
271caec
Compare
The migration e2e seeded the root scope with the current content-addressed Worker, so the transition every existing browser makes on its first visit, from /ccdp/v1/worker.js, ran only in unit tests. The seed now registers the earlier release's Worker at both scopes. It answers nothing, so the run completes only if Prefetch dispatches to the Worker it pins, including a waiting one. Signed-off-by: Wondertan <hlibwondertan@gmail.com> Assisted-by: Claude Opus 5.5
Traceability no longer describes the removed update check for LIBID-ASSET-014, and no longer claims Prover tests that clear retained captures for LIBID-OAUTH-023 (#95). The Worker entry names its content-addressed path, worker-ready-ms says registration starts once the connection is accepted, and the dev README pins the current spec. Signed-off-by: Wondertan <hlibwondertan@gmail.com> Assisted-by: Claude Opus 5.5
Wondertan
force-pushed
the
fix/ccdp-conformance
branch
from
October 2, 2026 13:41
fa8d3c0 to
f9d303f
Compare
No released build registered a nested /ccdp/v1/ Service Worker, so Prefetch no longer looks for one to retire. The Worker-transition e2e now starts from an earlier release's content-addressed Worker, the change every release makes. LIBID-ASSET-020 keeps the root-registration resolution and claim it still tests. Spec links pin PR13 at 66096eb, which drops the matching stale-registration rules. Signed-off-by: Wondertan <hlibwondertan@gmail.com> Assisted-by: Claude Opus 5.5
This was referenced Oct 2, 2026
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.
Stacked on #74. Aligns the implementation with PR13 at
66096eb:{ ccdpVersions, platforms }catalog; refuse an unsupported CCDP version before launch./auth/callbackredirect path. Release retained OAuth captures on terminal cleanup.Updates the cross-origin browser fixtures, package documentation and requirement traceability alongside the fixes.
Validation: 989 ceremony unit tests; 39 build/distribution/native-server checks; 51 ceremony browser checks and 99 dev-app checks across Chromium, Firefox and WebKit; typechecks, builds and lint. Live OAuth and verifier qualification were not rerun.