octwin-cli 0.1.13 → 0.1.15

package/CHANGELOG.md

@@ -5,6 +5,64 @@ Format: [Keep a Changelog](https://keepachangelog.com/) — newest first, bucket
 **Added · Changed · Deprecated · Removed · Fixed · Security**. The platform-wide view lives in the
 repo root [`CHANGELOG.md`](../../CHANGELOG.md); this file is the CLI-only cut that ships with the package.
 
+## [0.1.15] - 2026-07-25
+
+### Added
+- **`octwin agents [packId::agentId] [--prompt]` — see what your agent actually runs as.** The platform
+  gained *governed* agent settings: an operator platform default can override the `default_model`
+  (and history window / working-memory toggle) your manifest declares, and that override is invisible
+  from the pack source. The command prints each governed setting's **effective** value, **which layer
+  won** (project override → platform default → pack manifest), and warns explicitly when your pack's
+  declared value is *not* in force. `--prompt` prints the exact system prompt the LLM sees for this
+  project (pack instructions + platform protocol + any project overlay).
+- **`octwin orders [reference_id]` — the commerce a conversation produced.** The list (number,
+  status/payment, total, contact) or one order with its line items, the
+  subtotal/tax/shipping/discount/total breakdown, `payment_ref`, and the allowed transitions. On a
+  `pending`/`none` payment it explains *why that's expected*: the forward payment lifecycle is
+  **webhook-owned** (not patchable), and the default gateway-less `manual` driver makes
+  `payment_request` take its `empty` port — so the flow should confirm pay-on-delivery, not error.
+- **`octwin analytics [entity]` — stage conversion for any pipelined entity.** The funnel engine that
+  powered journeys is now generic, so any entity declared with a `pipeline:` charts conversion +
+  drop-off (`--overview` / `--milestones` / `--trends` / `--cost`, and `--stage <id>` for the records
+  currently at a stage). An empty result names **both** causes the platform folds into one response —
+  no `pipeline:`, or no `view` grant on `record.<entity>`.
+- **`octwin catalog [--readiness]`** — commerce products with price, availability and stock
+  (`untracked` when the SKU isn't inventory-tracked), plus the WhatsApp catalog binding.
+  `--readiness` runs the Meta Graph checklist with each failing item's suggested fix.
+- **`octwin scheduling [--slots <resourceRecordId>]`** — the engine state (bookable resource types,
+  upcoming slots, booked seats) or the computed slots for one resource. This is how you verify the
+  availability rules a `deploy --seed` created, which 0.1.14 could create but not read back.
+
+### Changed
+- **Auth failures now name the scope the command needs.** Every 401/403 appends the required scope
+  (and the plan feature, where the route is entitlement-gated) from one client-side mirror of the
+  platform's scope registry — replacing the per-command hardcoded strings, several of which named no
+  scope at all. It also spells out that `pack:deploy` / `media:generate` are direct-grant only, so a
+  `tenant:admin` preset token does **not** confer them (the most common "but my token is admin" dead end).
+
+## [0.1.14] - 2026-07-23
+
+### Fixed
+- **A failed demo seed no longer reports a clean `✓`.** `deploy` softens non-fatal
+  install steps (e.g. a demo-seed row) to warning frames, but the summary still printed
+  `✓ Deployed` and exited 0 — so a deploy that seeded ZERO records read as success (the
+  false-✓ trap). `deploy` now collects those step errors, prints `⚠ Deployed with N
+  warning(s) — data may be incomplete` with each message, and exits non-zero so CI /
+  a `deploy && chat` chain catches it.
+
+### Added
+- **`login` echoes what the token reaches.** After saving, `octwin login` calls
+  `/api/self/t/whoami` and prints the workspace, project pin, and scopes — so a fresh
+  token self-identifies without a second `octwin whoami` (best-effort; a network failure
+  never fails the save).
+- **`validate --remote` surfaces warnings + the data-store trap.** The remote validate now
+  renders advisory `⚠` warnings (which don't block deploy) and, for a pack declaring
+  `required_adapters: [data-store]`, reports the missing-data-store error the deploy would
+  have 409'd on — plus a warning that an `xrm.yaml` pack usually shouldn't declare that
+  adapter at all. It also now catches (offline) a list-form `entities:` block and a
+  `localized: true` field seeded with a bare string — traps that previously surfaced only
+  mid-seed at deploy.
+
 ## [0.1.13] - 2026-07-22
 
 ### Added

package/README.md

@@ -70,6 +70,11 @@ octwin status               # "✓ live and current" once it's warm
 | `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 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. |
+| `octwin analytics` | Stage-by-stage conversion for **any** entity declared with a `pipeline:` (`--overview` / `--milestones` / `--trends` / `--cost`; `--stage <id>` lists the records currently at a stage). Needs `records:read`. |
+| `octwin catalog` | Commerce products with price / availability / stock, plus the WhatsApp catalog binding. `--readiness` runs the Meta Graph checklist. Needs `catalog:read` + the `catalog` plan feature. |
+| `octwin scheduling` | The scheduling engine's state, or `--slots <resourceRecordId>` for the slots one bookable resource actually computes — how you verify the availability rules `deploy --seed` created. Needs `scheduling:read`. |
 | `octwin platform-kb pull` | Pull the platform's capability reference (built-ins, primitives, render intents, flow-DSL — as markdown + JSON) into `.octwin/platform-kb/`, for the **`octwin-pack`** Claude Code authoring plugin to consult. |
 | `octwin test` | Alias for `octwin validate --remote` — the platform's full manifest + flow-DSL check. |
 | `octwin help` | Show usage. Every subcommand also answers `--help`. |
@@ -90,6 +95,30 @@ octwin logs --as tester1                      # find the conversation, then:
 octwin logs <conversationId>                  # the full timeline (taps, renders, tool events)
 ```
 
+### Reading back the state your pack created
+
+`chat`/`logs` show what the bot *said*; these show what it *did*. A 401/403 on any of them names the
+token scope (and plan feature) that command needs, so you can mint a wider token instead of guessing.
+
+```bash
+octwin agents                                 # effective model per agent + which layer set it
+octwin agents my-pack::assistant --prompt     # the exact system prompt the LLM sees
+octwin orders                                 # then: octwin orders <reference_id>
+octwin analytics                              # then: octwin analytics <entity> [--stage <id>]
+octwin catalog                                # products + stock + the WhatsApp binding
+octwin scheduling --slots <resourceRecordId>  # the slots your availability rules compute
+```
+
+Three things worth knowing when you read the output:
+
+- **A `pending` payment is usually correct.** The forward payment lifecycle is **webhook-owned**, and a
+  workspace with no gateway runs the credential-free `manual` driver — so `payment_request` takes its
+  `empty` port and your flow should confirm pay-on-delivery. `octwin orders <ref>` says this inline.
+- **Your declared model may not be the one running.** An operator platform default overrides the pack
+  manifest; `octwin agents` is where that becomes visible.
+- **An empty funnel has two causes** — the entity has no `pipeline:`, or your token's role has no `view`
+  grant on `record.<entity>`. The command prints both rather than a bare "no data".
+
 ## Configuration
 
 The deploy target has four settings. Three live in a committed **`pack.json`** at the root of your