Remove legacy consumer UI

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.
-- Legacy consumer and circuit-first paths coexist; migration is transitional and still requires operational discipline.
+- The legacy consumer UI has been removed after complete migration; its server endpoints and retained database records are still pending final cleanup.

docs/circuit-list-editor-migration.md

@@ -46,7 +46,8 @@ Run in this order for local database workflows:
 The migration command finishes with a cutover verification across the complete
 database. It exits with an error while any legacy consumer lacks a migration
 mapping, including consumers that cannot be migrated because they have no circuit
-list assignment. Do not remove or disable the legacy path until this check passes.
+list assignment. The legacy multi-list UI was removed only after this check passed;
+old `/projects/:projectId/circuit-lists` bookmarks redirect to the project page.
 
 ## Validation Checks
 
@@ -77,6 +78,6 @@ Actions:
 
 Do not delete legacy consumers yet.
 
-- legacy endpoints/views remain enabled only until the cutover verification passes
+- legacy write endpoints remain temporarily available for the next server cutover step
 - migration trace tables reference old/new mapping
 - keeping legacy rows allows comparison and rollback validation during transition