Repository navigation
Reconnect local operations with scoped cancellation and no old authority - #50
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.
The local workbench now reconnects a refreshed page to the current bounded operation snapshot. It restores progress and scoped cancellation only; selected-directory authority, old plans and apply confirmation are not restored. Stale/missing cancel IDs cannot stop a later operation, and apply/finalizing phases refuse cancellation.
The snapshot uses existing loopback/origin/nonce guards and contains no paths,PID,commands,plans or report bodies. Polling owns one controller/timer, stops on hide/unload and after90 reads. Late plan replies and cached old report views are discarded; immutable history remains available. Shutdown reaps only its own CLI or picker.
Validation:766 tests passed,1 optional Docker reference skipped; type/lint/build pass. Real local Chrome390px used synthetic data and actual readonly CLI verification/safe fixture chmod with backup, covering refresh,cancel IDs,apply refusal,server restart/nonce rejection and browser return. Seven history files remained unchanged; no Skill script or Provider ran. No dependency,release,deployment or current user-data migration.