Issue reports carry only opened: the tracker holds every status, so no copy can drift

The import of slice 3 (ADR 0275) was checked against every folder: no report changed since the
commit it read, and the tracker holds each report's status, owner, fix, design amendment, replay
and closing day. The keys are removed from all 361 reports, cycle.py refuses them in any report,
and the playbooks, skills and READMEs that still pointed at them name the tracker instead.

02-DECISIONS/0019-how-this-repository-works.md

@@ -124,6 +124,10 @@ decision records, issue reports.
 > numbers collided and statuses were hard to see. Research overviews, design documents and decision
 > records carry their state here as before.
 
+> **Progressive insight — 2026-10-10, later.** The reports written before no longer keep their keys: once
+> the import was checked against every folder, one pull request removed them (ADR 0275's last note), and
+> `cycle.py` refuses a status key in any report.
+
 **There are no central status files.** Every cross-cutting view — a status matrix, a decision
 index, an open-issue list — is generated from frontmatter when asked for, never written to disk.
 Two places holding one fact drift, and the written one wins by being closer to hand.

02-DECISIONS/0080-the-development-cycle-is-checked.md

@@ -56,6 +56,10 @@ The development cycle is enforced mechanically, to the extent frontmatter can ca
 > refuses a status key in a report opened after the import. The decision stands: the cycle is checked,
 > not trusted; which program checks each rule is a fact that moved.
 
+> **Progressive insight — 2026-10-10, later.** `cycle.py` refuses a status key in any report, not only one
+> opened after the import: the keys the older reports carried were removed once the import was checked
+> against every folder (ADR 0275's last note).
+
 [`00-META/checks/cycle.py`](../00-META/checks/cycle.py) refuses violations, beside `records.py`
 and `index.py`; all three run before any merge here. What frontmatter cannot see — that code work
 actually started from a handoff — remains held by playbooks 04 and 07: a feature branch exists

02-DECISIONS/0275-the-mesh-numbers-and-tracks-its-issues-in-a-module-of-its-own-and-hq-keeps-only-the-narrative-of-a-design-or-governance-issue.md

@@ -154,6 +154,15 @@ along the way".
 > operator confirms before it is applied, done through `move`, `link` and `note` on the imported issues, not by
 > the import, which only ever creates. The decision stands as written.
 
+> **Progressive insight — 2026-10-10, the status keys removed.** The insight above said the status keys stay in the
+> reports as a dated snapshot. They did not stay: every folder was compared with `issue-tracker.get` after the import
+> (status, `located-in`, `fixed-by`, `amended-design`, `replay`, `replay-none` and the closing day), no report had
+> changed since the commit the import read, the tracker held every field the reports held, and one pull request then
+> removed the keys from all 361 reports, as §8 decided. A snapshot kept in the reports was a second copy every reader
+> had to be told not to believe; the record of what was known that day stays in this repository's history at that
+> commit, which every imported issue names. `cycle.py` refuses a status key in any report, not only one opened after
+> the import. The decision stands as written.
+
 ## Consequences
 
 - Collisions end at the source: a number is taken from one counter, not read from a repository many branches write.