test: move provider auth parity coverage out of core source#104974
Merged
Conversation
Contributor
Author
|
Land-ready proof for exact head
This is a pure test-ownership move: it restores the enforced |
Contributor
Author
|
Merged via squash.
|
vincentkoc
added a commit
that referenced
this pull request
Jul 12, 2026
* origin/main: test(plugins): move auth parity integration coverage (#104974) fix(qa): run mixed channel suites
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 12, 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.
What Problem This Solves
Fixes an issue where current-main
build-artifactsfails the core extension boundary because the bundled provider-auth parity integration test was placed undersrc/while intentionally loading bundled plugin public surfaces.Why This Change Was Made
The test moves to the root integration-test owner and updates only its relative core imports. The core boundary remains strict; no allowlist or production behavior changes are added.
User Impact
Maintainers regain a green core-support boundary while preserving the full 72-case provider-auth parity coverage. No shipped runtime or release behavior changes.
Evidence
node scripts/run-vitest.mjs test/extension-test-boundary.test.ts test/bundled-provider-auth-literal-parity.test.ts— 11 boundary tests and 72 parity tests passed.git diff --check— clean.build-artifactsreported onlysrc/plugins/bundled-provider-auth-literal-parity.test.tsas the boundary offender.