kaizen-agent 1.5.5 → 1.5.6

package/cli/state.test.ts

@@ -57,7 +57,11 @@ test("statusOf: waiting beats stage, mtime decides running vs stalled", () => {
 });
 
 test("columnOf: every stage word lands somewhere", () => {
-  expect(["plan", "build", "review", "done", "abandoned", "weird"].map(columnOf)).toEqual([1, 2, 3, 4, 4, 1]);
+  expect(["plan", "build", "review", "done", "abandoned", "weird"].map((s) => columnOf(s))).toEqual([1, 2, 3, 4, 4, 1]);
+  expect(columnOf("implement", "approvals.review")).toBe(3);
+  expect(columnOf("implement", "findings")).toBe(3);
+  expect(columnOf("implement", "approvals.each_file")).toBe(2);
+  expect(columnOf("plan", "approvals.plan")).toBe(1);
 });
 
 test("inbox round-trips and ignores malformed lines", () => {

package/cli/state.ts

@@ -348,12 +348,16 @@ export function statusOf(r: Run, now: number): Status {
   return now - r.moved < RUNNING_WITHIN_MS ? "running" : "stalled";
 }
 
-// A stage this build has never heard of still belongs somewhere visible, and
-// PLANNING is the honest guess: the run has started and has not finished.
-export function columnOf(stage: string) {
+// A stage this build has never heard of still belongs somewhere visible. What the
+// run is waiting on says where it really is (a run awaiting the review approval is
+// in Review whatever its stage word), and PLANNING is the honest guess otherwise:
+// the run has started and has not finished.
+export function columnOf(stage: string, awaiting: string | null = null) {
   if (stage === "build") return 2;
   if (stage === "review") return 3;
   if (stage === "done" || stage === "abandoned") return 4;
+  if (awaiting === "approvals.review" || awaiting === "findings") return 3;
+  if (awaiting === "approvals.each_file") return 2;
   return 1;
 }
 
@@ -588,7 +592,7 @@ export function boardCards(states: string[], now: number): Card[] {
     }
     for (const r of readRuns(st)) {
       next.push({
-        kind: "run", id: r.id, status: statusOf(r, now), text: short(r.id), state: st, where, column: columnOf(r.stage), moved: r.moved,
+        kind: "run", id: r.id, status: statusOf(r, now), text: short(r.id), state: st, where, column: columnOf(r.stage, r.awaiting), moved: r.moved,
         title: requestTitle(body(st, r.id)),
         awaiting: r.stage === "abandoned" ? null : r.awaiting,
         dim: r.stage === "abandoned",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kaizen-agent",
-  "version": "1.5.5",
+  "version": "1.5.6",
   "description": "Staged workflow for AI agents — code, writing, research, operations: plan, human approval, build, independent review, bounded fix loop.",
   "type": "module",
   "bin": {

package/skills/kaizen/spec.md

@@ -104,6 +104,18 @@ Write into `00-request.md`: the verbatim request, the deliverable, what done mea
 and what wrong means. Record in `state.json`: `id`, `mode`, `runner`, `agent`, `track`,
 `stage: "plan"`, `awaiting: null`.
 
+`stage` takes exactly one of five words, and boards key their columns on them:
+`plan`, `build`, `review`, `done`, `abandoned`. Set it when the stage starts —
+`build` before the builder touches anything, `review` before the reviewer reads — as
+its own write, not tacked onto a longer command that may not finish. Any other word
+(`implement`, `fix`, `building`) is unknown to every reader and shows as still planning.
+
+`awaiting` is `null` or the config key of the approval being waited on —
+`approvals.plan`, `approvals.review`, `approvals.each_file` — or `findings` when the
+run has stopped for the user to pick which review findings to fix. Boards read it to
+say what a run is waiting for and where it sits; a word outside this list is shown but
+not understood.
+
 `agent` is the tool this run is happening in — `claude`, `codex`, `agy`, `opencode`,
 `gemini`, or `cursor` — written once at intake and never changed, so a board can say
 which agent to look for when a run is waiting. The tool running this stage knows what