Repository navigation
fix(connections): require verified authorization and explain retryable checks - #147
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
[Medium impact] No new actionable issues were found; the stated coordinated merge and deploy hold still applies.
|
7ce8284 to
82a0c8c
Compare
Saved native connections previously displayed Connected whenever the credential row was ready. The Connections page now requires verified authorization for green readiness, shows the check's explanation and time, and retries through Refresh. Known sync failures remain warnings even when authorization verifies. Rejected credentials say Authorization inactive without claiming expiry or deletion.
Consumes additive relay-control health fields, including GitHub App authentication. Older servers show unverified when proof is absent. Existing logos and controls remain. Explicit Refresh passes
refreshAuthorization=trueto bypass the control-plane proof cache; ordinary loads reuse short-lived revision-bound proof.Validation after rebasing on main:
npm run lint;npm test -- --maxWorkers=1 --no-file-parallelism(982 tests/62 files);npm run build. Regressions cover unknown → Refresh → verified, forced provider retry, authorization with sync failure, and present saved credentials rejected by the provider.Depends on AgentWorkforce/relay-control#186 and merged AgentWorkforce/relayfile-providers#24; hosted parity is AgentWorkforce/cloud#6324. Khaliq authorized merging once green on 2026-11-16. Current-head CI and review checks are green; control dependency #186 merged as
59370e216ee72275ad1be6683c6010f9c592ef1c. The merge hold is released. No manual deployment.