Generated Inertia app lacks a static-file fallback for compiled frontend assets

[eas4ai]

The v2.0.0 Vue scaffold does not register a static-file fallback. The directory starter previously received 404 responses for its compiled assets until it explicitly registered the framework fallback.

Verified against release commit 3229aa9af542c991196274fa3c235cdce88a68e2:

• A Vue app generated with the rebuilt CLI has no fallback registration in src/routes.rs.
• The released scaffold templates contain no StaticFiles/fallback registration.
• The released StaticFiles module describes explicit fallback registration as its intended integration.

Expected: a generated Inertia application can serve its built frontend assets through the documented production server workflow, or the generated guide clearly requires and configures an external static server.

Suggested regression: generate an app, install/build the frontend, start its production HTTP server without Vite, request the asset URLs emitted in the HTML, and verify successful responses with appropriate content types. Preserve protections against serving private files.

Verification limit: generated routes and released source were inspected. A fresh 2.0.0 production server was not run in this audit; the 404 reproduction above belongs to the earlier directory-starter integration.

Sources:

• https://github.com/eas4ai/suprnova/blob/3229aa9af542c991196274fa3c235cdce88a68e2/suprnova-cli/src/templates/files/backend/routes.rs.tpl
• https://github.com/eas4ai/suprnova/blob/3229aa9af542c991196274fa3c235cdce88a68e2/framework/src/static_files.rs