@plot-pm/board 0.14.2 → 0.14.4

package/plot-host.sh

@@ -61,6 +61,30 @@
 #   pr-ready <number>              take a PR out of draft
 #                                 merge the PR
 #   pr-list [--state open|merged|closed|all] [--limit N] [--rich]
+#                                 [--since <iso>] narrows the listing to pull
+#                                 requests the host has seen change since that
+#                                 stamp. Measured 2026-09-21 on this repository:
+#                                 one `--state all` over 933 pull requests takes
+#                                 29 811 ms with the fields the board needs, and
+#                                 the same call over one day takes 943 ms for 3
+#                                 rows — factor 32, with every expensive field
+#                                 still included.
+#                                 THE STAMP IS THE HOST'S OWN, passed through
+#                                 byte-for-byte: a caller that re-renders it
+#                                 sends its own clock's spelling, and a client
+#                                 two seconds fast excludes the PRs updated in
+#                                 that gap from every later window — forever,
+#                                 because the window never reopens.
+#                                 GITHUB NARROWS AND BITBUCKET'S BULK LISTING
+#                                 CANNOT. `gh pr list` takes `--search`; `bb pr
+#                                 list` has no query flag at all (verified
+#                                 against bb 1.9.0: `unknown flag: --query`), so
+#                                 only the per-branch sweep's REST `q=` can
+#                                 carry it. The bulk Bitbucket listing SAYS it
+#                                 could not narrow and answers in full, because
+#                                 a full answer reported as a delta is what
+#                                 would let a caller advance a watermark over a
+#                                 window it never applied.
 #                                 [--repo <owner/repo>] pins the list to ONE
 #                                 repository, exactly as pr-state and pr-merged
 #                                 do. A checkout with remotes on two hosts lets
@@ -70,7 +94,24 @@
 #                                 JSON lines: {"number":N,"title":"...",
 #                                 "state":"...","head":"..."}
 #                                 --rich adds: draft, checks, mergeable, review,
-#                                 url, failing_checks — `failing_checks` names
+#                                 url, updatedAt, failing_checks —
+#                                 `updatedAt` is WHEN THE HOST LAST SAW THE PR
+#                                 CHANGE, in the host's own words and on the
+#                                 host's own clock (`updatedAt` on GitHub,
+#                                 `updated_on` on Bitbucket), "" where the CLI
+#                                 omits it. It is the field a durable store
+#                                 advances its watermark by, and it is the
+#                                 host's rather than this machine's because a
+#                                 client clock two seconds fast would exclude
+#                                 every PR updated in that gap from every later
+#                                 window — permanently, and silently.
+#                                 Measured 2026-09-21: over 937 PRs,
+#                                 `number,updatedAt` is 4715 ms against 5417 ms
+#                                 for the base fields and 18842 ms for
+#                                 `statusCheckRollup`. Asked on --rich ONLY —
+#                                 the plain arm is the cheap one and no shell
+#                                 caller reads a watermark.
+#                                 `failing_checks` names
 #                                 WHICH checks failed, the detail `checks`
 #                                 collapses to one word, from the same response
 #                                 at no extra call; [] on bitbucket and wherever
@@ -534,6 +575,436 @@ pr_list_call() { # "$@"=the host command → payload on stdout, or dies
   printf '%s' "$out"
 }
 
+# The exit code for an answer that is INCOMPLETE rather than absent.
+#
+# SEVEN, BECAUSE THE VOCABULARY IS FULL BELOW IT. `pr_list_failed` spends 6
+# (burst refusal), 5 (throttled) and 3 (everything else); 4 is the backend
+# having no such capability; 1 is a refusal before any call; 0 is a whole
+# answer. Two is left alone deliberately — it is bash's own conventional code
+# for a misused builtin, and a partial answer sharing it could not be told from
+# a shell-level fault the script never intended.
+#
+# NON-ZERO IS THE LOAD-BEARING PART. `plot-fleet-scan.sh:675` reads this code
+# DIRECTLY, not through the transport, and branches on `rc -ne 0`. Exiting 0 on
+# a partial answer would set `HOST_VERDICT=ok` over a page missing a whole
+# state — a complete reading reported over an incomplete one, which is the
+# quiet wrong answer this adapter refuses everywhere else. It would also
+# re-create precisely the state fixed on 2026-08-30, when `pr-list` swallowed
+# its own failure and exited 0 with empty stdout.
+PR_LIST_PARTIAL_RC=7
+
+# Run ONE `pr-list` over several host states, printing what answered.
+#
+# THE BITBUCKET ASYMMETRY THIS EXISTS FOR. `bb pr list` has no `all` state, so
+# `bb_states_for all` expands to three and the arm must call `bb` once per
+# state. GitHub takes `--state all` in a single call and can never reach this
+# shape: there, a failure means nothing was printed.
+#
+# ONE MECHANISM FOR THREE CALL SITES, and that is the point rather than a
+# tidy-up — `pr_list_call`'s own header makes the argument: *"a fix applied by
+# hand six times is a fix that drifts, and the arm that drifts is the one
+# nobody's repo exercises."* The three sites (rich+Jenkins, rich, plain) differ
+# ONLY in the jq program they pipe the payload through, so that program and its
+# arguments are what this takes.
+#
+# WHY THE LOOP CANNOT KEEP `|| exit $?`. That propagation is not a style tic:
+# `pr_list_call` is invoked in a command substitution — a subshell — so the
+# `exit` inside `pr_list_failed` leaves only that subshell, and without the
+# propagation the outer script carries on with an empty payload and jq emits
+# nothing. Collecting across states means the first failure can no longer end
+# the run, so the subshell's exit code is captured and classified instead: a
+# non-zero rc is THIS STATE FAILED, which is a different fact from this state
+# returning an empty list.
+#
+# WHAT IT EXITS WITH:
+#   0                       every state answered.
+#   PR_LIST_PARTIAL_RC      some answered and some did not — the rows of those
+#                           that answered are on stdout, and the failures are
+#                           named on stderr.
+#   the first failure's rc  NO state answered. A total outage keeps the code it
+#                           has always had (3, 5 or 6 by kind), so a genuine
+#                           outage can never read as a partial page.
+#
+# A SINGLE-STATE CALL HAS NO PARTIAL ANSWER TO REPORT. With one state asked,
+# "some answered and some did not" is unreachable by construction: either the
+# one state answered (0) or none did (its own code). The counting below gives
+# that for free rather than by a special case.
+# TWO VARIADIC LISTS, ONE `"$@"`. The host command and the jq arguments are
+# both open-ended, and bash has one positional array — so the jq side travels
+# in this global, set by the caller immediately before the call. It is read
+# once per state and never written here.
+PR_LIST_JQ_ARGS=()
+
+# --- the per-branch sweep (#333) --------------------------------------------
+#
+# THE JOIN ASKS ABOUT BRANCHES AND THE LIST ANSWERS ABOUT A REPOSITORY, and the
+# gap between those two questions is #333. `plot-fleet-scan.sh` holds a dozen
+# branch names and asks `pr-list` for every pull request the repository has
+# ever had, then indexes what came back by `head` and discards the rest.
+# Measured 2026-09-20 on `quatico/quaweb-website`: 12 board rows against 902
+# pull requests, of which the join uses about 1%.
+#
+# THAT WOULD ONLY BE WASTEFUL IF THE LIST WERE WHOLE. It is not. `bb pr list`
+# returns a fixed page of 50 per state, and the repository holds 886 MERGED
+# pull requests — so 836 of them are invisible to the join, and every branch
+# whose pull request is among them reads as having none. That is the fabricated
+# verdict `plot-fleet-scan.sh:876` rules against by name, reached from the one
+# direction the truncation detector below can report but not repair.
+#
+# SO THE SWEEP INVERTS THE QUESTION. Given the branches the caller actually
+# tracks, it asks the REST endpoint about each one by name, through the same
+# `q=` filter `bb` already builds for `--author`:
+#
+#   /repositories/{ws}/{repo}/pullrequests
+#     ?q=state="MERGED" AND source.branch.name="feature/x"&pagelen=50
+#
+# Measured on that repository: `size: 1 | values: 1 | ids: 902` — PR 902 is one
+# of the 836 a listing cannot reach — and a branch with no pull request answers
+# `size: 0`, which is an EXACT ABSENCE rather than a short page.
+#
+# WHY NOT PAGE THE LIST INSTEAD, since the endpoint carries a `next` cursor.
+# Two measurements refuse it. `fleet.ts:184` declares the per-refresh cost and
+# `prRefreshMsFor` stretches the interval by it so hourly spend stays 60;
+# walking all 18 merged pages makes the cost ~21 and the interval follows
+# mechanically, 240 s → 1260 s, with `MAX_CADENCE_STRETCH = 8` taking the worst
+# case to 2.8 hours. And the growth curve runs the wrong way: paging costs grow
+# with the repository's pull-request history — the very quantity whose growth
+# makes #333 worse — while a sweep costs what the CALLER TRACKS and is constant
+# in pull-request count. `pagelen=100` is refused by Bitbucket (HTTP 400), so
+# 50 is the ceiling and 18 pages was a floor rather than a safe estimate.
+#
+# THE LEADING SLASH IS LOAD-BEARING. `bb api` concatenates "${BB_API}${path}",
+# so a path without it yields `…/2.0repositories/…` and an HTTP 403 that reads
+# exactly like a missing scope. A previous plan was rejected for inferring a
+# scope problem from this symptom. It is written once, here, and pinned.
+#
+# `bb`'s OWN PAGINATOR IS NOT REACHED FOR, and that is deliberate rather than
+# incidental: `bb:203` caps at 10 pages — 500 rows at `pagelen=50`, 386 short
+# of 886 — and exits with no error and no marker. A helper that silently
+# returns a prefix is worse here than one that refuses.
+
+# Bitbucket's own state word for one of this adapter's states.
+#
+# The `q=` filter matches Bitbucket's vocabulary, which is upper-case and calls
+# a rejected pull request DECLINED. The adapter's own words are `bb pr list`'s,
+# which are lower-case. One mapping, so a caller never spells a state twice.
+bb_query_state() { # $1=adapter state word → Bitbucket's
+  case "$1" in
+    open)       printf 'OPEN' ;;
+    merged)     printf 'MERGED' ;;
+    declined)   printf 'DECLINED' ;;
+    superseded) printf 'SUPERSEDED' ;;
+    *) die "bb_query_state: unknown state '$1'" ;;
+  esac
+}
+
+# Percent-encode one value for a URL query string.
+#
+# BRANCH NAMES ARE NOT URL-SAFE and this repository proves it: `feature/x` is
+# the ordinary shape, and `/` inside an unencoded `q=` value ends the filter
+# early, so the query would ask about `feature` and answer about the wrong
+# branch — or about none. Encoding is done here rather than by the caller so
+# every query on this path is encoded the same way.
+#
+# `LC_ALL=C` makes the loop byte-wise, so a multi-byte character is encoded as
+# its bytes rather than mangled into one `?`. Branch names carrying non-ASCII
+# are rare and entirely legal.
+url_encode() { # $1=raw → percent-encoded on stdout
+  local _s="$1" _i _c _out=""
+  local LC_ALL=C
+  for (( _i = 0; _i < ${#_s}; _i++ )); do
+    _c="${_s:_i:1}"
+    case "$_c" in
+      [a-zA-Z0-9.~_-]) _out="$_out$_c" ;;
+      *) _out="$_out$(printf '%%%02X' "'$_c")" ;;
+    esac
+  done
+  printf '%s' "$_out"
+}
+
+# Ask Bitbucket about ONE branch in ONE state, and print the `values` array.
+#
+# WHAT IT PRINTS is the endpoint's `values` — a JSON array of 0 or 1 pull
+# request objects, in the SAME shape `bb pr list --json` emits, which is what
+# lets the existing jq programs consume it unchanged. The `--rich` field set
+# (`plot-host.sh:3247`) reads `.id`, `.title`, `.state`, `.source.branch.name`,
+# `.draft` and `.links.html.href`; the REST object carries all six.
+#
+# AN ABSENT ANSWER IS NOT A FAILED ONE, and the exit code is what says which.
+# `size: 0` is an honest absence — the branch has no pull request in this state
+# — and exits 0 with `[]` on stdout. A refused call exits non-zero and prints
+# nothing, so a caller reading the CODE can never mistake an outage for an
+# empty repository. `plot-fleet-scan.sh:891` records that exact confusion
+# happening from the other side: a host exiting 0 while printing nothing once
+# read as "this repo has no PRs".
+#
+# `pagelen=50` rather than 1. A branch may legitimately carry several pull
+# requests in one state — a merged attempt and a merged successor — and the
+# consumers rank them (`fleet.ts`'s `prOutranks`, the scan's OPEN-before-MERGED
+# sort). Asking for one would silently hand them whichever the host listed
+# first, which no adapter promises. Fifty is the endpoint's ceiling and costs
+# the same as one.
+# THE HOST'S OWN FAILURE TEXT LEAVES HERE UNCLASSIFIED, and that is the whole
+# reason this does not call `pr_list_call`. That wrapper classifies a failure
+# ONCE — throttled, burst, or everything else — and composes the sentence a
+# reader acts on. Calling it per branch and again around the sweep classifies
+# twice, and the second pass reads the FIRST pass's prose rather than the host's
+# message: measured here, a `429` became *"the host failed the request and said
+# nothing"* because `Rate limit … exceeded` was no longer in the text being
+# matched. So the raw stderr and the raw exit code travel out of this function
+# untouched, and the single `pr_list_call` that `pr_list_states` already wraps
+# the whole sweep in does the one classification — exactly the layering
+# `bb pr list` has always had.
+bb_branch_query() { # $1=branch $2=adapter state; rest=global bb args → values[]
+  local _br="$1" _st="$2"; shift 2
+  local _q _path _out _rc
+  _q="state=$(url_encode "\"$(bb_query_state "$_st")\"") AND source.branch.name=$(url_encode "\"$_br\"")"
+  # THE WINDOW COMPOSES WITH THE STATE FILTER AND NEVER REPLACES IT. Bitbucket
+  # takes ONE `q=` parameter, so a second one would silently win or lose
+  # depending on the host's parsing — and either way the state clause this query
+  # is built around would be the term at risk. `AND` is the same conjunction the
+  # two terms above already use.
+  #
+  # ENCODED LIKE EVERY OTHER TERM ON THIS PATH, and an ISO stamp needs it: `:`
+  # and `-` are not in `url_encode`'s safe set, and the block header records
+  # what an unencoded value costs — `/` ends the filter early, so the query asks
+  # about one thing and answers about another.
+  #
+  # `>=` RATHER THAN `>`, and the asymmetry with the GitHub arm is deliberate.
+  # Bitbucket's `updated_on` carries microseconds and GitHub's stamp does not,
+  # so an exclusive comparison against a truncated stamp would drop a PR updated
+  # inside the same second. Re-reading one row the caller already holds costs a
+  # row; missing one costs a change nobody ever sees again.
+  [ -n "$PR_LIST_SINCE" ] \
+    && _q="$_q AND updated_on>=$(url_encode "\"$PR_LIST_SINCE\"")"
+  # The space between the two terms is encoded too; `bb api` passes the path to
+  # curl verbatim and an unencoded space would truncate the request line.
+  _q="${_q// /%20}"
+  # THE LEADING SLASH. See the block header — without it this is a 403 that
+  # reads as a scope error.
+  _path="/repositories/{ws}/{repo}/pullrequests?q=${_q}&pagelen=50"
+  # `jq` is applied only to a SUCCESSFUL payload. Piping a failed call into it
+  # would turn the host's exit code into jq's, and a parse error and a spent
+  # quota are not the same fact.
+  _out="$(bb "$@" api "$_path")" || return $?
+  printf '%s' "$_out" | jq -c '.values // []'
+}
+
+# Ask about EVERY tracked branch in one state, printing one combined array.
+#
+# THE SHAPE `pr_list_states` ALREADY EXPECTS. It calls its host command once
+# per state and pipes the result through a jq program that starts `.[]`, so the
+# sweep's job is to produce the same thing a single `bb pr list --state X`
+# would have: one JSON array of pull request objects. The states loop, the row
+# counting, the truncation report and the partial-answer rule above all stay in
+# exactly one place — `pr_list_call`'s own header makes that argument, and a
+# sweep with its own copy of the loop is the drift it names.
+#
+# A BRANCH THAT FAILS ENDS THE STATE, and that is the conservative direction.
+# The combined array is only an answer if every branch in it was asked; one
+# refused query means absence is no longer derivable for that branch, and a
+# short array reported as whole is what #333 IS. So a failure propagates —
+# `pr_list_call` exits — and `pr_list_states` classifies the state as failed,
+# which reaches the caller as a partial answer (exit 7) when other states
+# answered, or as the failure's own code when none did. One vocabulary.
+# THE CALLING CONVENTION IS `pr_list_states`', NOT THIS FUNCTION'S OWN. That
+# helper appends `--state <s> --json` to whatever command it was given, so a
+# sweep that wants to sit in the same slot must accept those two trailing
+# arguments and read the state out of them. Doing it the other way — teaching
+# `pr_list_states` which of its commands is a sweep — would put a backend's
+# shape inside the one piece of this file that has none.
+#
+# `--json` is accepted and ignored. The REST payload is JSON whether or not it
+# is asked for, and refusing a flag the caller must pass would make the slot
+# incompatible for the sake of a distinction with no consequence.
+bb_branch_sweep() { # global bb args… --state <s> --json → one JSON array
+  local _st="" _args=() _acc="[]" _br _rc
+  while [ $# -gt 0 ]; do
+    case "$1" in
+      --state) _st="${2:?}"; shift 2 ;;
+      --json)  shift ;;
+      *) _args+=("$1"); shift ;;
+    esac
+  done
+  [ -n "$_st" ] || die "bb_branch_sweep: no --state"
+  # THE ANSWERS ARE SPOOLED TO A FILE AND JOINED ONCE, NEVER PASSED THROUGH
+  # ARGV. The first version accumulated with
+  # `jq -c --argjson add "$_one" '. + $add'`, which hands a whole branch's
+  # payload to `jq` as a command-line argument — and Linux caps one argument at
+  # `MAX_ARG_STRLEN` (128 KB) where macOS has no such ceiling.
+  #
+  # WHAT THAT COST, measured 2026-09-20 against a Debian container: a branch
+  # carrying 886 merged pull requests is a 147 KB payload, `jq` died with
+  # *"Argument list too long"*, `_acc` came back EMPTY, and the sweep exited 0
+  # while printing no rows AND stating its completeness — a confident claim of
+  # "no pull requests" over a branch that had 886. That is precisely the
+  # fabricated verdict this whole slice exists to remove, rebuilt one layer in.
+  # It passed on macOS and failed only on Linux, which is where CI and every
+  # board run.
+  #
+  # A FILE HAS NO SUCH CEILING, and one `jq -s add` over the spool replaces N
+  # re-parses of a growing accumulator: the old shape re-read every row it had
+  # already seen once per branch, so eleven branches parsed the first branch's
+  # payload eleven times.
+  local _spool
+  _spool="$(mktemp "/tmp/plot-host-sweep.$$.XXXXXX")" || return 3
+  for _br in $PR_LIST_BRANCHES; do
+    # RETURN, NOT EXIT. This runs inside the command substitution
+    # `pr_list_call` wraps the sweep in, so the code must travel back as this
+    # function's status for that wrapper to classify it. An `exit` here would
+    # leave the substitution with an empty payload and a code the wrapper reads
+    # as the sweep's own — the silent empty list `pr_list_call`'s header names.
+    #
+    # The spool is removed on EVERY exit path, including the failing one: a
+    # sweep that gives up mid-way must not leave a payload behind in /tmp.
+    bb_branch_query "$_br" "$_st" ${_args[@]+"${_args[@]}"} >> "$_spool" \
+      || { _rc=$?; rm -f "$_spool"; return $_rc; }
+  done
+  # `-s` reads the whole stream as one array of arrays; `add` flattens it.
+  # An EMPTY spool — every branch answered `[]` — makes `add` yield `null`, so
+  # the fallback keeps the contract that this prints a JSON ARRAY, which is
+  # what the caller's `.[]` needs.
+  _acc="$(jq -c -s 'add // []' < "$_spool")" || { rm -f "$_spool"; return 3; }
+  rm -f "$_spool"
+  printf '%s' "$_acc"
+}
+
+# The branches a sweep asks about, newline-or-space separated. Empty means the
+# caller named none, and the arm keeps the bulk listing it has always used.
+#
+# A GLOBAL FOR `PR_LIST_JQ_ARGS`' REASON, stated two hundred lines above: the
+# host command is already variadic and bash has one positional array. It is set
+# by the `pr-list` arm immediately before the call and read nowhere else.
+#
+# SPACE-SEPARATED, AND GIT IS WHAT MAKES THAT SAFE. `bb_branch_sweep` reads this
+# with an unquoted `for`, so a name carrying whitespace would split into two
+# branches that do not exist. `git check-ref-format` REFUSES a ref name
+# containing a space or a tab — verified 2026-09-20, both exit non-zero — so the
+# separator is git's guarantee rather than a hopeful convention.
+PR_LIST_BRANCHES=""
+
+# The window a sweep's query carries, the host's own stamp. Empty means ask
+# about everything, which is what every caller predating `--since` asks.
+#
+# A GLOBAL FOR `PR_LIST_BRANCHES`' REASON, and it travels the same route: the
+# `pr-list` arm sets it immediately before the call, `bb_branch_sweep` passes
+# through without reading it, and `bb_branch_query` composes it into the one
+# `q=` Bitbucket takes. Threading it through the sweep as an argument would mean
+# teaching that function a parameter it only forwards, and its header already
+# refuses the mirror of that — "teaching `pr_list_states` which of its commands
+# is a sweep would put a backend's shape inside the one piece of this file that
+# has none."
+PR_LIST_SINCE=""
+
+# How many branches the last sweep asked about, and how many answered.
+#
+# THE COMPLETENESS SIGNAL, AND WHY THE ARM STATES IT RATHER THAN THE SCAN
+# INFERRING IT. `plot-fleet-scan.sh:901` writes `.list-complete` when
+# `0 < rows < PR_LIST_LIMIT` — completeness read off a single page's size,
+# which is the only evidence a bulk listing offers. A sweep has no page: each
+# query returns 0 or 1, and `size: 0` is already an exact answer for that
+# branch. So completeness stops being a property of a row count and becomes a
+# property of the SWEEP — every tracked branch was asked and each one answered
+# — which is a stronger claim than the page heuristic could ever make, and one
+# this side can state as a fact rather than leave to be guessed from a number.
+#
+# A PARTIAL SWEEP MUST NOT MAKE THE CLAIM. If any branch's query failed, the
+# survivors are still valid answers and are still printed, but absence is no
+# longer derivable for the branches that went unasked. The line is emitted only
+# when every state answered.
+#
+# ONE COUNTER, NOT TWO. How many branches ANSWERED is not tracked beside this,
+# because a failed branch query ends its whole state (see `bb_branch_sweep`) and
+# the states tally `pr_list_states` already keeps is therefore the same fact. A
+# second counter would be a second answer to one question, and the two would
+# drift the first time either side changed.
+PR_SWEEP_ASKED=0
+
+# State on stderr that the sweep was WHOLE — the licence `.list-complete` needs.
+#
+# THE LINE IS A CONTRACT, not a log. `plot-fleet-scan.sh` reads it to decide
+# whether a cache miss means "no pull request" or "never asked", so its wording
+# is pinned by a test the same way the truncation report's is. It names both
+# counts, because a reader who sees the claim should be able to check it.
+#
+# WHAT IT LICENSES IS A SHORTCUT, NOT THE ANSWER. Without it, a `--ask` caller
+# whose branch missed the join falls through to a `pr-state` call per branch and
+# still gets a correct answer — the per-branch N+1 that #216 removed, which is a
+# COST regression rather than a wrong one. So withholding the line is always
+# safe and is what a partial sweep does.
+#
+# EVERY STATE MUST HAVE ANSWERED. A sweep asks each branch once per state, and a
+# branch's absence is only established when every state was asked about it: a
+# merged pull request missed because the `merged` state failed reads exactly
+# like a branch that never had one. So the claim is made on the STATES' tally,
+# which `pr_list_states` already keeps, rather than on a per-branch count that
+# would have to be reconciled with it.
+#
+# SILENT WHEN NO SWEEP RAN. The bulk path makes no per-branch claim and keeps
+# the row-count heuristic it has always used, so nothing is printed and no
+# existing caller's behaviour changes.
+pr_sweep_report() { # $1=states answered $2=states asked
+  [ -n "$PR_LIST_BRANCHES" ] || return 0
+  [ "$1" -eq "$2" ] 2>/dev/null || return 0
+  echo "plot-host: pr-list sweep complete ($PR_SWEEP_ASKED branches asked, $1 of $2 states answered) — every tracked branch was asked and each answered" >&2
+}
+
+pr_list_states() { # $1=backend $2=limit $3=states $4=jq-program; rest=the host command
+  local backend="$1" limit="$2" states="$3" jq_prog="$4"; shift 4
+  local _s _raw _rc _err _tmp _ok=0 _failed=0 _first_rc=0 _failed_states=""
+  for _s in $states; do
+    _tmp="/tmp/plot-host-prlist-state-err.$$.$_s"
+    # THE SUBSHELL'S CODE IS THE ONLY CHANNEL OUT, so it is captured rather
+    # than propagated. `pr_list_failed` runs INSIDE the substitution and has
+    # already composed its report and its repair line; that text is spooled
+    # here only so the state's name can be added to it before it is passed on.
+    _raw="$(pr_list_call "$@" --state "$_s" --json 2>"$_tmp")"; _rc=$?
+    _err="$(cat "$_tmp" 2>/dev/null)"; rm -f "$_tmp"
+    if [ "$_rc" -ne 0 ]; then
+      # THE HOST'S OWN REPORT GOES FIRST AND IS NEVER PREFIXED. `pr_list_failed`
+      # already composed the sentence that says WHY — a spent quota, a burst
+      # refusal, a DNS blip — and that sentence is what a reader acts on. A line
+      # of this helper's own naming WHICH state, emitted ahead of it, buries the
+      # reason under the bookkeeping: the scan reads the first stderr line into
+      # its error field, and a reader chasing `HTTP 429` would be shown
+      # `state 'open' failed` instead. That is #912's own failure mode — a
+      # message describing the wrong thing — reproduced one layer up, and the
+      # contract suite caught it.
+      [ -n "$_err" ] && printf '%s\n' "$_err" >&2
+      _failed=$((_failed + 1))
+      [ "$_first_rc" -eq 0 ] && _first_rc=$_rc
+      _failed_states="${_failed_states:+$_failed_states, }$_s"
+      continue
+    fi
+    [ -n "$_err" ] && printf '%s\n' "$_err" >&2
+    _ok=$((_ok + 1))
+    # A SWEEP MAKES NO PAGE CLAIM, so the page detector is not asked. Its rule
+    # is about a LISTING that cannot report a total — see its header — and a
+    # sweep's row count has no page semantics at all: the count is how many of
+    # the asked branches have a pull request in this state, and two of eleven is
+    # a complete answer rather than a short one. Running it here would print
+    # "possibly truncated" immediately before `pr_sweep_report` states the
+    # answer was whole, which is the adapter contradicting itself on one stream.
+    #
+    # THE DETECTOR ITSELF IS UNTOUCHED and still fires exactly as it did on
+    # every listing call — `host.test.mjs:3060` passes unedited. What changed is
+    # that a path exists whose premise it was never written about.
+    [ -n "$PR_LIST_BRANCHES" ] || pr_list_report_truncation "$backend" "$limit" "$_s" \
+      "$(jq 'length' <<<"$_raw" 2>/dev/null || echo 0)"
+    printf '%s' "$_raw" | jq -c ${PR_LIST_JQ_ARGS[@]+"${PR_LIST_JQ_ARGS[@]}"} "$jq_prog"
+  done
+  pr_sweep_report "$_ok" "$((_ok + _failed))"
+  [ -z "$_failed_states" ] && return 0
+  if [ "$_ok" -eq 0 ]; then
+    # NO STATE ANSWERED — a total outage, and it keeps the code it has always
+    # had so a real outage can never be read as a partial page.
+    echo "plot-host: pr-list: no state answered; this is not a partial answer" >&2
+    return "$_first_rc"
+  fi
+  echo "plot-host: pr-list: answered $_ok of $((_ok + _failed)) states; missing: $_failed_states" >&2
+  return "$PR_LIST_PARTIAL_RC"
+}
+
 # --- Jenkins CI integration ------------------------------------------------
 # A repo may declare `CI: jenkins` independently of `Git host`. When it does,
 # build status (`checks`) is resolved through `jen` — a multibranch job's
@@ -1683,6 +2154,33 @@ tracker_projects() {
   printf '%s' "$raw" | tr ',' '\n' | sed -E 's/^[[:space:]]+//; s/[[:space:]]+$//' | grep -v '^$' || true
 }
 
+# Reads ONE variable from a `.env`-shaped file. Evaluates nothing.
+#
+# NOT `set -a; . ./.env; set +a`, which is the usual one-liner. It was measured
+# aborting in zsh on a file whose third line holds an unquoted JSON object, and
+# it imports every unrelated variable in the file — which on a credentials path
+# is a reason of its own.
+#
+# NOT `grep '^NAME=' | cut -d= -f2-` either: measured 2026-09-17, that returns
+# EMPTY for an `export `-prefixed line and KEEPS THE QUOTES on a quoted one, and
+# a quoted token reaching `curl -u` produces the 401 this read exists to remove.
+#
+# THE STRIP ORDER IS THE DEFECT, and it has been got wrong twice. Whitespace is
+# stripped BEFORE the quotes and again after. On `T="tok"   ` the `"$` anchor
+# misses if the quotes go first, and the value keeps them:
+#
+#     quotes first: ["tok"]        whitespace first: [tok]
+#
+# `head -1` takes the first assignment, so a duplicated name resolves the way a
+# shell reading top-to-bottom would.
+read_env_var() { # $1=name $2=file → the value, or nothing
+  sed -n "s/^[[:space:]]*\(export[[:space:]]\+\)\{0,1\}$1=//p" "$2" \
+    | head -1 \
+    | sed -e 's/[[:space:]]*$//' \
+          -e 's/^"\(.*\)"$/\1/' -e "s/^'\(.*\)'\$/\1/" \
+          -e 's/[[:space:]]*$//'
+}
+
 # The env var scheme for Jira auth. The plan left the EXACT names open, to be
 # confirmed against a real instance; these follow Jira Cloud's documented Basic
 # scheme (email + API token, base64'd into an Authorization header):
@@ -1695,14 +2193,55 @@ tracker_projects() {
 # This guard is called in the MAIN shell, BEFORE the `$(jira_curl …)` capture —
 # `die3` exits the whole script only from there, not from inside a command
 # substitution where it would end only the subshell and leak a second error.
+#
+# WHERE BOTH ARE UNSET, THE REPOSITORY'S `.env` IS READ. The refusal below named
+# two variables without ever looking where a repository puts them, so an
+# operator holding working credentials — measured 2026-09-17, a 200 from
+# `/rest/api/3/myself` with the same pair — was sent to create a second token.
+# "Export it in your shell" does not reach the board either: it is a long-lived
+# process, which is why `plot-fleetctl.sh` bakes an environment into its unit.
+#
+# THE ENVIRONMENT WINS AND NOTHING IS READ WHERE IT ANSWERS. The file is opened
+# only when BOTH are unset, so a deliberate export is never second-guessed and
+# the common path touches no disk.
+#
+# AND THE SOURCE IS NAMED, which is a requirement rather than a nicety: two
+# tokens may exist, and an operator debugging a 401 must be able to tell which
+# one was used. `plot-board-probe.sh` reports `auth` as three words rather than
+# a boolean for the same reason. THE VALUE IS NEVER PRINTED — only the source.
+jira_load_env_file() {
+  local root env_file email token
+  [ -z "${JIRA_EMAIL:-}" ] && [ -z "${JIRA_API_TOKEN:-}" ] || return 0
+
+  # The repository root, `plot-config.sh:145`'s idiom. NO UPWARD WALK past it:
+  # a search toward $HOME would read a file the operator did not mean for this
+  # repository.
+  root="$(git rev-parse --show-toplevel 2>/dev/null)" || root="."
+  env_file="$root/.env"
+  [ -r "$env_file" ] || return 0
+
+  email="$(read_env_var JIRA_EMAIL "$env_file")"
+  token="$(read_env_var JIRA_API_TOKEN "$env_file")"
+  # BOTH OR NEITHER. Half a Basic credential authenticates nothing, and a
+  # partial pickup would turn today's honest refusal into a 401 further in.
+  [ -n "$email" ] && [ -n "$token" ] || return 0
+
+  JIRA_EMAIL="$email"
+  JIRA_API_TOKEN="$token"
+  export JIRA_EMAIL JIRA_API_TOKEN
+  echo "plot-host: JIRA_EMAIL and JIRA_API_TOKEN read from .env" >&2
+}
+
 jira_require_config() {
   if [ -z "$(tracker_base_url)" ]; then
     die3 "Tracker is jira but no base URL is configured (write 'Tracker: jira https://your.atlassian.net' or set PLOT_JIRA_BASE_URL)"
   fi
+  jira_load_env_file
   if [ -z "${JIRA_EMAIL:-}" ] || [ -z "${JIRA_API_TOKEN:-}" ]; then
     echo "plot-host: Jira needs JIRA_EMAIL and JIRA_API_TOKEN in the environment — an unauthenticated Jira must not read as an empty inbox" >&2
     echo "  Create a token at https://id.atlassian.com/manage-profile/security/api-tokens" >&2
-    echo "  then export JIRA_EMAIL=<your account email> and JIRA_API_TOKEN=<the token>." >&2
+    echo "  then export JIRA_EMAIL=<your account email> and JIRA_API_TOKEN=<the token>," >&2
+    echo "  or put both in this repository's .env (which .gitignore already excludes)." >&2
     exit 3
   fi
 }
@@ -1734,12 +2273,45 @@ jira_curl() {
   return $rc
 }
 
+# The account a Jira record is keyed on — DERIVED, never the email itself.
+#
+# THE EMAIL IS HALF A BASIC CREDENTIAL and this ledger is written on every call:
+# measured 2026-09-17, `$HOME/.plot/state/budget.tsv` held 2448 jira lines on one
+# machine. Until `.env` was read that happened only where somebody exported the
+# variable deliberately; it now happens wherever a `.env` exists — a population
+# that never consented to a machine-local record of it. A change that widens who
+# gets written down owns the writing down.
+#
+# AND IT STAYS PER-ACCOUNT DISTINGUISHABLE, because the field is a MATCH KEY and
+# not a label: `plot-budget.sh:250` is `if ($2 != want_c || $3 != want_a) next`,
+# `spend-rate` publishes it, and `decodeEntry`/`sameKey` read it. One machine's
+# ledger holds three distinct Jira accounts, so a CONSTANT redaction would merge
+# their rate windows and the rate a connector reads becomes the sum of several
+# people's. A hash keeps the key one-to-one while carrying no address.
+#
+# AT THE SOURCE rather than at `budget.tsv`, because fixing the one known writer
+# leaves the next to inherit the defect — `slots-file.ts:185` turns an account
+# into a DIRECTORY NAME and is one `slots.acquire` call away from being live.
+#
+# `jira:` prefixed and truncated to 12 hex: long enough that two accounts on one
+# machine will not collide, short enough to read in a ledger line.
+jira_budget_account() {
+  local raw="${JIRA_EMAIL:-}"
+  [ -n "$raw" ] || { printf 'unknown\n'; return 0; }
+  local h
+  h="$(printf '%s' "$raw" | shasum -a 256 2>/dev/null | awk '{print $1}')"
+  # No hasher, no guess: a raw email must never be the fallback, so an
+  # unhashable account degrades to the same word an absent one uses.
+  [ -n "$h" ] || { printf 'unknown\n'; return 0; }
+  printf 'jira:%s\n' "${h:0:12}"
+}
+
 # Records one Jira call. Jira meters, publishes no header this adapter reads,
 # and this slice does not add header parsing — so the reading is `unknown`,
 # which is never read as free.
 budget_record_jira() {
   [ -z "${PLOT_BUDGET_OFF:-}" ] || return 0
-  budget_append jira "${JIRA_EMAIL:-unknown}" api 1 - - - unknown
+  budget_append jira "$(jira_budget_account)" api 1 - - - unknown
 }
 
 # Split a jira_curl response into (body, status) and enforce the three outcomes.
@@ -1788,12 +2360,20 @@ jira_check() {
 #                               AT LEAST the requested limit — the host may have
 #                               had more that the limit hid. Fewer rows than the
 #                               limit PROVES completeness.
-#   bitbucket (IGNORES --limit): `bb pr list` has no --limit and cannot report a
-#                               total or a cursor, so it can NEVER prove
+#   bitbucket (IGNORES --limit): `bb pr list` has no --limit and reports neither
+#                               a total nor a cursor, so it can NEVER prove
 #                               completeness for a --limit call. Any non-empty
 #                               page is therefore possibly truncated. An empty
 #                               page had nothing to truncate.
 #
+# THE PREMISE ABOVE IS ABOUT `bb pr list`, AND IT WAS ONCE WRITTEN ABOUT
+# BITBUCKET. It said the host "cannot report a total or a cursor" — true of the
+# CLI's listing and false of the REST endpoint behind it, which carries both a
+# `size` and a `next`. That mattered the moment a path existed that could ask:
+# the per-branch sweep (#333) proves completeness exactly, per branch, and this
+# detector is deliberately not asked about it (`pr_list_states`). The rule below
+# is unchanged and still governs every listing call.
+#
 # No --limit was requested → the caller accepted the host's default page and is
 # owed no report, so no existing no-limit caller's behaviour changes.
 #
@@ -1961,6 +2541,18 @@ backend() {
 # written beside it.
 . "$here/plot-budget.sh"
 
+# THE MEMO IS SWEPT ON THE WAY OUT. `budget_rate` caches its reading under
+# `$PLOT_BUDGET_HOME/memo/$$` because a command substitution is a subshell and a
+# variable set inside one does not survive it — see the block above
+# `budget_rate`. A directory keyed on a pid must be removed by the process that
+# made it, or a long-lived machine accumulates one per `plot-host.sh` call.
+#
+# `EXIT` ALONE, deliberately. It runs on a normal return and on an uncaught
+# signal's default termination path is irrelevant here: the sweep is an
+# optimisation's housekeeping, and a cache that outlives one run costs a stale
+# reading at worst, which is the same staleness the memo grants by design.
+trap 'budget_memo_clear' EXIT
+
 # WHO IS SPENDING — read from the CLI's own config, never from an API call.
 #
 # `gh api user` would answer authoritatively and cost one request against the
@@ -2490,13 +3082,30 @@ case "$op" in
     else
       # Establish that bb supports --json BEFORE calling it — Done-when 5.
       bb_require_json
+      # THE SAME KEY SET AS THE GITHUB ARM, INCLUDING `mergeCommit`. This arm
+      # dropped that key on all four of its paths until 2026-09-18, and the
+      # consumer reads it as `.mergeCommit // empty` — where `jq` cannot tell an
+      # absent key from an empty one. So `plot-reconcile-scan.sh` reported
+      # `no merge commit → cannot resolve` for every delivered plan on a
+      # Bitbucket repository, which reads as a host that answered rather than an
+      # arm that never asked. `pr-list`'s arm is the precedent: it emits every
+      # key its GitHub arm does, because absent is not false.
+      #
+      # `merge_commit.hash` IS TAKEN FROM THE PAYLOAD ALREADY FETCHED — the same
+      # field `pr-merge-commit` reads from the same shape. A second `bb` call to
+      # re-ask for it would double a cost measured at ~10s per call.
+      #
+      # `// ""` COLLAPSES THREE SHAPES INTO ONE HONEST VALUE: `merge_commit`
+      # absent on an open PR, the object null, or the hash null. `""` is what
+      # the GitHub arm gives for anything unmerged, so a caller cannot tell the
+      # backends apart.
       if [[ "$ref" =~ ^[0-9]+$ ]]; then
         if out="$(bb ${repo_args[@]+"${repo_args[@]}"} pr view "$ref" --json 2>/tmp/plot-host-err.$$)"; then
           rm -f "/tmp/plot-host-err.$$"
-          jq -c '{number:.id,state:(if .state=="DECLINED" then "CLOSED" else .state end),draft:(.draft // false),url:.links.html.href}' <<<"$out"
+          jq -c '{number:.id,state:(if .state=="DECLINED" then "CLOSED" else .state end),draft:(.draft // false),url:.links.html.href,mergeCommit:(.merge_commit.hash // "")}' <<<"$out"
         else
           err="$(cat "/tmp/plot-host-err.$$" 2>/dev/null)"; rm -f "/tmp/plot-host-err.$$"
-          host_miss_or_fail "$err" '{"number":0,"state":"NONE","draft":false,"url":""}' || exit $?
+          host_miss_or_fail "$err" '{"number":0,"state":"NONE","draft":false,"url":"","mergeCommit":""}' || exit $?
         fi
       else
         # The list CALL succeeding and the branch being absent FROM the list are
@@ -2534,12 +3143,20 @@ case "$op" in
         if [ "$bb_rc" = 0 ]; then
           rm -f "/tmp/plot-host-err.$$"
           out="$(jq -c -s 'add // []' <<<"$out")"
+          # THE BRANCH ARM CARRIES `mergeCommit` TOO, and it is the path that
+          # matters most: `plot-pr-state.sh:33` asks `pr-state "idea/${SLUG}"` —
+          # a branch, not a number — and `:47` reads `.mergeCommit // empty`
+          # from the answer. A fix touching only the numeric pair above would
+          # leave that caller reading an absent key on every Bitbucket repo.
+          #
+          # The hash rides on the page the state walk already fetched, so this
+          # costs no extra call.
           jq -c --arg b "$ref" '[.[] | select(.source.branch.name==$b)][0] // null
-               | if .==null then {number:0,state:"NONE",draft:false,url:""}
-                 else {number:.id,state:(if .state=="DECLINED" then "CLOSED" else .state end),draft:(.draft // false),url:.links.html.href} end' <<<"$out"
+               | if .==null then {number:0,state:"NONE",draft:false,url:"",mergeCommit:""}
+                 else {number:.id,state:(if .state=="DECLINED" then "CLOSED" else .state end),draft:(.draft // false),url:.links.html.href,mergeCommit:(.merge_commit.hash // "")} end' <<<"$out"
         else
           err="$(cat "/tmp/plot-host-err.$$" 2>/dev/null)"; rm -f "/tmp/plot-host-err.$$"
-          host_miss_or_fail "$err" '{"number":0,"state":"NONE","draft":false,"url":""}' || exit $?
+          host_miss_or_fail "$err" '{"number":0,"state":"NONE","draft":false,"url":"","mergeCommit":""}' || exit $?
         fi
       fi
     fi
@@ -2768,17 +3385,60 @@ case "$op" in
     # that wants history says how much; the default stays the host's, so no
     # existing caller's result changes.
     limit=""
+    branches=""
+    # THE WINDOW, AND IT IS THE HOST'S OWN STAMP. Empty means ask about
+    # everything, which is what every caller predating this asks and what a
+    # caller with no stored watermark must ask. A caller that has one sends it
+    # verbatim — see the header: re-rendering it is how a window closes forever.
+    since=""
     while [ $# -gt 0 ]; do
       case "$1" in
         --state) state="${2:?}"; shift 2 ;;
         --limit) limit="${2:?}"; shift 2 ;;
         --rich) rich=1; shift ;;
         --repo) repo_args=(-R "${2:?}"); shift 2 ;;
+        # `${2:?}` REFUSES AN EMPTY VALUE, and that is the point rather than
+        # boilerplate. `--since ""` would reach GitHub as `--search "updated:>"`,
+        # a syntax error the host may answer with everything or with nothing —
+        # and a caller whose watermark was null would send exactly that.
+        --since) since="${2:?}"; shift 2 ;;
+        # THE BRANCHES THE CALLER TRACKS, repeatable, and OPT-IN. Given any,
+        # the Bitbucket arm sweeps the REST endpoint once per branch per state
+        # instead of listing the repository; given none, every existing caller
+        # gets exactly the listing it always got. Four callers pass none today
+        # (`plot-fleet-scan.sh`, `plot-open-pr.sh`, `plot-impl-status.sh` and
+        # `fleet.ts`), so the bulk path stays the default rather than the
+        # legacy one.
+        #
+        # WHY THE CALLER NAMES THEM AND THIS OP DOES NOT GUESS. The same rule
+        # `--repo` states a few lines up: the caller knows which branches its
+        # refs came from and this op cannot. Deriving them here — from remote
+        # refs, say — would make the adapter invent a working set, and a sweep
+        # over the wrong set answers confidently about branches nobody asked
+        # about while missing the ones they did.
+        --branch) branches="${branches:+$branches }${2:?}"; shift 2 ;;
         *) die "pr-list: unknown arg $1" ;;
       esac
     done
     limit_args=()
     [ -n "$limit" ] && limit_args=(--limit "$limit")
+    # THE WINDOW AS GITHUB TAKES IT, built once and appended at all three call
+    # sites — the same argument `pr_list_call`'s header makes about the six
+    # hand-applied fixes: three sites each composing their own search string is
+    # three places for the next window's shape to drift.
+    #
+    # `updated:>` is EXCLUSIVE, and that is the safe direction here. The
+    # watermark is the stamp of a row the caller has ALREADY stored, so
+    # excluding it re-asks nothing; including it would re-fetch that row every
+    # pass for no new information. A PR updated in the same second as the
+    # watermark is the one this can miss, and the periodic full read the caller
+    # is required to keep making is what corrects it.
+    #
+    # THE STAMP IS NOT QUOTED INSIDE THE QUERY. `gh` sends `--search`'s value as
+    # one API parameter and an ISO-8601 stamp carries no space, so a quote would
+    # travel to GitHub as part of the term and match nothing.
+    search_args=()
+    [ -n "$since" ] && search_args=(--search "updated:>$since")
 
     # --- Jenkins CI integration (orthogonal to Git host) ---
     # When `CI: jenkins` is configured, build status comes from Jenkins rather
@@ -2889,8 +3549,8 @@ case "$op" in
           #   $jstatus != "ok"  → Jenkins could not answer; every row `unknown`.
           #   $jentry == null   → the branch has no Jenkins job; `none`.
           #   otherwise         → the joined colour's `checks`, job named on fail.
-          _gh_raw="$(pr_list_call gh ${repo_args[@]+"${repo_args[@]}"} pr list --state "$state" ${limit_args[@]+"${limit_args[@]}"} \
-            --json number,title,state,headRefName,isDraft,mergeable,mergeStateStatus,reviewDecision,url)" || exit $?
+          _gh_raw="$(pr_list_call gh ${repo_args[@]+"${repo_args[@]}"} pr list --state "$state" ${limit_args[@]+"${limit_args[@]}"} ${search_args[@]+"${search_args[@]}"} \
+            --json number,title,state,headRefName,isDraft,mergeable,mergeStateStatus,reviewDecision,url,updatedAt)" || exit $?
           pr_list_report_truncation github "$limit" "$state" \
             "$(jq 'length' <<<"$_gh_raw" 2>/dev/null || echo 0)"
           printf '%s' "$_gh_raw" \
@@ -2910,6 +3570,7 @@ case "$op" in
                   else "unknown" end),
                 review:(.reviewDecision // ""),
                 url:.url,
+                updatedAt:(.updatedAt // ""),
                 failing_checks:(
                   if $jentry != null and $jentry.checks == "failing"
                   then [$jentry.job]
@@ -2918,8 +3579,8 @@ case "$op" in
               }'
         else
           # GitHub without Jenkins (or Jenkins not configured): use GitHub rollup
-          _gh_raw="$(pr_list_call gh ${repo_args[@]+"${repo_args[@]}"} pr list --state "$state" ${limit_args[@]+"${limit_args[@]}"} \
-            --json number,title,state,headRefName,isDraft,statusCheckRollup,mergeable,mergeStateStatus,reviewDecision,url)" || exit $?
+          _gh_raw="$(pr_list_call gh ${repo_args[@]+"${repo_args[@]}"} pr list --state "$state" ${limit_args[@]+"${limit_args[@]}"} ${search_args[@]+"${search_args[@]}"} \
+            --json number,title,state,headRefName,isDraft,statusCheckRollup,mergeable,mergeStateStatus,reviewDecision,url,updatedAt)" || exit $?
           pr_list_report_truncation github "$limit" "$state" \
             "$(jq 'length' <<<"$_gh_raw" 2>/dev/null || echo 0)"
           printf '%s' "$_gh_raw" \
@@ -2941,6 +3602,7 @@ case "$op" in
                   else "unknown" end),
                 review:(.reviewDecision // ""),
                 url:.url,
+                updatedAt:(.updatedAt // ""),
                 failing_checks:[
                   .statusCheckRollup[]? | select((if (.conclusion // "") != "" then .conclusion else (.status // .state) end) as $c
                     | $c=="FAILURE" or $c=="ERROR" or $c=="CANCELLED"
@@ -2949,7 +3611,7 @@ case "$op" in
               }'
         fi
       else
-        _gh_raw="$(pr_list_call gh ${repo_args[@]+"${repo_args[@]}"} pr list --state "$state" ${limit_args[@]+"${limit_args[@]}"} \
+        _gh_raw="$(pr_list_call gh ${repo_args[@]+"${repo_args[@]}"} pr list --state "$state" ${limit_args[@]+"${limit_args[@]}"} ${search_args[@]+"${search_args[@]}"} \
           --json number,title,state,headRefName)" || exit $?
         pr_list_report_truncation github "$limit" "$state" \
           "$(jq 'length' <<<"$_gh_raw" 2>/dev/null || echo 0)"
@@ -2972,7 +3634,11 @@ case "$op" in
       # Forwarding it errors with `unknown flag`, and dropping it silently
       # would serve a short page as if it were the whole set — the quiet wrong
       # answer this adapter refuses elsewhere. So it is dropped AND said.
-      if [ -n "$limit" ]; then
+      # A SWEEP IS NOT A PAGE AND OWES NO SUCH WARNING. `--limit` bounds a
+      # listing; a per-branch query returns that branch's pull requests and
+      # nothing was capped, so the notice would describe a truncation that did
+      # not happen. Said only for the listing it is about.
+      if [ -n "$limit" ] && [ -z "$branches" ]; then
         echo "plot-host: bitbucket ignores --limit $limit; bb returns a fixed page (50 at 1.0.0)" >&2
       fi
       # Establish that bb supports --json BEFORE calling it — Done-when 5.
@@ -2983,17 +3649,47 @@ case "$op" in
       # with no output — an unknown state reading as "no PRs matched", which
       # is the exact failure this translation exists to remove.
       bb_states="$(bb_states_for "$state")" || exit 1
+      # THE ONE PLACE THE SWEEP IS CHOSEN, and it is chosen as a COMMAND rather
+      # than as a flag the three sites below each test. They differ only in the
+      # jq program they pipe the payload through — `pr_list_states`' header says
+      # so — and a sweep that added an `if` to each would make them differ in two
+      # ways, which is how the six hand-applied fixes `pr_list_call` warns about
+      # began. One assignment here; the sites are untouched but for this word.
+      PR_LIST_BRANCHES="$branches"
+      # THE WINDOW REACHES THE SWEEP AND NOT THE LISTING, and the asymmetry is
+      # the CLI's rather than a choice. `bb pr list` takes `--state`, `--author`,
+      # `--json` and `--jq` and no query flag at all — verified against bb 1.9.0,
+      # which answers `unknown flag: --query` — so the only Bitbucket path that
+      # can carry `updated_on` is `bb_branch_query`'s own REST `q=`.
+      #
+      # SAID RATHER THAN SWALLOWED, for the reason `--limit` two blocks up is
+      # said: a caller that asked for a window and got a full listing must not
+      # read the answer as a delta. It would advance its watermark over a window
+      # it never applied — harmless this pass, since a full listing holds every
+      # row a narrow one would, and wrong the moment the caller uses the flag to
+      # decide whether its answer was complete.
+      PR_LIST_SINCE="$since"
+      if [ -n "$since" ] && [ -z "$branches" ]; then
+        echo "plot-host: bitbucket ignores --since $since on a listing; bb pr list has no query flag (bb 1.9.0) — answering in full" >&2
+        PR_LIST_SINCE=""
+      fi
+      PR_SWEEP_ASKED=0
+      bb_cmd=(bb ${repo_args[@]+"${repo_args[@]}"} pr list)
+      if [ -n "$branches" ]; then
+        # A SWEEP'S COST IS THE CALLER'S WORKING SET, and it is reported so the
+        # caller can check the claim it is about to be handed. Branches × states
+        # — 11 branches over 3 states is 33 exact queries, against 3 listings
+        # that answer for 50 of 902 rows.
+        for _b in $branches; do PR_SWEEP_ASKED=$((PR_SWEEP_ASKED + 1)); done
+        bb_cmd=(bb_branch_sweep ${repo_args[@]+"${repo_args[@]}"})
+      fi
       if [ "$rich" = 1 ]; then
         if [ "$ci" = "jenkins" ]; then
           # Bitbucket PR list, `checks` filled from Jenkins — the SAME overlay
           # the GitHub arm uses, which is why it lives above the backend branch.
           # `bb`'s standing `unknown` becomes a real value where Jenkins answers.
-          for _s in $bb_states; do
-            _bb_raw="$(pr_list_call bb ${repo_args[@]+"${repo_args[@]}"} pr list --state "$_s" --json)" || exit $?
-            pr_list_report_truncation bitbucket "$limit" "$_s" \
-              "$(jq 'length' <<<"$_bb_raw" 2>/dev/null || echo 0)"
-            printf '%s' "$_bb_raw" \
-              | jq -c --argjson jmap "$jen_map" --arg jstatus "$jen_status" '.[] |
+          PR_LIST_JQ_ARGS=(--argjson jmap "$jen_map" --arg jstatus "$jen_status")
+          pr_list_states bitbucket "$limit" "$bb_states" '.[] |
                 ($jmap[.source.branch.name] // null) as $jentry |
                 {
                   number:.id, title:.title,
@@ -3008,31 +3704,25 @@ case "$op" in
                   mergeable:"unknown",
                   review:"",
                   url:(.links.html.href // ""),
+                  updatedAt:(.updated_on // ""),
                   failing_checks:(
                     if $jentry != null and $jentry.checks == "failing"
                     then [$jentry.job]
                     else []
                   end)
-                }'
-          done
+                }' "${bb_cmd[@]}" || exit $?
         else
           # Bitbucket without Jenkins: checks remain unknown
-          for _s in $bb_states; do
-            _bb_raw="$(pr_list_call bb ${repo_args[@]+"${repo_args[@]}"} pr list --state "$_s" --json)" || exit $?
-            pr_list_report_truncation bitbucket "$limit" "$_s" \
-              "$(jq 'length' <<<"$_bb_raw" 2>/dev/null || echo 0)"
-            printf '%s' "$_bb_raw" \
-              | jq -c '.[] | {number:.id,title:.title,state:(if .state=="DECLINED" then "CLOSED" else .state end),head:.source.branch.name,draft:(.draft // false),checks:"unknown",mergeable:"unknown",review:"",url:(.links.html.href // ""),failing_checks:[]}'
-          done
+          PR_LIST_JQ_ARGS=()
+          pr_list_states bitbucket "$limit" "$bb_states" \
+            '.[] | {number:.id,title:.title,state:(if .state=="DECLINED" then "CLOSED" else .state end),head:.source.branch.name,draft:(.draft // false),checks:"unknown",mergeable:"unknown",review:"",url:(.links.html.href // ""),updatedAt:(.updated_on // ""),failing_checks:[]}' \
+            "${bb_cmd[@]}" || exit $?
         fi
       else
-        for _s in $bb_states; do
-          _bb_raw="$(pr_list_call bb ${repo_args[@]+"${repo_args[@]}"} pr list --state "$_s" --json)" || exit $?
-          pr_list_report_truncation bitbucket "$limit" "$_s" \
-            "$(jq 'length' <<<"$_bb_raw" 2>/dev/null || echo 0)"
-          printf '%s' "$_bb_raw" \
-            | jq -c '.[] | {number:.id,title:.title,state:(if .state=="DECLINED" then "CLOSED" else .state end),head:.source.branch.name}'
-        done
+        PR_LIST_JQ_ARGS=()
+        pr_list_states bitbucket "$limit" "$bb_states" \
+          '.[] | {number:.id,title:.title,state:(if .state=="DECLINED" then "CLOSED" else .state end),head:.source.branch.name}' \
+          "${bb_cmd[@]}" || exit $?
       fi
     fi
     ;;