Repository navigation
Validate runtime startup and clarify supported control boundaries - #75
Merged
Merged
Conversation
Pitot coding-agent E2EIntelligence Flow is the verification source; Pitot's public README carries the latest
Runtime capabilities
Source commit: |
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.
Change contract
When: A Go application starts Pitot with process registrations or relies on its documented control boundary.
Before: Direct
runtime.Startcallers could bypass configuration checks and launch unsupported registrations or panic on empty commands. Some public descriptions overstated the supported action scope and failure guarantees.After: Startup validates every registration before launching children. Documentation distinguishes native shell control, application-issued requests, and host hook failures.
Boundaries preserved
Evidence
Failure and recovery
Invalid registrations return an error and no runtime manager. Valid registrations whose executables are unavailable retain their configured fallback and diagnostic behavior. Revert this PR to restore the previous startup contract.
Remaining limits
A functioning hook's denial does not establish protection against every host or hook failure. The shipped priority integrations supervise shell tools; SDK support for usage envelopes does not add runtime usage collection.