@@ -18,10 +18,10 @@
 # ⛔ The token this run WRITES with is the App installation token step 3
 # mints — narrowed to the payload's repository (and, for a `transfer` stroke
 # alone, that transfer's one target too: `transferIssue` needs issues write on
-# both ends) and to the permissions the op table declares (`issues: write`, `pull-requests: write`, the
-# `contents: write` GitHub's auto-merge mutations require, and the
-# `metadata: read` the sender gate's permission read needs) — and revoked by
-# that action's post step. The workflow's own `GITHUB_TOKEN` gets nothing
+# both ends) and to the permissions the op table declares (`issues: write`,
+# `pull-requests: write`, the `contents: write` GitHub's auto-merge mutations
+# require, and the `metadata: read` the sender gate's permission read needs)
+# — and revoked by that action's post step. The workflow's own `GITHUB_TOKEN` gets nothing
 # (`permissions: {}` below); the job grants it `contents: read` for the
 # checkout and nothing else, so the run's ONLY write path is the App token,
 # and it exists only inside the execute step's environment.
 
@@ -1290,10 +1290,9 @@ let selfTestReachedVerdict = false;
  * five board tools, the token minter (its one POST creates no content, but a
  * write verb is a write verb and the roster below is mechanical), the
  * card-creation door, the card-transfer door, and the two halves of the
- * fleet-write relay — the
- * seat-side dispatcher (its one POST is the `repository_dispatch` that
- * carries a stroke) and the runner-side executor (the writes that stroke asked
- * for, paced on the runner's own log).
+ * fleet-write relay — the seat-side dispatcher (its one POST is the
+ * `repository_dispatch` that carries a stroke) and the runner-side executor
+ * (the writes that stroke asked for, paced on the runner's own log).
  *
  * Spelled REPO-RELATIVE, because the dispatch derivation reads every
  * separator-bearing literal in a gate's source as a path lead: a bare