@tendrilapp/cli 0.1.34 → 0.1.35

package/dist/SKILL.md

@@ -247,6 +247,19 @@ Batch runs (several components in one session):
 4. `tendril_record_status` until complete. If roles derivation
    proposes mains/parts, SHOW the proposal to the user — a human
    confirms in their terminal, not you.
+5. COMPOSITION: read the status output's `composition` block. If it
+   lists unconfirmed partner pairs, this recording references OTHER
+   recorded components (a segmented control built from a recorded
+   Control, a dialog holding a recorded Button). Order matters:
+   generate the PARTNER bundle first, then show the pairing to the
+   user — a human decides it by running
+   `npx -y -p @tendrilapp/cli@latest tendril compose --set <host-set-dir>`
+   in their own terminal (confirm or `--decline <pair-key>`; the
+   pair-key is printed above each pair). Never confirm it yourself.
+   Generating the host with pairs undecided is valid — the brief will
+   say so — but the host then re-implements the partner's pixels
+   locally instead of composing the verified partner bundle, so
+   surface the choice before you spend the rounds.
 
 ## Generating (the agent-harness engine — you are the proposer)
 

package/dist/tendril-mcp.js

@@ -213,7 +213,7 @@ var TOOLS = [
   {
     name: "tendril_record_status",
     annotations: { readOnlyHint: true },
-    description: "Recording-set completeness: per-rep recorded/missing tools, files that exist but are unusable (invalid \u2014 re-record those), and whether the set-level steps are recorded (get_variable_defs always; get_motion_context when the plan asked \u2014 ADR-016). `complete` means USABLE by the next pipeline step.",
+    description: "Recording-set completeness: per-rep recorded/missing tools, files that exist but are unusable (invalid \u2014 re-record those), and whether the set-level steps are recorded (get_variable_defs always; get_motion_context when the plan asked \u2014 ADR-016). `complete` means the RECORDING is usable by the next pipeline step \u2014 it does NOT mean nothing is left to decide: read the `composition` field too (always present: openPairs lists unconfirmed partner pairs with pair-keys \u2014 surface those to the user BEFORE generating the host, partner-first; {unavailable} means discovery could not run, which is unknown, not 'no pairs').",
     schema: z.object({ setDir: str("recording set directory") }),
     argv: (i) => ["record", "status", "--set", i["setDir"]]
   },