@plot-pm/board 0.20.0 → 0.22.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.20.0",
3
+ "version": "0.22.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",
package/plot-config.sh CHANGED
@@ -162,6 +162,22 @@
162
162
  # Hosts plans yes | no (no = refuse plan files)
163
163
  # Tracker plot | jira | github-issues | linear (+ URL)
164
164
  # (plot = plans in this repo ARE the tracker; absent = same)
165
+ # Sprint owner plot (absent = same as unset)
166
+ # Independent of `Tracker`: who owns /plot-sprint, as
167
+ # opposed to where issues live. Absent, or any value but
168
+ # `plot`, changes nothing — sprints follow `Tracker` alone,
169
+ # same as before this key existed. `Sprint owner: plot`
170
+ # is the one declaration that lets plot own sprints
171
+ # while `Tracker` still names an external tracker for
172
+ # issues (e.g. a Bitbucket repo with Jira tickets).
173
+ # Tracker approved status
174
+ # the status word a plan's issues are set to when the plan
175
+ # reaches Approved, in the tracker's own vocabulary
176
+ # (`Approved`, `In Progress`). Read by plot-issue-status.sh.
177
+ # Absent or empty = Approved writes nothing. Unlike the
178
+ # `plan:*` label `plot-plan-state.sh` writes at every
179
+ # phase including Approved, this status word is optional
180
+ # and Jira-shaped — the two writes are separate paths.
165
181
  # Tracker delivered status
166
182
  # the status word a plan's issues are set to when the plan
167
183
  # reaches Delivered, in the tracker's own vocabulary
@@ -215,6 +231,15 @@
215
231
  # Read back by /plot-board-setup to verify auth against
216
232
  # the right instance — without it the only runnable
217
233
  # check verifies nothing.
234
+ # Default branch job a job path (`<folder>/<job>`) that builds the default
235
+ # branch outside the multibranch job `Jenkins instance`
236
+ # names. Read by `jenkins_sha_runs` only for the
237
+ # repository's own default branch (`git symbolic-ref
238
+ # refs/remotes/origin/HEAD`); every other branch still
239
+ # reads the multibranch job. `PLOT_JENKINS_JOB` overrides
240
+ # it, as it overrides `Jenkins instance`. Absent: the
241
+ # default branch reads the multibranch job like any
242
+ # other branch, unchanged.
218
243
  #
219
244
  # `Plan template` is a repo-root-relative path to the plan template /plot-idea
220
245
  # instantiates; when absent, /plot-idea falls back to the shipped template.
package/plot-dispatch.sh CHANGED
@@ -824,7 +824,7 @@ request_brief() { # $1 = branch, $2 = slug → 0 if a command was started
824
824
  # being written.
825
825
  _brief_settings="$(bash "$(dirname "${BASH_SOURCE[0]}")/plot-agent-settings.sh" 2>/dev/null || echo "")"
826
826
  ( set -m; cd "$repo_root" \
827
- && PLOT_UNATTENDED=1 PLOT_PLAN_SLUG="$bslug" PLOT_BRIEF_BRANCH="$branch" \
827
+ && PLOT_UNATTENDED=1 PLOT_MAIN_CHECKOUT_WRITER=1 PLOT_PLAN_SLUG="$bslug" PLOT_BRIEF_BRANCH="$branch" \
828
828
  PLOT_AGENT_SETTINGS="$_brief_settings" \
829
829
  exec nohup sh -c "$cmd \"\$@\"" plot-brief \
830
830
  "$(brief_prompt "$branch" "$bslug")" \
@@ -1555,7 +1555,7 @@ start_worker() {
1555
1555
  # the export reaches the wrapper and nothing else.
1556
1556
  { [ -n "$capabilities" ] && export PLOT_CAPABILITIES="$capabilities"; true; } && \
1557
1557
  PLOT_BRANCH="$branch" PLOT_WORKTREE="$wt" \
1558
- PLOT_SLUG="$slug" \
1558
+ PLOT_SLUG="$slug" PLOT_MAIN_CHECKOUT_WRITER= \
1559
1559
  PLOT_SESSION_ID="$session" \
1560
1560
  PLOT_AGENT="${PLOT_AGENT:-}" \
1561
1561
  PLOT_HARNESS="$launch_harness" \
@@ -954,12 +954,14 @@ EOF
954
954
  # REPORTED ONLY WHERE THE LISTING ARRIVED. A failed or throttled call writes no
955
955
  # `.list-arrived`, and carrying its empty cache forward would turn one refusal
956
956
  # into a listing the next pulse trusts.
957
+ #
958
+ # `.list-arrived` IS THE LAST LINE. A scan killed while it prints the rows has
959
+ # printed no `.list-arrived`, so `carried_listing` refuses the partial listing,
960
+ # and `scanOnce` adopts a killed scan's listing only where `.list-arrived` is
961
+ # its last line.
957
962
  report_listing() {
958
963
  [ -n "$HOST_STATE_CACHE" ] || return 0
959
964
  [ -f "$HOST_STATE_CACHE/.list-arrived" ] || return 0
960
- printf 'listing: %s\t%s\t%s\t%s\n' .list-arrived 1 - - >&2
961
- [ -f "$HOST_STATE_CACHE/.list-complete" ] \
962
- && printf 'listing: %s\t%s\t%s\t%s\n' .list-complete 1 - - >&2
963
965
  # WHAT THE LISTING COST, MEASURED RATHER THAN MODELLED. The Bitbucket arm sweeps
964
966
  # one request per tracked branch per state, and this scan is the only thing that
965
967
  # knows how many branches it tracked. A board predicting the number from the
@@ -986,6 +988,9 @@ EOF
986
988
  # sentinel the host payload's plain rows already use.
987
989
  printf 'listing: %s\t%s\t%s\t%s\n' "$key" "$_st" "${_chk:--}" "${_dft:--}" >&2
988
990
  done
991
+ [ -f "$HOST_STATE_CACHE/.list-complete" ] \
992
+ && printf 'listing: %s\t%s\t%s\t%s\n' .list-complete 1 - - >&2
993
+ printf 'listing: %s\t%s\t%s\t%s\n' .list-arrived 1 - - >&2
989
994
  }
990
995
 
991
996
  prefill_pr_states() {