octwin-cli 0.8.0 → 0.8.3

package/README.md

@@ -73,7 +73,7 @@ octwin status               # "✓ live and current" once it's warm
 | `octwin chat "msg"` | Drive a turn through the dev web channel and print **every render with its tap ids**. `--as <handle>` picks the test user; `--tap "<tap-id>"` presses a rendered button/list row; `--json` dumps the raw envelopes. |
 | `octwin logs` | List recent conversations (handle, status, last activity; `--as` filters), or show one conversation's full event timeline — including what each turn rendered. `--json` for raw payloads. |
 | `octwin records` | Inspect the pack's XRM data (needs a `records:read` token). No args = list entities. |
-| `octwin cases` | Inspect casework (support tickets): the inbox, one case + its timeline and decisions, or `--queues` for queue keys + open counts. |
+| `octwin work` | The work inbox: worked records across queues, one item + its timeline and decisions, or `--queues` for queue keys + open counts. Casework is one shape of it — the command spans every entity a pack works. |
 | `octwin projects` | The `--project <slug>` values this token can name, with the plan's project cap. `--archived` includes archived ones. A `pack:deploy` token reaches it — it names a project in every other command, so this turns "guess the slug" into "read the list". |
 | `octwin agents` | The agent roster with each agent's **effective** model / history window and **which layer set it** (project override → platform default → pack manifest) — an operator platform default can override what your manifest declares. `--prompt` prints the exact system prompt the LLM sees. Needs `agents:read`. |
 | `octwin orders` | The orders a conversation produced. No args = the list; with a `reference_id` = line items, the subtotal/tax/shipping/discount/total breakdown, `payment_ref`, and the allowed transitions. Needs `orders:read` + the `orders` plan feature. |
@@ -93,14 +93,14 @@ octwin status               # "✓ live and current" once it's warm
 
 ### Writing, not just reading
 
-Every read command above has a write half behind a **leading verb**, so `octwin cases` reads and
-`octwin cases note <id> "…"` writes. Each needs the matching `:write` scope — `octwin <cmd> --help`
+Every read command above has a write half behind a **leading verb**, so `octwin work` reads and
+`octwin work note <id> "…"` writes. Each needs the matching `:write` scope — `octwin <cmd> --help`
 lists the verbs and their exact flags.
 
 | Command | Verbs |
 | --- | --- |
 | `octwin records` | `create <entity> --set k=v` · `patch <id> --entity <e>` · `stage <id> --to <s>` · `note <id> "…"` · `tasks` · `task complete <id>` |
-| `octwin cases` | `assign <id> --to user:<uuid>\|none` · `note` · `transition <id> --to <status>` · `decide <id> --action <a> [--dry-run]` |
+| `octwin work` | `assign <id> --to user:<uuid>\|none` · `note` · `transition <id> --to <status>` · `decide <id> --action <a> [--dry-run]` |
 | `octwin orders` | `transition <ref> --to <status>` · `refund <ref> --force` |
 | `octwin catalog` | `availability <sku> --to "in stock"` · `stock <sku> [--set-on-hand n]` |
 | `octwin scheduling` | `rules --resource <id>` · `rule add\|rm` · `exception add\|rm` |