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>

OperatingRhythm.md

@@ -25,13 +25,18 @@ Rules:
 
 ## Queue hygiene (every agent session touching this repo)
 
-1. `DecisionQueue.md` — resolved items moved to the log; nothing older than
+1. `DecisionQueue.md` — resolved items get `status: resolved` set in place
+   (not moved to a separate log — CUST-WP-0061-T05); nothing older than
    14 days without escalation (RISK-003 rule).
 2. `OfficeHourQueue.md` — every queued item has prepared material before the
-   next command day; stale items pruned.
+   next command day; done items get `status: done` in place; stale items
+   pruned.
 3. `AutopilotWorkQueue.md` — never empty; agents with idle capacity pull from
-   the top.
+   the top; closed items get `status: closed` in place (CUST-WP-0061-T05).
 4. Workplan files match hub state (fix-consistency covers drift).
+5. `WORK-RECORDS.md` (generated, all three queues above) stays current —
+   `statehub fix-consistency` regenerates it automatically (C-33); nothing
+   to hand-maintain.
 
 ## Bridge scheduler (workstation cron)