fix(physics): keep remote placement and targeting in one world frame

CreateObject positions are landblock-local, but Runtime first-entry previously submitted remotes with a zero world offset. Runtime now owns the accepted local-player world-frame center and converts remote placements before SetPosition. The local physics host also publishes body.Position rather than CellPosition's landblock-local origin, so TargetManager no longer directs monsters toward a phantom player position. User gate: monster/static placement, chase, and attacks accepted outside Tusker Barracks.

src/AcDream.Runtime/Entities/RuntimeRemoteFirstEntryState.cs

@@ -346,7 +346,8 @@ internal sealed class RuntimeRemoteFirstEntryState
                     lease.Route.SetPositionFlags,
                     collisionSource,
                     gameTime,
-                    out RuntimeSetPositionCommand command);
+                    out RuntimeSetPositionCommand command,
+                    resolveWorldOffsetFromRuntimeFrame: true);
             if (moverStatus
                 == RuntimeSetPositionMoverPreparationStatus.RetrySetupUnavailable)
             {