feat: add live-model validation for Vercel schema selection#44
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
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
Add an opt-in live-model validation path for the TypeScript Vercel AI SDK schema-selection example.
The provider-free tests remain the canonical proof. The new live-model path demonstrates that authoritative Context Compiler state continues to control schema selection when using a real Vercel AI SDK
generateObjectcall.Why
The repository already includes a provider-free Vercel AI SDK schema-selection example.
This change adds a Tier 3 validation path showing that the same host-controlled schema-selection behavior survives a real model call while keeping provider-free tests as the primary proof.
Example metadata
ai,@ai-sdk/openai)Checklist
Notes
Validation performed:
npm run buildnpm run typechecknpm test./scripts/validate_typescript_fast.shmarkdownlintLive-model validation:
gpt-4o-mini✅gpt-5-mini✅gpt-5✅gpt-5.4✅The live-model path is opt-in and does not change schema-selection semantics.