CUST-WP-0061-T05: retarget queue closures to WORK-RECORDS.md (generated)

Convention change, not new code: closing an item now means setting its
terminal status (status: closed/resolved/done + outcome where
applicable) directly on the item's own yaml block in place, instead of
deleting it and hand-writing a bullet in a separate "Completed"/
"Resolved decisions" log. WORK-RECORDS.md (CUST-WP-0061-T04, generated
by fix-consistency's C-33) already lists every closed/resolved/done
record with status/lane/source -- that supersedes the hand-maintained
logs as the going-forward view.

- AutopilotWorkQueue.md: closing note added; "## Completed" relabeled
  "(historical -- pre-canon, 2026-07-21)", frozen as-is, nothing
  migrated or deleted
- DecisionQueue.md: closing note added -- its "## Resolved decisions"
  entries were already structured as in-place yaml blocks with
  status: resolved (ahead of AWQ's convention already), so this only
  clarifies the log is superseded going forward, no structural change
- OfficeHourQueue.md: closing note added -- items already live under
  "## Queued items" with status: queued|prepared|done in place, no
  separate log ever existed here
- OperatingRhythm.md: queue-hygiene checklist updated to describe
  in-place status transitions instead of "moved to the log"; added
  item 5 noting WORK-RECORDS.md needs no hand-maintenance

Re-ran fix-consistency: WORK-RECORDS.md content unchanged (correctly
idempotent -- these were prose-only edits, no yaml block content
changed).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

AutopilotWorkQueue.md

@@ -2,6 +2,16 @@
 
 > Status: live document — evergreen Green/Blue work any agent may pull when
 > idle. Keep ordered by leverage; never let it run empty (OperatingRhythm.md).
+>
+> **Closing an item (CUST-WP-0061-T05, 2026-07-21):** set `status: closed`
+> and `outcome: promoted | declined | absorbed` directly on the item's own
+> yaml block in place — don't delete it and hand-write a bullet below.
+> `statehub fix-consistency` (C-32/C-33) registers the closure and
+> regenerates `WORK-RECORDS.md`, which is the generated, always-current
+> view of every closed item (id, status, lane, source) — that replaces the
+> "## Completed" log below as the going-forward record. The entries already
+> in "## Completed" are historical (pre-canon) and stay as prose; nothing
+> there needs migrating.
 
 ## Queue
 
@@ -44,7 +54,10 @@ Take the top item you can complete, mark it `in_progress` with your agent
 name, finish or return it with a note. Completed items move to the log below
 with a one-line outcome.
 
-## Completed
+## Completed (historical — pre-canon, 2026-07-21)
+
+> New closures go in the item's own block (`status: closed`) — see the
+> note at the top of this file. This section is frozen history.
 
 - **AWQ-010** (2026-07-19, agt-claude-workstation): promoted to workplan
   **BINKY-WP-0005** (registered in hub). Integration package delivered: