Repository navigation
integration(identity): promote merged #172 token-delivery boundary into main - #175
Merged
Merged
Conversation
… owner Refs #162 #83 #85. Preserve issuance/claim transaction timing, legacy derivation and receipt bytes, expiry and one-time response semantics. Application only composes/delegates; authentication shares the exact verifier. Narrow current clock/window providers preserve live settings changes. All three native source blobs match the reviewed local text.
…dary-20260929 refactor(identity): separate one-time token delivery from Application composition
LIghtJUNction
marked this pull request as ready for review
September 29, 2026 10:06
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Sep 29, 2026
LIghtJUNction
added a commit
that referenced
this pull request
Sep 29, 2026
…authority Closes #161. Independent HostingRuntime and canonical callback-free Registry/auth, no writer secrets or startup writes; explicit group-read publication and dedicated OS/DB deployment. Retains #174 ownership/isolation regression provenance and #175 token history. Final head2b80 / treef377ce7 verified: hosting41, token122, full1935 exact-node-ID union, conformance8, actual tokenizer, wheel/sdist and contracts gate all pass with zero test failures/errors/skips. Full36553079854; artifact hashes and source identity in #173. Synthetic merge4827630 onto actual mainedbfbae has identical tree. No production deployment or broader acceptance closure.
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.
Closes #162. Refs #172 #83 #85.
Why this promotion exists
#172 merged into
fix/executor-core-20260929-2045, not main. This PR promotes its exact merge commitb0b51205c8273c2d89bf99c7facf9e56767bc8d2to main without modifying either original branch or reimplementing credential delivery. Compared with main261c8816, the six-file delta is only the original token-boundary change.Reviewed ownership and preserved contract
security.token_delivery.TokenDeliveryexclusively owns derivation, recovery binding, transactional recording and response-only release. Application constructs it and retains policy-free compatibility forwarding. Authentication imports the same recovery verifier. The capability takes explicit metadata/key/clock/window dependencies, not Application/Registry/signers/vault/Root. Read the complete owner and all seven new boundary tests.Issuance/recovery binding remains in the business transaction. Release eligibility is claimed and committed before the adapter sees the secret. A lost response uses the existing bound recovery flow; persisted results/events/receipts never gain the token. IDs, purposes, operation versions, signatures, recovery deadlines and replay policy are unchanged.
Independently inspected current-head evidence
Head b0b5120. Focused source manifest: merge checkout
8c86062ba7c60f63d7a4824bce66db1db0f0001c, treeebe1facca432803854d0c04aaa93519a589ff93f, Python3.15.0rc2, attempt1.9079f195d8d49568fe502c140ec7e2f05412bf751852ef180d74e681610a3312verified.msg.nodeidwith each selected list and the shared complete inventory: 1901 passed, no missing/extra/duplicate nodes, zero failures/errors/skips. Shards: 465/496/483/457.Full artifact SHA256 by shard:
0 /11025483081
c41a6794601749addc90807efe9d0ec4184bea5db069c30ff120cf136c152ada1 /11025244066
8bab2e991b774c4c27b28e70c25593d4104105f6750dd77fc3651dbb57b56eea2 /11025219177
c8e42dba88fe618477ff393827fd11a91c7f90f01c0b0428ae82f24aa5c284b63 /11025740416
0dc2452ab2439dcae67de399bb436b5711d7bdf3d156bd8fcf106d424c6681e9Original RED/history remains in
docs/TOKEN_DELIVERY_BOUNDARY_PROGRESS.md; this PR records the final promotion evidence without an unnecessary source-changing documentation commit. #173 already preserves this head as a real parent and is independently testing the combined hosting/token/ownership tree; its gates remain separate. Merge serially with an expected-head check, then verify main's actual tree.All execution/tests/builds were in GitHub Actions. No deployment, production secrets, real Root/PIN, funds, outbound delivery or recovery promotion. Closing #162 does not close the umbrella/production acceptance issues or reopen completed #67.