docs: close #338 — headline refuted by full-capture statistics; AD-68 files the real residual

The three-site probe answered it in one run: prepare and publish carry
the authored 0.600/1.500 to the publication candidate, and resolve
receives exactly those values for the entire session after one early
0.400 reading. Re-reading the ORIGINAL 337-support.log with statistics
instead of an eyeball: authored pair 111,248 lines, 0.400 pair 358. The
filing was built on an early line of a 255k-line capture; the alleged
mechanism (values never wired to the mover) does not exist.

The 358 are AD-68, now registered: GetSetupMoverShape's placeholder
(empty spheres -> legacy capsule, 0.4/0.4 steps) during an entity's
async Setup-residency window, plus the local player's own seconds-long
window between controller construction and publication-candidate
adoption. Retail loads synchronously and has no such window. Left as-is
deliberately: shrinking it is streaming work.

The filing still paid for itself: three false doc-comment claims
corrected in PlayerMovementController (retail '~0.4 m' twice, and an
ApplyStepHeights writer that never existed anywhere in the tree —
replaced with the real writer chain), retail's actual fallback pinned at
0.04 (CTransition::step_up @0x0050b655), and the resolve probe now
prints the mover id, because the early 0.400 was most plausibly a
REMOTE player — remotes also carry IsPlayer — and the guid rule
(feedback_probe_identity_attribution) exists precisely to stop that
misread.

No production behaviour changed; nothing for the morning gate. AD
section 50 -> 51. Suite 11,234 / 4 / 0.

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

src/AcDream.Core/Physics/PhysicsEngine.cs

@@ -1935,6 +1935,14 @@ public sealed class PhysicsEngine
             // its two resolve calls. A silent probe proves nothing, so this
             // one sits where every caller must pass through. Filtered to the
             // player so remotes cannot drown it.
+            // #338 self-report, once per process, UNCONDITIONAL. The probe has
+            // now been silent through two placements, and "no output" cannot
+            // distinguish "this site is never reached" from "the flag is
+            // false". This line answers both directly instead of a third round
+            // of inference. One Interlocked per process; strip with the probe.
+            PhysicsDiagnostics.AnnounceStepHeightProbeOnce(
+                (moverFlags & ObjectInfoState.IsPlayer) != 0);
+
             // The flag test MUST precede the interpolated string: this site runs
             // per resolve, and building the detail eagerly cost 128 B/resolve
             // with the probe OFF — caught by Slice I1's zero-allocation gate,
@@ -1942,9 +1950,14 @@ public sealed class PhysicsEngine
             if (PhysicsDiagnostics.ProbeStepHeightsEnabled
                 && (moverFlags & ObjectInfoState.IsPlayer) != 0)
             {
+                // The mover id is REQUIRED here (feedback_probe_identity_attribution):
+                // remote players also carry IsPlayer, and the one early
+                // 0.400 reading this probe caught was nearly misattributed to
+                // the local player for exactly that reason — it was a remote
+                // in its Setup-residency window (AD-68).
                 PhysicsDiagnostics.LogStepHeights(
                     "resolve", stepUpHeight, stepDownHeight,
-                    $"onGround={isOnGround} hasBody={body is not null}");
+                    $"mover=0x{movingEntityId:X8} onGround={isOnGround} hasBody={body is not null}");
             }
 
             transition.ObjectInfo.StepDown = true;