Docs: LANTERN — record operator decisions (all parked questions resolved 2026-07-14)

Build Phase 1 gym first; standing ★-review auth; build A0 material foundation now;
delete siege branches. Phase 1: manual aim (auto-target cut), 4 discrete ability buttons,
Harpooner yanks target-to-you, roadmap 5 Sparks. Fresh save epoch (no migration).
Dark-side contact = non-telegraphed chip. Lantern = free-position plant.

Locked into: operator-questions (resolved summary), Phase 1 spec (open forks -> resolved),
currency spec (fresh saves), world-model Build Spec (operator-resolutions block).

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

Docs/Vault/06_Roadmap/Lantern_Currency_ReMean.md

@@ -42,10 +42,10 @@ one; append the new ones:
 
 - **Flame** and **Loudness** are **not** ledger bytes (Health; a derived meter). Do not give them `ResourceId`s.
 - ⚠ **Re-meaning byte 3 (Charge→Tallow) changes a persisted VALUE's meaning.** The save persists `Ledger[]` as
-  `{ItemId, Count}` rows — an old save's `ItemId=3` (Charge) would load as Tallow. **Recommendation:** since
-  the pivot is a hard direction change and old co-op-Hades saves are not carried into LANTERN, **start LANTERN
-  saves fresh** (a new save version epoch) rather than migrate — cleaner than a value-remap migration. Confirm
-  with the operator (parked). If saves must migrate, add a `SaveData.Version`-gated remap in `SaveService.Load`.
+  `{ItemId, Count}` rows — an old save's `ItemId=3` (Charge) would load as Tallow. **RESOLVED (operator,
+  2026-07-14): start LANTERN saves FRESH** — a new save version epoch, no migration of co-op-Hades saves (old
+  saves won't load into LANTERN). This dodges the value-remap entirely; the byte-3 (Charge→Tallow) reuse is
+  safe because no old save is ever read.
 
 ## What changes vs. stays