Repository navigation
feat: integrate immutable review artifacts with sandboxed orchestration - #26
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
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.
Summary
Implements M4.3b orchestration wiring and tightens the M4.2 process lifecycle contract.
terminates_process_tree_on_exitto SandboxBackend capabilities; backends that cannot prove descendant cleanup are ineligible.--require-sandboxis enabled, using a sanitized environment and profile timeout.Security boundary / limitations
No production OS backend exists yet. Therefore
--require-sandboxstill fails closed before the Agent starts, and this integration cannot yet complete a sandboxed task end-to-end. Legacy unsandboxed runs continue to work but do not auto-export immutable review artifacts and cannot be treated as isolated.The backend must prove process-tree inheritance and kill all descendants before returning; otherwise the workspace cannot be considered frozen. The Artifact Broker still uses conservative sensitive-path filtering, not a full secret scanner.
Validation
CI will run the repository quality/security gate and full unittest suite.