Keep explicitly internal histories out of ordinary chat discovery - #187
Merged
Brian Krabach (bkrabach) merged 5 commits intoSep 23, 2026
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
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.
Explicit internal jobs and runtime children no longer appear in ordinary chat discovery, counts, or default history searches. Saved metadata and transcripts stay intact; deliberate independent forks remain ordinary chats. Unmarked legacy jobs remain visible because classification requires reliable provenance.
The consumer reads native history metadata directly. It never imports, installs or invokes amplifier-app-cli. The earlier cross-repository CLI test helper and CLI-based producer workaround are excluded; standalone memory inference is being handled separately.
Validation: 172 focused history/navigation/recall Python tests passed; focused frontend navigation/MCP lifecycle tests passed; integrated frontend assets rebuilt against current main. Existing prior candidate CI passed. No live Spark session access or reclassification was performed.