#81 follow-ups: peer warp must not stomp the POV vortex; panel draw probe; mech3 ghost symbols

Two field observations from watching the 4-node stress, both run down:

1. "A respawn happened without the blue vortex" -- REAL.  The translocation
   effect is ONE global slot shared by the POV lifecycle and the world-anchored
   peer sphere (a port extension).  A peer's un-wreck arriving while the local
   pilot's own collapse/wait/expand was in flight overwrote gWarpPhase/gWarpPOV
   and killed the POV vortex.  Invisible before the respawn fix only because
   overlapping respawns barely existed; now they are routine.  Fix: the POV
   lifecycle owns the slot -- BTStartWarpEffect self-skips while it is active
   ([tloc] peer warp SKIPPED).  2-node bench: 20/20 POV collapse+expand pairs,
   9 peer spheres played, 11 correctly skipped; solo: 8/8 pairs unchanged.

2. "Comms panel counted no deaths" -- panel machinery CORRECT; the 4-node
   zeros were the bench's own CPU crush (4 core-pinned instances starved the
   PilotList to <0.6 Hz, so rows redrew minutes-stale).  Added the arbiter:
   [score] panel DRAW slot/pilot/kills/deaths edge log (BT_SCORE_LOG) -- the
   2-node rerun drew 0->9 / 0->11 live on both nodes, local AND replicated
   (SBMIRROR rows confirm owner->replicant tally flow on all 4 stress nodes).

Also: the mech3 offline-authoring stubs declared every <Subsystem>::DefaultData
as Entity__SharedData while the real statics are Simulation__SharedData (this
engine derives Entity FROM Simulation) -- ~20 ghost symbols /FORCE silently
resolved to garbage.  DefaultData half fixed (SubsystemDefaultData now returns
the true common base Simulation::SharedData); the CreateStreamedSubsystem stub
signatures remain wrong (nested SubsystemResource* + ResourceFile*), are
cold (no callers), and are tracked in open-questions + gotchas §6 stub-typedef
corollary.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

context/open-questions.md

@@ -879,6 +879,14 @@ register.  ⚠ The audit also flags the damage-economy item as SELF-CONTRADICTOR
 ## Content build sub-project (low priority)
 - Lab/other-build maps (`des`/`burnt`/`frstrm`) are source-only (`.map` in CONTENT/BT/MAPS/); would
   need compiling into a RES via the DOS `btl4tool.exe`. The 8 RES maps cover testing.
+- **Offline subsystem-authoring dispatch is un-linked (known, cold, 2026-07-30).** mech3.cpp's
+  `Mech::CreateSubsystemStream` dispatches to 20 per-class `CreateStreamedSubsystem` stubs whose
+  guessed signatures (`void*`/`int`) don't match the real modules (nested `<X>::SubsystemResource*`
+  + trailing `ResourceFile*`, e.g. mechtech.cpp:407) — all 20 are /FORCE-silenced unresolved
+  externals. No callers exist, so it cannot crash today; before wiring any authoring tool through
+  it, convert each to a per-module bridge fn in a complete-type TU (gotchas §6 stub-typedef
+  corollary). The parallel `DefaultData` half of the table WAS the same trap and is fixed
+  (`Simulation__SharedData`).
 
 ## Key Relationships
 - Feeds from: every subsystem/render topic (their deferral notes collect here).

context/reconstruction-gotchas.md

@@ -121,6 +121,17 @@ mislanch.cpp's extern but not projweap.cpp's → first AUTOCANNON shot AV'd). **
 bridge-signature change, `grep -rn "extern .*<name>"` and update every declaration; then grep
 the fresh link output for the symbol name** — the pre-existing LNK2019 wall camouflages new
 entries if you only eyeball it.
+**Stub-typedef corollary (mech3 tool path, 2026-07-30):** a LOCAL stub TU that re-declares a
+sibling class's STATIC MEMBER with the wrong typedef mangles to a **ghost symbol** — mech3.cpp
+declared every `<Subsystem>::DefaultData` as `Mech::SharedData` (= `Entity__SharedData`) while
+the real definitions are the inherited `Simulation__SharedData` (in THIS engine `Entity` derives
+from `Simulation`; `Entity__SharedData : public Simulation::SharedData`, ENTITY3.h:9) → ~20
+unresolved externals, all /FORCE-silenced, all cold (offline authoring dispatch has no callers).
+Fixed for the DefaultData statics; the `CreateStreamedSubsystem` stub SIGNATURES are still wrong
+(real ones take the class's NESTED `SubsystemResource*` + trailing `ResourceFile*`) and stay
+unresolved-by-design until bridged per-module ([[open-questions]]). **Rule: when a "benign" LNK
+wall exists, `tail` on the build output hides the fleet — always grep the FULL log; and verify a
+stub's member TYPE against `dumpbin /symbols` of the defining obj, not against what looks right.**
 **Duplicate-GLOBAL corollary (glass per-display windows, 2026-07-20):** a global DEFINED in two
 libs (the 1995 headers declare free globals without `inline`/`extern`, so `application`,
 `ghWnd`, … exist in BOTH `munga_engine` and `bt410_l4`) links under `/FORCE:MULTIPLE` with

context/translocation-warp.md

@@ -121,7 +121,12 @@ Local player's own death → `BTStartWarpCollapsePOV()` (btplayer.cpp `VehicleDe
 (local-guarded). `BTWarpForceUnmask()` on mission-end / no-DropZones. **Peer warp IS wired + visible
 (`160b78e`):** an observer sees a peer's death/respawn warp — the replicant un-wreck fires the
 world-anchored `BTStartWarpEffect(x,y,z)` at the peer's position (mechdmg.cpp:1074, gated to
-`ReplicantInstance`; `simulationState` rides every update-record header so the observer tracks the
+`ReplicantInstance`; the effect machine is a SINGLE global slot, and since 2026-07-30 the local
+pilot's own POV lifecycle OWNS it — `BTStartWarpEffect` self-skips while `gWarpPhase!=0 && gWarpPOV`
+(`[tloc] peer warp SKIPPED`), because a peer's un-wreck landing mid-collapse/wait/expand used to
+overwrite the machine and kill the POV vortex ("my respawn had no blue whirlwind"). Invisible
+before the #81 respawn fix only because overlapping respawns barely existed; 2-node bench: 20/20
+POV collapse+expand pairs, 9 peer spheres played, 11 correctly skipped; `simulationState` rides every update-record header so the observer tracks the
 peer's state). The ONLY remaining nuance [T3, non-gating]: the observer's peer sphere is anchored to
 the peer's WORLD position rather than the peer's authentic `DropZoneLocation` (that attribute isn't
 replicated) — a fidelity refinement, not a missing effect.