Harden Core workflows and plugin lifecycle

[wizzomafizzo]

Summary

• move pairing and Online approval ownership into generation-scoped backend workflows with conservative cancellation and encryption rollback
• preserve modals and structured log-upload results across temporary QAM unmounts while bounding external upload, bootstrap, and unload behavior
• improve controller-facing errors, Warp availability, control grouping, and Core/plugin version presentation

Validation

• pnpm check
• pnpm package
• No new root/debug flags, binaries, remote code, or filesystem boundaries
• External URLs, persistence, permissions, and dependencies documented
• Changed controller or Steam behavior tested on a Steam Deck

Steam Deck validation included a dev.21 self-reinstall: Decky unloaded the worker in 0.1 seconds without SIGKILL, then reconnected to the Core notification stream.

[coderabbitai]

Warning

Review limit reached

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

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 15 minutes

Limit details: You’ve used the included review currently available. Your 90 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cf8e7982-6e5e-4838-a729-d6c1504036a3

📥 Commits

Reviewing files that changed from the base of the PR and between 4ce235d and d26487f.

📒 Files selected for processing (17)

• README.md
• docs/architecture.md
• main.py
• package.json
• src/Content.test.tsx
• src/Content.tsx
• src/api.ts
• src/index.tsx
• src/logUploadLifecycle.test.ts
• src/logUploadLifecycle.ts
• src/modalLifecycle.test.ts
• src/modalLifecycle.ts
• src/types.ts
• src/validation.test.ts
• src/validation.ts
• src/version.ts
• tests/test_main.py

---

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