@lahat-group/cli 1.1.8 → 2.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lahat-group/cli",
-  "version": "1.1.8",
+  "version": "2.0.1",
   "description": "CLI + Claude Skill to build, validate, price, and save wardrobe designs.",
   "license": "UNLICENSED",
   "type": "module",
@@ -30,7 +30,6 @@
     "test": "vitest run"
   },
   "devDependencies": {
-    "@wardrobe/shared": "*",
     "commander": "^12.0.0",
     "ky": "^1.14.3",
     "tsup": "^8.0.0",

package/skill/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wardrobe-configurator
-description: Use when the user wants to build, configure, validate, price, or order a wardrobe/closet design from the terminal — phrases like "configure a wardrobe", "price a design", "build a closet layout", "validate my wardrobe config" — OR wants to look up existing wardrobe data: projects, customers, designers, orders and their PDFs, e.g. "which projects does this designer have", "find the customer with phone 05x", "who is on this project", "what is the status of this order", "download the order PDF". Drives the `wardrobe` CLI (HTTP client over the configurator API); a WardrobeConfig JSON file on disk is the unit of work for design verbs, and every lookup verb is read-only.
+description: Use when the user wants to build, configure, validate, price, or order a wardrobe/closet design from the terminal — phrases like "configure a wardrobe", "price a design", "build a closet layout", "validate my wardrobe config" — OR wants to look up existing wardrobe data: projects, customers, designers, orders, quotations and their PDFs, or (staff only) registered users across the whole system, e.g. "which projects does this designer have", "find the customer with phone 05x", "who is on this project", "what is the status of this order", "download the order PDF", "who signed up recently", "which account owns this phone number", "what's the latest quote we generated". Drives the `wardrobe` CLI (HTTP client over the configurator API); a WardrobeConfig JSON file on disk is the unit of work for design verbs, and every lookup verb is read-only.
 ---
 
 # Wardrobe Configurator CLI
@@ -12,8 +12,13 @@ agent loop is: **init → edit → validate → price → plan → apply**.
 ## Prerequisites
 
 - Install the CLI: `npm install -g @lahat-group/cli` (or run ad-hoc via `npx @lahat-group/cli <verb>`).
-  It ships as a self-contained binary — no build step, no extra dependencies.
-- **Authenticate once**: `wardrobe login` runs the OAuth device flow — it prints a
+  It ships as a self-contained binary — no build step, no extra dependencies. It holds
+  no domain logic of its own; the rules live in the API.
+- **Authenticate first — every verb needs it.** The CLI is a thin HTTP client: `init`,
+  `validate` and `describe` are served by the API just as `price` and `apply` are, so
+  none of them work offline. `Not authenticated. Run \`wardrobe login\` first.` means
+  exactly that.
+- `wardrobe login` runs the OAuth device flow — it prints a
   user code, opens `/activate` in the browser, and stores a scoped agent key at
   `~/.config/wardrobe/config.json` (chmod 600). Confirm with `wardrobe whoami`.
 - The CLI targets the **production** API by default. Set `WARDROBE_API_URL` to override
@@ -26,7 +31,8 @@ agent loop is: **init → edit → validate → price → plan → apply**.
    emits a fresh, valid `WardrobeConfig` (full-width, split into optimal columns).
 2. **edit** — modify `wardrobe.json` directly (see shape below).
 3. **validate** — `wardrobe validate wardrobe.json` (or `-` for stdin). Runs the
-   **shared constraint pipeline fully offline** — byte-identical to the web app.
+   **live** constraint pipeline server-side — the same rules `wardrobe price` enforces,
+   so a config `validate` approves can never be one `price` rejects.
    Exit 0 = valid; exit 1 + structured errors otherwise. Do this after every edit.
 4. **price** — `wardrobe price wardrobe.json` → authoritative total in **NIS** from
    the API's unified area×rate engine.
@@ -65,7 +71,7 @@ or a saved design id.
 ## Reading what exists
 
 Every read the key can reach has a verb. **All of them are GETs** — the CLI can read
-customers and orders but never create or change them (`customers:write`,
+customers, orders and quotations but never create or change them (`customers:write`,
 `orders:write` and `quotations:write` are not on the CLI's key, so those routes
 answer `403 insufficient_scope` whoever signed in).
 
@@ -80,32 +86,67 @@ answer `403 insufficient_scope` whoever signed in).
 | `wardrobe customers get <id>` | One customer |
 | `wardrobe customers projects <id>` | That customer's projects |
 | `wardrobe designs list --project <id>` | Designs saved in a project |
+| `wardrobe designs list` | The newest designs across every project you can see (all yours, or the whole tenant with `staff:read`) |
+| `wardrobe designs list --limit <n>` `--since <ISO>` | Same, paged — `--limit` caps rows (default 20, max 100), `--since` filters by `updatedAt >=` |
 | `wardrobe designs thumbnail <id> --out f.jpg` | The design's rendered thumbnail |
 | `wardrobe orders list --project <id>` | Every order the project has had |
 | `wardrobe orders list --project <id> --open` | Only its active (non-cancelled) order |
+| `wardrobe orders list` | The newest-**updated** orders across every project you can see — "what moved", not "what's new": a status change or a revision surfaces an old order here too |
+| `wardrobe orders list --limit <n>` `--since <ISO>` | Same, paged (`--since` filters by `updatedAt >=`) |
 | `wardrobe orders pdf <id> --out f.pdf` | The order PDF |
+| `wardrobe quotations list --project <id>` | That project's quote number + full revision history |
+| `wardrobe quotations list` | Every quotation you can see, **newest-generated first** — this is "latest quotes generation" |
+| `wardrobe quotations list --limit <n>` `--since <ISO>` | Same, paged (`--since` filters by `updatedAt >=`, i.e. last generated at/after) |
+| `wardrobe users list` | Registered accounts, **newest-registered first** — staff only, see below |
+| `wardrobe users list --limit <n>` `--since <ISO>` | Same, paged (`--since` filters by `createdAt >=`) — `--limit 5` with no `--since` is "the latest registered users"; omit both, paging with `--since` off the last row's timestamp, for "every user in the system" |
+| `wardrobe users by-phone <number>` | The account(s) tied to that phone number: the linked client account plus every designer who owns a project for a customer with it — staff only |
 | `wardrobe help-texts` | The help-text table |
 
 `projects list` already returns each project's **customer and owning designer inline** —
 so "who is the customer on each of this designer's projects" is one call plus a filter,
 never one call per project. Prefer `--phone` / `--designer` over fetching and grepping.
 
+Every cross-project/cross-tenant list (`designs`, `orders`, `quotations`, `users`) takes
+`--limit` (1–100, default 20) and a `--since` cursor — pass the last row's timestamp
+back as `--since` to page further instead of guessing an offset. A malformed `--since` or
+an out-of-range `--limit` is a `400`, not a silently-ignored filter — read the error
+rather than retrying blind.
+
 ### What you can see is not what exists
 
 The list is bounded by the key, so an empty result is as often a **visibility** answer as
 a data one. `wardrobe whoami --json` reports the truth under `agent.scopes` and `role`:
 
-- An ordinary designer or client sees **their own** projects plus ones they were invited
-  to. A project belonging to someone else answers `403 Forbidden`, not `404`.
+- An ordinary designer or client sees **their own** projects, designs, orders and
+  quotations, plus ones they were invited to. A project belonging to someone else
+  answers `403 Forbidden`, not `404`. `wardrobe users list` and `users by-phone` answer
+  `403 Forbidden` outright — there is no per-row visibility to fall back to; the whole
+  surface is staff-only (see below).
 - A key approved by an **admin or support** user *and* carrying **`staff:read`** sees
-  **every** project, customer and order in the system. That scope is granted only to
+  **every** project, customer, order and quotation in the system — and can use
+  `wardrobe users list` / `users by-phone` at all. That scope is granted only to
   staff, only for GETs, and is listed by name on the consent screen. The same approver
   also receives **`staff:write`**, which lets `designs create` / `designs update` land in
-  a project the admin does not own. A key logged in before 2026-09-05 lacks it — a `403
-  Forbidden` on a write to someone else's project means `wardrobe login` again.
+  a project the admin does not own. A key logged in before 2026-09-05 lacks `staff:read`
+  and before 2026-09-12 lacks `quotations:read` — a `403 insufficient_scope` on
+  `quotations list`, or a `403 Forbidden` on a write to someone else's project, means
+  `wardrobe login` again.
 
 Never tell a user something does not exist when you only know your key cannot see it.
-Say which it is: `403 Forbidden` means the row is someone else's, `404` means it is gone.
+Say which it is: `403 Forbidden` means the row is someone else's (or, for `users`, that
+your key isn't staff at all), `404` means it is gone.
+
+### `wardrobe users` is a directory lookup, not a customer lookup
+
+`users list` / `users by-phone` read the `User` **account** table — designers, admins,
+support and self-serve clients who can sign in — not the per-project `Customer` contact
+card `wardrobe customers` reads. A phone number usually resolves to a **designer**
+(whoever owns the project for the customer with that number), occasionally to a
+**client** account too (if that customer accepted a project invitation and has their own
+login). It is normal for `users by-phone` to return more than one account, or to return
+zero when the number belongs to a customer nobody has invited to sign in — that is not
+an error, and it does not mean the phone number is unknown; check `wardrobe projects list
+--phone <number>` for the project/customer side of the same question.
 
 ### Not available here
 
@@ -113,8 +154,6 @@ Don't reach for these; they are not CLI verbs and not agent-reachable:
 
 - **Anything under `/admin`**, plus commissions and invitations — barred to every agent
   key at the mount (`403 agent_not_permitted`). No scope unlocks them.
-- **Quotation history.** `POST /quotations/pdf` is open to other clients, but reading a
-  project's past quotes is JWT-only — a human in the web app.
 - **Manufacturing-files export.** Staff-only, through the web app.
 
 ## WardrobeConfig shape (top-level)
@@ -141,10 +180,11 @@ Prefer generating the skeleton with `wardrobe init` rather than hand-writing it
 
 - **The CLI can read orders but never place one.** Its key carries `profile:read`,
   `projects:read`, `customers:read`, `designs:read`, `designs:write`, `orders:read`,
-  `price:read` (+ `staff:read` and `staff:write` for staff) — **every write beyond designs is absent**,
-  and so is every admin scope. `wardrobe orders list` and `orders pdf` work; creating
-  or changing an order, a customer or a quotation answers `403 insufficient_scope`.
-  Don't attempt it, and don't attempt admin/catalog operations.
+  `price:read`, `quotations:read` (+ `staff:read` and `staff:write` for staff) —
+  **every write beyond designs is absent**, and so is every admin scope. `wardrobe
+  orders list`, `orders pdf` and `quotations list` work; creating or changing an order,
+  a customer or a quotation answers `403 insufficient_scope`. Don't attempt it, and
+  don't attempt admin/catalog operations.
 - To turn a saved design into an order, direct the **human** to the web app: they
   open the project, review the design, and complete the **verify-details** flow —
   which computes the final price, freezes the PDF, and advances the order. Only a