fix(dor): scope the dor-stuck mark by ownership, not by the gate label

[TaekeK]

A latent regression from #1002. Nothing is in Building on either board today, which is the only reason it has not fired yet.

The bug

The 💀 notice is the only signal a died build produces — the flow dies with the sidekick, so it never reaches its own error handling. It comments directly on the affected issue, and is meant to do so once; the dor-stuck label is how it remembers:

marked="$(gh issue list … --label dor-stuck --label "$LABEL" …)"
for num in $stalled; do
  case " $marked " in *" $num "*) continue ;; esac    # already told them
  gh issue edit "$num" --add-label dor-stuck
  gh issue comment "$num" --body "💀 …"
done

Before #1002 the walk only ever saw gate-labelled issues, so stalled and marked were drawn from the same population. Since #1002 the walk follows board membership, so stalled can hold an issue carrying no gate label — and --label dor-stuck --label "$LABEL" can never return that issue. Its mark is invisible, the dedupe never fires, and the comment repeats every hour, on an issue that is already broken.

38 open Feature-board items have no gate label, so this was one dead build away from firing.

The fix

Scope the lookup by the same ownership rule the walk uses (belongs_here: bug → Bug Pipeline, otherwise → Feature Pipeline) rather than by the gate label. Equivalent for gate-labelled issues, and the "clear the mark once it recovers" loop now only touches issues this pipeline owns, instead of potentially clearing marks belonging to the other board.

Why the harness missed it

The stub served the marked list regardless of the --label arguments, so the gate-labelled query and the ownership-scoped one looked identical to it. It now models GitHub's AND-ing of repeated --label filters, which is precisely what makes the two distinguishable.

Two assertions added, 33 total. Against main, exactly one fails:

FAIL  an already-marked stalled issue is not commented on again

Also anchored three 💀 assertions on the comment's target (COMMENT: issue comment 370) instead of the phrase "died mid-flight" — that phrase appears in the health digest as well, so they could not distinguish a direct comment from a line in the report. One of them was passing for the wrong reason.

Not fixed here

Two other paths remain gated on the gate label, both deliberately:

• The heal path (§2) — the label is the opt-in that says "this issue belongs in the pipeline". Sweeping every open issue in the repo would drag in meta and docs issues that must never reach the board. The 38 unlabelled issues are therefore un-healable if they ever fall off the board, which is an argument for labelling them, not for changing the query.
• §3b, closed issues still holding a sidekick — pre-existing, unchanged by feat(dor): sweep the whole board, and notify only when findings change #1002. Narrowing it by ownership would mean dropping the label filter from a --limit 50 window sorted by creation date, which risks missing older entries. Left alone rather than traded for a subtler gap.

🤖 Generated with Claude Code