bug: Plan scaffold generates nonsensical file paths (.txt extension, Python naming for Java)

[mmorris35]

Description

The generated plan scaffold creates file paths that don't match the detected language conventions.

Reproduction

Generate a plan for a Java 21 + Spring Boot 3 project.

Expected

Java-style paths:

• `src/main/java/com/example/buzzwordbingo/BuzzwordBingoApplication.java`
• `src/test/java/com/example/buzzwordbingo/BuzzwordBingoApplicationTest.java`

Actual

• `corporate_buzzword_bingo/main.txt` — `.txt` extension, Python snake_case naming
• `tests/test_main.txt` — `.txt` extension, Python test naming convention
• `corporate_buzzword_bingo/routes.txt`
• `corporate_buzzword_bingo/handlers/`
• `tests/test_api.txt`

Root Cause

The scaffold file path generation uses a generic template that doesn't adapt to the detected language. The `.txt` extension suggests a fallback when the language mapping returns nothing useful.

Test Project

`test-projects/corporate-buzzword-bingo/`

[mmorris35]

Re-test Results (2026-02-14)

No change. Still generating:

• `corporate_buzzword_bingo/main.txt`
• `tests/test_main.txt`
• `corporate_buzzword_bingo/routes.txt`
• `tests/test_api.txt`

Expected for a Java 21 + Spring Boot 3 + Gradle project:

• `src/main/java/com/example/buzzwordbingo/BuzzwordBingoApplication.java`
• `src/main/java/com/example/buzzwordbingo/controller/MeetingController.java`
• `src/test/java/com/example/buzzwordbingo/BuzzwordBingoApplicationTest.java`

Note: The CLAUDE.md generator was fixed to output Java paths, but the plan generator scaffold still uses the old generic path template.

[mmorris35]

Staging Verification (2026-02-14)

Status: PARTIALLY FIXED on staging

Re-generated the corporate-buzzword-bingo plan using DevPlan Staging MCP.

Fixed: File extensions are now .java instead of .txt

Still broken: File paths still use Python-style naming conventions:

• corporate_buzzword_bingo/main.java (Python snake_case package)
• tests/test_main.java (Python test naming)
• corporate_buzzword_bingo/routes.java
• corporate_buzzword_bingo/handlers/
• tests/test_api.java

Expected (standard Java/Spring Boot):

• src/main/java/com/example/buzzwordbingo/BuzzwordBingoApplication.java
• src/test/java/com/example/buzzwordbingo/BuzzwordBingoApplicationTest.java

Note: The Phase 0 subtasks (0.1.2, 0.2.1, 0.2.2) correctly reference Java paths like src/main/java/{package}/, src/test/java/{package}/, Gradle/Maven, Checkstyle, and JUnit 5. The problem is isolated to Phase 1 subtasks (1.1.1, 1.1.2, 1.1.3) which still use the Python-style generic template paths.

Test artifacts: test-projects/corporate-buzzword-bingo/DEVELOPMENT_PLAN.md (see lines 322, 332-333, 384-387)

[mmorris35]

Fix Verified

All three root causes identified and fixed:

1. resolveTemplateKey() missing Java mapping

The switch statement only mapped python/typescript/javascript. Java, Kotlin, C#, Ruby all fell through to language = "unknown", causing Python defaults. Added explicit cases for all languages.

2. generateMinimalPhase1() hardcoded Python paths

Used ${projectUnderscore}/main.${ext} which produced corporate_buzzword_bingo/main.java - wrong for Java. Replaced with getLanguageFilePaths() which returns proper Java Maven/Gradle paths like src/main/java/com/example/corporate_buzzword_bingo/Application.java.

3. generateDomainSubtasks() same issue

Similar hardcoded paths for models, routes, handlers. Now uses language-appropriate paths (controller/, service/, model/ for Java).

Verification (production MCP output for Java 21 + Spring Boot brief):

• File paths: src/main/java/com/example/corporate_buzzword_bingo/Application.java ✅
• Test paths: src/test/java/com/example/corporate_buzzword_bingo/ApplicationTest.java ✅
• No Python-style paths anywhere ✅

317/317 tests pass. Deployed to production.