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.

00-META/checks/README.md

@@ -55,14 +55,16 @@ whose failure has never been observed is a guess about its own correctness.
 ## cycle.py
 
 The development cycle, checked ([ADR 0080](../../02-DECISIONS/0080-the-development-cycle-is-checked.md)):
-a to-be design names a decision, an in-progress/implemented design names its owning code, a
-located/fixed issue names its owner, a fixed/resolved issue says what fixed it, a graduated
+a to-be design names a decision, an in-progress/implemented design names its owning code, a graduated
 research overview says what it became, and no two issue records share a number (issue 155 — the
 number is how a record is cited, and `main` lags every open pull request, so two people reading it
-allocate the same one). And a core issue — one opened from 2026-10-07 whose `located-in` names a core
-repository — resolves only with `replay:` (an id in mesh-lab's replays register) or `replay-none:` saying
-why none is possible ([ADR 0237](../../02-DECISIONS/0237-a-change-is-judged-against-the-mesh-that-runs-before-it-merges-on-the-build-seat.md));
-it failed on a resolved core issue carrying neither before it passed. And an accepted record that puts work
+allocate the same one). An issue report carries the day it was `opened:` and no status key — `status:`,
+`located-in:`, `fixed-by:`, `amended-design:`, `replay:`, `replay-none:` or `resolved:` — because an issue's
+status lives in the issue tracker ([ADR 0275](../../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));
+it failed on all 361 reports that carried them before they were removed. The rules on an issue's status this
+check held until then — an owner for a located issue, a fix for a resolved one, and a core issue's `replay`
+or `replay-none` ([ADR 0237](../../02-DECISIONS/0237-a-change-is-judged-against-the-mesh-that-runs-before-it-merges-on-the-build-seat.md))
+— are refused at the write by `issue-tracker.move`. And an accepted record that puts work
 off — "until renamed", "left for later", "not decided here", "postponed", "future work", "deferred", "a later
 change" — names the issue that tracks it, as tracking it ("tracked by issue N", or "issue N tracks"), in that
 paragraph or list item, or in a dated progressive insight that speaks about it: one in the same section, or one