Project: ai-business-copilot

Service: backend (the FastAPI service)

Repo migrated from personal GitHub account to Ryvech-Systems organization ~3 days ago. Since then, the GitHub integration shows persistent "Bad credentials" error on the Branch connected to production field, no GitHub webhook gets created, and auto-deploy doesn't fire on push to main.

What I've tried (all failed to clear the error):

- Verified Railway App installed at Ryvech-Systems org level with full read+write permissions and "All repositories" access

- Disconnected and reconnected the source repo via Railway dashboard multiple times

- Toggled Wait for CI on/off

- Revoked Railway App from personal GitHub Authorized GitHub Apps list, reauthorized via Railway's source dropdown — fresh OAuth flow showed all 6 Ryvech-Systems repos available, but selecting ai-business-copilot still produces "Bad credentials" immediately

- Confirmed Railway has no "Authorized OAuth App" entry on personal GitHub (uses GitHub App flow only)

Diagnosis: Railway has stale internal state — likely cached installation_id or OAuth token from the pre-migration personal-account context. Reconnect updates the visible repo selection but doesn't refresh the underlying credentials.

Request: Please reset the GitHub integration state for this service on your backend so reconnect can complete cleanly. Specifically, clear the cached installation_id binding so the next connect attempt forces a fresh handshake with GitHub.

Workaround in use: Manual railway up from CLI after every PR merge. Production is fine, just no auto-deploy.