@everfir/az8-cli 0.3.0-preview.3 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everfir/az8-cli",
-  "version": "0.3.0-preview.3",
+  "version": "0.3.0",
   "description": "Semantic Project Canvas client for AZ8 Studio agents.",
   "license": "UNLICENSED",
   "type": "module",
@@ -16,7 +16,7 @@
   "main": "./dist/main.js",
   "publishConfig": {
     "access": "public",
-    "tag": "preview"
+    "tag": "latest"
   },
   "scripts": {
     "build": "pnpm build:dependencies && rm -rf dist && esbuild src/main.ts --bundle --platform=node --format=esm --target=node22.12 --banner:js='import { createRequire } from \"node:module\"; const require = createRequire(import.meta.url);' --outfile=dist/main.js",

package/skills/az8-cli/SKILL.md

@@ -247,7 +247,8 @@ one-shot processes.
 2. Query `capabilities.detail` and validate the planned Operation input against its schema.
 3. When artifact type and placement are already clear, make the first meaningful Canvas state
    visible before doing lengthy prompt refinement or generation planning:
-   - create the empty generation target first, then plan and edit its Draft;
+   - create the generation target first, inspect whether its eligible default Draft was
+     initialized, then plan and edit;
    - create an empty manual Text Resource with `text: ""`, then fill it with
      `editTextContent`;
    - create a Note with its useful content directly rather than creating an empty sticky.
@@ -276,7 +277,9 @@ Generation is an explicit sequence, never one transaction:
 
 1. Create a target with `createGenerationTarget` and retain its View Node ID. It accepts `audio`,
    `image`, `text`, or `video`; `createMediaTarget` remains a compatibility capability for non-text
-   targets when advertised.
+   targets when advertised. The same creation interaction initializes an account-eligible default
+   Draft when one exists; inspect `draftInitialized`, `definitionId`, and `selectionSource`. This is
+   convenience state only: it does not start or estimate generation.
 2. Call the read-only `planGeneration` Operation with the target, prompt, and any references. Use
    `detail: "detail"` when configuration fields or dynamic enum options are needed.
    Every reference must be `{ "viewNodeId": "..." }`. If the desired Core Node is not currently
@@ -316,9 +319,11 @@ Generation is an explicit sequence, never one transaction:
    acknowledged. This completes the start interaction; it does not mean generation finished.
 6. Retain the Workflow Run ID. The Session automatically covers its terminal state through
    `system.workflow-terminal`; call one foreground `az8 session watch` whenever completion is the
-   next useful event. The terminal summary contains the Run, target View Node, and output Core Node
-   identities supplied by Workflow Runtime. Continue other work first when it does not require the
-   output, and use `getWorkflowRun` at a meaningful authoritative checkpoint.
+   next useful event. The terminal summary includes the target View Node only when the Session can
+   map it uniquely from authoritative launch or Canvas History facts. If `targetResolution` is
+   `unresolved` or `ambiguous`, query the Run and Canvas rather than guessing. Continue other work
+   first when it does not require the output, and use `getWorkflowRun` at a meaningful
+   authoritative checkpoint.
 7. Use `waitWorkflowRun` only when the next step actually requires terminal output and the current
    request lane can remain dedicated to waiting. Choose one intentional observation window; do not
    emulate polling with repeated short waits. An observation-window timeout while the authoritative
@@ -343,6 +348,13 @@ discovery, not an account-wide or historical Workflow event log.
 Workflow Definitions change over time. Query `workflowDefinitions.summary`, then
 `workflowDefinition.detail` only when planning detail is insufficient. Never guess a Definition,
 configuration option, modality, cost, or media compatibility from its display name.
+Summary discovery, defaults, planning, and start are filtered to Definitions available to the
+authenticated account. Detail may retain an unavailable historical Definition for diagnosis and
+marks it with `availableForAccount` and `accessReason`.
+
+Workflow tags classify compatibility, access, and rollout; they are not pricing evidence.
+`available:free` means a free-tier account may select that Workflow. It does not mean generation
+costs zero credits. Use planning/start estimates and terminal usage records for credit information.
 
 The start Receipt may report `usage.credits.status` as `estimated`, `not-consumed`, or `unknown`.
 Estimated cost is informational, not final charged usage. There is no second confirmation. Never