Repository navigation
Prove one-use grants across two local Node processes - #234
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.
Milestone
Extend the optional host-owned approval store from one process to two Node workers sharing a trusted local filesystem. Both workers race to create one exclusive claim marker before the simulated tool callback. A recorded run shows one callback and one blocked replay.
Visual proof
Add a new GitHub Pages race page and SVG, driven by a checked-in JSON report that a fresh CLI run must match. Link the page from the repository README, the action pilot, quickstart, milestones, and live lab.
Verification
node --test test/action-boundary-file-grant.test.js test/action-boundary-one-shot.test.js test/action-boundary-guarded-tool.test.jsnode pilots/action-boundary/file-grant-race-demo.mjsLimits
Project-authored local filesystem prototype only. It does not authenticate an approver, work across machines or network filesystems, send a message, prove delivery, or cover unwrapped tools. A production host needs private storage, cleanup, clock policy, idempotency, and authorization.