Repository navigation
refactor(provider-core): move provider-agnostic helpers into provider-core - #17286
Closed
juliusmarminge wants to merge 1 commit into
Closed
juliusmarminge wants to merge 1 commit into
juliusmarminge wants to merge 1 commit into
Conversation
…-core Drivers and adapters import a set of helpers that know nothing about the server: id derivation, provider failure items, MCP session lookup and tool presentation, process-group signals, T3 orchestration instructions, instance environments and home expansion, status probes and version advisories, update-ownership resolution, usage limits, and the shared text-generation prompts and operations. Move them into @t3tools/provider-core/server/* with their tests so a provider package can import them without reaching into apps/server. The Windows command-not-found check now lives with the status probe, and ContextHandoffBudgetError with the failure items that describe it. The id allocator's service key follows its new module path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
juliusmarminge
added this pull request to stack #17289
October 8, 2026 19:33
github-actions
Bot
added
the
vouch:trusted
This was referenced Oct 8, 2026
github-actions
Bot
added
the
size:XL
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.
Drivers and adapters import a set of helpers that know nothing about the server, but they lived in
apps/server, so a provider package could not use them.This moves them into
@t3tools/provider-core/server/*with their tests: id derivation, provider failure items, MCP session lookup and tool presentation, process-group signals, T3 orchestration instructions, instance environments and home expansion, status probes and version advisories, update-ownership resolution, usage limits, and the shared text-generation prompts and operations. The Windows command-not-found check now lives with the status probe, andContextHandoffBudgetErrorwith the failure items that describe it.No behavior change.
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