feat(500): one end-of-turn request - the completion-section check folds into the reply check

The Stop hook sent the finished reply twice: scribe_report_check.sh checked a
task-closing reply for the completion sections in shell and reported to
/report-check, and scribe_reply_check.sh sent the same reply to /reply-rules
for the rule hold. Now the reply goes once. When the turn closed a task the
hook adds the close count and ids, and the server runs the section check
(services/report_check, the same three patterns) beside the reply hold,
folding both into one reason.

The report_check adherence log is still written for every checked reply
(milestone 409's number). A section hold marks the session, so its rewrite is
sent back once with rewrite:true to record how it came out, and is never held.
The block reason carries the completion shape's one line and points at
list_reply_shapes rather than at the skill. #5496 (step 4 of milestone 500).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

plugin/README.md

@@ -82,15 +82,16 @@ On install you'll be asked for:
   answer" line (8 s budget here — it runs after the tool, so it gates
   nothing). The extractor, the prose/data skip list, the local by-name
   duplicate arm and the outage line are shared in `hooks/scribe_defs.sh`.
-- `hooks/hooks.json` → Stop hook (`hooks/scribe_report_check.sh`): when the
-  turn closed a Scribe task (`update_task`/`create_task` with status done),
-  checks the reply that ends it for the completion sections — where the work
-  sits, what needs you, what comes next — and reports the outcome to
-  `GET /api/plugin/report-check`. If sections are missing it blocks once with
-  the reason the server returns, and records how the rewrite came out; it
-  never blocks twice, and never blocks when the instance did not record the
-  check (unconfigured or unreachable). Outcomes land in the admin logs under
-  category `plugin`, action `report_check`.
+- `hooks/hooks.json` → Stop hook (`hooks/scribe_reply_check.sh`): sends the
+  reply that ends the turn to `POST /api/plugin/reply-rules`, which holds it
+  once for an unopened rule mounted on the reply moments or matching the reply.
+  When the turn closed a Scribe task (`update_task`/`create_task` with status
+  done), the same request has the server check the reply for the completion
+  sections — where the work sits, what needs you, what comes next. If they are
+  missing it blocks once with the reason the server returns, and records how
+  the rewrite came out; it never blocks twice, and never blocks when the
+  instance did not record the check (unconfigured or unreachable). Outcomes
+  land in the admin logs under category `plugin`, action `report_check`.
 - `hooks/hooks.json` → a second Stop hook (`hooks/scribe_shape_check.sh`): the
   write hooks note every definition a write names (and every new file) in a
   session ledger; at the end of the turn this sends them to