spoint 0.1.636 → 0.1.638

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spoint",
-  "version": "0.1.636",
+  "version": "0.1.638",
   "description": "Physics and netcode SDK for multiplayer game servers",
   "type": "module",
   "workspaces": [

package/src/sdk/WorkerEntry.js

@@ -190,14 +190,25 @@ export async function init({ worldDef, apps = [], migrationSnapshot = null, loca
   ctx.onClientConnect = createConnectionHandlers(ctx).onClientConnect
 
   stageLoader.loadFromDefinition('main', worldDef)
+  // server-scale-worldpersistence-async-trimesh-race-and-in-flight-flush-frequency: wait (bounded) for
+  // every autoTrimesh/addTrimeshCollider build the spawn loops above just kicked off (including
+  // custom._interior placed-models like env-sillos's trimesh floor, apps/placed-model/index.js) to
+  // settle before anything else can run against these entities. src/sdk/ServerAPI.js's loadWorld()
+  // already does this for the real multiplayer server; singleplayer's in-Worker path had NO equivalent
+  // wait, and unlike a human joining a remote server (real network latency covers the gap), a local
+  // client can connect fast enough to spawn its player capsule before env-sillos's floor trimesh body
+  // exists -- live-witnessed: player fell straight through, position Y drifting from spawn (2.27) to
+  // -100 and still falling (onGround:false) by tick 38, X/Z correctly at the declared spawn point.
+  try { await appRuntime.waitForPendingTrimeshBuilds?.() } catch (e) { console.error('[world-persistence] waitForPendingTrimeshBuilds error:', e.message) }
   // Restore-on-boot: must run after BOTH the world-def spawn (stageLoader.loadFromDefinition, immediately
   // above) AND the placed-model replay loop (the `for (const p of placed)` block above, already run before
   // this point in this file) have finished creating every entity -- see WorldPersistence.js's own header
-  // comment for the full ordering rationale and the accepted async-autoTrimesh-body gap. A missing/
-  // version-mismatched/world-mismatched snapshot (including a genuinely fresh IndexedDB with nothing saved
-  // yet -- every first-ever singleplayer session) is a clean no-op, matching server.js's ServerAPI.js
-  // loadWorld() call site exactly: this never throws into init(), a broken/absent snapshot degrades to
-  // "world boots exactly as it always did today", never a boot failure.
+  // comment for the full ordering rationale. The async-autoTrimesh-body race this comment used to accept
+  // as an open gap here is now closed above (waitForPendingTrimeshBuilds), matching ServerAPI.js's own
+  // ordering exactly. A missing/version-mismatched/world-mismatched snapshot (including a genuinely fresh
+  // IndexedDB with nothing saved yet -- every first-ever singleplayer session) is a clean no-op, matching
+  // server.js's ServerAPI.js loadWorld() call site exactly: this never throws into init(), a broken/absent
+  // snapshot degrades to "world boots exactly as it always did today", never a boot failure.
   try { await restoreWorldSnapshot(ctx) } catch (e) { console.error('[world-persistence] restore error:', e.message) }
 
   // Host migration (client/HostMigration.js): the newly-elected host boots this SAME WorkerEntry.init()