chore(v5): archive V5 implementation and remove runtime integration
Move V5 source, migrations, UI, scripts, and tests into documentation, then remove V5 routes, models, jobs, configuration, dependencies, and application hooks.
2026-08-15 17:13:30 +00:00
|
|
|
# Archived V5 Production Activation Checklist
|
|
|
|
|
|
|
|
|
|
The previous V5 implementation has been removed from the application and is no
|
|
|
|
|
longer available in development or production. This file remains only to record
|
|
|
|
|
that the old activation plan was abandoned.
|
|
|
|
|
|
|
|
|
|
- Migration prototypes are archived under `docs/v5/migrations/`.
|
|
|
|
|
- UI prototypes are archived under `docs/v5/ui/`.
|
|
|
|
|
- All remaining backend, configuration, development tooling, and test sources
|
|
|
|
|
are archived under `docs/v5/archive/` using their original paths.
|
|
|
|
|
- Archived files are non-executable and must not be registered, imported, built,
|
|
|
|
|
or served.
|
|
|
|
|
- A future V5 implementation must define a new architecture, database strategy,
|
|
|
|
|
rollout plan, and production checklist.
|
