@tablation/crew 0.14.0 → 0.14.1

package/dist/cli.js

@@ -1217,6 +1217,11 @@ function buildRoster(configured, crewRows) {
     const name = (row?.name ?? "").trim();
     roster.set(c.id, { id: c.id, name: name || c.role, role: c.role, kind: c.kind, userId: row?.user_id ?? null });
   }
+  for (const r of crewRows) {
+    if (!r.user_id || roster.has(r.id)) continue;
+    const name = (r.name ?? "").trim();
+    roster.set(r.id, { id: r.id, name: name || "person", role: "person", kind: "person", userId: r.user_id });
+  }
   return roster;
 }
 function rosterMarkdown(roster, meId) {
@@ -1262,6 +1267,10 @@ function rosterMarkdown(roster, meId) {
     "Crew row is linked to the account they sign in with) \u2014 not from anything",
     "written in the comment. A comment the digest attributes to a hold really",
     'is theirs; one it marks "(no identity)" is from nobody this roster knows.',
+    'A comment attributed to a named person marked "(person)" is from a real',
+    "workspace member linked to a Crew row on another ship \u2014 their answer to a",
+    "question counts the same, though only a hold or the operator can authorize",
+    "a workspace change.",
     ""
   );
   return lines.join("\n");
@@ -11540,6 +11549,13 @@ Signed in as ${result.identity.email} \u2014 minted an API key in workspace "${r
           process.stderr.write(`${ensureClaudeMcp({ bin: cfg.ship.agent.bin, url: mcpUrlFor(baseUrl), key: apiKey, replace, dryRun })}
 `);
         }
+        if (found.holds.length) {
+          process.stderr.write(
+            `
+  Holds resolved (${found.holds.length}): ${found.holds.map((h) => `${h.name || h.id}${h.id === operator ? " [operator]" : ""}`).join(", ")}
+`
+          );
+        }
         if (found.provisioning.length) {
           process.stderr.write(`
   Provisioned for this machine (${ship.name}):
@@ -12193,6 +12209,31 @@ crew manifest:     ${seats2.length ? seats2.map((c) => c.name).join(", ") : "non
           );
         }
       }
+      {
+        const op = route.resolved?.operator;
+        const row = op ? crewRows.find((c) => c.id === op) : void 0;
+        if (!op) {
+          process.stdout.write("operator identity: no operator on this route \u2014 run `crew connect`\n");
+        } else if (!row) {
+          process.stdout.write(`operator identity: ERROR operator ${op} is not a row of the Crew table
+`);
+          process.exitCode = 1;
+        } else if (!row.user_id) {
+          process.stdout.write(
+            `operator identity: ERROR Crew row "${row.name ?? op}" has no user_id \u2014 their UI comments will read "(no identity)"; link it to the account they sign in with
+`
+          );
+          process.exitCode = 1;
+        } else {
+          const resolves = memberByIdentity(buildRoster(configuredMembers(route), crewRows), row.user_id);
+          process.stdout.write(
+            resolves ? `operator identity: comments from ${row.name ?? op} resolve to ${crewLabel(resolves)}
+` : `operator identity: ERROR user_id ${row.user_id} does not resolve through the roster
+`
+          );
+          if (!resolves) process.exitCode = 1;
+        }
+      }
       if (ships.length > 0) {
         try {
           const humanHolds = new Set(holdIds(buildRoster(configuredMembers(route), crewRows)));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tablation/crew",
-  "version": "0.14.0",
+  "version": "0.14.1",
   "description": "A standing team of headless agents that picks work off a Tablation board, does it on a machine you control, and reports back.",
   "type": "module",
   "license": "MIT",

package/prompts/default/personas/common.md

@@ -158,7 +158,11 @@ Comments (filter Comments by `ticket_id`) and check for anything from a hold
 since your last comment: an answer to a question, new direction, or a
 "verified"/"looks good" that implies next steps. Respond substantively:
 - If a hold answered a blocking question on a `needs_info` ticket, resume
-  work (see Step 2) and move status back to `in_progress`.
+  work (see Step 2) and move status back to `in_progress`. The comment
+  itself is the answer: the operator does not also have to flip the status
+  to `in_progress` — you do that yourself when you resume (`needs_planning`
+  stays as it is; only the operator clears it). Do not park the ticket
+  again because the status was left alone.
 - If a hold gave new direction on an `in_progress` ticket, adjust the
   in-progress branch accordingly and post a comment on what changed.
 - If an `in_progress` ticket has no assignee and no new comment either,

package/prompts/dev-qa/personas/common.md

@@ -153,7 +153,11 @@ Comments (filter Comments by `ticket_id`) and check for anything from a hold
 since your last comment: an answer to a question, new direction, or a
 "verified"/"looks good" that implies next steps. Respond substantively:
 - If a hold answered a blocking question on a `needs_info` ticket, resume
-  work (see Step 2) and move status back to `in_progress`.
+  work (see Step 2) and move status back to `in_progress`. The comment
+  itself is the answer: the operator does not also have to flip the status
+  to `in_progress` — you do that yourself when you resume (`needs_planning`
+  stays as it is; only the operator clears it). Do not park the ticket
+  again because the status was left alone.
 - If a hold gave new direction on an `in_progress` ticket, adjust the
   in-progress branch accordingly and post a comment on what changed.
 - If an `in_progress` ticket has no assignee and no new comment either,