Repository navigation
feat: expose requester-scoped connection diagnostics - #19
Draft
ishankunam wants to merge 1 commit into
Draft
ishankunam wants to merge 1 commit into
ishankunam wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 30, 2026
ishankunam
added this pull request to stack #25
September 30, 2026 05:04
This was referenced Sep 30, 2026
This branch was successfully deployed
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.
Teammates repeatedly ask which connections work, but credential availability alone does not prove access. Add
check_connectionsto perform fixed, read-only credential, identity, MCP, and retrieval checks inside Vee, with service-specific recovery steps.Slack checks always use the verified requester. Checks never start consent, request private scopes, or substitute another grant. Shared-provider probes are blocked in private-context sessions. Journal configuration is explicitly distinguished from tested connectivity. At most two providers run concurrently.
Stack: #17 → #18: traces → #19: connection status → #20: event/task proposals → #21: announcement drafts.
Validation: 9 diagnostic tests passed, TypeScript check, and whitespace check. No live writes or provider configuration changes.