Name the session that pushed a head in its pull request, so a head that needs a new one names its author (ADR 0505 §5)

00-META/process/07-feature-branches.md

@@ -251,7 +251,12 @@ issue whether it is being fixed in between, after the delivery, or waits, and on
    the review record** (ADR 0421 §5), one line the lead writes from the reviewer's approval:
    `Reviewed-by: <who@node> at <full sha>` (the issue 1022 note gives its form). mesh-delivery reads it at every new
    head and puts it in the Approve's ask; a missing line, or one naming another commit, is said first in the ask.
-   It is never a gate.
+   It is never a gate. **Beside it, the description names the session that pushed the head**, one line
+   `Pushed-by: <who@node>` (ADR 0505 §5): when the head cannot merge because its check failed after the Approve (a
+   conflict, a failed check, a rejected group), the cure is that session's new head, and mesh-delivery tells the
+   operator only after two hours with no new head, naming the branch's author and this session. The session that
+   pushed watches its own pull request (the instruction follow-what-you-start) and pushes the new head well inside
+   those two hours. A description without the line names the branch alone.
    **The description names its issues as `issue <n>`, and only its own** (2026-10-21: okioki #9 listed its four
    issues bare, `Issues: 1608, 1646, …`, and named a milestone-2 issue as `issue 1654` and a follow-up as
    `issues 1665, 1666, 1667`, so mesh-delivery carried 1654 and 1665 as the pull request's issues and the Approve's

00-META/process/08-small-fixes.md

@@ -64,7 +64,7 @@ one delivery**. Everything before the try is local and fast.
    them again as the gate (playbook [07](07-feature-branches.md) step 3). They are never run on the machine. A
    failed try or check goes back to the same agent with the failure, and the reviewer reads only the change it makes.
 6. **The pull request's description carries the review record** (`Reviewed-by: <who@node> at <full sha>`,
-   playbook [07](07-feature-branches.md) step 3), and mesh-delivery asks the operator's Approve as soon as its
+   playbook [07](07-feature-branches.md) step 3) and the session that pushed it (`Pushed-by: <who@node>`, ADR 0505 §5), and mesh-delivery asks the operator's Approve as soon as its
    checks pass and merges the approved head (ADR 0421); nobody marks, labels, comments or rechecks. A fix to a module that changes how it runs carries an
    integration test starting the module whole against the real bus and store, run by `mesh-controller.try` and the forge's checks
    (ADR 0391 §1, §6); unit tests alone are not that proof, and the lab is not used. The operator's word is waited for only when the fix changes what the operator sees, removes data,

00-META/process/playbooks.html

@@ -465,7 +465,7 @@ const P = [
  {n:"07",name:"Features",kind:"build",c:"--build",
   trig:"Work that changes code across issues or repositories, too large for a small fix.",
   who:"A lead (larger model), one fixing agent per repository (smaller), one reviewer (larger).",
-  steps:["Prepare: name the branch, make the worktrees, settle every question.","Write one context file per repository.","Write the findings and acceptance criteria into each issue.","Survey every other reader and writer of each changed value. (new)","List every part the change reaches; copy fixtures from the real writer.","Develop: one agent per repository, one commit per issue.","A test fails first on behaviour, not on compiling. (new)","Bring each branch up to the trunk, push, and try it. (new)","Review all of it with the tries' results; at most 3 rounds.","Push the reviewed heads; try again only what changed.","Open one pull request per repository, together, with Reviewed-by.","The operator's Approve on Telegram; the group merges in one pass.","Follow the delivery plan to done; resolve the issues; clean up."],
+  steps:["Prepare: name the branch, make the worktrees, settle every question.","Write one context file per repository.","Write the findings and acceptance criteria into each issue.","Survey every other reader and writer of each changed value. (new)","List every part the change reaches; copy fixtures from the real writer.","Develop: one agent per repository, one commit per issue.","A test fails first on behaviour, not on compiling. (new)","Bring each branch up to the trunk, push, and try it. (new)","Review all of it with the tries' results; at most 3 rounds.","Push the reviewed heads; try again only what changed.","Open one pull request per repository, together, with Reviewed-by and Pushed-by.","The operator's Approve on Telegram; the group merges in one pass.","Follow the delivery plan to done; resolve the issues; clean up."],
   prod:"One pull request per repository, one delivery plan, resolved issues, no branch or worktree left.",
   next:"02 (when it ships)",bounds:"Prepare 15 min · 30 min per issue · review 15 min, ≤ 3 rounds · one try and one check",
   prev:["Pull requests as scratchpads","Context bought again and again","Review rounds spent on what a run would show"],