feat(qa): embedded ecosystem detection + emulated test discovery (PlatformIO/Zephyr)

[OBenner]

Summary

Slice C1 of the Device & GUI Verification Roadmap (follows Android slices #422/#423): embedded projects go from L0 (builds cleanly) to L1/L2 — host-side and emulated test runs, never assuming hardware.

Test discovery

Ecosystem	Detection	Command	Level
PlatformIO	platformio.ini with [env:native]	pio test -e native	L1 (host-side)
PlatformIO	platformio.ini without native env	pio test	project's default envs
Zephyr workspace	west.yml	west twister -p qemu_x86 -T tests	L2 (QEMU)
Zephyr application	prj.conf + CMakeLists.txt	same	L2 (QEMU)

A stray prj.conf without CMake deliberately does not trigger twister (negative test included).

Also

• Framework detection for planner context: platformio, zephyr, esp-idf (via sdkconfig)
• Allowlist via FRAMEWORK_COMMANDS: pio/platformio, west/twister + QEMU system binaries, idf.py
• ESP-IDF gets detection/allowlist only — its emulation story is weakest, so no test entry (per roadmap it stays build-only until a Renode/QEMU slice)

Testing

tests/test_discovery.py + tests/test_project_analyzer.py: 164 passed (9 new: native-env preference, fallback, workspace/application detection, negative cases, framework detection per ecosystem). Ruff check + format clean.

🤖 Generated with Claude Code

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

@OBenner, 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: cd44afb8-1957-49b2-bb1a-76008ce017f6

📥 Commits

Reviewing files that changed from the base of the PR and between eb534ab and 7717336.

📒 Files selected for processing (5)

• apps/backend/analysis/test_discovery.py
• apps/backend/project/command_registry/frameworks.py
• apps/backend/project/framework_detector.py
• tests/test_discovery.py
• tests/test_project_analyzer.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/embedded-test-discovery

---

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