fanout-cli 0.9.0 → 0.9.2

package/dist/view.html

@@ -327,6 +327,11 @@
       .waiting .who {
         color: var(--fg);
       }
+      /* The other project's name, said quietly: it is context, not the subject of the row. */
+      .from {
+        color: var(--fg-faint);
+        font-size: var(--text-xs);
+      }
       .waiting .what {
         color: var(--fg-dim);
       }
@@ -615,7 +620,7 @@
        * of it; a page that worked out its own answer would eventually tell someone a run was ready while the
        * merge tool refused it.
        */
-      function waitingSection(waiting) {
+      function waitingSection(waiting, here) {
         const section = el("section");
         const head = el("h2");
         head.append(document.createTextNode("Waiting on you"));
@@ -639,6 +644,15 @@
           // The work, not the run id — the id is for the tools, and is on the row for anyone who needs it.
           row.title = item.runId;
           row.append(el("span", "who", item.task ?? item.runId));
+          /*
+           * Where it came from, when it did not come from here. One daemon serves the whole machine, so a row
+           * with no repository asks somebody to review work they may never have seen the project for.
+           */
+          if (item.repo && item.repo !== here) {
+            const from = el("span", "from", item.repo.split("/").pop());
+            from.title = item.repo;
+            row.append(from);
+          }
           row.append(
             el(
               "span",
@@ -801,7 +815,12 @@
         main.append(crew);
 
         // Above the runs: it is the only thing on this page that asks something of whoever is reading it.
-        main.append(waitingSection(snapshot.waiting ?? []));
+        /*
+         * The repository this page is about: the one the mission on screen belongs to. Rows from anywhere else
+         * are labelled, because one daemon serves the whole machine and an unlabelled row is a request to review
+         * work from a project the reader may not even have open.
+         */
+        main.append(waitingSection(snapshot.waiting ?? [], mission?.repo?.root));
 
         const runs = el("section");
         const runsHead = el("h2");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fanout-cli",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "description": "Let Claude Code lead the other coding-agent CLIs you already pay for.",
   "license": "MIT",
   "type": "module",
@@ -27,22 +27,24 @@
     "README.md",
     "LICENSE"
   ],
+  "scripts": {
+    "typecheck": "tsc -p tsconfig.json",
+    "build": "node ../../scripts/bundle-cli.mjs",
+    "prepack": "node ../../scripts/bundle-cli.mjs",
+    "prepublishOnly": "node ../../scripts/check-publish.mjs"
+  },
   "dependencies": {
     "@modelcontextprotocol/sdk": "1.30.0",
     "ws": "8.21.3",
     "zod": "4.6.2"
   },
   "devDependencies": {
-    "fanout-adapter-claude": "0.9.0",
-    "fanout-adapter-codex": "0.9.0",
-    "fanout-core": "0.9.0",
-    "fanout-adapter-grok": "0.9.0",
-    "fanout-adapter-fake": "0.9.0",
-    "fanout-daemon": "0.9.0",
-    "fanout-mcp": "0.9.0"
-  },
-  "scripts": {
-    "typecheck": "tsc -p tsconfig.json",
-    "build": "node ../../scripts/bundle-cli.mjs"
+    "fanout-adapter-claude": "workspace:*",
+    "fanout-adapter-codex": "workspace:*",
+    "fanout-adapter-fake": "workspace:*",
+    "fanout-adapter-grok": "workspace:*",
+    "fanout-core": "workspace:*",
+    "fanout-daemon": "workspace:*",
+    "fanout-mcp": "workspace:*"
   }
-}
+}

package/plugin/.claude-plugin/plugin.json

@@ -1,12 +1,19 @@
 {
   "name": "fanout",
   "description": "Lead a crew of the coding-agent CLIs you already pay for: plan, fan out into isolated git worktrees, watch, and review before anything merges.",
-  "version": "0.6.0",
+  "version": "0.9.2",
   "author": {
     "name": "elberacasa"
   },
   "homepage": "https://github.com/elberacasa/fanout",
   "repository": "https://github.com/elberacasa/fanout",
   "license": "MIT",
-  "keywords": ["agents", "orchestration", "codex", "grok", "worktrees", "local-first"]
+  "keywords": [
+    "agents",
+    "orchestration",
+    "codex",
+    "grok",
+    "worktrees",
+    "local-first"
+  ]
 }

package/plugin/commands/fanout.md

@@ -7,24 +7,30 @@ The user wants this done by the crew: **$ARGUMENTS**
 
 You are the lead. Work in this order, and do not skip the parts that keep it safe.
 
-1. **Look before planning.** Call `repo_overview` and `seats`. If no seat is ready, say so and stop: there is no
+1. **Say back what you heard, before anything else.** Restate the goal in one line — `Planning: <goal>` — in the
+   words you received it in. A prompt pasted into a terminal can arrive with characters missing, silently: a real
+   paste turned "fails on the old code" into "fails on the olcode" and nothing reported it. A goal that lost a
+   word still produces a confident plan, and every step after that looks reasonable, so this line is the only
+   place the input itself is ever visible. If it reads as truncated, contradictory or half a sentence, ask
+   instead of guessing.
+2. **Look before planning.** Call `repo_overview` and `seats`. If no seat is ready, say so and stop: there is no
    crew to lead.
-2. **Split the work honestly.** One line per piece that can stand alone, each with:
+3. **Split the work honestly.** One line per piece that can stand alone, each with:
    - a **write scope** narrow enough that no two lines that run at once can touch the same file;
    - a **prompt** that names the exact files, the expected behaviour with an example, the project's check commands,
      and "do not commit";
    - a **seat**: give the risky or subtle piece to the strongest seat, the mechanical piece to the cheapest, and
      read-only work to an auditor. Claude is opt-in; prefer the other subscriptions.
    Dependent work goes in `dependsOn` rather than in one big line.
-3. **Check before launching.** Call `plan_check`. Fix what it blocks; do not argue with it. Show the user the plan
+4. **Check before launching.** Call `plan_check`. Fix what it blocks; do not argue with it. Show the user the plan
    as a short list (line, seat, scope) and the dry run if they ask.
-4. **Launch** with `launch`, then tell the user the mission id and what each line is doing.
-5. **Watch** with `mission_status`. While runs are going, do not start unrelated work in this session: you are the
+5. **Launch** with `launch`, then tell the user the mission id and what each line is doing.
+6. **Watch** with `mission_status`. While runs are going, do not start unrelated work in this session: you are the
    lead, and reviewing is your job.
-6. **Review each finished run** with `run_diff`. Read the risky lines yourself. Anything written outside its scope
+7. **Review each finished run** with `run_diff`. Read the risky lines yourself. Anything written outside its scope
    is the first thing you look at. Then tell the user, per run: what it changed, what you would keep, what you would
    not, and what you could not verify.
-7. **Merging is the user's call, and it is not automatic.** Apply a diff yourself only when they say so, run the
+8. **Merging is the user's call, and it is not automatic.** Apply a diff yourself only when they say so, run the
    project's real checks afterwards, and never present an agent's "tests pass" as your own verification.
 
 If something fails, say which line, why, and what you propose — never "it didn't work".