Creator SDK Runtime Package Bridge

The Creator SDK can now turn a generated game template into the minimal package shape accepted by everarcade-runtime.

Creator flow

node creator-sdk/cli/everarcade.mjs new --template arena --name audit-arena --dir /tmp/audit-arena
node creator-sdk/cli/everarcade.mjs build --project /tmp/audit-arena
node creator-sdk/cli/everarcade.mjs test --project /tmp/audit-arena
node creator-sdk/cli/everarcade.mjs package --project /tmp/audit-arena

The package command does not compile Rust and does not require a WASM toolchain. It writes:

dist/runtime-package/
  manifest.json
  world.wasm
  world.json

Expected success output:

Runtime Package: PASS (<game-id>)

Runtime package format

manifest.json contains the fields required by the runtime package loader:

{
  "package_id": "<game-id>",
  "package_version": "<game-version>",
  "runtime_compatibility": "everarcade-runtime-v0.1",
  "wasm_path": "world.wasm",
  "wasm_hash": "<64 character sha256 hex>",
  "signature": "sha256:<wasm_hash>",
  "world_id": "<world-id>"
}

The Creator SDK discovers the runtime compatibility string from runtime/everarcade-runtime/src/runtime/configuration.rs, where RUNTIME_VERSION is currently everarcade-runtime-v0.1.

World metadata

world.json is human-readable metadata for the runtime boot proof. It includes:

• world_id
• game_id
• game_name
• template
• classification
• package_classification
• created_by
• runtime_package_version
• runtime_compatibility

For v0.1 packages generated by this bridge, the classification is:

deterministic-placeholder-wasm
placeholder-runtime-package

Placeholder WASM limitation

world.wasm is a deterministic placeholder payload derived from Creator SDK game metadata. The current runtime validates bytes, SHA-256 hash, signature placeholder, manifest fields, and world metadata, but it does not execute game WASM.

This proves runtime boot from a creator-generated package. It does not yet prove real WASM game execution or interactive multiplayer.