@wji.ai/cli 0.1.1 → 0.2.0

package/skill/wji/SKILL.md

@@ -83,6 +83,10 @@ wji ws use <workspaceId>
 After that, `wji ws get`, `wji fs`, `wji gen` and `wji preset list` all default
 to that workspace. Use `wji ws use` rather than repeating `--workspace`.
 
+`wji ws create <name>` seeds the default template — Dataset, DatasetImageGeneration and
+InfiniteCanvas — because the API creates no apps on its own; pass `-a` to choose apps or
+`--no-apps` for an empty workspace.
+
 ## Reading and editing the tree
 
 ```bash
@@ -95,12 +99,15 @@ wji fs get <nodeId> --json | jq .content
 wji fs mkdir <parentId> characters --nickname 角色
 wji dataset new <folderId> "Ada" -t character -d "a tired detective"
 wji fs describe <nodeId> @description.md
-wji fs set <nodeId> --images <assetId> <assetId>
+wji fs set <nodeId> --merge content=@body.md --merge viewMode=content   # merged into content
+wji fs set <nodeId> --add-images <assetId> <assetId>                    # appended
+wji fs set <nodeId> --images <assetId> <assetId>                        # replaced
 ```
 
-`wji fs set --content` **replaces** the whole content object. To change one
-field, read it first (`wji fs get <id> --json | jq .content`), merge, then
-write — or use `wji fs describe`, which merges `content.description` for you.
+`wji fs set --content` **replaces** the whole content object, and so does
+`--set content.x=…`. To change fields inside `content`, use `--merge key=value`
+(dotted keys, `@file` values) — it reads the node and deep-merges for you, like
+`wji fs describe` does for `content.description`.
 
 Several GET endpoints are cached server-side for 10 seconds, so a plain read
 immediately after a write can come back stale. `wji fs describe` and
@@ -242,11 +249,11 @@ a Ref model.
 
 ```bash
 wji fs get <datasetId> --scope full --json | jq '{images: [.images[]? | {id, type}], icon, primaryAudio}'
-wji fs set <datasetId> --images <headshot> <sheet> <voice> --icon <headshot> --set primaryAudio=<voice>
+wji fs set <datasetId> --add-images <headshot> <sheet> <voice> --icon <headshot> --set primaryAudio=<voice>
 ```
 
-`--images` replaces the whole list — read the current list first and keep
-what is already there.
+`--add-images` appends; `--images` replaces the whole list — use it only when
+the user wants the list rewritten, after reading what is there.
 
 ## Assets
 
@@ -302,12 +309,19 @@ use `skill push` for large files.
 
 ## Canvas
 
-An Infinite Canvas holds **nodes** (text, title, comment, image, video, audio…)
-and **edges** between them. An edge into a media node makes the source one of
-its **references**, numbered per kind in edge order: `@image1`, `@image2`,
-`@video1`. A media node is either a **display** node (shows an existing asset)
-or a **generate** node (prompt + model + settings; generating fills in its
-asset).
+An Infinite Canvas holds **nodes** (text, title, comment, image, video, audio,
+dataset…) and **edges** between them. An edge into a media node makes the
+source one of its **references**, numbered per kind in edge order: `@image1`,
+`@image2`, `@video1`. A media node is either a **display** node (shows an
+existing asset) or a **generate** node (prompt + model + settings; generating
+fills in its asset). A **dataset** node is a card bound to a workspace dataset
+(`canvas add dataset --dataset <fsnodeId>`) — good for showing a character
+or scene next to its sheets, but `canvas gen` cannot take it as a reference:
+reference the image display node that shows the asset instead.
+
+A workspace's InfiniteCanvas app can hold several canvases (`wji canvas list`);
+`wji canvas create <name>` adds an empty one — e.g. one canvas per episode or
+per character set.
 
 **The link.** The user opens a canvas in the browser and presses the link
 button in its top bar. That stores the open workspace, canvas and **the nodes
@@ -321,8 +335,11 @@ wji canvas nodes                      # every node; * marks generate nodes
 wji canvas get <nodeId>               # full detail incl. references
 wji asset download <assetId…> -o <dir>   # then look at the images yourself
 
+wji canvas create E01 -w <workspaceId>  # new empty canvas; then --canvas <id>
 wji canvas add video --from <imgNode> <imgNode> -m <model> -r 16:9 -d 8 -p "@image1 … @image2 …"
 wji canvas add text -t "shot list…" --at 0,600
+wji canvas add image --asset <assetId> -n "Ada sheet"     # display node for an existing asset
+wji canvas add dataset --dataset <fsnodeId>                # card bound to a workspace dataset
 wji canvas set <nodeId> -p "new prompt"        # merges: other settings stay
 wji canvas set <nodeId> -m <model> --resolution 720p --set seed=42
 wji canvas connect <from> <to>  /  wji canvas disconnect <from> <to>
@@ -412,8 +429,9 @@ wji org list && wji org use <orgId>
      anything you find afterwards — new targets need a new question.
 - **Overwrites don't prompt at all.** `fs set --content`, `--images` and
   `--tags`, and the update commands' tag options, replace the whole value.
-  Read the current value first, and check with the user before replacing
-  anything they did not ask to change.
+  Prefer the merging forms (`--merge`, `--add-images`, `fs describe`); when
+  you must replace, read the current value first and check with the user
+  before replacing anything they did not ask to change.
 - **Generation costs credits — one image just runs; video and batches ask
   first.** This is the user's standing policy. Follow it without asking them
   to restate it:

package/skill/wji/reference/commands.md

@@ -67,7 +67,7 @@ switch endpoint.
 | `ws list [-k keyword] [-s all\|me\|shared\|favorite] [--page] [--limit]` | `GET /workspace/search` — `--limit` max 100, `-1` returns at most 500 |
 | `ws get [id]` | `GET /workspace/list/:id` |
 | `ws use <id>` | stores the default workspace locally |
-| `ws create <name> [-d] [-r ratio] [-l lang] [-t type] [-a app...]` | `POST /workspace/create` |
+| `ws create <name> [-d] [-r ratio] [-l lang] [-t type] [-a app...] [--no-apps]` | `POST /workspace/create` — without `-a` the workspace gets the default template `dataset datasetimagegeneration canvas`; `--no-apps` creates it empty (the API itself adds nothing) |
 | `ws update [id] [-n] [-d] [-r] [-l] [--set]` | `PUT /workspace/list/:id` |
 | `ws rm <id> [-y]` | `DELETE /workspace/list/:id` (owner only) |
 | `ws favorite <id> [--off]` | `PUT /workspace/list/:id/favorite` |
@@ -99,7 +99,7 @@ Restriction from the backend: `Dataset`, `Draw`, `DatasetImageGeneration` and
 | `fs path <id>` | `GET /fsnode/list/:id/path` |
 | `fs mkdir <parent> <name> [--nickname] [--content]` | `POST /fsnode/create` type=folder |
 | `fs touch <parent> <name> [--mimetype] [--asset] [--content]` | `POST /fsnode/create` type=file |
-| `fs set <id> [-n] [--nickname] [--content] [--tags] [--images] [--icon] [--asset] [--sort] [--set]` | `PATCH /fsnode/list/:id` |
+| `fs set <id> [-n] [--nickname] [--content] [--tags] [--images] [--add-images] [--icon] [--asset] [--sort] [--set] [--merge]` | `PATCH /fsnode/list/:id` — `--merge key=value` deep-merges into `content` (reads first; `@file` values), `--add-images` appends to `images`; `--content`, `--images`, `--set content.*` replace |
 | `fs describe <id> <text>` | merges `content.description` |
 | `fs rm <id> [-y]` | `DELETE /fsnode/list/:id` (soft delete, whole subtree) |
 | `fs sort <parent> <ids...>` | `PATCH /fsnode/list/:id/children/sort` |
@@ -161,10 +161,11 @@ updates live.
 | `canvas status` (`link`) | `GET /canvas-link`, then the selected nodes read fresh from the canvas |
 | `canvas unlink` | `DELETE /canvas-link`; the tab turns its button off at its next heartbeat (≤ 60s) |
 | `canvas list [-w]` | canvases under each InfiniteCanvas app: `GET /workspace/list/:id/fs/:appId` → `workspace-v2/canvases` children |
+| `canvas create <name> [-w] [--app]` | `POST /fsnode/create` a `workspace-v2/canvas` folder under that `canvases` folder with the web's initial content (`{data:{viewport, backgroundMode:'dots'}, metadata:{}}`) |
 | `canvas nodes [-c] [-k kind]` | `GET /fsnode/list/:canvasId/children?limit=-1` + `POST /assets/check-status` |
 | `canvas get <nodeId> [-c]` | same load; one node with references (`@image1 ← id`) and frame slots |
 | `canvas edges [-c] [--node]` | the `canvas/edge` children |
-| `canvas add <kind> [-c] [-n] [-t\|--text-file] [--asset] [-p\|--prompt-file] [-m] [-r] [--resolution] [-d] [--set] [--from ids…] [--at x,y]` | `POST /fsnode/create` (`canvas/node/<kind>`), then one `canvas/edge` per `--from`. Kinds: text, title, comment, image, video, audio |
+| `canvas add <kind> [-c] [-n] [-t\|--text-file] [--asset] [--dataset] [-p\|--prompt-file] [-m] [-r] [--resolution] [-d] [--set] [--from ids…] [--at x,y]` | `POST /fsnode/create` (`canvas/node/<kind>`), then one `canvas/edge` per `--from`. Kinds: text, title, comment, image, video, audio, dataset. `add dataset --dataset <fsnodeId>` writes `content {datasetId, datasetName, datasetType, datasetParentName, description}` from the dataset node (must be `workspace/dataset`); it takes no `--from` |
 | `canvas set <nodeId> [-c] [-n] [-t] [--move x,y] [-p] [-m] [-r] [--resolution] [-d] [--set]` | read → merge → `PATCH /fsnode/list/:id` |
 | `canvas connect <from> <to> [-c]` | `POST /fsnode/create` (`canvas/edge`); a first/last-frame video model gets `videoFrameSlot` start, then end |
 | `canvas disconnect <from> <to> [-c]` | `DELETE /fsnode/list/:edgeId` |