diff --git a/docs/CONSUMERS.md b/docs/CONSUMERS.md
index e00e085..3160b0a 100644
--- a/docs/CONSUMERS.md
+++ b/docs/CONSUMERS.md
@@ -304,7 +304,8 @@ together at the same pin:
 The consumer keeps its path mapping in `.github/labeler.yml` and its
 review panel plus scope taxonomy in `.github/labels.conf`.
 
-**Additive means additive** (available at `0.3.0` and later — #130): the scope job's only label
+**Additive means additive** (available at `0.3.0` and later — #130): the
+scope job's only label
 write is `POST /issues/{n}/labels`, which adds the derived scopes and removes
 nothing, so a label applied while the job runs survives it. Earlier tags used
 `actions/labeler@v5`, which — even under `sync-labels: false` — replaces the
@@ -522,9 +523,8 @@ allowed to mint issues without the sweep applying `needs-triage`. Label rows use
 `name|color|description`; blank lines are ignored and extra pipes are refused.
 There are no comment lines: every non-blank line must be the `panel=`
 setting, a `panel[<login>]=` row, the `triage-actors=` setting, or a label
-row, so `#`-prefixed prose
-is a parse failure, not a comment (rig #13's conversion found this the hard
-way — keep the file data only).
+row, so `#`-prefixed prose is a parse failure, not a comment (rig #13's
+conversion found this the hard way — keep the file data only).
 Core state, blocker, work-queue, and release labels come from ceremony. Scope
 rows remain consumer-owned because paths and surfaces differ by repository.
 
diff --git a/test/labels-reconcile.test.sh b/test/labels-reconcile.test.sh
index accba15..f1b0aa6 100755
--- a/test/labels-reconcile.test.sh
+++ b/test/labels-reconcile.test.sh
@@ -1027,6 +1027,25 @@ expect "a re-draft after a passed round is building again" \
 REQUESTED="$HUMAN"
 expect "...even with the human requested — a draft never reads needs-human" \
   state:building "$(decide_state)"
+# Round 1's 224-case hole (claude's differential): a draft with a LIVE HUMAN
+# REQUEST plus a standing block or comment fell through to round_state,
+# whose human-request precedence sits above BLOCK/FEEDBACK — and read
+# needs-human on a PR GitHub cannot merge. These are the same inputs as the
+# addressing rows above with REQUESTED="$HUMAN", which is where the
+# criterion can actually fail.
+REQUESTED="$HUMAN" REVIEWS_JSON="$(reviews \
+  "$(rev "$BOT1" CHANGES_REQUESTED head1 no t1)" \
+  "$(rev "$BOT2" APPROVED head1 ok t2)" \
+  "$(rev "$BOT3" APPROVED head1 ok t3)")"
+expect "a draft with a human request and a standing block is addressing" \
+  state:addressing "$(decide_state)"
+REVIEWS_JSON="$(reviews \
+  "$(rev "$BOT1" COMMENTED head1 thoughts t1)" \
+  "$(rev "$BOT2" APPROVED head1 ok t2)" \
+  "$(rev "$BOT3" APPROVED head1 ok t3)")"
+expect "a draft with a human request and an owed reply is addressing" \
+  state:addressing "$(decide_state)"
+
 # The must-not-paper-over combination: a live panel request on a draft is a
 # board defect (the bots ignore drafts by design) and stays VISIBLE as
 # bots-reviewing rather than being absorbed into building.