@helix3/helix-cli 0.1.14-helix3.160 → 0.1.14-helix3.161
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -250,6 +250,12 @@ A published world ships only its **built bundle**, so there is nothing on the se
|
|
|
250
250
|
channel for exactly that reason.
|
|
251
251
|
- **Limit**: 128 MiB compressed, checked locally before anything is uploaded.
|
|
252
252
|
|
|
253
|
+
Before upload, module-based multiplayer worlds are checked for server realizability: every bank must
|
|
254
|
+
be published with the declared checksum and the shared manifest validator must accept all module
|
|
255
|
+
budgets under the 100,000 tick-node ceiling. Fix the named module/bank when this gate refuses a
|
|
256
|
+
publish. For exceptional recovery only, `--skip-realizability-check` bypasses this check; flat-v0
|
|
257
|
+
worlds are unaffected.
|
|
258
|
+
|
|
253
259
|
The programmatic surface (`publishWorld`, `checkBundle`, `whoAmI`, …) is exported for other CLI
|
|
254
260
|
modules. Agent integrations should instruct or delegate to the `helix` commands above rather than
|
|
255
261
|
reimplementing operational behavior in a transport package.
|
package/package.json
CHANGED