@plot-pm/board 0.17.0 → 0.19.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plot-pm/board",
3
- "version": "0.17.0",
3
+ "version": "0.19.0",
4
4
  "description": "Local Kanban board for Plot — a glanceable view of plan phases from docs/plans, with sprint and story filters",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -54,6 +54,7 @@
54
54
  },
55
55
  "devDependencies": {
56
56
  "@plot-pm/domain": "workspace:*",
57
+ "@plot-pm/fleet": "workspace:*",
57
58
  "@radix-ui/react-checkbox": "^1.3.0",
58
59
  "@radix-ui/react-popover": "^1.1.0",
59
60
  "@tailwindcss/vite": "^4.3.0",
@@ -48,7 +48,7 @@ manifest_string() { # $1=manifest $2=field → prints the value, or nothing
48
48
  #
49
49
  # WHY THIS EXISTS. `free = process alive AND manifest names no branch`, and the
50
50
  # second half was unreachable. `seal_declaration` runs the moment a branch is
51
- # done; `update_manifest_on_hop` runs after `--next` answers and a worktree is
51
+ # done; the hop that follows runs after `--next` answers and a worktree is
52
52
  # built. Between those two points the agent genuinely holds no slice and the
53
53
  # manifest still named the last one, so `isFree`'s empty-branch arm — written,
54
54
  # exported and unit-tested since `a-dispatch-asks-for-a-free-agent` — had no
@@ -60,7 +60,7 @@ manifest_string() { # $1=manifest $2=field → prints the value, or nothing
60
60
  # and the liveness check with it, since both are keyed on the worktree path.
61
61
  # `wavesCount` counts hops and no hop has happened yet. The node one-liner
62
62
  # round-trips the whole object, so every other field survives verbatim, the same
63
- # property `update_manifest_on_hop` records.
63
+ # property the hop's own write records.
64
64
  #
65
65
  # ADDED, NOT SUBSTITUTED. The hop still rewrites `branch` and `worktree`
66
66
  # together; this writes the empty value that sits between two slices. A worker
@@ -69,7 +69,7 @@ manifest_string() { # $1=manifest $2=field → prints the value, or nothing
69
69
  #
70
70
  # ABSENT IS NOT A FAILURE. No manifest — a hand-started loop, an older
71
71
  # dispatcher — means there is nothing to clear and nothing to report, so this
72
- # returns 0 like `update_manifest_on_hop` does.
72
+ # returns 0 like the hop's own write does.
73
73
  clear_manifest_branch() { # $1=manifest
74
74
  local manifest="$1"
75
75
  [ -f "$manifest" ] || return 0
@@ -114,13 +114,13 @@ plot_session_id() {
114
114
  # into both, and they part at the first hop to a new branch: `session` names the
115
115
  # agent and its manifest file for the agent's whole life, while `resumeId` names
116
116
  # the current slice's conversation and is what the board joins the transcript
117
- # on. Reading this field rather than `$PLOT_SESSION_ID` is what makes the
118
- # hop's write (`update_manifest_on_hop` in `plot-worker-loop.sh`) mean anything:
119
- # a reader asks for the handle, and gets the one the hop last wrote.
117
+ # on. Reading this field rather than `$PLOT_SESSION_ID` is what makes the hop's
118
+ # write (`writeResumeId` in `manifest-stamp.ts`) mean anything: a reader asks
119
+ # for the handle, and gets the one the hop last wrote.
120
120
  #
121
- # A PARSE FAILURE AND AN ABSENT MANIFEST ARE ONE ANSWER, the shape
122
- # `assigned_branch` in `plot-worker-loop.sh` already takes: no handle. A hand-started loop has no
123
- # manifest, and a manifest nobody can read is not a handle.
121
+ # A PARSE FAILURE AND AN ABSENT MANIFEST ARE ONE ANSWER: no handle. A
122
+ # hand-started loop has no manifest, and a manifest nobody can read is not a
123
+ # handle.
124
124
  manifest_resume_id() { # $1=manifest → prints the handle, or nothing
125
125
  manifest_string "$1" resumeId
126
126
  }