docs(6204): shipped instruction text describes the product, not this instance's records

MCP tool docstrings and comments, the server's orientation notes, the plugin
skills, every hook script and the plugin README/PACKAGING drop record ids,
milestone numbers, dates and incident stories, and state each non-obvious why
as a present-tense fact. History stays in the task logs.

Corrections found on the way:
- plugin README/PACKAGING said every hook is a GET; moment, rule-opened and
  reply-rules POST, so the plugin's key needs write scope. Both now say so,
  name Settings -> MCP Access, and list every wired hook and endpoint.
- the contract-change hint printed "(lesson #4207)", this instance's record,
  to every install. It no longer cites a record.
- tasks.py claimed there is no delete_task; there is.
- rulebooks.py cited delete_event and a design spec that no longer exist.
- scribe_after_write.sh carried an always-empty etag_q; removed.
- test_write_path_trigger pinned "| tac | scribe_defs | head -1", text that
  existed only in a comment about the old code; it now pins the real tail -1
  pipeline.
- docs/development.md: CI runs on Gitea Actions.

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

plugin/hooks/scribe_reply_check.sh

@@ -1,6 +1,5 @@
 #!/usr/bin/env bash
-# Scribe — Stop hook: the reply moment (milestone 458 step 4, folded in from
-# milestone 456 step 8).
+# Scribe — Stop hook: the reply moment.
 #
 # A reply is the one act no tool call marks, and it is where "please check
 # this on your end" or "it's done" gets said — so every arm that fires on a
@@ -9,11 +8,10 @@
 # text against every rule's trigger, as the backstop for whatever the earlier
 # arms missed. An unopened rule from either half holds the reply for one read.
 #
-# ONE END-OF-TURN REQUEST (milestone 500 step 4). When the turn closed a task,
-# the same request carries the task ids and the server also checks the reply
-# for the completion sections — once a Stop hook of its own
-# (scribe_report_check.sh), now the same call. The section check's outcome is
-# recorded (`report_check`, milestone 409's adherence number), and when it
+# ONE END-OF-TURN REQUEST. When the turn closed a task, the same request
+# carries the task ids and the server also checks the reply for the completion
+# sections. The section check's outcome is recorded (`report_check`, the
+# adherence number), and when it
 # held the reply, the rewrite is sent back once with `rewrite: true` so the
 # server can record how it came out. A rewrite is never held.
 #