Controllers/views inside /app

[zainforbjs]

Describe the bug
The /app directory in a Wheels application contains pre-existing controllers and views that are part of framework functionality (e.g., browser testing fixtures or internal utilities).

This is problematic because the /app directory is intended to contain only application-specific code created and managed by the developer (controllers, models, and views for their own app).

To Reproduce
Steps to reproduce the behavior:

1. Create a new Wheels application
2. Open the /app directory
3. Observe the presence of controllers and/or views that are not user-created and appear to be framework-provided

Expected behavior
The /app directory should be reserved exclusively for developer-defined application code.

Framework-provided controllers and views should instead live in:

• vendor/wheels/...
• or another internal/framework-specific location

Desktop:

• OS: Any