[dashboard] fix: decouple refresh payloads

[Wangmerlyn]

Summary

• Decouple dashboard refresh payloads so /api/gpus and /api/sessions can update independently.
• Preserve successful start/release messages when the follow-up refresh only emits a partial-refresh warning.
• Rebuild the packaged dashboard asset and document the dashboard refresh invariant.
• Keep the README clean and preserve the Zenodo DOI badge.

Local review

• Local subagent review found no Critical or Important issues.
• One Minor coverage suggestion was resolved by adding the symmetric partial-failure test.
• Follow-up local subagent review confirmed no remaining issues and marked the branch ready to merge.

Verification

• npm test in web/dashboard: 5 files passed, 53 tests passed.
• npm run build in web/dashboard: passed and regenerated packaged dashboard assets.
• PYTHONPATH=$PWD/src pytest tests/mcp/test_http_api.py -q -k 'dashboard or static or api_gpus or sessions': 43 passed, 72 deselected.
• PYTHONPATH=$PWD/src pytest -q: 843 passed, 11 skipped.
• PYTHONPATH=$PWD/src mkdocs build --strict: passed with the existing Material for MkDocs upstream warning.
• pre-commit run --all-files --show-diff-on-failure: passed.
• git diff --check: passed.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Review limit reached

@Wangmerlyn, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 19faf5ac-92a6-47b1-ba6b-a20fc1efae8d

📥 Commits

Reviewing files that changed from the base of the PR and between df05eb6 and 99d3f2d.

📒 Files selected for processing (7)

• AGENTS.md
• docs/guides/cli.md
• docs/plans/dashboard-decouple-refresh.md
• src/keep_gpu/mcp/static/assets/dashboard.js
• web/dashboard/src/App.jsx
• web/dashboard/src/lib/refresh.js
• web/dashboard/src/lib/refresh.test.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/dashboard-decouple-refresh

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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