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

@@ -1,25 +1,23 @@
 #!/usr/bin/env bash
-# Scribe — record that this session OPENED a rule, not merely saw it named (#4100).
+# Scribe — record that this session OPENED a rule, not merely saw it named.
 #
-# WHAT THIS CLOSES
+# WHAT THIS ANSWERS
 #
-# The rule arms keep a ledger of every id they have NAMED, and the injected
-# line used to tell the reader "You saw it earlier this session". That claim
-# was never checked. The line those arms emit is a TEASER — title, trigger,
-# `get_rule(N)` — so a session can be named a rule twenty times and never read
-# one word of it, and after a compaction the teaser is summarised away leaving
-# nothing at all. The server was asserting something about the reader's
-# context that it had no way to know.
+# The rule arms keep a ledger of every id they have NAMED. The line those arms
+# emit is a TEASER — title, trigger, `get_rule(N)` — so a session can be named
+# a rule twenty times and never read one word of it, and after a compaction
+# the teaser is summarised away leaving nothing at all. Named is not read, so
+# the server needs to be told which rules were opened.
 #
 # This is the observable half. PostToolUse fires for MCP tools (the event's own
 # output schema carries `updatedMCPToolOutput`, which would be meaningless
 # otherwise), so the `get_rule` CALL can be watched directly.
 #
-# WHY THIS IS NOT THE SELF-REPORT MILESTONE 386 REJECTED
+# WHY THIS IS NOT SELF-REPORT
 #
-# 386 ruled out asking the session whether it holds a rule, because a model
-# asked "do you still hold rule 156?" will say yes and the answer is
-# unverifiable self-report. That objection is about ASKING. This asks nobody:
+# Asking the session whether it holds a rule is useless: a model asked "do you
+# still hold rule N?" will say yes, and the answer is unverifiable. That
+# objection is about ASKING. This asks nobody:
 # a tool call happened or it did not, and the harness reports it either way.
 # Recording what a session DID is a different kind of evidence from believing
 # what it says about itself.
@@ -28,13 +26,12 @@
 #
 # It does not prove the rule is still in context — nothing can, and a
 # compaction can drop it moments later. That is why `.opened.ids` ages exactly
-# like `.rules.ids` and is cleared on the same events (#3749): both ledgers
+# like `.rules.ids` and is cleared on the same events: both ledgers
 # describe a context that no longer exists once the context is destroyed. The
 # claim it supports is only ever "you opened this, pull it again if you no
 # longer hold it", which stays true in every case and carries its own remedy.
 #
-# SINCE MILESTONE 458 STEP 7 it also reports the open, with the calls that
-# came just before it, so the server can learn which moments a rule belongs
+# It also reports the open, with the calls that came just before it, so the server can learn which moments a rule belongs
 # on (below). Silent on outage, like every arm that fires per call.
 #
 # EXIT 0, ALWAYS. This decorates a ledger; a bookkeeping failure must never
@@ -73,7 +70,7 @@ safe_sid=$(printf '%s' "$session_id" | tr -c 'A-Za-z0-9._-' '_')
 # (`scribe_rules_live`) ages both, and the last entry for an id wins.
 printf '%s\n' "$rule_id" | scribe_rules_append "$state_dir/${safe_sid}.opened.ids"
 
-# ── What came just before the open (milestone 458 step 7) ─────────────────
+# ── What came just before the open ───────────────────────────────────────
 #
 # scribe_moment.sh writes every call to `scribe-moment/<sid>.acts`. The ones
 # from the last three minutes go to the server with this rule's id: a rule