@tablation/crew 0.43.2 → 0.43.4

package/dist/cli.js

@@ -5933,7 +5933,7 @@ function filedBy(t, i) {
   return t.reporter_name ? `${t.reporter_name} (unverified)` : "\u2014";
 }
 function lastComment(i, ticketId) {
-  const forTicket = i.comments.filter((c) => c.ticket_id === ticketId).sort((a, b) => a.created_at < b.created_at ? -1 : a.created_at > b.created_at ? 1 : 0);
+  const forTicket = i.comments.filter((c) => c.ticket_id === ticketId && (c.kind ?? "comment") !== "event").sort((a, b) => a.created_at < b.created_at ? -1 : a.created_at > b.created_at ? 1 : 0);
   const last = forTicket[forTicket.length - 1];
   if (!last) return "\u2014";
   return `${last.created_at.slice(0, 16)}Z ${author(last, i)}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tablation/crew",
-  "version": "0.43.2",
+  "version": "0.43.4",
   "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/skills/grill-me.md

@@ -116,6 +116,10 @@ Map go active now, or stay a draft?**
      - Any `draft` Issue tied to this Epic that this session's ticket
        set does NOT include (i.e. dropped by this revision) → flip to
        `status: closed_obsolete`.
+  5. Set the Epic itself to `status: planned` (Epics table) if it is
+     still `new`. An active Map is the planning decision for the Epic;
+     leave an Epic that has already moved on (`in_progress`, `done`,
+     `cancelled`) alone.
 
 Do all of this yourself via direct MCP writes. There is no automation
 watching for this — if you don't do it, it doesn't happen.

package/prompts/dev-qa/skills/grill-me.md

@@ -116,6 +116,10 @@ Map go active now, or stay a draft?**
      - Any `draft` Issue tied to this Epic that this session's ticket
        set does NOT include (i.e. dropped by this revision) → flip to
        `status: closed_obsolete`.
+  5. Set the Epic itself to `status: planned` (Epics table) if it is
+     still `new`. An active Map is the planning decision for the Epic;
+     leave an Epic that has already moved on (`in_progress`, `done`,
+     `cancelled`) alone.
 
 Do all of this yourself via direct MCP writes. There is no automation
 watching for this — if you don't do it, it doesn't happen.