@garaje/base 0.1.3 → 0.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@garaje/base",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "license": "MIT",
   "repository": {
     "type": "git",

package/rules/00-workspace.md

@@ -3,7 +3,7 @@
 - The repo root is `/workspace`, bind-mounted from the host. Edits here are
   immediately visible on the host and in sibling containers.
 - This is a **garaje**: it parks codebases into `bays/<name>/` and runs them.
-  Parked code is materialized by `bin/garaje sync` from `garaje.yaml`; each bay
+  Parked code is materialized by `garaje sync` from `garaje.yaml`; each bay
   is its own git checkout, gitignored from this repo.
 - A bay's `recipe.yaml` declares how it runs (toolchain, app processes,
   backing services, env, secrets). `garaje park` turns recipes into the
@@ -16,7 +16,7 @@
 - `packages/` holds the garaje **framework** being extracted from this repo:
   `packages/cli` (the TypeScript `garaje` CLI) and `packages/base` (the
   `@garaje/base` pi package), as npm workspaces. The recipe→compose codegen now
-  lives here; `bin/garaje park` runs it.
+  lives here; `garaje park` runs it.
 - `scratch/` is a host-shared dropbox for screenshots, logs, and paste-ins.
   Use it for ephemeral artifacts; it is gitignored.
 - `sessions/` holds pi session transcripts, bind-mounted from the host and

package/skills/park/SKILL.md

@@ -29,6 +29,10 @@ If the bay isn't in `garaje.yaml` yet, add it under `bays:`:
     ref: main
 ```
 
+A fresh manifest reads `bays: []`. That is an empty *flow* sequence — list
+items cannot be appended beneath it. Replace it with a bare `bays:` first, or
+`garaje sync` will reject the file as malformed YAML.
+
 Then materialize it (git credentials are already forwarded in-container):
 
 ```bash