fix(#158): address bot feedback — correct S8/S10 description, fix §9 prose break

docs/dev-loop-spec.md

@@ -274,7 +274,7 @@ Every worker template begins with an `⛔ ABSOLUTE CONSTRAINTS` section containi
 - **NEVER use the gitea-aweiker token.** All API calls use the gitea-rodin token only.
 - **NEVER act on a PR with active REQUEST_CHANGES.** Fix the findings first.
 
-The first two constraints are statically enforced by `check-invariants.sh`: S1 and S9 cover the dispatch script (no merge, no close); S8 and S10 cover worker templates (no merge calls, no close calls, and NEVER-close text present in each). The remaining two constraints (token usage and REQUEST_CHANGES gate) are enforced by runtime logic.
+The first two constraints are statically enforced by `check-invariants.sh`: S1 and S9 cover the dispatch script (no merge, no close); S8 covers worker templates (no merge calls); S10 covers worker templates (no close calls, with NEVER-close text verified present in each). The remaining two constraints (token usage and REQUEST_CHANGES gate) are enforced by runtime logic.
 
 ---
 
@@ -296,4 +296,6 @@ script never had a close call, but workers could reason their way into calling
 `PATCH /pulls/{id}` with `state=closed`. All worker templates now include
 `NEVER close a PR` in their ABSOLUTE CONSTRAINTS section. Invariant S9 verifies
 the dispatch script contains no close calls. Invariant S10 verifies
-worker templates contain no close calls and each contains the NEVER-close text. Regression tests in `dispatch.bats` statically verify all of these constraints.
+worker templates contain no close calls and each contains the NEVER-close text.
+
+Regression tests in `dispatch.bats` statically verify all of these constraints.