@erclx/canon 5.13.0 → 5.14.1

package/claude/skills/role-orchestrator/scripts/poll.sh

@@ -1,504 +0,0 @@
-#!/usr/bin/env bash
-# Reports pull request movement since the last run. Reads only.
-#
-# The shebang is load-bearing. An earlier version ran under the operator's zsh,
-# where an unquoted parameter expansion does not word-split, so `set -- $line`
-# left every field but the first empty and every head compared unequal. The
-# poll reported movement that had not happened, which is the one failure that
-# makes a detection tool worth less than no tool.
-set -e
-set -o pipefail
-
-# The baseline is per-machine mutable state, so it stays in gitignored scratch
-# even though the script is tracked. Resolving the main worktree root rather
-# than this file's own folder keeps a poll started from a linked worktree
-# reading the baseline a poll started from main wrote.
-MAIN_ROOT="$(git worktree list --porcelain 2>/dev/null | awk '/^worktree /{print $2; exit}')"
-if [ -z "$MAIN_ROOT" ]; then
-  echo "poll: not a git repository, so nothing is classified" >&2
-  exit 1
-fi
-STATE_DIR="$MAIN_ROOT/.canon/tmp/pr/poll"
-mkdir -p "$STATE_DIR"
-STATE="$STATE_DIR/baseline.txt"
-touch "$STATE"
-
-# The base branch is read rather than assumed, since this ships to projects that
-# do not all call it `main`. A wrong base is not a visible failure: merge-tree
-# reports every pull request as conflicted against a ref that does not resolve.
-BASE_REF="$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null || true)"
-if [ -z "$BASE_REF" ]; then
-  BASE_REF="origin/$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name 2>/dev/null || echo main)"
-fi
-BASE_BRANCH="${BASE_REF#origin/}"
-
-# These eight strings are owned elsewhere and pinned here. `review-pr`
-# writes `## Review` and `## Review closed`, and states the full eight-heading
-# set once, beside the threshold it already states once. `review-address`
-# writes `## Review response`, `## Rebase`, and `## Post-review findings`, the
-# last for a finding a worker produces after a close-out rather than in answer
-# to one already on the thread. `canon pr evidence`, run through `git-pr` and
-# `git-followup`, writes `## Evidence`. `review-ui` writes `## UI review` and
-# `## UI review closed`. All these surfaces ship separately, so a heading added
-# in any of them breaks a test here that no check reaches across.
-#
-# All four families match on the first line alone so the tests stay
-# symmetric. The reply family carries `## Rebase` and `## Post-review
-# findings` beside `## Review response` because neither answers a comment
-# already on the thread, which is why both were kept outside the `## Review`
-# family rather than folded into it. `## Evidence` answers no comment either,
-# and it stays out of the reply family rather than joining it: an evidence
-# comment is not a response to a review, so counting it as one would send the
-# poll back for a re-review nothing asked for. It is excluded from the
-# unmatched filter below instead, on its own.
-#
-# The review family reaches this file through `canon pr review-state` rather
-# than through a filter of its own, so the two headings are pinned here only in
-# the fallback that answers for a target whose CLI predates that verb.
-# The count alone answers whether a reply is new to this script, which is not
-# the same question as whether it is newer than the pass it answers. The stamp
-# of the newest reply comes out of the same selection so the recency test costs
-# no second filter, and it is the one this file compares against `submittedAt`.
-JQ_REPLY_STATE='
-  [ .comments[]
-    | select((.body // "") | split("\n")[0] | rtrimstr("\r")
-             | . == "## Review response" or . == "## Rebase"
-             or . == "## Post-review findings")
-  ] as $replies
-  | ($replies | length | tostring)
-    + " "
-    + ([ $replies[] | .createdAt // empty | fromdateiso8601 | floor ]
-       | max // 0 | tostring)
-'
-# A comment matching neither family above is the gap this filter exists to
-# surface rather than absorb: a worker inventing a sixth heading used to reach
-# this script as silence, indistinguishable from no comment at all. The count
-# is read the same way the reply count is, a rising value against the baseline
-# being new to this script, and the newest heading's text rides along for the
-# report. It carries its spaces intact rather than encoded, since it is the
-# last field on both sides of the pipe: `${unmatched_state#* }` below strips
-# only the first space, and `read -r` further down hands its last named
-# variable the rest of the line whole. Neither reads a heading's own spaces
-# as a field separator, so a heading round-trips verbatim into the report a
-# person reads when deciding whether to answer it by hand.
-JQ_UNMATCHED_STATE='
-  [ .comments[]
-    | (.body // "") | split("\n")[0] | rtrimstr("\r")
-    | select(startswith("## "))
-    | select(. != "## Review" and . != "## Review closed"
-              and . != "## Review response" and . != "## Rebase"
-              and . != "## Post-review findings" and . != "## Evidence")
-  ] as $unclassified
-  | ($unclassified | length | tostring)
-    + " "
-    + (($unclassified | last) // "none")
-'
-
-# Four fields describe the last review pass: the commit it covered, whether it
-# left anything owed, how long it has sat, and the instant it read. All four come
-# out of `canon pr review-state`, which is the one place the read-time marker
-# `review-pr` writes into its own body is parsed. Reading `commit.oid` and
-# `submittedAt` off the thread here instead is what this replaces: GitHub stamps
-# both when a review is submitted, so a push landing between a pass's read and
-# its post moves them onto a commit that pass never opened, and `SEEN` below then
-# reports it covered. That is the failure that loses work silently, measured on
-# a pull request in this toolkit on 2026-09-07.
-#
-# `review-pr` posts `## Review` exactly when a dispatch is owed, per the
-# threshold that skill states, so the heading is what separates a thread waiting
-# on a worker from one nothing is owed on. A project editing the two comment
-# filters above for its own headings has nothing to edit here, since the verb
-# owns the review family now.
-#
-# The age is derived from `submittedAt` alone and the pass instant from
-# `readAt // submittedAt`, which is deliberate rather than an oversight. The age
-# measures how long a posted comment has waited on a human, a question about the
-# submission, and the pass instant bounds what that pass had read, a question
-# about the read. jq computes the elapsed seconds itself, since `date -d` is
-# GNU-only and this script runs wherever the plugin is installed. A review
-# carrying no stamp reads as age zero and classifies nothing, which is the same
-# answer the carry-forward path gives a pull request this run could not read, and
-# reads as pass instant zero, where it sends a reply to be reported rather than
-# suppressed. The two readers fail in opposite directions on the same absent
-# field on purpose.
-#
-# `source` is the field this branches on rather than the exit status, since an
-# operator shell profile can wrap canon in a function that flattens every
-# refusal to zero. A refusal record carries `reason` and no `source`, and it
-# yields nothing here, which is what sends the read to the fallback below. A
-# record read as a bare answer instead would report every refusal as a pull
-# request nobody has reviewed.
-JQ_SCOPE_FROM_VERB='
-  if (.source // "") == "" then empty else
-  (.commit // "none") as $prior
-  | (.state // "none") as $heading
-  | (if .submittedAt == null then 0
-     else (.submittedAt | fromdateiso8601 | floor) end) as $at
-  | (if .readAt == null then $at
-     else (.readAt | fromdateiso8601 | floor) end) as $read
-  | $prior + " " + $heading
-    + " " + (if $at == 0 then "0" else (((now | floor) - $at) | tostring) end)
-    + " " + ($read | tostring)
-  end
-'
-# The fallback for a target whose CLI predates the verb, mirroring the `canon pr
-# head` fallback below. It reads the submission stamps and therefore carries the
-# defect the verb closes, which is the behavior this poll already had. It does
-# not parse the marker: a second reader of that format here is the drift the
-# verb exists to prevent, and one that lags the format silently reports a
-# reviewed commit as unreviewed.
-JQ_SCOPE_FALLBACK='
-  [ .reviews[]
-    | select((.body // "") | split("\n")[0] | rtrimstr("\r")
-             | . == "## Review" or . == "## Review closed")
-  ] | last
-  | if . == null then "none none 0 0"
-    else (if .submittedAt == null then 0
-          else (.submittedAt | fromdateiso8601 | floor)
-          end) as $at
-      | ((.commit.oid // "none")
-         + " "
-         + (.body | split("\n")[0] | rtrimstr("\r")
-            | if . == "## Review" then "open" else "closed" end)
-         + " "
-         + (if $at == 0 then "0" else (((now | floor) - $at) | tostring) end)
-         + " "
-         + ($at | tostring))
-    end
-'
-
-# The UI family is posted as a pull request review the way the code family is,
-# so it is read off `.reviews` rather than `.comments`. No verb parses it, so
-# the filter here is its only reader. The newest UI heading decides the state,
-# and the head it covered comes from the `review-ui` marker on the body's last
-# line, since the submission stamp moves onto a commit pushed while the pass
-# drove. A body carrying no marker falls back to that stamp.
-JQ_UI_STATE='
-  [ .reviews[]
-    | select((.body // "") | split("\n")[0] | rtrimstr("\r")
-             | . == "## UI review" or . == "## UI review closed")
-  ] | last
-  | if . == null then "none none"
-    else (.body | split("\n")[0] | rtrimstr("\r")
-          | if . == "## UI review" then "open" else "closed" end) as $state
-      | ([ .body | split("\n")[] | rtrimstr("\r") | select(. != "") ]
-         | last // ""
-         | (capture("^<!-- review-ui: head=(?<sha>[0-9a-f]{7,40}) -->$").sha)
-           // null) as $marked
-      | $state + " " + ($marked // .commit.oid // "none")
-    end
-'
-
-# An open pass this old has nobody on it. The cycle it has to clear is a review
-# landing and a worker pushing a follow-up, measured between ten and thirty
-# minutes across a day of runs on 2026-08-14, so two hours sits about four times
-# past the slowest observed and still well inside a working session. Shorter
-# starts catching the slow healthy case this threshold exists to exclude, and
-# longer lets a dead dispatch sit past the point a person would have noticed.
-# A project whose workers run longer than that raises it here.
-STALE_AFTER=7200
-
-# A pull request this run could not read keeps the line it had, so the GONE
-# sweep below does not read the gap as a merge and the baseline does not lose
-# the head it already knew. Saying so on stderr is the point: a silent skip is
-# how the failure this script was fixed for went unnoticed for a session.
-carry_forward() {
-  local n=$1 reason=$2 old
-  old=$(grep "^$n " "$STATE" || true)
-  if [ -n "$old" ]; then
-    # Every other classification compares a field against itself on a carried
-    # line, so it fires nothing. That is also what keeps the two stamps unread
-    # here: the baseline never held them, so both arrive empty, and the count
-    # test in front of them fails before either reaches a numeric comparison.
-    # STALLED reads a heading that is carried too, so
-    # the field is blanked to a value no branch matches. Echoing it intact would
-    # classify a pull request this run never reached while stderr below says the
-    # opposite, and one successful read restores it a run later. An already
-    # reported thread keeps its marker, or an unreadable run would let the same
-    # thread be reported a second time.
-    echo "$old" | awk '{ if ($6 != "reported") $6 = "carried"; print }'
-    echo "poll: #$n $reason, so it keeps its last known state and goes unclassified" >&2
-  else
-    echo "poll: #$n $reason, and it has no last known state, so it goes unclassified" >&2
-  fi
-}
-
-snapshot() {
-  local numbers n payload head prior resp merges scope review_scope review_state
-  git fetch -q origin "$BASE_BRANCH" 2>/dev/null || true
-
-  # A failed list reaches the caller as no open pull requests, and that reports
-  # every tracked one as GONE. It is a louder wrong answer than the one this
-  # script was fixed for, so the run aborts rather than classify on it.
-  if ! numbers=$(gh pr list --state open --json number --jq '.[].number' 2>/dev/null); then
-    echo "poll: the open pull request list could not be read" >&2
-    return 1
-  fi
-
-  for n in $numbers; do
-    # A query that failed and a pull request with genuinely no reviews both
-    # arrive as an empty result. Reading the first as the second reported a
-    # reviewed pull request as never reviewed, which routes the re-review to
-    # the first-pass branch, where it reports and stops, so the movement sits
-    # unreviewed until a person notices. One query per pull request gives that
-    # failure a single place to surface.
-    if ! payload=$(gh pr view "$n" --json headRefOid,reviews,comments 2>/dev/null); then
-      carry_forward "$n" "could not be read"
-      continue
-    fi
-
-    # The tip is the authority for the head, not the pull request object. That
-    # object lags the ref by up to a minute after a push, so MOVED fired late
-    # and the merge-tree read below judged a commit the branch had already left
-    # behind. Read on the record's own field rather than on the exit, since an
-    # operator shell profile can wrap canon in a function that flattens it.
-    # The trailing assignment is load-bearing under `set -e` and `set -o
-    # pipefail` at the top of this file. Every refusal exits 1, and a refusal
-    # here is ordinary rather than exceptional, so an unguarded pipeline would
-    # end the whole poll on the first pull request whose branch was deleted.
-    head=$(canon pr head "$n" --json 2>/dev/null | jq -r '.tip // empty') || head=""
-
-    # The object's head is the fallback rather than the source. This script
-    # ships with the plugin and the verb ships with the CLI, so a target on an
-    # older binary reaches no `pr head` at all, and answering there with the
-    # lagging head is the behavior this poll already had.
-    if [ -z "$head" ]; then
-      head=$(jq -r '.headRefOid // empty' <<<"$payload")
-    fi
-
-    if [ -z "$head" ]; then
-      carry_forward "$n" "returned no head"
-      continue
-    fi
-
-    # Split here rather than carried whole, because the count keeps the fourth
-    # column every baseline written so far already reads, and the stamp goes to
-    # the end of the line beside the pass stamp it is compared against.
-    reply_state=$(jq -r "$JQ_REPLY_STATE" <<<"$payload")
-    resp=${reply_state%% *}
-    reply_at=${reply_state##* }
-
-    # The marker `review-pr` writes is the authority for what a pass covered,
-    # and the verb is the only reader of it. The trailing assignment is
-    # load-bearing under `set -e` and `set -o pipefail`: every refusal exits 1,
-    # and a refusal here is ordinary rather than exceptional, so an unguarded
-    # pipeline would end the whole poll on the first pull request it could not
-    # answer for.
-    scope=$(canon pr review-state "$n" --json 2>/dev/null) || scope=""
-    review_scope=$(jq -r "$JQ_SCOPE_FROM_VERB" <<<"$scope" 2>/dev/null) || review_scope=""
-    if [ -z "$review_scope" ]; then
-      review_scope=$(jq -r "$JQ_SCOPE_FALLBACK" <<<"$payload")
-    fi
-    # Four space-separated fields. The commit leads, so the line below carries
-    # it as its own third the way every baseline already reads, and the other
-    # three ride on as the sixth, seventh, and eighth.
-    prior=${review_scope%% *}
-    review_state=${review_scope#* }
-    # Split the same way as the reply state, carried as the line's tenth and
-    # eleventh fields.
-    unmatched_state=$(jq -r "$JQ_UNMATCHED_STATE" <<<"$payload")
-    unmatched_count=${unmatched_state%% *}
-    unmatched_heading=${unmatched_state#* }
-
-    # One token, so the heading above stays the line's last field and keeps its
-    # spaces. A marker may name a short sha, so coverage is a prefix match.
-    ui_read=$(jq -r "$JQ_UI_STATE" <<<"$payload")
-    ui_heading=${ui_read%% *}
-    ui_commit=${ui_read#* }
-    if [ "$ui_heading" = none ]; then
-      ui_state=none
-    elif [ "$ui_commit" != none ] && [[ "$head" == "$ui_commit"* ]]; then
-      ui_state="$ui_heading-head-${ui_commit:0:7}"
-    else
-      ui_state="$ui_heading-behind-${ui_commit:0:7}"
-    fi
-
-    # `gh pr view --json mergeable` reports UNKNOWN until GitHub finishes
-    # computing it, which is exactly when a poll asks. merge-tree answers
-    # locally against the base this machine has, so it never returns UNKNOWN.
-    git fetch -q origin "pull/$n/head" 2>/dev/null || true
-    if ! git cat-file -e "${head}^{commit}" 2>/dev/null ||
-      ! git rev-parse --verify -q "$BASE_REF" >/dev/null; then
-      # merge-tree exits non-zero on a ref it cannot resolve as well as on a
-      # real conflict, and the two are indistinguishable from its status. Both
-      # sides are checked, because an unresolvable base reports every pull
-      # request as conflicted rather than one, which is the louder half.
-      merges=unknown
-    elif git merge-tree --write-tree "$BASE_REF" "$head" >/dev/null 2>&1; then
-      merges=clean
-    else
-      merges=conflict
-    fi
-
-    echo "$n $head ${prior:-none} $resp $merges $review_state $reply_at $unmatched_count $ui_state $unmatched_heading"
-  done
-}
-
-# The reason is printed by whichever branch failed, since this one cannot tell
-# a list query from a parse and naming either would misattribute the other.
-if ! NEW=$(snapshot); then
-  echo "poll: nothing is classified this run and the baseline is unchanged" >&2
-  exit 1
-fi
-CHANGED=0
-# The baseline is written from here rather than from the snapshot, because the
-# heading field is the one column a classification rewrites. STALLED reports a
-# standing condition rather than a transition, so without a written marker it
-# would fire on every later run and the board would never read "No movement."
-FINAL=""
-
-while read -r n head prior resp merges heading age pass_at reply_at unmatched_count ui unmatched_heading; do
-  [ -z "$n" ] && continue
-  state=$heading
-  old=$(grep "^$n " "$STATE" || true)
-  if [ -z "$old" ]; then
-    # A pull request first seen here may already carry a pass, when it opened
-    # and was reviewed between two runs. Reporting it as new invites a first
-    # pass the thread already has.
-    if [ "$prior" = "$head" ]; then
-      echo "SEEN      #$n at ${head:0:7}, first sighting, already covered by a pass"
-    elif [ "$merges" = unknown ]; then
-      # `unknown` means no merge was attempted, so it is left off the line
-      # rather than printed where a verdict belongs.
-      echo "OPENED    #$n at ${head:0:7}"
-    else
-      echo "OPENED    #$n at ${head:0:7}, $merges against $BASE_BRANCH"
-    fi
-    CHANGED=1
-    FINAL+="$n $head $prior $resp $merges $state $unmatched_count $ui"$'\n'
-    continue
-  fi
-  old_head=$(echo "$old" | cut -d' ' -f2)
-  old_resp=$(echo "$old" | cut -d' ' -f4)
-  old_merges=$(echo "$old" | cut -d' ' -f5)
-  # Only the marker is read off this field, so a baseline written before it
-  # existed yields empty and reads as not yet reported, which is what it is. The
-  # age decides the rest, so the first run after an upgrade needs no history and
-  # classifies a thread already past the threshold rather than waiting a run.
-  old_heading=$(echo "$old" | cut -d' ' -f6)
-  old_unmatched=$(echo "$old" | cut -d' ' -f7)
-  # Written from the first run that read a UI pass, so an older baseline yields
-  # empty and the first UI state this script sees is reported as new.
-  old_ui=$(echo "$old" | cut -d' ' -f8)
-
-  # A conflict arrives from the base moving, not from the branch, so it is
-  # reported on the transition rather than only when the head changes.
-  if [ "$merges" = conflict ] && [ "$old_merges" != conflict ]; then
-    echo "CONFLICT  #$n no longer merges into $BASE_BRANCH"
-    CHANGED=1
-  fi
-
-  # A rising count is what is new to this script, the same test RESPONSE
-  # below runs against the reply family. It fires on a tracked pull request
-  # only: a first sighting reports SEEN or OPENED and takes whatever count
-  # already sits on the thread as its starting baseline rather than flagging
-  # history retroactively. A carried line supplies neither, since
-  # carry_forward re-echoes the shorter baseline shape rather than a full
-  # snapshot line, so both sides default to zero the way old_unmatched
-  # already does.
-  if [ "${unmatched_count:-0}" -gt "${old_unmatched:-0}" ]; then
-    echo "UNMATCHED #$n posted under '$unmatched_heading'"
-    CHANGED=1
-  fi
-
-  # The UI pass reports on its transition, the way CONFLICT does, since its
-  # state moves on a post or on a push and either one is the moment it is owed
-  # an action. A carried line supplies no state, so nothing fires on it. A
-  # verdict a push left behind reports separately from MOVED above, since it
-  # owes a fresh UI pass rather than a code re-review. The state carries the
-  # covered commit, so a second UI pass at a new head reads as a transition even
-  # when its heading repeats.
-  if [ -n "$ui" ] && [ "$ui" != none ] && [ "$ui" != "$old_ui" ]; then
-    ui_heading=${ui%%-*}
-    ui_commit=${ui##*-}
-    case "$ui" in
-    open-head-*)
-      echo "UI-OPEN   #$n open at $ui_commit"
-      ;;
-    closed-head-*)
-      echo "UI-CLOSED #$n closed at $ui_commit"
-      ;;
-    *)
-      echo "UI-STALE  #$n $ui_heading at $ui_commit, behind ${head:0:7}"
-      ;;
-    esac
-    CHANGED=1
-  fi
-
-  if [ "$head" != "$old_head" ]; then
-    if [ "$prior" = "none" ]; then
-      echo "MOVED     #$n -> ${head:0:7}, never reviewed"
-    elif [ "$prior" = "$head" ]; then
-      # An out-of-band pass reviewed this head before the poll saw it move, so
-      # the range is empty because it is covered rather than because it broke.
-      # Without this the force-push branch below claims a rewrite that never
-      # happened, which is the class of false report the shebang note names.
-      echo "SEEN      #$n -> ${head:0:7}, already covered by the last pass"
-    else
-      # The range needs both commits local, and a force-push leaves the prior
-      # one unreachable. Count what resolves and say nothing when it does not,
-      # rather than reporting a zero that reads as no new work.
-      git fetch -q origin "pull/$n/head" 2>/dev/null || true
-      since=$(git log --oneline "${prior}..${head}" 2>/dev/null | wc -l | tr -d ' ' || true)
-      if [ -n "$since" ] && [ "$since" != "0" ]; then
-        echo "MOVED     #$n -> ${head:0:7}, $since commit(s) since your last pass"
-      else
-        echo "MOVED     #$n -> ${head:0:7}, range unresolved, likely force-pushed"
-      fi
-    fi
-    CHANGED=1
-  elif [ "$resp" -gt "$old_resp" ] &&
-    { [ "$pass_at" = 0 ] || [ "$reply_at" -gt "$pass_at" ]; }; then
-    # The count says the reply is new to this script and the stamp says it is
-    # newer than the pass, and both are needed. A worker answers a finding and
-    # the reviewing session closes out seconds later, so the count alone reports
-    # an answered thread on the next run and the session spends a turn learning
-    # `review-pr` will refuse it. The gaps observed were 96, 24, and 35
-    # seconds, which is a reviewing session reading a reply and posting, so this
-    # is the ordinary handback rather than a race.
-    #
-    # A pull request carrying no pass at all reads as stamp zero and reports,
-    # which is the case the count was the right test for: a reply with nothing
-    # behind it is a worker talking to nobody and worth the turn. The test is
-    # strictly greater to match the guard `review-pr` states on the same
-    # two fields, which drops a reply landing inside the same second as the
-    # pass, a narrower failure than the one it removes.
-    #
-    # The gate sits in the condition rather than in the body so a suppressed
-    # reply falls through to STALLED below, which is a thread this run should
-    # still be able to reach.
-    echo "RESPONSE  #$n answered with no new commit"
-    CHANGED=1
-  elif [ "$heading" = open ] && [ "$old_heading" != reported ] &&
-    [ "$prior" = "$head" ] && [ "$age" -ge "$STALE_AFTER" ]; then
-    # Three things at once: the last pass is open, it covers the head so no
-    # commit followed it, and the two branches above found no reply either. The
-    # open heading is posted exactly when a dispatch is owed, per the threshold
-    # `review-pr` states, so a pass owing one left it here at any grade
-    # it carried. Any two of these describe an ordinary review waiting on a
-    # worker, which is why the age carries the third: without it every
-    # dispatched worker is reported minutes into the work it was sent to do,
-    # and a signal firing on the healthy path is one an operator learns to
-    # skip. The report still asks for a confirmation rather than asserting.
-    echo "STALLED   #$n open at ${head:0:7}, no commit or reply in $((age / 3600))h"
-    state=reported
-    CHANGED=1
-  elif [ "$heading" = open ] && [ "$old_heading" = reported ]; then
-    # Nothing above fired, so the thread has not moved since it was reported.
-    # Carry the marker rather than the freshly derived heading, or the state
-    # re-enters next run and STALLED oscillates instead of reporting once.
-    state=reported
-  fi
-  FINAL+="$n $head $prior $resp $merges $state $unmatched_count ${ui:-$old_ui}"$'\n'
-done <<<"$NEW"
-
-while read -r n _rest; do
-  [ -z "$n" ] && continue
-  echo "$NEW" | grep -q "^$n " || {
-    echo "GONE      #$n merged or closed"
-    CHANGED=1
-  }
-done <"$STATE"
-
-[ "$CHANGED" -eq 0 ] && echo "No movement."
-printf '%s' "$FINAL" >"$STATE"