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>
