# Known Issues and Deliberate Limitations — Release 02.01.00

1. **No tables exist yet.** The database may be empty; this release verifies only connectivity. Migration history and the core schema are Release 02.02.00.
2. **No authentication UI or accounts exist.** Users, login, roles, permissions, lockouts and password recovery are subsequent Phase 02 work.
3. **The application must run at a dedicated document-root origin.** Subdirectory mounting is not supported in this release.
4. **Trusted proxy matching accepts exact IP addresses only.** CIDR/range support will be added only if the production network requires it.
5. **CSP is intentionally strict.** Any later external proctoring, media, analytics or identity endpoint must be explicitly reviewed and allowlisted.
6. **The staging home page exposes the release and environment label.** It will be replaced by the actual application entry/login page before production cutover.
7. **File logs are the initial operational channel.** Security/audit events will move into a structured database audit subsystem; application logs will remain for runtime diagnostics.
8. **`robots.txt` blocks all indexing.** This is correct for the entire rebuild period and must not be removed prematurely.
9. **The CLI PHP configuration may differ from the domain's PHP-FPM configuration.** Validate both the CLI output and HTTPS response behavior.
10. **No legacy code/data is imported.** This is intentional isolation, not missing functionality.