@forgeax/engine-fbx 0.1.4 → 0.1.6

package/README.md

@@ -19,21 +19,20 @@ FBX bytes -> ufbx (wasm) -> JSON POD -> parse-*.ts -> meta.json
 ## AI user consumption path
 
 The importer key `'fbx'` is unchanged from the SDK era -- zero migration for
-existing `.fbx.meta.json` sidecars. The host installs the Scene owner decoder
-and loads the published payload by its typed kind:
+existing `.fbx.meta.json` sidecars. The engine resolves the importer
+automatically via `loadByGuid`:
 
 ```ts
-import { sceneAssetKind } from '@forgeax/engine-scene';
+// 1) Point the asset registry at the pack index
+assets.configurePackIndex('/pack-index.json');
 
-// 1) load the Pack payload through the typed Scene owner
-const res = await assets.load(guid, sceneAssetKind);
+// 2) loadByGuid dispatches on meta.importer: 'fbx' automatically
+const res = await assets.loadByGuid<SceneAsset>(guid);
 if (!res.ok) {
   console.error(res.error.code, res.error.hint);
   return;
 }
-// 2) World owns the shared ref and performs the scene instantiation
-const scene = world.internSharedRef('SceneAsset', res.value);
-const root = world.instantiateScene(scene);
+const scene = res.value; // SceneAsset -- ready for instantiate()
 ```
 
 Under the hood, `vite-plugin-pack` calls `fbxImporter.import(ctx)` which
@@ -97,18 +96,11 @@ Do not copy-paste the member list; inspect the source for the current union.
 
 ## Contributor toolchain
 
-> [!NOTE]
-> A source tree containing `.forgeax-public-distribution` is the public SDK
-> source mode. It already carries the checked `pkg/` closure, so ordinary SDK
-> install/build work does not need `fetch-wasm`, emcc, or a network connection.
-> Rebuild the bundle only when the FBX WASM source or toolchain changes. The
-> fetch/build paths below describe a contributor checkout.
-
 <details>
 <summary>Getting pre-built WASM (fetch-wasm)</summary>
 
-In a contributor checkout, the `pkg/` directory is **not committed to git**
-(zero-binary invariant). A workspace `pnpm install` or `bun install` runs a package-local, best-effort
+The `pkg/` directory is **not committed to git** (zero-binary invariant). A
+workspace `pnpm install` or `bun install` runs a package-local, best-effort
 postinstall hook that fetches the matching bundle when it is absent. The hook
 is idempotent and non-fatal: it skips a complete `pkg/`, and an unavailable
 release leaves installation successful with the explicit recovery command