Repository navigation
Expose typed lazy discussion reads through workbench services - #189
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.
Scope
Refs #178. Service-only foundation building on merged #187; the broader issue remains incomplete.
Verification
Explicit limits
No UI controls, completion-generation state, transcript import, persistence/resume or new snapshot schema. UI callers still need exact session/generation and pinned-identity guards, including same-head refresh. No new concurrent-permit saturation test or UI completion-race qualification; cancellation is checked before/after reads, not a claim of transactional cancellation. No live Entire/native GUI verification. No verified inline anchor or approval/merge-readiness claim.