Merge pull request #245 from cndgrr/build/242-post-merge-pr-order

fix(issueflow): the deliverable PR is the last merged, not the highest numbered

actions/issueflow-reconcile/issueflow-reconcile.sh

@@ -157,9 +157,19 @@ post_merge_decision() { # $1 merged Refs PR, $2 linked open PR, $3 already handl
   fi
 }
 
-post_merge_pr_for_issue() { # $1 issue; records are ISSUE<TAB>PR
+post_merge_pr_for_issue() { # $1 issue; records are ISSUE<TAB>PR<TAB>MERGED_AT
-  awk -F '\t' -v issue="$1" '$1 == issue { print $2 }' \
+  # The deliverable is the PR that merged last, not the one numbered highest.
-    <<<"${MERGED_REF_PR_RECORDS:-}" | sort -n | tail -n1
+  # Merge order is not number order in this family: crew#176's two Refs PRs
+  # merged #184 at 19:05:16Z and #182 at 19:05:18Z — the higher number two
+  # seconds earlier. Number order is also what spends a marker on the wrong
+  # PR: crew#321 carries `post-merge-transition-pr-326` while its real
+  # deliverable crew#322 — a lower number, merging later — is still open, so
+  # under the old rule the transition it owes could never fire (#242).
+  # mergedAt is ISO-8601 UTC, so it sorts as a string; ties break by highest
+  # PR number so the answer never depends on input order.
+  awk -F '\t' -v issue="$1" '$1 == issue { print $3 "\t" $2 }' \
+    <<<"${MERGED_REF_PR_RECORDS:-}" \
+    | sort -t $'\t' -k1,1 -k2,2n | tail -n1 | cut -f2
 }
 
 post_merge_transition_marker() { # $1 merged PR number
@@ -507,16 +517,24 @@ main() {
     query($owner: String!, $name: String!, $endCursor: String) {
       repository(owner: $owner, name: $name) {
         pullRequests(first: 100, states: MERGED, after: $endCursor) {
-          nodes { number body }
+          nodes { number mergedAt body }
           pageInfo { hasNextPage endCursor }
         }
       }
     }' --jq '.data.repository.pullRequests.nodes[]
-      | .number as $pr | .body | split("\n")[]
+      | .number as $pr | .mergedAt as $merged | .body | split("\n")[]
-      | [$pr, .] | @tsv' \
+      | [$pr, $merged, .] | @tsv' \
-    | while IFS=$'\t' read -r pr body; do
+    | while IFS= read -r record; do
+        # Split on exact tabs rather than IFS: tab is IFS whitespace, so bash
+        # collapses a run of them, and a middle column that ever came back
+        # empty would silently shift the body one field left. The body is
+        # arbitrary text and stays last, where the remainder belongs.
+        pr="${record%%$'\t'*}"
+        rest="${record#*$'\t'}"
+        merged="${rest%%$'\t'*}"
+        body="${rest#*$'\t'}"
         while IFS= read -r issue; do
-          [ -n "$issue" ] && printf '%s\t%s\n' "$issue" "$pr"
+          [ -n "$issue" ] && printf '%s\t%s\t%s\n' "$issue" "$pr" "$merged"
         done < <(refs_references <<<"$body")
       done)"
 

changelog.d/242.md

@@ -0,0 +1,5 @@
+### Fixed
+
+- The issue-flow sweep now reads an issue's deliverable as the `Refs` PR that
+  merged last, not the one numbered highest — merge order is not number order,
+  and the old rule spent the transition marker on the wrong PR (#242).

test/issueflow-reconcile.test.sh

@@ -106,6 +106,44 @@ check "a handled merged Refs episode does not transition again" 0 "KEEP" \
   post_merge_decision 12 false true <<<"- [ ] verify after merge"
 check "merged Refs with all criteria checked does not transition" 0 "KEEP" \
   post_merge_decision 12 false false </dev/null
+
+# The deliverable is the PR that merged last, not the one numbered highest
+# (#242). The first row is crew#176's measured shape — #184 merged
+# 19:05:16Z, #182 merged 19:05:18Z — so it fails against the old sort -n.
+MERGED_REF_PR_RECORDS=$'176\t184\t2026-07-30T19:05:16Z\n176\t182\t2026-07-30T19:05:18Z'
+check "the later merge wins over the higher PR number" 0 "182" \
+  post_merge_pr_for_issue 176
+MERGED_REF_PR_RECORDS=$'12\t100\t2026-07-30T10:00:00Z\n12\t101\t2026-07-30T11:00:00Z'
+check "number order agreeing with merge order still answers the later merge" 0 "101" \
+  post_merge_pr_for_issue 12
+MERGED_REF_PR_RECORDS=$'176\t184\t2026-07-30T19:05:16Z\n321\t326\t2026-08-03T14:44:46Z\n176\t182\t2026-07-30T19:05:18Z\n321\t322\t2026-08-03T16:00:00Z'
+check "interleaved issues each resolve to their own last merge" 0 "182" \
+  post_merge_pr_for_issue 176
+check "...and a neighbouring issue's later merge never leaks in" 0 "322" \
+  post_merge_pr_for_issue 321
+# Two PRs can share a mergedAt second, so the tie-break is specified rather
+# than left to whichever record the sweep happened to emit first.
+MERGED_REF_PR_RECORDS=$'55\t70\t2026-07-30T19:05:16Z\n55\t71\t2026-07-30T19:05:16Z'
+check "an identical mergedAt breaks to the highest PR number" 0 "71" \
+  post_merge_pr_for_issue 55
+MERGED_REF_PR_RECORDS=$'55\t71\t2026-07-30T19:05:16Z\n55\t70\t2026-07-30T19:05:16Z'
+check "...and swapping the two input lines gives the same answer" 0 "71" \
+  post_merge_pr_for_issue 55
+MERGED_REF_PR_RECORDS=$'176\t184\t2026-07-30T19:05:16Z'
+check "an issue with no merged Refs PR still answers empty" 0 "" \
+  test -z "$(post_merge_pr_for_issue 999)"
+check "...so its post-merge decision is KEEP" 0 "KEEP" \
+  post_merge_decision "$(post_merge_pr_for_issue 999)" false false \
+  <<<"- [ ] verify after merge"
+MERGED_REF_PR_RECORDS=""
+# mergedAt must stay a field on the merged-PR node set already fetched: the
+# record shape gets richer, the request count does not (#242).
+check "the sweep still issues exactly two GraphQL queries" 0 "2" \
+  grep -c 'gh api graphql' "$ROOT/actions/issueflow-reconcile/issueflow-reconcile.sh"
+check "...with mergedAt selected on the merged-PR node it already fetched" 0 "" \
+  grep -qF 'nodes { number mergedAt body }' \
+  "$ROOT/actions/issueflow-reconcile/issueflow-reconcile.sh"
+
 check "one closed offsite PR nudges" 0 "NUDGE" offsite_resolved_decision <<<"CLOSED"
 check "two closed offsite PRs nudge" 0 "NUDGE" offsite_resolved_decision <<< $'CLOSED\nCLOSED'
 check "one open offsite PR keeps quiet" 0 "QUIET" offsite_resolved_decision <<< $'CLOSED\nOPEN'
@@ -279,10 +317,10 @@ issue_stub_gh() {
   fi
 }
 
-issue_probe() { # $1 issue, $2 labels, $3 assignees, $4 open PR, $5 merged PR, $6 body
+issue_probe() { # $1 issue, $2 labels, $3 assignees, $4 open PR, $5 merged PR specs, $6 body
   (
-    local assignees="${3:-1}" open_pr="${4:-false}" merged_ref_pr="${5:-}"
+    local assignees="${3:-1}" open_pr="${4:-false}" merged_ref_prs="${5:-}"
-    local body="${6:-}" assignee_json='[]'
+    local body="${6:-}" assignee_json='[]' spec pr merged_at
     [ "$assignees" -eq 0 ] || assignee_json='[{"login":"owner-bot"}]'
     REPO=owner/repo NOW="$INOW"
     ISSUE_LABELS="$2"
@@ -290,11 +328,18 @@ issue_probe() { # $1 issue, $2 labels, $3 assignees, $4 open PR, $5 merged PR, $
       --argjson assignees "$assignee_json" --arg body "$body" \
       '{created_at: $at, assignees: $assignees, body: $body}')"
     if [ "$open_pr" = true ]; then OPEN_PR_ISSUES="$1"; else OPEN_PR_ISSUES=""; fi
-    if [ -n "$merged_ref_pr" ]; then
+    # Records are ISSUE<TAB>PR<TAB>MERGED_AT (#242). A spec is `PR` or
-      MERGED_REF_PR_RECORDS="$(printf '%s\t%s\n' "$1" "$merged_ref_pr")"
+    # `PR@<iso>`; the bare form takes a fixed hour-old merge, which is every
-    else
+    # probe that does not care about merge order. An empty list is no record
-      MERGED_REF_PR_RECORDS=""
+    # at all, so the no-merged-PR probes read exactly as they did.
-    fi
+    MERGED_REF_PR_RECORDS="$(
+      # shellcheck disable=SC2086 # the spec list is deliberately word-split
+      for spec in $merged_ref_prs; do
+        pr="${spec%%@*}"
+        merged_at="${spec#*@}"
+        [ "$merged_at" != "$spec" ] || merged_at="$(iso_at $((INOW - 3600)))"
+        printf '%s\t%s\t%s\n' "$1" "$pr" "$merged_at"
+      done)"
     run() { "$@"; }
     gh() { issue_stub_gh "$@"; }
     reconcile_issue "$1" 2>&1
@@ -432,6 +477,25 @@ check "a later merged Refs PR gets an episode-specific transition comment" 0 ""
 check "...and the later episode still transitions" 0 "" \
   grep -qF 'merged Refs PR -> post-merge; claim released' <<<"$second_transition"
 
+# End to end on the crew#321 shape: the later merge is the *lower*-numbered
+# PR, and its marker is already on the issue. Selecting by number would find
+# no marker for #461, fire the transition a second time, and release a claim
+# the board already released (#242).
+recent_timeline 46
+jq -n --arg b '<!-- issueflow:post-merge-transition-pr-460 -->' \
+  --arg at "$(iso_at $((INOW - 60)))" \
+  '[{"body":$b,"created_at":$at}]' >"$(cfix 46)"
+spent_edit_count="$(wc -l <"$TMP/issue-edits")"
+spent="$(issue_probe 46 claimed 1 false \
+  "461@$(iso_at $((INOW - 7200))) 460@$(iso_at $((INOW - 3600)))" \
+  '- [ ] verify after merge')"
+check "the marker of the later-merged lower-numbered PR is the one read" 0 "" \
+  test -z "$spent"
+# shellcheck disable=SC2016 # positional parameters belong to bash -c
+check "...so the spent transition is not fired a second time" 0 "" \
+  bash -c 'test "$1" -eq "$(wc -l <"$2")" && test ! -f "$3"' _ \
+  "$spent_edit_count" "$TMP/issue-edits" "$TMP/posted-46"
+
 printf '[]\n' >"$(cfix 45)"
 issue_probe 45 $'claimed\npost-merge' >/dev/null
 # shellcheck disable=SC2016 # Markdown backticks are literal evidence
@@ -632,7 +696,7 @@ check "...and the sweep still runs" 0 "" \
 # Keep this at main() granularity: the GraphQL gather and loop are the code
 # a sourced decision probe cannot exercise (#91's lesson).
 printf '%s\n' \
-  '{"data":{"repository":{"pullRequests":{"nodes":[{"number":400,"body":"Refs #40","closingIssuesReferences":{"nodes":[]}}],"pageInfo":{"hasNextPage":false,"endCursor":null}}}}}' \
+  '{"data":{"repository":{"pullRequests":{"nodes":[{"number":400,"mergedAt":"2026-07-30T19:05:16Z","body":"Refs #40","closingIssuesReferences":{"nodes":[]}}],"pageInfo":{"hasNextPage":false,"endCursor":null}}}}}' \
   >"$ARRIVAL/fixtures/graphql.json"
 printf '[{"number":40}]\n' \
   >"$ARRIVAL/fixtures/repos_owner_repo_issues_state_open_per_page_100.json"