Uh oh!
There was an error while loading. Please reload this page.
Phase 5: preserve mixed-source context across follow-up turns - #1070
Merged
Paul Lizer (paullizer) merged 1 commit intoJul 23, 2026
Conversation
Paul Lizer (paullizer)
merged commit Jul 23, 2026
d7e04ec
into
fix/1031-tabular-row-orchestration-scale
2 checks passed
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Summary\n- Add a default-off �nable_mixed_source_conversation_continuity flag, effective only with the existing Phase 2 Chat/Search flag.\n- Persist a compact, privacy-safe continuity record through the existing conversation metadata path, with source identity, role/order, native engine, version, terminal status, aggregate coverage flags, and citation/artifact counts.\n- Keep current explicit selections authoritative. History references are reauthorized through the existing Phase 1 manifest before native evidence processing; version changes and incomplete prior coverage require fresh execution.\n- Cover compact serialization, selection precedence, revocation/version decisions, standard/streaming parity wiring, and version alignment.\n- Update feature documentation and release notes for