Create clean release database baseline

docs/spec/07-implementation-phases-todo.md

@@ -342,9 +342,8 @@ Implemented foundation:
 - circuit-device-row transaction tests cover both successful commits and forced SQLite rollbacks
 - project-device row synchronization has real multi-row SQLite commit and rollback coverage
 - BMK swaps and section reorder have real SQLite commit and rollback coverage
-- the legacy consumer migration service depends only on narrow domain ports;
-  all concrete repositories are composed at the script entry point
-- legacy circuit, row, mapping and report writes have real late-failure rollback coverage
+- the former Consumer migration service, mappings and reports were removed with
+  the pre-release database cutover
 - circuit and device-row persistence value mapping is separated from the general repositories
 - obsolete direct Circuit, CircuitDeviceRow, CircuitList, DistributionBoard and
   Project repository writes are removed; integration fixtures live under
@@ -362,8 +361,9 @@ Implemented foundation:
   direct global SQLite access
 - TypeScript maintenance and upgrade scripts have a dedicated no-emit
   typecheck, including all referenced application modules
-- the legacy consumer UI and application read/write endpoints are removed after verified data cutover
-- retained legacy rows are accessible only through explicit database upgrade tooling
+- the former Consumer UI, API, tables and upgrade tooling are removed
+- migration `0000` is the clean baseline for new installations; pre-baseline
+  development databases are intentionally unsupported
 - project devices no longer persist duplicate legacy power, phase, cosPhi or remark fields
 
 ## Phase 12: Project Revisions and Persistent Undo / Redo
@@ -618,7 +618,8 @@ Implemented handoff:
 
 - README is a concise setup and project entry point without prototype status lists
 - `docs/README.md` separates current, operational, future, specification and archived material
-- current runtime, module boundaries and upgrade-only legacy data are documented explicitly
+- current runtime and module boundaries are documented without unsupported
+  upgrade-only data paths
 - contributor workflow covers clean databases, safe demo data, migrations, tests and commits
 - development Compose is clearly separated from the currently unsupported production deployment
 - `AGENTS.md` points LLM-assisted work to supported code paths and deferred architecture