feat(project): framework detection for JVM, .NET, C/C++, Elixir, and Swift

[OBenner]

Summary

Roadmap phase 3 (follows #387/#388/#390/#394): planner/coder context previously knew web frameworks for scripting languages only. This extends FrameworkDetector to the compiled ecosystems:

Ecosystem	Frameworks	Detection source
JVM	Spring Boot, Quarkus, Micronaut, Android, Compose	pom.xml, build.gradle(.kts), settings.gradle(.kts)
.NET	ASP.NET Core, MAUI, Unity	csproj SDK/package refs, ProjectSettings/ProjectVersion.txt
C/C++	Qt, Boost, GTest, Catch2	find_package markers in CMakeLists.txt
Elixir	Phoenix, Ecto	mix.exs deps
Swift	Vapor	Package.swift

Detected frameworks now also allowlist their tooling via new FRAMEWORK_COMMANDS entries (mn, quarkus, adb, qmake/moc/uic/rcc, vapor, …).

GTest/Catch2 detection additionally feeds the QA loop: it signals the test stack for C++ projects discovered by #388's CTest support.

Testing

tests/test_project_analyzer.py: 78 passed (8 new covering every new ecosystem). Ruff 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: 51 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: e7107f7b-efc7-4bfd-93de-992fa4ad8f7b

📥 Commits

Reviewing files that changed from the base of the PR and between a85fff1 and 925aa6f.

📒 Files selected for processing (3)

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/framework-detection-jvm-dotnet-native

---

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