@pix3/cli 1.6.0 → 1.6.2

package/templates/idea-blank/files/scenes/main.pix3scene

@@ -1,37 +1,37 @@
-# Pix3 Scene File (YAML)
-# Idea-stage placeholder scene: a Full HD canvas with nothing on it but a background.
-# Deliberately bare — the idea stage mounts no runtime, and the recipe that will fill this
-# project in is not chosen until "Start prototype". The canonical `game-root` id is kept so
-# routines and assertions written against it keep working after the recipe is applied.
-version: 1.0.0
-metadata:
-  author: Pix3 Template
-  description: Empty canvas for a project still at the idea stage
-root:
-  - id: game-root
-    type: Group2D
-    name: Game Root
-    properties:
-      width: 1920
-      height: 1080
-      layout:
-        enabled: true
-        horizontalAlign: stretch
-        verticalAlign: stretch
-    children:
-      - id: background
-        type: ColorRect2D
-        name: Background
-        properties:
-          width: 1920
-          height: 1080
-          color: "#1a1a2e"
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: stretch
-            verticalAlign: stretch
-        children: []
+# Pix3 Scene File (YAML)
+# Idea-stage placeholder scene: a Full HD canvas with nothing on it but a background.
+# Deliberately bare — the idea stage mounts no runtime, and the recipe that will fill this
+# project in is not chosen until "Start prototype". The canonical `game-root` id is kept so
+# routines and assertions written against it keep working after the recipe is applied.
+version: 1.0.0
+metadata:
+  author: Pix3 Template
+  description: Empty canvas for a project still at the idea stage
+root:
+  - id: game-root
+    type: Group2D
+    name: Game Root
+    properties:
+      width: 1920
+      height: 1080
+      layout:
+        enabled: true
+        horizontalAlign: stretch
+        verticalAlign: stretch
+    children:
+      - id: background
+        type: ColorRect2D
+        name: Background
+        properties:
+          width: 1920
+          height: 1080
+          color: "#1a1a2e"
+          transform:
+            position: [0, 0]
+            scale: [1, 1]
+            rotation: 0
+          layout:
+            enabled: true
+            horizontalAlign: stretch
+            verticalAlign: stretch
+        children: []

package/templates/idea-blank/template.yaml

@@ -1,10 +1,10 @@
-id: idea-blank
-title: Idea (blank)
-description: Starting point for the Flow idea stage — one empty Full HD 2D canvas, no game. The recipe is chosen later, when the idea becomes a prototype.
-projectType: 2d
-targetPlatform: universal
-viewport: { width: 1920, height: 1080 }
-# Last in every ordering, and hidden from the pickers: this template is reached only through the
-# idea-stage bootstrap, never chosen by a user or by the recipe resolver.
-order: 99
-hidden: true
+id: idea-blank
+title: Idea (blank)
+description: Starting point for the Flow idea stage — one empty Full HD 2D canvas, no game. The recipe is chosen later, when the idea becomes a prototype.
+projectType: 2d
+targetPlatform: universal
+viewport: { width: 1920, height: 1080 }
+# Last in every ordering, and hidden from the pickers: this template is reached only through the
+# idea-stage bootstrap, never chosen by a user or by the recipe resolver.
+order: 99
+hidden: true

package/templates/minigame-2d/files/README.md

@@ -1,44 +1,44 @@
-# {{PROJECT_NAME}}
-
-A Pix3 project created from the **Minigame 2D** template.
-
-## Scenes and the flow
-
-The menu and the game are **separate scenes**, so you can play the game on its own
-while iterating and still ship the full menu → game flow in a build:
-
-- **Game scene** (`scenes/main.pix3scene`) — the gameplay. This is the
-  editor's startup scene: it opens first and is what you (and agents) play directly,
-  with no menu in the way. Build your minigame here. Driven by `scripts/GameFlow.ts`
-  (its MENU button transitions back to the menu; extend it with your win/lose flow).
-- **Menu scene** (`scenes/menu.pix3scene`) — title, PLAY and SETTINGS
-  buttons. This is the project's **entry scene** (Project Settings → Default Export
-  Scene Path): a build and *Start Game* boot here so you can debug the whole flow.
-  Driven by `scripts/MenuFlow.ts`: PLAY transitions to the game scene, SETTINGS
-  opens the settings window.
-- **Settings window** (`scenes/ui/settings-window.pix3scene`) — the modal,
-  in its own file so the menu opens clean. The menu carries it as a one-line
-  `instance: res://scenes/ui/settings-window.pix3scene` marked `visible: false`
-  (an editor-only hide; `MenuFlow` shows it at run time). Music/SFX checkboxes
-  mute the engine audio buses, wired by `scripts/SettingsWindow.ts`. Reuse it
-  from any scene the same way.
-
-Scenes switch at runtime with a fade transition:
-`this.scene.changeScene('res://scenes/main.pix3scene', { transition: 'fade' })`.
-
-## Project structure
-
-- `design/` — game design document and reference images
-- `design/tests/` — agent-testing material: `routines/*.json` (named, replayable
-  step + assertion scripts) and `reachability.json` (the journal of on-screen
-  controls physically proven reachable). Routines are executed by the gameplay
-  test harness, which is still in development — the format and location are
-  fixed now so a routine written today keeps working.
-- `scenes/` — scene files; `main.pix3scene` (game) is the startup scene,
-  `menu.pix3scene` is the build entry point
-- `scenes/ui/` — full-screen / modal overlays (`settings-window.pix3scene`),
-  instanced into host scenes with `visible: false`
-- `sprites/` — images and textures
-- `scripts/` — game scripts (`export class X extends Script`, used as `user:X`)
-- `audio/` — music and sound effects
-- `AGENTS.md` — rules and pointers for AI agents working on this project
+# {{PROJECT_NAME}}
+
+A Pix3 project created from the **Minigame 2D** template.
+
+## Scenes and the flow
+
+The menu and the game are **separate scenes**, so you can play the game on its own
+while iterating and still ship the full menu → game flow in a build:
+
+- **Game scene** (`scenes/main.pix3scene`) — the gameplay. This is the
+  editor's startup scene: it opens first and is what you (and agents) play directly,
+  with no menu in the way. Build your minigame here. Driven by `scripts/GameFlow.ts`
+  (its MENU button transitions back to the menu; extend it with your win/lose flow).
+- **Menu scene** (`scenes/menu.pix3scene`) — title, PLAY and SETTINGS
+  buttons. This is the project's **entry scene** (Project Settings → Default Export
+  Scene Path): a build and *Start Game* boot here so you can debug the whole flow.
+  Driven by `scripts/MenuFlow.ts`: PLAY transitions to the game scene, SETTINGS
+  opens the settings window.
+- **Settings window** (`scenes/ui/settings-window.pix3scene`) — the modal,
+  in its own file so the menu opens clean. The menu carries it as a one-line
+  `instance: res://scenes/ui/settings-window.pix3scene` marked `visible: false`
+  (an editor-only hide; `MenuFlow` shows it at run time). Music/SFX checkboxes
+  mute the engine audio buses, wired by `scripts/SettingsWindow.ts`. Reuse it
+  from any scene the same way.
+
+Scenes switch at runtime with a fade transition:
+`this.scene.changeScene('res://scenes/main.pix3scene', { transition: 'fade' })`.
+
+## Project structure
+
+- `design/` — game design document and reference images
+- `design/tests/` — agent-testing material: `routines/*.json` (named, replayable
+  step + assertion scripts) and `reachability.json` (the journal of on-screen
+  controls physically proven reachable). Routines are executed by the gameplay
+  test harness, which is still in development — the format and location are
+  fixed now so a routine written today keeps working.
+- `scenes/` — scene files; `main.pix3scene` (game) is the startup scene,
+  `menu.pix3scene` is the build entry point
+- `scenes/ui/` — full-screen / modal overlays (`settings-window.pix3scene`),
+  instanced into host scenes with `visible: false`
+- `sprites/` — images and textures
+- `scripts/` — game scripts (`export class X extends Script`, used as `user:X`)
+- `audio/` — music and sound effects
+- `AGENTS.md` — rules and pointers for AI agents working on this project

package/templates/minigame-2d/files/design/tests/reachability.json

@@ -1 +1 @@
-{ "version": 1, "proven": [] }
+{ "version": 1, "proven": [] }

package/templates/minigame-2d/files/design/tests/routines/mute-music.json

@@ -1,44 +1,44 @@
-{
-  "name": "mute-music",
-  "description": "From the menu: open the settings window, switch music off, close it again.",
-  "note": "Run it with game_run {routine:'mute-music'}. Steps are the game_input vocabulary plus {type:'command'} for a registered intent; `expect` holds the ordinary game_run predicates, ANDed and judged once after the last step. Only a STEP takes a `why` — an assertion is exactly the predicate object game_run takes, with no extra fields. The `toggled` expectation is the load-bearing one here: the box ships checked, so \"it is off now\" would also be true of a box nothing ever reached, while `toggled` fires only on a real state change and cannot be satisfied by a tap that bounced off a disabled control.",
-  "scope": "scenes/menu.pix3scene",
-  "params": {},
-  "uses": ["menu-root", "settings-button", "settings-window", "music-toggle", "close-button"],
-  "steps": [
-    {
-      "type": "command",
-      "name": "open-settings",
-      "why": "The highest channel available: the SETTINGS button dispatches this intent, so the routine keeps working after any relayout of the menu — and the dispatch is journalled with the frame it happened on."
-    },
-    {
-      "type": "invoke",
-      "target": "music-toggle",
-      "interaction": "setChecked",
-      "args": { "checked": false },
-      "why": "The scene's `settings.toggle-music` command FLIPS the box, so it cannot express \"off\" from an unknown state; setChecked can. It still goes through the control's own funnel, so the checkmark, the audio bus and the `toggled` signal all land exactly as they would on a tap."
-    },
-    {
-      "type": "command",
-      "name": "close-settings",
-      "why": "The CLOSE button's intent — same reason as opening."
-    }
-  ],
-  "expect": [
-    { "kind": "signal", "name": "toggled", "node": "music-toggle" },
-    {
-      "kind": "nodeProperty",
-      "name": "music-toggle",
-      "path": "checked",
-      "op": "eq",
-      "value": false
-    },
-    {
-      "kind": "nodeProperty",
-      "name": "settings-window",
-      "path": "visible",
-      "op": "eq",
-      "value": false
-    }
-  ]
-}
+{
+  "name": "mute-music",
+  "description": "From the menu: open the settings window, switch music off, close it again.",
+  "note": "Run it with game_run {routine:'mute-music'}. Steps are the game_input vocabulary plus {type:'command'} for a registered intent; `expect` holds the ordinary game_run predicates, ANDed and judged once after the last step. Only a STEP takes a `why` — an assertion is exactly the predicate object game_run takes, with no extra fields. The `toggled` expectation is the load-bearing one here: the box ships checked, so \"it is off now\" would also be true of a box nothing ever reached, while `toggled` fires only on a real state change and cannot be satisfied by a tap that bounced off a disabled control.",
+  "scope": "scenes/menu.pix3scene",
+  "params": {},
+  "uses": ["menu-root", "settings-button", "settings-window", "music-toggle", "close-button"],
+  "steps": [
+    {
+      "type": "command",
+      "name": "open-settings",
+      "why": "The highest channel available: the SETTINGS button dispatches this intent, so the routine keeps working after any relayout of the menu — and the dispatch is journalled with the frame it happened on."
+    },
+    {
+      "type": "invoke",
+      "target": "music-toggle",
+      "interaction": "setChecked",
+      "args": { "checked": false },
+      "why": "The scene's `settings.toggle-music` command FLIPS the box, so it cannot express \"off\" from an unknown state; setChecked can. It still goes through the control's own funnel, so the checkmark, the audio bus and the `toggled` signal all land exactly as they would on a tap."
+    },
+    {
+      "type": "command",
+      "name": "close-settings",
+      "why": "The CLOSE button's intent — same reason as opening."
+    }
+  ],
+  "expect": [
+    { "kind": "signal", "name": "toggled", "node": "music-toggle" },
+    {
+      "kind": "nodeProperty",
+      "name": "music-toggle",
+      "path": "checked",
+      "op": "eq",
+      "value": false
+    },
+    {
+      "kind": "nodeProperty",
+      "name": "settings-window",
+      "path": "visible",
+      "op": "eq",
+      "value": false
+    }
+  ]
+}

package/templates/minigame-2d/files/scenes/main.pix3scene

@@ -1,84 +1,84 @@
-# Pix3 Scene File (YAML)
-# Minigame 2D — the GAME scene. `main.pix3scene` is the editor's startup scene:
-# the one you iterate on and that agents open and play directly (no menu in the
-# way). A full build instead boots the MENU scene (see menu.pix3scene / Project
-# Settings → Default Export Scene Path); the menu's PLAY button transitions here.
-# The MENU button returns to the menu via a scene transition (scripts/GameFlow.ts).
-version: 1.0.0
-metadata:
-  author: Pix3 Template
-  description: Gameplay scene — build your minigame here
-root:
-  - id: game-root
-    type: Group2D
-    name: Game Root
-    properties:
-      width: 1920
-      height: 1080
-      layout:
-        enabled: true
-        horizontalAlign: stretch
-        verticalAlign: stretch
-    components:
-      - id: game-flow
-        type: user:GameFlow
-        enabled: true
-        config:
-          menuScene: res://scenes/menu.pix3scene
-          menuButton: menu-button
-    children:
-      - id: game-background
-        type: ColorRect2D
-        name: Game Background
-        properties:
-          width: 1920
-          height: 1080
-          color: "#0f3460"
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: stretch
-            verticalAlign: stretch
-        children: []
-      - id: game-placeholder
-        type: Label2D
-        name: Game Placeholder
-        properties:
-          label: "YOUR GAME GOES HERE"
-          labelFontSize: 64
-          labelColor: "#ffffff"
-          labelAlign: center
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: center
-        children: []
-      - id: menu-button
-        type: Button2D
-        name: Menu Button
-        properties:
-          width: 220
-          height: 80
-          label: "MENU"
-          labelFontSize: 32
-          labelColor: "#ffffff"
-          backgroundColor: "#3a3a5e"
-          hoverColor: "#4a4a6e"
-          pressedColor: "#2a2a4e"
-          buttonAction: back-to-menu
-          transform:
-            position: [-820, 460]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: left
-            verticalAlign: top
-        children: []
+# Pix3 Scene File (YAML)
+# Minigame 2D — the GAME scene. `main.pix3scene` is the editor's startup scene:
+# the one you iterate on and that agents open and play directly (no menu in the
+# way). A full build instead boots the MENU scene (see menu.pix3scene / Project
+# Settings → Default Export Scene Path); the menu's PLAY button transitions here.
+# The MENU button returns to the menu via a scene transition (scripts/GameFlow.ts).
+version: 1.0.0
+metadata:
+  author: Pix3 Template
+  description: Gameplay scene — build your minigame here
+root:
+  - id: game-root
+    type: Group2D
+    name: Game Root
+    properties:
+      width: 1920
+      height: 1080
+      layout:
+        enabled: true
+        horizontalAlign: stretch
+        verticalAlign: stretch
+    components:
+      - id: game-flow
+        type: user:GameFlow
+        enabled: true
+        config:
+          menuScene: res://scenes/menu.pix3scene
+          menuButton: menu-button
+    children:
+      - id: game-background
+        type: ColorRect2D
+        name: Game Background
+        properties:
+          width: 1920
+          height: 1080
+          color: "#0f3460"
+          transform:
+            position: [0, 0]
+            scale: [1, 1]
+            rotation: 0
+          layout:
+            enabled: true
+            horizontalAlign: stretch
+            verticalAlign: stretch
+        children: []
+      - id: game-placeholder
+        type: Label2D
+        name: Game Placeholder
+        properties:
+          label: "YOUR GAME GOES HERE"
+          labelFontSize: 64
+          labelColor: "#ffffff"
+          labelAlign: center
+          transform:
+            position: [0, 0]
+            scale: [1, 1]
+            rotation: 0
+          layout:
+            enabled: true
+            horizontalAlign: center
+            verticalAlign: center
+        children: []
+      - id: menu-button
+        type: Button2D
+        name: Menu Button
+        properties:
+          width: 220
+          height: 80
+          label: "MENU"
+          labelFontSize: 32
+          labelColor: "#ffffff"
+          backgroundColor: "#3a3a5e"
+          hoverColor: "#4a4a6e"
+          pressedColor: "#2a2a4e"
+          buttonAction: back-to-menu
+          transform:
+            position: [-820, 460]
+            scale: [1, 1]
+            rotation: 0
+          layout:
+            enabled: true
+            horizontalAlign: left
+            verticalAlign: top
+        children: []