[dashboard] fix: accept integer vram status values

[Wangmerlyn]

Summary

• accept integer-byte session params.vram values during dashboard refresh validation
• add a regression test so valid API/MCP sessions are not hidden as malformed
• rebuild the packaged dashboard asset and document the dashboard/session contract

Test Plan

• npm --prefix web/dashboard test -- src/lib/refresh.test.js (RED failed before implementation, GREEN passed after)
• npm --prefix web/dashboard test
• npm --prefix web/dashboard run build
• PYTHONPATH=src pytest tests/mcp/test_http_api.py tests/test_package_metadata.py -q
• mkdocs build --strict
• pre-commit run --all-files --show-diff-on-failure

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 49 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: 7722506b-3ec9-43cb-857e-391cadcdd75f

📥 Commits

Reviewing files that changed from the base of the PR and between bd760a4 and 868d57d.

📒 Files selected for processing (5)

• AGENTS.md
• docs/guides/mcp.md
• src/keep_gpu/mcp/static/assets/dashboard.js
• 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-integer-vram

---

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.}

[gemini-code-assist]

Code Review

This pull request updates the dashboard session refresh validation to accept both string and integer-byte VRAM values, aligning it with the public session contract. Specifically, it introduces a new helper function isVramValue in refresh.js to validate the vram parameter (allowing strings or integers between 4 bytes and 1 PiB), updates the documentation in AGENTS.md and docs/guides/mcp.md, and adds a corresponding unit test in refresh.test.js. I have no feedback to provide as there are no review comments.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.