describe the bug
the github connection is OAuth-connected and shows as "connected" in the app, but neither a pipe runtime nor the local API can retrieve a usable token, so pipes cannot create github issues/comments.

steps:

1. connect github via the OAuth flow (shows "connected").
2. from a pipe (or via the local API) try to read the connection: GET http://localhost:3030/connections/github returns {"credentials":{}} — no access token.
3. token endpoints like /connections/github/token, /connections/oauth/github/token, /connections/github/credentials all return 404.
4. a pipe that tries to POST to https://api.github.com/repos/.../issues has nothing to authenticate with and the run finishes without creating anything.

expected: a pipe with the github connection privilege should be able to obtain the OAuth token (or call a connection-level "create issue/comment" endpoint) so it can file issues programmatically. the connection description even says "Create GitHub issues and comments. Connected via OAuth, with repository selection handled by pipe-level settings" — but there's no reachable mechanism to actually do it.

system info

• os: macOS 26.5.1
• screenpipe version: 0.4.15

additional context
hit while building a pipe to auto-file screenpipe issues. the OAuth token appears to live somewhere the API/pipe runtime can't read it. either expose the token to authorized pipes or provide a connections/github/issues create endpoint.