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>

OfficeHourQueue.md

@@ -5,6 +5,13 @@
 > ~two office-hour command days per month. Agents preload each day with a
 > runbook; the day is scarce strategic infrastructure — protect it from
 > low-leverage work.
+>
+> **Closing an item (CUST-WP-0061-T05, 2026-07-21):** set `status: done`
+> directly on the item's own yaml block in place — it already stays under
+> "## Queued items" as the historical record; no separate log to move it
+> to. `WORK-RECORDS.md` (generated by `statehub fix-consistency`) is the
+> always-current cross-cutting view of every engagement including done
+> ones.
 
 ## Item template