mesh-issues: read merged from the pull request, not the state, so a closed one is withdrawn (hq issue 483)

mesh-delivery says stopped for a pull request closed unmerged too; read as
merged, it was said stuck to the operator for good. Cite ADR 0284 for the
worker rules, which the comments gave as 0283.

modules/mesh-issues/README.md

@@ -30,13 +30,13 @@ what it refuses.
 | `reserve` | `kind` (`decision` or `research`), optionally `for` (one line: what the record is about) | the next number of that kind, spent forever; answers `kind` and `number` (and `prefix`, the number as the record's name starts with it); see below |
 
 **The cycle's rules, at the write** (hq playbook 03, which `00-META/checks/cycle.py` enforced on the
-folders until the import, and hq ADR 0283): a status is one of `open`,
+folders until the import, and hq ADR 0284): a status is one of `open`,
 `diagnosing`, `located`, `fixing`, `resolved`, `wontfix`; `diagnosing` and `fixing` need `by`; `located` needs
 `located-in`; `resolved` is reached only from `fixing` and needs `located-in` and `fixed-by`; a core issue (located in the controller, the node-engine, the tool runner,
 the SDK, or the catalogue's bus, forge or build agent) resolves with `replay` or `replay-none`; `wontfix`
 needs a `reason`. A refused change changes nothing and says which rule refused it.
 
-**Who works on it** (hq ADR 0283). A move to `diagnosing` or `fixing` names in `by` the issue's **worker**: who
+**Who works on it** (hq ADR 0284). A move to `diagnosing` or `fixing` names in `by` the issue's **worker**: who
 works on it and its node, as `who@node` (such as `fix-399@g14` or `jochen@shanks`, kept in lower case). The issue
 keeps its worker (`worker`: `by`, `since`, `active`) while it stays at either status; any other status ends the
 work. `get` shows it, with `worker-stale`, and each `list` row shows `worker`, `since` and `stale`. A move to either
@@ -113,7 +113,10 @@ nothing.
 **The fixes of an issue are its `fixed-by` and the pull requests linked to it** (link kind `pull-request`; hq issue
 483): agents link a pull request while the issue is in fixing and give `fixed-by` at the resolve, so a delivery read
 on `fixed-by` alone missed every fix being verified. Readiness still reads `fixed-by` alone, so a pull request linked
-and abandoned holds no dependent back. A pull request linked after its delivery moved hears no transition again: each
+and abandoned holds no dependent back. A pull request closed without merging (`stopped`, and never merged) is **withdrawn**: not
+a fix awaiting delivery, not delivered, not open; the line says "fix withdrawn: …" when it is the only one. Merged is
+read from the delivery's `merged_as` or the pull request's own `merged`, never from the state, since `stopped` is
+also what a closed pull request becomes. A pull request linked after its delivery moved hears no transition again: each
 sweep asks mesh-delivery for at most five fixes never heard of, of issues not resolved.
 
 The ready-to-verify note names each fix with when it was delivered, and the issue's worker; the event carries
@@ -282,7 +285,7 @@ said (hq issue 483).
 - `decision-floor`, `research-floor` — the highest decision and research numbers taken where the tracker cannot
   read, such as an open branch of hq (293 and 45 when this was written: 0293 on an open branch, 045 on main).
   Read once, when that kind's counter starts; see *Decision and research numbers*.
-- `worker-stale-after` — how long an issue's worker stays current with nothing done on the issue (hq ADR 0283),
+- `worker-stale-after` — how long an issue's worker stays current with nothing done on the issue (hq ADR 0284),
   as a duration; `24h` when empty.
 - `owners` — the registered list `located-in` may name: repositories, and modules as
   `mesh-catalog modules/<module>`. An entry of `located-in` is an owner, or an owner followed by a space or a