@dreamboard-games/cli 0.1.30-alpha.3 → 0.1.30-alpha.30

package/skills/dreamboard/references/quickstart.md

@@ -14,13 +14,13 @@ npm install -g dreamboard
 Log in:
 
 ```bash
-dreamboard login
+dreamboard auth login
 ```
 
-Create a game:
+Create a project:
 
 ```bash
-dreamboard new my-game --description "A trick-taking card game"
+dreamboard project create my-game --description "A trick-taking card game"
 cd my-game
 ```
 
@@ -30,25 +30,27 @@ Edit `rule.md` and `manifest.json`. Use
 [Manifest authoring](./manifest-authoring.md) for the manifest
 schema.
 
-Regenerate scaffolded files from your authored source:
+Commit and push your authored source with Git:
 
 ```bash
-dreamboard sync
+git add .
+git commit -m "Create my game"
+git push -u origin main
 ```
 
-Compile the current authored head:
+Check server state for the pushed commit:
 
 ```bash
-dreamboard compile
+dreamboard project status --commit HEAD --wait
 ```
 
-Run the game locally:
+Verify the exact commit:
 
 ```bash
-dreamboard run
+dreamboard verify --commit HEAD
 ```
 
-Start a local server to play the compiled game
+Start a local server to play the project:
 
 ```bash
 dreamboard dev
@@ -56,9 +58,10 @@ dreamboard dev
 
 Useful follow-up commands:
 
-- `dreamboard pull` reconciles authored changes when the remote has advanced.
-- `dreamboard status` compares local and remote state.
-- `dreamboard clone <game-slug>` pulls an existing game into a local workspace.
+- `dreamboard project clone <project>` clones an existing project repository.
+- `dreamboard test` runs offline reducer tests.
+- `dreamboard build --commit HEAD` creates a server build for a pushed commit.
+- `dreamboard preview --commit HEAD` creates a preview for a pushed commit.
 
 For a concise command reference, see [CLI](./cli.md).
 

package/skills/dreamboard/references/testing.md

@@ -34,26 +34,20 @@ be edited manually.
 
 ## Command flow
 
-Generate reducer-native test artifacts:
-
-```bash
-dreamboard test generate
-```
-
 Run all scenarios:
 
 ```bash
-dreamboard test run
+dreamboard test
 ```
 
 Run one scenario:
 
 ```bash
-dreamboard test run --scenario test/scenarios/win-the-game.scenario.ts
+dreamboard test --scenario test/scenarios/win-the-game.scenario.ts
 ```
 
-Re-run `dreamboard test generate` after changes that affect the runtime shape of
-the game, including:
+`dreamboard test` regenerates reducer-native artifacts automatically when
+changes affect the runtime shape of the game, including:
 
 - `manifest.json`
 - reducer code under `app/`
@@ -111,7 +105,6 @@ Use `defineScenario(...)` from `test/testing-types.ts`.
 | `id` | Yes | Scenario identifier |
 | `description` | No | Short human-readable summary |
 | `from` | Yes | Base ID from `test/bases/*.base.ts` |
-| `runners` | No | Defaults to reducer runner |
 | `when` | Yes | Async action flow |
 | `then` | Yes | Assertions over state, view, and history |
 
@@ -232,7 +225,7 @@ then: ({ phase, history, expect, publicState }) => {
 
 If the generated test artifacts no longer match the compiled game, refresh them:
 
-- `dreamboard test generate`
+- `dreamboard test`
 
 Common symptoms:
 
@@ -244,6 +237,6 @@ Common symptoms:
 
 This page documents the scaffolded reducer-native test workspace.
 
-If you also use `dreamboard run` for manual debugging or operational inspection,
+If you also use `dreamboard dev` for manual debugging or operational inspection,
 treat that as a separate workflow. It is useful for ad hoc runtime exploration,
 but it is not the primary authored test surface for a new Dreamboard project.