Characterize SessionService extraction behavior#58
Closed
ashwin-pc wants to merge 1 commit into
Closed
Conversation
Owner
Author
|
Closing this experimental stacked refactor and removing its branch as requested. |
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
1 participant
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.
Stage 2e safety ratchet
Adds API-level characterization tests before moving session ownership behind
SessionService. These cover regressions that a first green-but-invalid extraction exposed:retryFromFailurehelperinvocationNameornameThe only production changes bind the existing extension UI context in mock sessions so these compatibility paths can be exercised. No runtime behavior is added.
Validation: typecheck, full unit/E2E suite, build, diff check.