docs(ui): finalize MVP plan structure and de-archaeologize topic docs

MVP web client (Phases 1-30) is complete; reorganize planning + living docs around that.

- PLAN.md kept as the staged MVP record (1-30) with a status block + pointers; removed the 31-36 stages, regression scenarios, and deferred-TODO section (moved out); fixed a stale cross-machine plan path.

- ui/PLAN-finalize.md (new): active web-finalization plan in 8 stages (visual system, a11y, i18n, error UX, PWA, build hygiene, docs, owner manual-QA loop); absorbs former Phases 33 and 35.

- ui/ROADMAP.md (new): post-MVP (Wails, Capacitor, realistic projection, acceptance + regression scenarios) and triaged deferred follow-ups.

- ui/docs/README.md (new): grouped topic-doc index.

- De-archaeologized all 20 ui/docs topic docs + ui/README.md + ui/core/README.md: stripped Phase-N build history, rewritten as current-state; deferred work now points at ROADMAP.md / PLAN-finalize.md. Docs-only; no code change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

ui/docs/cargo-routes-ux.md

@@ -1,13 +1,12 @@
 # Cargo routes UX
 
-This document covers the cargo-route surface added in Phase 16: the
-four-slot inspector subsection, the map-driven destination pick, and
-the optimistic overlay that keeps the inspector and the map in lock-
-step with the local order draft. The user-visible spec lives in
-[`../PLAN.md`](../PLAN.md) Phase 16; the engine semantics are quoted
-from [`game/rules.txt`](../../game/rules.txt) section "Грузовые
-маршруты" (lines 808–843); this file is the source of truth for how
-the UI surfaces those rules.
+This document covers the cargo-route surface: the four-slot
+inspector subsection, the map-driven destination pick, and the
+optimistic overlay that keeps the inspector and the map in lock-step
+with the local order draft. The engine semantics are quoted from
+[`game/rules.txt`](../../game/rules.txt) section "Грузовые маршруты"
+(lines 808–843); this file is the source of truth for how the UI
+surfaces those rules.
 
 ## Engine semantics in one paragraph
 
@@ -44,7 +43,7 @@ section). `Remove` emits a `removeCargoRoute` command. The collapse
 rule on the order draft store ensures only one entry per
 `(source, loadType)` slot survives in the draft at any time, so a
 sequence of `Add → Edit → Remove` collapses to the latest verb only
-(matching the production-controls pattern from Phase 15).
+(matching the production-controls pattern).
 
 Disabled state: every button is disabled when the
 `OrderDraftStore` or `MapPickService` context is missing (the
@@ -98,8 +97,8 @@ centre + zoom before each remount and restores them when the game
 id is unchanged, so adding a route mid-pan does not jolt the view.
 
 Arrows are drawn as a shaft plus two short arrowhead wings. Per-type
-styling (placeholder Phase 16 colours; final values land in Phase
-35 polish):
+styling (visual refinements are deferred to the finalization plan
+(../PLAN-finalize.md)):
 
 | Load type | Stroke colour | Notes                    |
 | --------- | ------------- | ------------------------ |
@@ -132,11 +131,11 @@ ownership of the *origin*). The picker mirrors that contract: the
 `reachableSet()` in `cargo-routes.svelte` filters out only the
 source planet itself.
 
-Why inline rather than via a Go calc bridge? See the Phase 15 / 16
-deferral note in [`calc-bridge.md`](./calc-bridge.md). The formula
-is trivial (`tech × 40`) and the WASM glue would be premature
-infrastructure; when the calc bridge phase lands the shared
-`pkg/calc.FligthDistance` will replace this implementation.
+Why inline rather than via a Go calc bridge? See the deferral note
+in [`calc-bridge.md`](./calc-bridge.md). The formula is trivial
+(`tech × 40`) and the WASM glue would be premature infrastructure;
+when the calc bridge lands the shared `pkg/calc.FligthDistance` will
+replace this implementation.
 
 ## Tests