docs: device & GUI verification roadmap (mobile, embedded, native desktop)

[OBenner]

Summary

"Roadmap 2" — the plan for the three verification targets the language support roadmap explicitly left out of scope: mobile, embedded, and native desktop GUI.

Key ideas:

• Same pipeline, new adapters — every slice reuses the established chain: detection → allowlist → test discovery → MCP tool → QA prompt honesty. Precedents: Electron MCP, run_cli_session (feat(qa): CLI E2E harness tool for terminal applications #415).
• L0–L5 verification levels (builds / unit / emulated / screenshot / interactive / on-device) so QA reports state exactly what was verified — an emulated pass must never read as a hardware pass.
• Priority = impact per effort: Android first (fully CLI-scriptable via Gradle managed devices + adb = computer-use loop), Flutter next, embedded via emulation (PlatformIO/Zephyr/QEMU/Renode + a pyserial run_serial_session mirror of the CLI harness), desktop GUI phased starting from screenshot verification (the QA agent is multimodal — one screenshot answers most "did the UI change land?" checks), iOS last.
• Non-goals: device farms, HIL beyond serial, commercial GUI automation.

Includes a 11-slice PR breakdown and a cross-reference from the phase 5 section of the first roadmap.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 48 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: eebc2dd2-382f-4338-8d5e-5aacf0cf9666

📥 Commits

Reviewing files that changed from the base of the PR and between 49d908b and 85e316e.

📒 Files selected for processing (2)

• docs/DEVICE_GUI_VERIFICATION_ROADMAP.md
• docs/LANGUAGE_SUPPORT_ROADMAP.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/device-gui-verification-roadmap

---

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

[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