diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md
index 9214cffc..fdf2a9a9 100644
--- a/00-META/process/07-feature-branches.md
+++ b/00-META/process/07-feature-branches.md
@@ -234,6 +234,12 @@ never into the running one, unless it blocks the running one.
    `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.
+   **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
+   ask named them): mesh-delivery takes a pull request's issues from the words `issue <n>` and `issues <n>` in its
+   description (the plural yields its first number only), so write `issue 1608, issue 1646`, and name any other
+   issue in words, never by `issue <n>` or `issues <n>`.
    **A catalogue pull request that removes a module, or a subject a module names, is also judged by the
    controller's unit tests against the catalogue's branch**, because those tests read the catalogue and no check
    of the catalogue runs them: on 2026-10-20 mesh-catalog #381 removed the old delivery module, and every