@forgeax/game 0.3.7 → 0.3.9

package/docs/release-0.3.3.md

@@ -1,73 +0,0 @@
-# `@forgeax/game` 0.3.3 release guide
-
-Version `0.3.3` adds the EA depot without removing the public AW path. The packaged
-provider is unchanged; one explicit library selection binds the matching depot and
-gateway together.
-
-> [!IMPORTANT]
-> EA is currently available only through the office-network `local` gateway.
-> There is no reachability-based fallback: silently changing libraries would make
-> identical queries resolve to different assets.
-
-## User contract
-
-```bash
-# Public/default
-npx -y @forgeax/game@0.3.3 asset3d enable
-
-# Office network
-npx -y @forgeax/game@0.3.3 asset3d enable --library ea
-
-npx -y @forgeax/game@0.3.3 asset3d doctor --json
-```
-
-The selected mode writes these non-secret provider settings:
-
-| Mode | Depot | Built-in gateway |
-|:--|:--|:--|
-| Default or `--library aw` | `aw` | Existing public AW service |
-| `--library ea` | `ea` | `http://test-ultrongw.woa.com/trpc.oasismetric.omcontentserver.http` |
-
-`FORGEAX_ASSET_LIBRARY=aw|ea` is the deployment selector. `--base-url` and
-`FORGEAX_ASSET_LIBRARY_BASE_URL` remain gateway overrides and never change the
-selected depot. The project stores only the service URL, depot name, private
-credential-file path, and live-derived download origins.
-
-## Transaction-bound search
-
-`search_asset` accepts the execution UUID returned by `asset3d begin`; it no longer
-accepts a caller-selected `output_dir`. The Game Plugin bridge verifies the execution
-and exact query list, then injects the private quarantine path before invoking the
-packaged provider. This removes agent path guesses such as `assets` from the tool
-contract while preserving the existing provider implementation.
-
-The bridge also persists the exact checked TextContent by execution. A normal commit
-is now `asset3d commit --execution <uuid> --json`; agents no longer reconstruct large
-provider JSON as shell input.
-
-`asset3d enable` now installs the generic `asset3d-search` bridge into every Agent
-host previously selected by `install`. The user-level launch command carries no key
-and no project path; it discovers the active project's owned Provider configuration
-from its working directory. Disabled projects advertise zero Asset3D tools. Start a
-new Agent session after enabling so the host refreshes its MCP tool inventory.
-
-## Verified migration
-
-- [x] EA access check succeeded through the packaged provider.
-- [x] Query `wooden barrel` returned EA asset `SM_Prop_Bucket_001.zip`.
-- [x] The provider downloaded and converted the result to GLB.
-- [x] Delivered result was 565,650 bytes with SHA-256
-  `17897a89e652170e7ab98b08dd71f10c4289e58b38caac52e0b41e44b5f72185`.
-- [x] The primary GLB was 314,908 bytes.
-- [ ] Registry publication and registry-downloaded tarball verification.
-
-## Release gates
-
-```bash
-bun run typecheck
-bun test test/*.test.ts
-FORGEAX_ASSET3D_PROVIDER_BUNDLE=<audited-provider-archive> bun run build
-FORGEAX_ASSET3D_PROVIDER_BUNDLE=<audited-provider-archive> \
-  npm pack --ignore-scripts --json --pack-destination <audited-directory>
-bun scripts/check-package-artifact.ts <audited-directory>/forgeax-game-0.3.3.tgz
-```

package/docs/release-0.3.4.md

@@ -1,66 +0,0 @@
-# @forgeax/game 0.3.4 release contract
-
-Version `0.3.4` adds a self-contained Linux x64 Asset3D Provider while preserving
-the existing opt-in workflow. Ordinary `install` and `init` remain platform-neutral
-and keep Asset3D disabled. A user enables Asset3D only from an initialized game:
-
-```bash
-npx -y @forgeax/game@0.3.4 asset3d enable
-npx -y @forgeax/game@0.3.4 asset3d doctor --json
-```
-
-## Supported Provider targets
-
-| Host | Provider archive SHA-256 | Status |
-|---|---|---|
-| Darwin arm64 | `9492c507a3afe5cafcd50b5f782b313c8716c2e52f5def06592c6a100c0459db` | Supported |
-| Linux x64 | `e6ac3df76c8b82f9fe2c063dd3f221324a9dad5176fd52535a5144b0ff6002d8` | Supported; Python 3.11 or 3.12 required |
-
-Both archives bind Provider commit
-`c181c48fbffc933a7ce9a0836f7878ca5e6d77e1`. The package build fails if either
-source archive is absent, is a symlink, or differs from its approved digest. The npm
-artifact gate repeats those checks against the packed bytes.
-
-The offline wheelhouses omit upstream dependency test suites and redact
-credential-shaped user-info from dependency documentation examples. Runtime modules
-and package metadata remain present, each rewritten wheel is re-RECORDed and
-hash-locked, and the resulting platform archives are byte-reproducible. This keeps
-test-only public tokens and false credential patterns out of the npm payload.
-
-Linux arm64 and Windows are not part of this release. `asset3d enable` fails closed
-with `asset3d_provider_target_unreleased` on those hosts; it does not install a
-different target or fall back to downloaded Provider code.
-
-## Linux release gate
-
-The Ubuntu x64 CI job performs the Linux-specific verification from the same package
-assets that are published:
-
-1. Provision the Provider into an empty managed cache without downloading Provider
-   code or Python dependencies.
-2. Verify the archive manifest, target, file digests, wheel lock, and converter.
-3. Execute the bundled Linux x64 `FBX2glTF` binary.
-4. Launch the installed Provider over stdio MCP and require `search_asset` in
-   `tools/list`.
-
-This proves Linux provisioning and MCP capability discovery. It does not substitute
-for an authenticated request to the internal AW service, which requires network
-reachability and user credentials and remains a separate environment acceptance
-gate.
-
-## Maintainer checklist
-
-- [ ] `bun run typecheck`
-- [ ] `bun test`
-- [ ] `bun run build`
-- [ ] `npm pack --ignore-scripts --pack-destination <empty-directory>`
-- [ ] `bun run release:check -- <exact-tarball>`
-- [ ] Ubuntu x64 `asset3d-linux-x64` CI job is green on the exact release commit.
-- [ ] The packed artifact contains both Provider archives and no credential, source
-      checkout, managed cache, or provisioned Python environment.
-- [ ] The exact tarball passes the repository secret and private-path scans before
-      publication.
-
-The AW production default and explicit EA override remain as documented in
-[`release-0.3.3.md`](release-0.3.3.md). Credential storage and real search/import
-acceptance boundaries remain unchanged and are defined in [`asset3d.md`](asset3d.md).

package/docs/release-0.3.5.md

@@ -1,32 +0,0 @@
-# @forgeax/game 0.3.5
-
-## Compatibility repair
-
-| Boundary | Release behavior |
-|:--|:--|
-| Engine SDK | Exact dependency 0.1.26, commit `f3d0db12405e168e4204e32a9cde32e0df8d87ae` |
-| Project discovery | Recognizes strict `forge.json` v2 with `defaultScene`; does not inject the forbidden legacy `entry` field |
-| SDK manifest | Validates the released 1.7.0 manifest and exact Engine/DevKit identities |
-| Preview | Uses Engine-owned `--port 0` allocation instead of conflicting with another game on port 5173 |
-| Asset3D upgrade | Refreshes existing older package-owned bridges during install/update; preserves custom configurations |
-
-## Install or update
-
-```bash
-npx -y @forgeax/game@0.3.5 install --ide codex,cursor,claude
-# In a genuinely empty game directory:
-npx -y @forgeax/game@0.3.5 init
-```
-
-For an existing Engine 0.1.26 project, run `update --ide codex` with this package,
-then restart the host session. Asset3D remains opt-in with `asset3d enable`.
-
-> [!IMPORTANT]
-> This release pins Engine 0.1.26. It does not silently migrate games using Engine
-> 0.1.7. Keep those games on plugin 0.3.4 until deliberately migrating through the
-> Engine-supported workflow. Do not add `entry` to a v2 manifest to work around the
-> old plugin's project detection.
-
-The plugin must return Engine-owned Preview readiness and matching root/build
-identity. A direct Engine CLI preview or a listening port alone is not MCP
-acceptance. Asset search/import and visible gameplay require separate verification.