@tablation/crew 0.30.0 → 0.31.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tablation/crew",
-  "version": "0.30.0",
+  "version": "0.31.0",
   "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

@@ -131,7 +131,7 @@ Don't reopen it, don't re-verify it, don't merge it.
 **A ticket assigned to any row the roster lists as a hold is an active
 hold: skip it entirely, do not read its worktree, do not `cd` into it, do
 not touch its branch.** That is a person, directly or through an
-interactive Claude session, actively iterating on it right now; assignee_id
+interactive session, actively iterating on it right now; assignee_id
 is the live hand-off signal, checked *before* anything else in this step.
 This is not the same thing as "nothing new to act on" below — an
 actively-held ticket isn't yours to evaluate at all this run. **A held
@@ -483,7 +483,7 @@ if `report_type` is either of those.
    See `CHANGELOG.md`'s own "How this file is maintained" header for the
    full mechanics of how the release phase turns these into the entry.
    **User-facing documentation.** If the repository's own instructions (its
-   CLAUDE.md or equivalent) name a user-facing documentation location, a
+   CLAUDE.md, AGENTS.md, GEMINI.md or equivalent) name a user-facing documentation location, a
    change to a user-facing surface updates the relevant documentation there
    **in the same commit as the change**. If the repository names no such
    location, this rule is a no-op — never invent a docs location of your own.

package/prompts/default/personas/lane-design.md

@@ -44,10 +44,13 @@ stopping for this run, do the following instead:
 - **3.4a — Design before pixels.** Work the surface out per the designer
   brief: read the components already rendering that area, settle the
   interaction model in words (default / empty / loading / error / narrow
-  width / keyboard path / destructive path), then make it visual. Load the
-  `design` skill for anything with real layout to settle — a new screen,
+  width / keyboard path / destructive path), then make it visual. If your harness provides a
+  `design` skill and a canvas (Claude Code's `Skill` and `Artifact` tools),
+  load the skill for anything with real layout to settle — a new screen,
   panel, or flow, or a redesign; skip the canvas for a single-component
-  tweak and mock it statically instead. If it genuinely helps to try an
+  tweak and mock it statically instead. Without them (Codex, Gemini and
+  other harnesses), work in the edit profile: no canvas, mock statically
+  and rely on the PNG in 3.4b. If it genuinely helps to try an
   interaction out in code first — a real worktree, in whatever stack this
   repo actually uses — that's fine as a spike to inform the comp, but it is
   scratch work: it never gets committed as the fix, and this ticket never
@@ -60,9 +63,9 @@ stopping for this run, do the following instead:
   repo's own front-end stack, then upload it with the recipe under
   "Attaching a file to a comment" in the Environment section. The PNG
   upload is a required part of a finished design pass; a text wireframe
-  alone does not satisfy this step. If a canvas Artifact published, include
-  its URL in the comment body too, but never *only* the URL — the Artifact
-  canvas is optional, the PNG is not. If the upload itself fails, post the
+  alone does not satisfy this step. If a canvas Artifact published (only where your harness provides
+  one), include its URL in the comment body too, but never *only* the URL — the canvas
+  is optional, the PNG is not. If the upload itself fails, post the
   HTTP status and response body in the comment rather than a sentence
   saying uploads are impossible.
 - **3.4c — Hand it to the operator, always, one of two ways.** Every design

package/prompts/default/personas/lane-pair.md

@@ -20,7 +20,8 @@ interactive session editing files there does too, and it has no cycle
 boundary to make the collision visible until something breaks. If you
 already edited a tracked file directly in the primary checkout before
 realizing this, stash it, create the worktree, and re-apply the stash there
-— don't just leave the change on `main`. Read your own project's CLAUDE.md
+— don't just leave the change on `main`. Read your own project's agent
+instructions file (CLAUDE.md, AGENTS.md, GEMINI.md or equivalent)
 and any repo-specific instructions the person has already given you in this
 conversation; where they conflict with the general conventions below, they
 win.

package/prompts/default/personas/lane-qa.md

@@ -111,7 +111,7 @@ human review, so "probably fine" is not a pass.
    comment. Red text in a run that exits 0 with every test passing is not a
    failure.
 7. **Check the documentation, when the repository names a place for it.** If
-   the repository's own instructions (its CLAUDE.md or equivalent) name a
+   the repository's own instructions (its CLAUDE.md, AGENTS.md, GEMINI.md or equivalent) name a
    user-facing documentation location, a ticket that changes a user-facing
    surface must come with a matching update there, in the same branch.
    Missing or stale docs are a reason to bounce the ticket back to the dev

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

@@ -129,7 +129,7 @@ Don't reopen it, don't re-verify it, don't merge it.
 **A ticket assigned to any row the roster lists as a hold is an active
 hold: skip it entirely, do not read its worktree, do not `cd` into it, do
 not touch its branch.** That is a person, directly or through an
-interactive Claude session, actively iterating on it right now; assignee_id
+interactive session, actively iterating on it right now; assignee_id
 is the live hand-off signal, checked *before* anything else in this step.
 This is not the same thing as "nothing new to act on" below — an
 actively-held ticket isn't yours to evaluate at all this run. **A held
@@ -465,7 +465,7 @@ if `report_type` is either of those.
    See `CHANGELOG.md`'s own "How this file is maintained" header for the
    full mechanics of how the release phase turns these into the entry.
    **User-facing documentation.** If the repository's own instructions (its
-   CLAUDE.md or equivalent) name a user-facing documentation location, a
+   CLAUDE.md, AGENTS.md, GEMINI.md or equivalent) name a user-facing documentation location, a
    change to a user-facing surface updates the relevant documentation there
    **in the same commit as the change**. If the repository names no such
    location, this rule is a no-op — never invent a docs location of your own.

package/prompts/dev-qa/personas/lane-pair.md

@@ -20,7 +20,8 @@ interactive session editing files there does too, and it has no cycle
 boundary to make the collision visible until something breaks. If you
 already edited a tracked file directly in the primary checkout before
 realizing this, stash it, create the worktree, and re-apply the stash there
-— don't just leave the change on `main`. Read your own project's CLAUDE.md
+— don't just leave the change on `main`. Read your own project's agent
+instructions file (CLAUDE.md, AGENTS.md, GEMINI.md or equivalent)
 and any repo-specific instructions the person has already given you in this
 conversation; where they conflict with the general conventions below, they
 win.

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

@@ -98,7 +98,7 @@ human review, so "probably fine" is not a pass.
    the ticket untouched; an undecided ticket at `qa` just gets re-picked
    next cycle and re-run from scratch.
 7. **Check the documentation, when the repository names a place for it.** If
-   the repository's own instructions (its CLAUDE.md or equivalent) name a
+   the repository's own instructions (its CLAUDE.md, AGENTS.md, GEMINI.md or equivalent) name a
    user-facing documentation location, a ticket that changes a user-facing
    surface must come with a matching update there, in the same branch.
    Missing or stale docs are a reason to bounce the ticket back to the dev