feat(web): integrate provider authentication diagnostics - #443
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
2 participants
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.
Problem and value
Integrate #390's useful Provider authentication diagnostics onto current main while preserving the contributor's implementation. Authenticated GET /api/providers/auth-status reports which Pi providers support API keys or OAuth, whether they are configured, and a bounded non-secret source category. It does not return credentials, labels, commands or tokens.
The original branch conflicts with newer main changes. This integration preserves both its additions and the existing trust, capability, diagnostics and cancellation behavior. No feature fixes or policy changes are added on behalf of the author; there is no new UI or authentication write path.
Attribution
Original contribution: #390, authored by testikun 320479488+testikun@users.noreply.github.com. The cherry-picked commit preserves that author identity; the squash merge must retain the same contributor as a co-author.
Validation
bun run check: passed.bun run test:1,453 Node tests passed,1 skipped;92 Vitest tests passed.Refs #348. Integrates #390, which will be closed with the merge receipt afterward.