@tendrilapp/cli 0.1.50 → 0.1.51

package/dist/SKILL.md

@@ -279,7 +279,19 @@ Batch runs (several components in one session):
    scanned" never reads as "no relationship".
    CONNECTING COMPONENTS THAT ALREADY EXIST (both recorded, both
    generated): step ONE is putting both recording sets in one scanned
-   root (co-locate, or --library). If the pairing then shows as
+   root (co-locate, or --library). If a set is not on this machine at
+   all — a fresh checkout, a different laptop, a component a teammate
+   published — do NOT conclude the work needs the original machine:
+   `tendril_pull <component name>` downloads the recording set the
+   published verdict was measured against, into
+   `./recordings/<component>/`. One call per component; the name is
+   exact, and a name that does not resolve comes back with the
+   account's real component names to pick from. It needs a portal
+   session (`tendril_login`) because a recording set belongs to the
+   account that published it — everything after the pull is local and
+   account-less as always. A publication published before recording
+   sets travelled, or published with `--no-recordings`, says so: that
+   is an honest stop, not a retry. If the pairing then shows as
    NAME-ONLY (the host was recorded over MCP, so Figma's instance→
    component bindings were never captured), run
    `tendril_record_bindings` on the HOST set — one or two batched
@@ -496,6 +508,15 @@ automatically) → `tendril_publish` → surface what it returns:
   moment for a step no click will confirm.
 - Not signed in? Surface `tendril_login` first — the sequence pauses at
   sign-in; it never silently skips publishing.
+- A publish also carries the RECORDING SET the verdict was measured
+  against, so the work can be picked up on any machine the user signs
+  in from (`tendril_pull`). It is private to their account — no share
+  link and no public page reaches it — and it rides the same deletion
+  as everything else. If the publish result says it went without the
+  recording set, relay that line as-is: it names why, and it is never
+  a failed publish. The first time an account carries one, the portal
+  asks for one browser Accept naming the new custody; relay that link
+  the way you relay an approve link, and never urge the decision.
 
 Sub-bar runs do NOT publish — the CLI refuses a declined run, and the
 honest failure report is that run's correct terminal state. The

package/dist/tendril-mcp.js

@@ -138,6 +138,23 @@ var TOOLS = [
     }),
     argv: (i) => ["publish", i["bundleDir"], "--approve-wait", "--wait-window", "55", ...typeof i["portal"] === "string" ? ["--to", i["portal"]] : []]
   },
+  {
+    name: "tendril_pull",
+    description: "Bring a published component's RECORDING SET onto this machine \u2014 the recorded design truth its verdict was measured against. Use it when the recordings are not here: a fresh machine, a clone with no recordings/ directory, or a component someone else on the team published. ONE bounded call, no wait twin. Needs a portal session (tendril_login) because a recording set belongs to the account that published it; everything afterwards \u2014 verify, compose, republish \u2014 is local, offline and account-less as always. The name is EXACT and the portal's refusals list the user's real component names, so a name that does not resolve is a one-step correction rather than a dead end; when one name spans two design systems, pass `figmaFile`. It writes to ./recordings/<component>/ and never overwrites a different set already there. AFTER pulling, call tendril_record_status on each set you pulled, then continue the connect prompt from its step 3.",
+    schema: z.object({
+      component: str("the component name, exactly as the user's library shows it"),
+      figmaFile: optStr("the design system's Figma file key \u2014 only when one name spans several of the user's design systems (the portal's refusal says when)"),
+      dest: optStr("where the set lands (default: ./recordings/<component>)"),
+      portal: optStr("portal origin override for self-hosted portals (defaults to the stored session's portal)")
+    }),
+    argv: (i) => [
+      "pull",
+      i["component"],
+      ...typeof i["figmaFile"] === "string" ? ["--figma-file", i["figmaFile"]] : [],
+      ...typeof i["dest"] === "string" ? ["--dest", i["dest"]] : [],
+      ...typeof i["portal"] === "string" ? ["--to", i["portal"]] : []
+    ]
+  },
   {
     name: "tendril_record_next",
     annotations: { readOnlyHint: true },