describe the bug
the github integration shows as "connected" (OAuth) in the app and its description says "Create GitHub issues and comments. Connected via OAuth, with repository selection handled by pipe-level settings." but there is no reachable mechanism for an agent (chat or pipe runtime) to actually use it:

• GET http://localhost:3030/connections/github returns {"credentials":{}} — no token.
• token/proxy endpoint variants (/connections/github/token, /connections/oauth/github, /connections/github/proxy, /connections/github/issues, etc.) all return 404/403.
• the openapi spec (78 routes on 0.4.15) contains no github/oauth/connection-proxy route at all — only sync/connections/pull|push (settings sync, not API proxying).

net effect: with the integration "connected," agents repeatedly try the documented-sounding connection path, fail, and fall back to the browser or get stuck. the only thing that actually files issues is the gh CLI if it happens to be installed and authenticated — which the integration doesn't advertise or guarantee.

steps to reproduce

1. connect github via OAuth (shows "connected").
2. from a chat agent or a pipe, attempt to create an issue using the connection.
3. observe: no token is retrievable, no proxy/create endpoint exists, the run produces nothing.

system info

• os: macOS 26.5.1
• screenpipe version: 0.4.15

additional context
this wastes agent turns every session — the integration's presence implies a working path that isn't exposed to the local API or pipe runtime. requests:

• either expose the OAuth token (or a connections/github/proxy/* / connections/github/issues create endpoint) to authorized pipes/agents, or
• update the connection description so agents don't assume a programmatic path exists, and/or document the gh CLI as the supported method.