@lahat-group/cli 1.1.7 → 2.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lahat-group/cli",
-  "version": "1.1.7",
+  "version": "2.0.0",
   "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

@@ -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.
@@ -99,7 +105,10 @@ a data one. `wardrobe whoami --json` reports the truth under `agent.scopes` and
   to. A project belonging to someone else answers `403 Forbidden`, not `404`.
 - 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
-  staff, only for GETs, and is listed by name on the consent screen.
+  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.
 
 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.
@@ -138,7 +147,7 @@ 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` for staff) — **every write beyond designs is absent**,
+  `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.