cli: build functional scaffolds for template-backend-kotlin, template-backend-groovy, template-frontend-vue and template-frontend-react

[marioserrano09]

Context

Only dynamiatools/template-backend-java has real content. The CLI wizard (dynamia new) advertises 3 backend languages (Java/Kotlin/Groovy) and 2 frontend frameworks (Vue/React), but only Java actually works today. Related: #90.

The 4 repos already exist as empty placeholders (README/LICENSE/.gitignore) in the org:

• https://github.com/dynamiatools/template-backend-kotlin
• https://github.com/dynamiatools/template-backend-groovy
• https://github.com/dynamiatools/template-frontend-vue
• https://github.com/dynamiatools/template-frontend-react

Pending work per repo

template-backend-kotlin / template-backend-groovy

Mirror template-backend-java (same tools.dynamia.* dependencies in pom.xml, same src/main/<lang>/com/example/demo structure, same application.yaml), adapted to each language's syntax. Should follow the placeholder conventions documented in platform/packages/cli/README.md ("Template author conventions"): {{GROUP_ID}}, {{ARTIFACT_ID}}, {{BASE_PACKAGE}}, etc. — see also the placeholder gap tracked in #92.

template-frontend-vue / template-frontend-react

Vite + Vue3/React project with @dynamia-tools/sdk and @dynamia-tools/ui-core (or @dynamia-tools/vue for Vue) already installed, using the {{PROJECT_NAME}} token (the only one generateFrontend currently replaces, in src/generators/frontend.ts). Should include a minimal SDK usage example (login + CRUD list) so the scaffold isn't empty.

Once each repo is done

Go back to platform/packages/cli/cli.properties and set enabled=true for that template (see #90).

[marioserrano09]

Backend scaffolds done, functional and verified end-to-end (CLI generate → mvn clean verify → BUILD SUCCESS):

• ✅ template-backend-java (already existed, now also fixed — see ModuleContainer requires List<ModuleProvider>, but DynamiaBaseConfiguration's emptyModuleProvider() fallback never registers for a minimal app #102)
• ✅ template-backend-kotlin — dynamiatools/template-backend-kotlin@9dbe2c0
• ✅ template-backend-groovy — dynamiatools/template-backend-groovy@59b3991
• ⬜ template-frontend-vue — still a placeholder
• ⬜ template-frontend-react — still a placeholder

PR enabling the two backend templates in cli.properties: #103.

Frontend scaffolds (Vue/React + Vite + @dynamia-tools/sdk) remain open on this issue.

[marioserrano09]

Vue frontend done too, merged (#104):

• ✅ template-frontend-vue — dynamiatools/template-frontend-vue@a9a510a, built on @dynamia-tools/tailadmin-vue (admin shell) + @dynamia-tools/sdk + @dynamia-tools/vue
• ⬜ template-frontend-react — still a placeholder, left disabled for now per Mario

All 4 templates that are going to ship this round (java/kotlin/groovy/vue) are enabled=true in cli.properties on main. Note: dynamia.version/npm.*.version were bumped to 26.9.0 (this release's target) ahead of the actual npm/Maven Central publish — CI on the template repos will be red until 26.9.0 ships, expected and not a regression.

Leaving this issue open for template-frontend-react.