Language Support

Language support — ✅ COMPLETE

Source: docs/LANGUAGE_SUPPORT_ROADMAP.md. ← Overview

The pipeline (spec → planner → coder → QA) is language-agnostic, but support depth varied. All 5 phases brought ~20 languages to parity with Python/JS. Completed: PR #418.

Phase	What	Status
1	Detection fixes + test discovery (JVM/.NET/native/scripting)	✅ #387, #388
2	SAST / dependency audit (C/C++ cppcheck, Go gosec, Rust cargo-audit, PHP composer-audit + osv-scanner)	✅ #390, #394
3	Framework detection (Spring/Quarkus/Micronaut/Android, ASP.NET/MAUI/Unity, Qt/Boost/GTest, Phoenix/Ecto, Vapor)	✅ #395
4	Targeted test commands + full test discovery in the index; ccache/sccache for fresh worktrees	✅ #402, #412
5	CLI E2E harness run_cli_session (pseudo-terminal for terminal apps, for QA agents)	✅ #415

---

Subsystems that define "language support"

#	Subsystem	Location
1	Stack detection	project/stack_detector.py
2	Command allowlist	project/command_registry/languages.py
3	Test discovery	analysis/test_discovery.py (FRAMEWORK_PATTERNS)
4	Security scanners & rules	security/language_rules.py
5	Framework detection	project/framework_detector.py
6	E2E verification	Electron MCP / Puppeteer (core/client.py)

Left out of scope (tracked separately): native GUI, mobile, embedded — see Device & GUI verification.

Audit note: LANGUAGE_SECURITY_SCANNERS/LANGUAGE_SECURITY_RULES are a public API with no runtime consumers yet; actual scanning happens in analysis/security_scanner.py.