figura-cli 0.20.0 → 0.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "figura-cli",
-  "version": "0.20.0",
+  "version": "0.22.0",
   "description": "Command-line client for the Figura visualization SaaS",
   "license": "MIT",
   "type": "module",
@@ -28,16 +28,22 @@
     "node": ">=20"
   },
   "scripts": {
-    "build": "bun run scripts/bundle-skill.mjs && bun build src/index.ts --target=node --minify --outfile=dist/index.js && bun build ../mcp/src/index.ts --target=node --minify --outfile=dist/mcp.js",
+    "build": "bun run scripts/bundle-skill.mjs && bun build src/index.ts --target=node --minify --external ws --outfile=dist/index.js && bun build ../mcp/src/index.ts --target=node --minify --outfile=dist/mcp.js",
     "dev": "bun run src/index.ts",
     "prepublishOnly": "bun run build"
   },
+  "dependencies": {
+    "ws": "^8.18.0"
+  },
   "devDependencies": {
     "@panofm/figura-core": "workspace:*",
     "@types/node": "^20.14.0",
+    "@types/ws": "^8.5.12",
     "axios": "^1.7.9",
+    "nostr-tools": "^2.10.4",
     "package-manager-detector": "^1.8.0",
     "postgres": "^3.4.9",
-    "typescript": "^5.5.0"
+    "typescript": "^5.5.0",
+    "zod": "^3.25.76"
   }
 }

package/skills/fig/SKILL.md

@@ -101,6 +101,9 @@ so you hand it the studied structure in the brief (see step 3, "Server render").
      wrong tenant). Tell the user to run `figura link` in this repo, then
      re-verify. If the response has no `binding` field (older CLI/MCP), confirm
      the team slug matches this project with the user before proceeding.
+   - **Update notice?** If the whoami response carries a `notice` field, relay it
+     to the user verbatim (a one-line "figura-mcp is behind / below min — run …"),
+     then proceed. It's a passive nudge, shown once per session — never a blocker.
 
 2. **Default — build it yourself, with YOUR Claude.** Fetch the **canonical
    authoring scaffold** — **`figura_fig_scaffold`** (CLI:
@@ -231,14 +234,10 @@ truncation, and doesn't need a library):
   status chip and ONE condensed context line (`+ / –`). This view is for
   scanning and picking a direction, not for reading detail. The grid must
   wrap to one column before it can overflow — **a fig never scrolls
-  horizontally**, at any viewport. To shrink the framed phones, set the kit's
-  **`--fig-scale`** custom property (e.g. `style="--fig-scale:.42"` on each
-  `.fig-device`, or on the grid container — it inherits) — Figura shrinks the
-  whole framed phone and reserves the scaled layout box so the minis tile
-  without overlapping. **Do NOT** write your own rule on `.fig-device`
-  (a `width`/`height` or `transform: scale()`): `--fig-scale` is the one
-  sanctioned scaling knob, and hand-sizing the frame fights the injected
-  geometry.
+  horizontally**, at any viewport. To shrink the framed phones, wrap each in the
+  kit's **`.fig-mini`** wrapper (see "Scaling a framed device" below), never a
+  rule on `.fig-device` and never CSS `zoom` (zoom leaks an unzoomed
+  `scrollWidth` into horizontal overflow — the exact thing this view forbids).
 - **Focus — full frame.** One state at a time behind state pills (Today / A /
   B / …), each state framed identically so flipping states in place reads as
   spot-the-difference. This is where the context lives, pinned on the frame
@@ -344,9 +343,28 @@ omit the whole-fig `<meta name="figura:artboard">`, the `.fig-device` /
 `data-device` frame markup (Figura stamps the bezel, Dynamic Island, and
 safe-area insets **before** your `<style>`, so you normally leave those classes
 alone — if you do style one, your rule wins by cascade and the frame still
-works; to shrink a frame use the `--fig-scale` custom property, never a
-hand-written `.fig-device` width/height/transform), the `figura:context` /
-`figura:feature` metas, and the valid devices all live in the canonical scaffold.
+works; to shrink a frame use the `.fig-mini` wrapper, never a hand-written
+`.fig-device` width/height/transform), the `figura:context` / `figura:feature`
+metas, and the valid devices all live in the canonical scaffold.
+
+**Scaling a framed device — use `.fig-mini`, never a rule on `.fig-device`.**
+An overview grid needs shrunken frames, and the obvious way to write that is a
+CSS rule on the injected class. Don't: your rule wins over the kit, so the frame
+stops matching real device geometry — and `zoom` is worse, it leaks the unzoomed
+width into scrollable overflow. The kit ships the wrapper instead:
+
+```html
+<div class="fig-mini" style="--fig-scale:.34">
+  <div class="fig-device portrait" data-device="iphone-16">
+    <div class="fig-screen">…</div><div class="fig-di"></div><div class="fig-homebar"></div>
+  </div>
+</div>
+```
+
+`.fig-mini` scales its device with `transform` and takes the **scaled** layout
+box, so a row of minis lays out at its visual size instead of reserving
+full-size phones. Add `landscape` to the device (or the wrapper) and the box
+flips with it. `--fig-scale` defaults to `.34`; set it per element.
 
 - **`figura_fig_scaffold`** (CLI: `figura fig scaffold`) is authoritative for the
   presentation model, the frame markup, and the output contract. Fetch it and