fix(frontend): recover stale organization selection

[WcaleNieWolny]

Summary

• validate the current organization against fresh selectable organization results
• recover to a valid persisted organization or the first selectable organization when the previous selection disappears
• add a regression test for an organization refresh that replaces the selected organization

Root cause

fetchOrganizations() preserved currentOrganization.gid without checking whether that ID still existed in the refreshed RPC results. When membership was revoked, an organization was deleted, or client state otherwise became stale, the store could have selectable organizations while assigning undefined to currentOrganization. The apps page then logged Current organization is null, cannot fetch apps and rendered an empty list.

Test plan

• bun lint
• bun typecheck
• bun test:unit (188 files, 1,362 tests)
• regression mutation check: old selection logic fails with expected org-b, received undefined; corrected logic passes

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 81dc01f7-fd2d-4b6b-b5ad-a444aa8e9d3c

📥 Commits

Reviewing files that changed from the base of the PR and between 5abacbf and 5c4cc6f.

📒 Files selected for processing (4)

• docs/superpowers/plans/2026-08-05-stale-current-organization.md
• docs/superpowers/specs/2026-08-05-stale-current-organization-design.md
• src/stores/organization.ts
• tests/organization-store-delete.unit.test.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing wolny/fix-stale-current-organization (5c4cc6f) with main (8f4e6dd)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cubic-dev-ai]

All reported issues were addressed across 4 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud