Repository navigation
refactor(provider-testing): extract the provider replay toolkit - #17284
Closed
juliusmarminge wants to merge 1 commit into
Closed
juliusmarminge wants to merge 1 commit into
juliusmarminge wants to merge 1 commit into
Conversation
Replay fixtures are how adapters prove behavior, but the pieces a provider needs to record and replay transcripts lived in the server's orchestration testkit. Move the provider-agnostic parts into a new @t3tools/provider-testing package: NDJSON transcript decoding and workspace placeholders, the replay gate, and the git checkpoint workspace. Each module gains focused tests. The orchestrator-backed harness and the runtime-instruction rewrite stay in the server for now, because they depend on orchestration services and server prompt text. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
the
vouch:trusted
juliusmarminge
added this pull request to stack #17289
October 8, 2026 19:33
github-actions
Bot
added
the
size:L
This was referenced Oct 8, 2026
juliusmarminge
added
the
macroscope-review
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
Member
Author
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.
Replay fixtures are how adapters prove behavior, but the provider-agnostic replay pieces lived in the server's orchestration testkit.
This adds
@t3tools/provider-testingwith the NDJSON transcript decoder and workspace placeholders, the replay gate, and the git checkpoint workspace, each with focused tests. The orchestrator-backed harness and the runtime-instruction rewrite stay in the server for now, because they depend on orchestration services and server prompt text.Part of the provider-packages stack: #17282 → #17283 → #17284 → #17285 → #17286 → #17287 → #17288.
Done by Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code