@onceworlds/cli 0.6.0 → 0.7.0

package/README.md

@@ -60,6 +60,10 @@ with the link) or Public (also listed on Onceworlds).
 }
 ```
 
+`engine` (`"1"`, `"1.2"` or an exact `"1.2.3"`) makes a game run on the engine the platform hosts: it adds an import map
+so `import { createGame } from '@onceworlds/engine'` works in a page with no build step. `"1"` is the newest 1.x, which gets
+fixes without a redeploy; an exact version never changes. A deploy fails, saying what is available, for a version that doesn't exist.
+
 `dir` is the folder to publish (for example `dist` after a build); it must contain
 `index.html`. `productionBranch` (default `main`) picks the branch that goes live;
 the dashboard can change it too, and the file wins again only when this value changes.
@@ -79,6 +83,18 @@ from the running game and commit them under `store/`. `onceworlds doctor` says w
 
 ## Commands
 
+- `onceworlds new [folder] --kit <name>` starts a game from a kit: a complete game on the engine, one per kind of game
+  (`--list` shows them). It writes the kit with an `onceworlds.json` for your game (`--name`, `--slug`, `--description`;
+  the folder's name by default) and the engine guide as `AGENTS.md` and `CLAUDE.md`. `--template party` or `starter` starts a
+  small game on the SDK alone.
+- `onceworlds check [dir]` is what to run before a deploy: doctor's findings and, for an engine game, the game's own tests
+  (`npm test`) and simulated matches played with no browser, with a reloaded host, a dropped player, the host changing (also while
+  paused), a late joiner and garbage messages. A failing test or a match with errors exits with an error. The game's config is
+  read from `game.config.js` (or `src/game.config.js`, or `--config <file>`): `export const config = {...}`, and `export const actions`
+  lets check compare "How to play" with the action map exactly. Needs `npm install` in the game folder.
+- `onceworlds posters [dir]` draws each `game.poster()` scene of your latest draft (`?poster=<name>`) in a browser on this
+  computer and saves the pictures into `store/`, naming them in `onceworlds.json` when it has no icon or thumbnails.
+  `--only cover,icon` picks some.
 - `onceworlds init [dir]` sets a game folder up, with the files the dashboard's import commits. It writes
   `onceworlds.json` (the link and name come from `package.json`'s name or the folder's; `dir` is your build's
   output folder when `package.json` has a build script, else `.` or the folder with your `index.html`),
@@ -94,8 +110,9 @@ from the running game and commit them under `store/`. `onceworlds doctor` says w
 - `onceworlds doctor [dir]` looks through the game's files for what games often ship with: no viewport
   tag, text fields under 16px (Safari zooms the page when one is focused), `confirm()` and other dialogs
   (blocked in the game frame), localStorage (gone on reload), and, for games with rooms, `Date.now()` for
-  shared time and no use of the platform's lobby. It only suggests: nothing in it stops a deploy
-  (`--strict` exits with an error on likely bugs, for CI).
+  shared time and no use of the platform's lobby. For an engine game it also reads the action map
+  (`Input.axis2d`, `Input.button`) and offers the `controls` it implies: `--fix` writes them into `onceworlds.json` when it has
+  none. It only suggests: nothing in it stops a deploy (`--strict` exits with an error on likely bugs, for CI).
 
 Games talk to the platform through the injected `window.onceworlds` SDK. The
 starter template's `AGENTS.md` documents it for AI coding tools.