build: add capsec capability-security tokens to CLI and infra adapters#103
Draft
build: add capsec capability-security tokens to CLI and infra adapters#103
Conversation
Thread capsec SendCap tokens through the CLI boundary into all I/O adapters (filesystem, network, subprocess). This is plumbing-only: tokens are minted at the entry point and passed to adapter constructors to make I/O permissions explicit in the type system. Actual enforcement is limited to FileConfigStore and LocalFileArtifact; git2 and reqwest adapters hold tokens as documentation markers for now.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Auths Commit Verification
Result: ✅ 1/1 commits verified |
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.
Thread capsec SendCap tokens through the CLI boundary into all I/O
adapters (filesystem, network, subprocess). This is plumbing-only:
tokens are minted at the entry point and passed to adapter constructors
to make I/O permissions explicit in the type system. Actual enforcement
is limited to FileConfigStore and LocalFileArtifact; git2 and reqwest
adapters hold tokens as documentation markers for now.