@onceworlds/cli 0.12.0 → 0.14.0

package/README.md

@@ -7,7 +7,7 @@ players) with no server code.
 ## Deploy from GitHub Actions
 
 Deploys run from GitHub Actions: GitHub vouches for the repo, so there are no API
-keys. The easiest setup is to import the repo at https://onceworlds.com/create?new=github,
+keys. The easiest setup is to import the repo at https://onceworlds.com/upload?new=github,
 which adds `onceworlds.json` and `.github/workflows/onceworlds.yml` for you (that
 workflow also builds with npm, pnpm, yarn or bun when there's a build script). To write
 the same files into a folder before it is on GitHub, run `npx @onceworlds/cli init` there.
@@ -96,7 +96,7 @@ from the running game and commit them under `store/`. `onceworlds doctor` says w
   whose idea, look and screens are never yours; it adds its own notes as `KIT.md` and its fingerprints as `.onceworlds/kit.json`,
   so `check` can note what is still the kit's. `--template party` or `starter` starts from a complete game on the SDK, and
   `--template <name>` from a scene project of Onceworlds Build.
-- `onceworlds check [dir]` is what to run before a deploy, for any game (canvas, three.js, PixiJS, Phaser, the DOM, the engine):
+- `onceworlds check [dir]` is what to run before a deploy, for any game (canvas, three.js, PixiJS, Phaser, the DOM, the engine, a Godot or Ren'Py web export):
   doctor's findings, plus the hosts the platform's CSP won't let the game reach, WebSockets of its own, text too small for a phone,
   a second countdown under the platform's lobby, shared state written from `Math.random()` or the device's clock, and a `DESIGN.md`
   silent on originality and the first minute. Then it plays the game on the local platform (`serve`'s) in headless Chrome: it loads
@@ -123,7 +123,7 @@ from the running game and commit them under `store/`. `onceworlds doctor` says w
   imports it (next to a `AGENTS.md` of your own it writes `ONCEWORLDS.md` and adds a pointer to yours). It never
   overwrites a file you have: `--force` replaces only what init writes, never your own `AGENTS.md`, `CLAUDE.md` or `.gitignore`.
   `onceworlds new` writes the same workflow and `.gitignore` into every game it makes.
-  Then commit, push, and import the repo at https://onceworlds.com/create?new=github.
+  Then commit, push, and import the repo at https://onceworlds.com/upload?new=github.
 - `onceworlds deploy [dir]` uploads only the files that changed and publishes the game
   (the workflow runs it). It lists every file it skipped because Onceworlds can't serve it. A game's tests never go up: `*.test.js`, `vitest.config.*` and the `test/` folder at the top of the game.
 - `onceworlds serve [dir]` plays any game in your own browser on this computer, offline and with no login, on a local platform