Repository navigation
Add deletion approval prototype with installed replay and operator console - #92
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.
Changing a Cursor rule's glob can remove a deletion-approval requirement from the selected target while both scans still score 100. This adds a reproducible prototype showing the released ACS review gate detecting that loss, a repair passing review, and a separate host executor refusing a single-file deletion without a matching operator grant.
The repository example includes an operator console, 12 scripted execution scenarios with real temporary-file postconditions, retained JSON/Markdown evidence from the official PyPI 0.26.1 installation, and 13 gate regression tests. Installed-wheel CI replays both layers on Linux, Windows and macOS and retains the reports.
The executor is example code, not a new ACS runtime feature. Automated operator approval is explicitly a harness simulation. The host must exclusively own a stable local workspace and deny the agent other execution/filesystem channels; arbitrary code, shell access and concurrent path replacement are outside this prototype's boundary. OS errors report an unknown effect instead of successful refusal. Existing runtime, version and GIF assets are unchanged.
Validation: full local suite (648 tests, 13 platform skips); focused gate suite (13 passed after final error-status adjustment); official installed-wheel replay (2 static comparisons and 12 execution scenarios); console approve/refuse paths; existing-output and missing-interpreter refusal; retained input hashes; repository score gate and diff checks. CI must pass before merge.