octwin-cli 0.8.13 → 0.8.15

package/CHANGELOG.md

@@ -7,6 +7,58 @@ repo root [`CHANGELOG.md`](../../CHANGELOG.md); this file is the CLI-only cut th
 
 ## [Unreleased]
 
+## [0.8.15] - 2026-10-06
+
+### Fixed
+- **`octwin records` said nothing useful for a pack with no record types of its own.** Its message read
+  `has_xrm`, which the platform never sent, so it could not show. The platform sends it now; the CLI
+  says the pack declares no record types and that platform records still read by name
+  (`octwin records order | product | case`). `records create` and `records tasks` read `has_data` —
+  "no AI Agent is loaded in this project" — instead of the same unsent field.
+
+## [0.8.14] - 2026-10-06
+
+### Added
+- **`octwin seed --reset`** — archive every row the pack's demo loaded, then load it again. Needed
+  once for demo rows seeded before 2026-10-05 (the seed says so), and a clean slate on demand; records
+  a customer made are never touched.
+- **`octwin records <entity> --search "<words>"`** — the entity's ranked search (fuzzy, plus semantic
+  when the entity declares it), best match first, each row printed with its score. The platform has
+  served it to the console for months; the CLI never asked. `--json` returns the rows with their scores.
+- **`press:<label>` in `octwin chat --script`, and `--press <label>`.** Taps the button of the reply just
+  received by its label — exactly, or the same words without emoji or case, or the one label containing
+  them. A form or checkout button's tap id carries its run id (`t:resume:…:run_id=…`), which exists only
+  once the reply arrives, so a script could not get past the first form step: `tap:` needs an id nobody
+  can write in advance. No match, or several buttons, stops the script and lists the buttons. A lone
+  `--press` picks from the reply the conversation is waiting on. The rules are the AI Author's `press`,
+  byte for byte (`src/lib/press.ts`). An older CLI sends a `press:` line as a typed message.
+
+### Fixed
+- **`octwin chat` prints a card's link buttons and its forms.** A button that opens a link prints as
+  `[link] title → url` (a card may now carry links beside its reply buttons), and a form prints as
+  `[flow form] …` — it compared the hint type `'flow'`, which the wire never sends (`form_flow`).
+- **`--json` output always parses.** `records --json` and `projects create --json` printed a
+  `→ Reading …` line in front of their JSON, and `logs --json` with no conversations printed a sentence
+  and no JSON at all (reported 2026-10-01). Under `--json`, stdout now carries the result and nothing
+  else — progress, tables and hints go to stderr — and every write verb of a JSON command (`records
+  create`, `work note`, `agents set`, `catalog stock`, `scheduling rule add`, `projects rm --yes`, …)
+  returns what the platform answered. A test runs every JSON command and parses its stdout.
+- **`octwin chat` prints the pictures, files, voice notes and map pins a reply carries.** Only a reply's
+  text and buttons were printed, so a reply that sent a picture read as a caption with nothing under it.
+  Now `[image] <path>` (without the signed query), `[file] <name> → <url>`, `[voice note] 12s → <url>`,
+  `[location] <name> (lat, long)`, and `(image)` on a carousel card that has a picture
+  (`src/lib/media-lines.ts`).
+
+### Changed
+- **`--json` on a command that has no JSON output is refused by name** (`whoami`, `deploy`, `validate`,
+  …), with the list of commands that have it. It used to print the prose to stderr and leave stdout
+  empty. `chat --json` and `login --json` print one JSON object per line, as before.
+- **Under `--json`, the progress lines move from stdout to stderr.** A script that read them from stdout
+  reads them from stderr now; human output (no `--json`) is unchanged.
+- **`octwin pull` can pull an Octwin (first-party) pack.** The platform now lets a workspace read the
+  source of its own packs and of Octwin's — never another workspace's — and the 403 hint says so. A
+  platform change: an older CLI pulls first-party packs too, it only prints the older hint.
+
 ## [0.8.13] - 2026-09-27
 
 ### Added

package/README.md

@@ -62,6 +62,11 @@ octwin status               # "✓ live and current" once it's warm
 
 ## Commands
 
+**`--json` puts the result on stdout and nothing else.** Progress lines, tables and hints go to stderr,
+so `octwin records lead --json | jq` always parses. A command that prints a stream (`chat`, `login`)
+writes one JSON object per line. `--json` on a command with no JSON output (`deploy`, `whoami`, …) is
+refused by name rather than leaving stdout empty.
+
 | Command | What it does |
 | --- | --- |
 | `octwin init <dir>` | Scaffold a new pure-YAML pack into `<dir>` (writes a starter `manifest.yaml`, flow, prompt, `.gitignore` and `README.md` — pack content only). Options: `--id`, `--description`, `--display-name`. |
@@ -73,7 +78,7 @@ octwin status               # "✓ live and current" once it's warm
 | `octwin pull <packId>` | Write a **deployed** pack's source back to disk — the inverse of `deploy`, and how a pack pushed from one machine is recovered. Defaults to the version installed on the target project; `--version` overrides, `--dir` defaults to `./<packId>`, a non-empty dir needs `--force`. You may pull a pack your tenant **owns**. |
 | `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. Each reply line says who sent it: plain `← …` is the AI Agent, `← [notify] …` a reminder or notification (never taken for the turn's reply), `← [operator: Name] …` a person in Live chat, `← [platform] …` a handoff line. |
 | `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. Writes (`records:write`): `create`, `patch`, `stage`, `note`, and `archive <id>` / `restore <id>` — there is no delete; archive takes a record (test data too) out of every list and count, and restore brings it back. |
+| `octwin records` | Inspect the pack's XRM data (needs a `records:read` token). No args = list entities. `<entity> --search "<words>"` runs the entity's ranked search (it must declare `search:`) and prints each match's score. Writes (`records:write`): `create`, `patch`, `stage`, `note`, and `archive <id>` / `restore <id>` — there is no delete; archive takes a record (test data too) out of every list and count, and restore brings it back. |
 | `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`. |