Repository navigation
test(search): verify discovery in published CLI binaries - #12
Merged
Merged
Conversation
This was referenced Oct 10, 2026
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.
Published CLI discovery previously had only a temporary verification script tied to the documentation build. Add an on-demand cli-testing harness that seeds an isolated synthetic archive using the published store API and judges both strict and discovery search through the actual installed tg/max binaries.
The fixture verifies eligible reply retrieval, parent provenance, author filtering and unchanged strict defaults. The preloader rejects network/DNS/keyring sockets; inherited account configuration is discarded. Exact package versions, runtime and verifier hashes are recorded. This is a small contract check, not a ranking or live-provider benchmark; it stays outside the published runner suite.
Validation: tg 0.44.0 and max 0.43.0 freshly installed with scripts disabled both passed; lint, typecheck, 59 runner tests with coverage and docs checks passed. Synthetic reports and installation lock remain in /tmp.