test(e2e): verify persistent work item continuations - #949
Closed
Neonforge98 wants to merge 2 commits into
Closed
Conversation
Collaborator
Author
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.
Problem
The Work Item continuation stack had unit coverage but no rendered two-instance proof that a non-owner comment runs locally, reuses one durable runner, advances only the shared-plane delta, and becomes visible on the owner instance. The dual-instance harness also let its WebView identifier and Rust service ports disagree, producing false Git-scope failures.
Solution
Potential risks
The F2 fixture is intentionally large because it drives two real Tauri/WebDriver instances and the official cloud RPC boundary. It runs against the mock provider to avoid spending user credentials, so real External CLI subscription execution remains a separate manual/targeted verification cell. Runtime identity remains bounded to instance ids 2..99; invalid profiled identifiers fail closed to the primary profile.
Verification