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.

.claude/skills/hq-amend-design/SKILL.md

@@ -26,7 +26,9 @@ and says they disagree.
 1. Write the decision record. If it reverses an earlier one, that record gets
    `status: superseded` and `superseded-by:` — its text is never edited.
 2. Edit the design; set `updated:` to today.
-3. If this came from an issue, set that issue's `amended-design:`.
+3. If this came from an issue, give the issue the document in the issue tracker: `amended-design` on its
+   `issue-tracker.move` to `resolved`, or `issue-tracker.link` with kind `design` before then. Never in the
+   report's frontmatter (ADR 0275).
 
 ## Amending the as-is layer
 

.claude/skills/hq-new-issue/SKILL.md

@@ -52,7 +52,7 @@ Decide the shape first:
 
    then `# NNN. The title`, the title given to the tracker. **No status key**: the issue's status, owner and fix
    live in the tracker (ADR 0275), and `cycle.py` refuses `status:`, `located-in:`, `fixed-by:`,
-   `amended-design:`, `replay:` or `replay-none:` in a report opened after the import. Notes and links go to the
+   `amended-design:`, `replay:` or `replay-none:` in any report. Notes and links go to the
    tracker.
 4. Write the symptom **as observed**, in plain terms, with the evidence that it happened.
 5. Say why it matters beyond the instance. An issue that is only one occurrence is a knowledge

.claude/skills/hq-status/SKILL.md

@@ -21,9 +21,8 @@ generated on demand and never written back to disk.
 ## Steps
 
 1. Read the frontmatter block from every file above — a grep across each tree is enough, no
-   need to load bodies — and the issues from the tracker. The `status:` keys the reports numbered
-   001 to 364 still carry are the import's snapshot of 2026-10-10 (ADR 0275), not where an issue
-   stands.
+   need to load bodies — and the issues from the tracker. An issue report carries no status;
+   where an issue stands is only in the tracker (ADR 0275).
 2. Render what was asked as Markdown tables. Group and sort sensibly. The **ADR index** is one
    of these views, and it is the only place the list of records is shown
    ([ADR 0248](../../../02-DECISIONS/0248-the-decision-index-is-generated-when-it-is-read-and-never-stored.md)):