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_record_outcome.sh

@@ -1,16 +1,16 @@
 #!/usr/bin/env bash
 # Scribe — record that this session said what a rule DID, not merely that it
-# read one (#4216, milestone 419).
+# read one.
 #
-# THE THIRD LEDGER, AND WHY THE TWO THAT EXIST ARE NOT ENOUGH.
+# THE THIRD LEDGER, AND WHY THE OTHER TWO ARE NOT ENOUGH.
 #
-# `.rules.ids` says a rule was NAMED. `.opened.ids` says it was READ (#4100 —
-# a PostToolUse hook watches the `get_rule` call, so it is a recorded event
+# `.rules.ids` says a rule was NAMED. `.opened.ids` says it was READ (a
+# PostToolUse hook watches the `get_rule` call, so it is a recorded event
 # rather than a model's claim about its own context). Neither can say what
-# happened next, and that is the whole of what milestone 419 is about: a rule
-# read and followed and a rule read and forgotten leave identical traces.
+# happened next: a rule read and followed and a rule read and forgotten leave
+# identical traces.
 #
-# `rule_outcome` (#4212) is the call that closes that gap, and the server
+# `rule_outcome` is the call that closes that gap, and the server
 # records it. But the server's row carries no session — `rule_usage_events` is
 # per user over a window — so a SESSION-scoped readout cannot be asked of it.
 # The question "which rules changed something in THIS session" has to be
@@ -18,13 +18,11 @@
 #
 # SAME EVIDENCE CLASS AS `.opened.ids`, deliberately. A tool call happened or
 # it did not, and the harness reports it either way; nothing here asks the
-# model whether it followed anything. That is the distinction milestone 386
-# drew when it ruled out self-report, and this stays on the right side of it.
+# model whether it followed anything, so it is evidence, not self-report.
 #
 # WHAT IT CANNOT SAY: that the rule was followed WELL, or that `applied` was
 # honest. It records that an outcome was declared. The value of that is not the
-# claim itself — it is that the absence of one becomes visible, which is the
-# state nothing could previously name.
+# claim itself — it is that the absence of one becomes visible.
 #
 # EXIT 0, ALWAYS. This decorates a ledger; a bookkeeping failure must never
 # turn a successful tool call into a hook error.