Repository navigation
feat(channels): complete conversation continuity v2 - #432
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.
Summary
LingThread,LingTurn, andConversationItem, with explicit Root, Topic-anchor, and Thread surfaces.Test Coverage
All new critical paths have automated coverage, including:
Pre-Landing Review
No unresolved findings. SQL/data safety, concurrency, LLM trust boundaries, enum consumers, API contracts, Web state races, performance, and legacy-authority cleanup were reviewed against the final diff.
Design Review
Lite design review: no issues found. This change reuses existing Channel UI surfaces and introduces no new CSS or visual system.
Eval Results
Provider-independent semantic fixtures cover Chinese and English continuation, topic switching, ambiguous references, content generation versus execution, explicit commands, inaccessible Segment ids, and multi-agent privacy. No paid live-provider call is required for this merge gate.
Scope Drift
Scope Check: CLEAN. The diff completes S7 API/Web/authority cleanup and does not introduce a second timeline store, compatibility layer, new infrastructure, or unrelated UI redesign.
Plan Completion
Continuity v2 implementation tasks G0 and T0-T8 are complete. No architecture, ownership, or product decisions remain unresolved.
Verification Results
git diff --check: passedDocumentation
Updated the daemon API reference, Continuity v2 owning design and implementation plan, Channel streaming, intent selection, session, governance, shared conversation capabilities, and implementation status.
Closes #421