Remove legacy consumer API

docs/circuit-list-editor-api.md

@@ -148,14 +148,12 @@ Request sketch:
 }
 ```
 
-## Legacy Endpoints (Temporary)
+## Removed Legacy Endpoints
 
-- `GET /consumers/projects/:projectId`
-- `POST /consumers`
-- `PUT /consumers/:consumerId`
-- `DELETE /consumers/:consumerId`
-
-These remain for migration/legacy views. New circuit-list interactions must use circuit-first endpoints above.
+The former `/consumers` read/write endpoints were removed after every retained
+consumer had a verified Circuit-First migration mapping. Database upgrade tooling
+reads retained legacy rows directly; application features must use the Circuit-First
+endpoints above.
 
 ## Linked Project Device Review
 

docs/circuit-list-editor-known-limitations.md

@@ -10,4 +10,4 @@
 - No full norm-compliant voltage-drop and protection-dimensioning calculation flow yet.
 - Sorting is view-only until users explicitly apply sorted order.
 - Cross-section circuit drag-reorder is intentionally blocked.
-- The legacy consumer UI has been removed after complete migration; its server endpoints and retained database records are still pending final cleanup.
+- Legacy consumer UI and server endpoints are removed; retained source rows and migration mappings remain available only for upgrade traceability.

docs/circuit-list-editor-migration.md

@@ -78,6 +78,6 @@ Actions:
 
 Do not delete legacy consumers yet.
 
-- legacy write endpoints remain temporarily available for the next server cutover step
+- legacy read/write endpoints have been removed from the application server
 - migration trace tables reference old/new mapping
 - keeping legacy rows allows comparison and rollback validation during transition

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

@@ -342,6 +342,8 @@ Implemented foundation:
 - the legacy consumer migration receives its database dependency at the script entry point
 - legacy circuit, row, mapping and report writes have real late-failure rollback coverage
 - circuit and device-row persistence value mapping is separated from the general repositories
+- 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
 
 ## Phase 12: Project Revisions and Persistent Undo / Redo