fix(cloud): clear reconnect warning after successful OAuth reconnect

[tofikwest]

Summary:\n- store reconnect timestamp after successful cloud OAuth reconnect\n- use reconnect timestamp in cloud reconnect policy so warning clears correctly\n- pass reconnect timestamp through cloud providers and integration detail reconnect checks\n- add reconnect policy tests for reconnect marker behavior\n\nValidation:\n- apps/app vitest cloud reconnect policy and tests layout\n- apps/api bun run build

---

Summary by cubic

Fixes cloud OAuth reconnect banners not clearing. We now record a reconnect timestamp and use it in the reconnect policy and UI so the warning disappears after a successful reconnect.

• Bug Fixes
  • On cloud OAuth success, save reconnectedAt in connection metadata in apps/api OAuthController.
  • Expose reconnectedAt from the API and into the app (CloudSecurityQueryService, app provider types).
  • Update requiresCloudReconnect to consider reconnectedAt against the cutoff; add unit tests.
  • Pass reconnectedAt into UI checks in cloud tests and provider detail views to clear the banner.

^{Written for commit 4faab40. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
app	Ready	Preview, Comment	Apr 13, 2026 9:59pm
comp-framework-editor	Ready	Preview, Comment	Apr 13, 2026 9:59pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal	Skipped		Apr 13, 2026 9:59pm

[cubic-dev-ai]

No issues found across 7 files

_{Auto-approved: Fixes persistent cloud reconnect banners by tracking and checking a 'reconnectedAt' timestamp. Low-risk logic update with corresponding unit tests.}

[claudfuen]

🎉 This PR is included in version 3.22.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀