refactor(core): hard-rename provider definition APIs - #1716
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
1609213
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://12cb7a5b.agentv.pages.dev |
| Branch Preview URL: | https://av-kfik-53-1-provider-defini.agentv.pages.dev |
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.
Summary
AgentV's core provider-definition API now matches the supported
providersauthoring surface instead of exposing target-era configured-provider names. Current repo consumers useProviderDefinition,ResolvedProviderBackend,readProviderDefinitions,listProviderLabels,resolveProviderDefinition, andresolveDelegatedProviderDefinition; the old target-named exports were removed rather than kept as deprecated aliases.This is scoped to the configured-provider API slice. Runtime/artifact compatibility fields such as result
target, SDK target proxy/client names, and broader CLI selection internals remain intentionally deferred to the existing follow-up Beads.Related: Bead av-kfik.53.1
Validation
bun test packages/core/test/evaluation/providers/targets-file.test.ts packages/core/test/evaluation/providers/targets.test.ts packages/core/test/evaluation/providers/targets-cwd-fallback.test.ts packages/core/test/evaluation/providers/fallback-targets.test.ts packages/core/test/evaluation/providers/pi-runtime.test.tsbun test packages/core/test/evaluation/loaders/config-loader.test.ts packages/core/test/evaluation/yaml-parser.test.ts apps/cli/test/commands/eval/targets.test.ts apps/cli/test/commands/eval/run-command-options.test.ts apps/cli/test/commands/eval/task-bundle.test.ts apps/cli/test/commands/eval/bundle.test.tsbun --filter @agentv/core typecheckbun --filter agentv typecheckbunx biome check $(git diff --name-only)git diff --checkrgscan confirmed the removed exact exported names are absent frompackages/core,apps/cli, and the current custom provider docs.Code review: skipped because this is a mechanical exported-symbol rename with no behavior logic change.
Post-Deploy Monitoring & Validation
No additional operational monitoring required. This is a compile-time API rename in TypeScript source and docs; CI typecheck, tests, and lint are the merge gate.