@tablation/crew 0.23.0 → 0.23.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tablation/crew",
-  "version": "0.23.0",
+  "version": "0.23.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/lane-qa.md

@@ -148,7 +148,7 @@ human review, so "probably fine" is not a pass.
      branch you expected. A person built it; the operator has to push it.
    - **It doesn't** → `status` = `in_progress`, `assignee_id` = the building
      lane's own Crew row id from the roster above — the dev seat if
-     `needs_design` is false or null, the design seat if true. **Exception:** when the Issues table has a `held_by_ship_id` column, **clear** `assignee_id` *and* `held_by_ship_id` instead of naming a seat — the
+     `needs_design` is false or null, the design seat if true. **Exceptions:** in a `hybrid` project (the digest's `mode` column) an unassigned ticket is off limits to every lane, so clearing the assignee would strand the bounce: assign the building seat on this ship (ids under "Seats on this ship" in the Environment section, else the roster) and, if the Issues table has a `held_by_ship_id` column, still clear that. In an `automatic` project, when the Issues table has a `held_by_ship_id` column, **clear** `assignee_id` *and* `held_by_ship_id` instead of naming a seat — the
      hold on a `qa` ticket is yours, as verifier, and seats are per ship, so
      naming this ship's seat would hand the bounce to a ship that never built
      it. An unassigned, unheld `in_progress` ticket is picked up by whichever

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

@@ -134,7 +134,7 @@ human review, so "probably fine" is not a pass.
      builder: set `needs_info` and assign the operator, with a comment naming the
      branch you expected. A person built it; the operator has to push it.
    - **It doesn't** → `status` = `in_progress`, `assignee_id` = the dev
-     seat's own Crew row id from the roster above. **Exception:** when the Issues table has a `held_by_ship_id` column, **clear** `assignee_id` *and* `held_by_ship_id` instead of naming a seat — the
+     seat's own Crew row id from the roster above. **Exceptions:** in a `hybrid` project (the digest's `mode` column) an unassigned ticket is off limits to every lane, so clearing the assignee would strand the bounce: assign the building seat on this ship (ids under "Seats on this ship" in the Environment section, else the roster) and, if the Issues table has a `held_by_ship_id` column, still clear that. In an `automatic` project, when the Issues table has a `held_by_ship_id` column, **clear** `assignee_id` *and* `held_by_ship_id` instead of naming a seat — the
      hold on a `qa` ticket is yours, as verifier, and seats are per ship, so
      naming this ship's seat would hand the bounce to a ship that never built
      it. An unassigned, unheld `in_progress` ticket is picked up by whichever