ISSUES: mesh-issues reads git.pull, git.contains and the runner's list and show, not mesh-delivery.checks and the forge's tools

Pull request facts come from seat git's pull, ancestry from contains, the review time from the runner's review step,
and get shows one pipeline row per module (no run where the runner's list answers none).

Builds: design 47 G §654, A-75

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

modules/mesh-issues/README.md

@@ -89,7 +89,7 @@ still read as that issue's verdict.
 **Ready.** An issue is ready when it is not resolved or wontfix and every issue it depends on is wontfix, or
 resolved with every pull request its `fixed-by` names (`<repository>#<number>`) delivered. The module consumes
 `mesh-delivery-gate.transition` and marks a pull request delivered on every issue naming it; at its own `moved` to
-resolved it asks `seat:mesh-delivery.checks` once for what it has not heard. An issue made ready gains a note and
+resolved it asks `seat:git.pull` once for what it has not heard. An issue made ready gains a note and
 the event `ready`. `get` answers `waits-for`, `needed-by` and `ready`; `list` filters on `severity`, `needs` and
 `ready` — an agent looking for work asks `severity=minor`, `needs=none`, `ready=true`. `set` changes severity,
 needs and suggested owner as a person decides. `link` refuses a `depends-on` that would close a cycle.
@@ -106,8 +106,8 @@ key-value state has no schema to migrate.
 ## Whether the fix is delivered (hq ADR 0281)
 
 For each pull request an issue's `fixed-by` names, the module keeps what `mesh-delivery-gate.transition` last said —
-state, why, merged and when — or asks `seat:mesh-delivery.checks` once (at its own `moved`) for one it has not
-heard of. Nothing sets it by hand. `get` and every `list` row carry `delivery`, one line derived from it, worst
+state, why, merged and when — or asks `seat:git.pull` once (at its own `moved`) for one it has not
+heard of. Nothing sets it by hand. `get` also carries `pipelines`: one row per module's pipeline of each live fix's head commit with its steps, `no run` where the runner's list answers none. `get` and every `list` row carry `delivery`, one line derived from it, worst
 first: "fix not delivered: …", "held: …", "fix merged, not delivered: …", "fix not merged: …", "nothing heard from
 the delivery of …", "delivered to every machine it should reach" (covered by a later merge says so).
 
@@ -163,8 +163,8 @@ core one, counted from the move to `fixing`), `over`, the fix delivered last (`f
 | phase | ends at | read from |
 |---|---|---|
 | implementing | its pull request opened | mesh-delivery's `opened` (the pull request's first head heard) |
-| review | the first approval at its head | the forge's reviews (`gitea_pull_reviews`): the forge's own approval, or a comment review whose first line is `Verdict: approve at <sha>`, the sha the head it was posted at or a prefix of at least seven characters (the forge refuses an approval of one's own pull request, so the mesh's independent reviews are comments) |
-| checks | its merge, required checks and any wait for the merge included | mesh-delivery's `merged_at` |
+| review | the first review that passed at its head | the runner: `seat:mesh-pipeline-runner.list` given the head commit `seat:git.pull` answers, and `show` of each pipeline, the review step's `ended`; the forge's own reviews are read nowhere |
+| checks | its merge, required checks and any wait for the merge included | the gate's `merged_at`, or `seat:git.pull`'s `merged-at` |
 | merge to running | delivered | the delivery's `delivered` (its delivery time) |
 
 A phase whose end came before the end of the phase before it counts zero; a phase whose end is not known (no