Reduce open work: archive CUST-WP-0038, finish STATE-WP-0093, trim STATE-WP-0079

CUST-WP-0038 (HA migration of a retiring service): archived, 8 tasks cancelled.
STATE-WP-0093: finished; T04 closed on its state-hub part, hub-core owns the rest.
STATE-WP-0079: T09 cancelled (owned by HUB-WP-0011), T07 folded into T05;
T05 records the three verified retirement candidates pending the meter write.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 7184@bnt-lap001
Assistant-Session: 4b436ae2-b17c-4b40-8754-200b161b26e4

workplans/STATE-WP-0079-retirement-strangler.md

@@ -9,7 +9,7 @@ flavor: refactoring
 owner: codex
 topic_slug: infotech
 created: "2026-08-09"
-updated: "2026-09-05"
+updated: "2026-09-22"
 parent_project: prj-state-hub-retirement
 parent_workplan: SHR-WP-0001
 related:
@@ -563,6 +563,24 @@ future silence: unresolved task/workstream-detail/SBOM-index attribution is T07.
 Available pod logs begin after the last calls. Evidence and limits:
 `docs/evidence/STATE-WP-0079-caller-and-receiver-review-20260905.md`.
 
+**Review 2026-09-22 (now also owns former T07).** The 2026-09-22 capture
+(`docs/evidence/legacy-meter-weekly-review-20260922.json`) lists three
+retirement candidates: `GET /sbom/` (quiet 10d, needs 7), `PATCH
+/workstreams/{workstream_id}` (quiet 36d, needs 30) and `POST /workstreams/`
+(quiet 37d, needs 30). Replacements verified the same day: `POST /workplans/`
+and `PATCH /workplans/{workplan_id}` in the live OpenAPI (`GET /workplans/`
+200); SBOM Nexus `GET /sbom/` returned 200 from the State Hub pod on
+railiance01. The founder approved retiring the three. The meter PATCH itself
+was not run from the agent session: the harness blocked the production
+write. It is still pending. Run it attended (`PATCH
+/legacy-meter/interfaces/{id}` with `status: retired`, ids `d0294dce`,
+`b1aae931`, `ed6451c9`) and store the receipt as
+`docs/evidence/STATE-WP-0079-legacy-retirement-20260922.json`. Still held
+after that: `GET /tasks/?workstream_id` (live, caller unattributed), and
+`GET /workstreams/`, `GET /workstreams/{workstream_id}` and
+`GET /workstreams/{workstream_id}/dependencies/` (quiet since 2026-08-21 or
+2026-09-03, not yet candidates).
+
 ## Stabilization window and archive prep
 
 ```task
@@ -586,7 +604,7 @@ fresh central meter demonstrates the required zero normal read/write window.
 
 ```task
 id: STATE-WP-0079-T07
-status: wait
+status: cancel
 priority: high
 state_hub_task_id: "2ac16837-454a-5a92-9385-c91cd3219aa2"
 ```
@@ -601,6 +619,11 @@ verified replacements, and attach fresh quiet-window evidence before retirement.
 Use `X-StateHub-Component` for direct agent HTTP requests. No inference from
 an `unknown` bucket alone is sufficient to assign an owner.
 
+**Folded into T05, 2026-09-22.** Cancelled to reduce open tasks. Attributing
+and migrating the remaining legacy readers is the same work as retiring those
+interfaces, so T05 now owns it: `GET /tasks/?workstream_id` (8 calls in the
+week to 2026-09-22, component `unknown`) and the quiet `/workstreams/` reads.
+
 ## Prove the first deployed hub-core message-read contract
 
 ```task
@@ -636,7 +659,7 @@ residual HUB-WP-0011 and T09; no production client or writer switched.
 
 ```task
 id: STATE-WP-0079-T09
-status: wait
+status: cancel
 priority: high
 state_hub_task_id: "da1d9a95-91bb-5662-a063-eed2a2f96c92"
 ```
@@ -649,6 +672,12 @@ switch and rollback using current source parity. State Hub remains the message
 writer throughout this read cutover. The private snapshot reader must not be
 advertised as a fresh production inbox.
 
+**Cancelled here, 2026-09-22.** This task only waited on HUB-WP-0011 in hub-core
+(still `proposed`), which owns the refresh/staleness contract, credential
+delivery and the client switch. Tracking the same gate in both repos doubled
+the open count. State Hub remains the message writer; nothing is needed from
+this repo until hub-core asks for a switch review.
+
 ## Acceptance
 
 - [x] Freeze policy documented