fix(workplans): declare records the hub already holds as workplans

Canon defines six work-record kinds — workplan, task, intake, decision,
engagement, register-entry. These files declared none of them (feature, runbook,
bug-report, extension-workplan, scorecard, session-note, adhoc) while the hub
held each as a workplan.

Selection is by 'type: workplan', so the mismatch made them invisible to any
projection: a forge-derived reset read their correct hub records as no longer
deriving and proposed retiring live work.

Where a file also lacked a canonical identifier, one was assigned continuing the
repository's sequence. Existing hub identifiers are preserved, so no record is
orphaned.

Refs STATE-WP-0083

workplans/CUST-WP-0023-tpsc.md

@@ -1,6 +1,6 @@
 ---
 id: CUST-WP-0023
-type: feature
+type: workplan
 title: Third-Party Services Catalog (TPSC)
 domain: infotech
 status: done

workplans/CUST-WP-0024-repo-doi-gate.md

@@ -1,6 +1,6 @@
 ---
 id: CUST-WP-0024
-type: feature
+type: workplan
 title: Repository DoI automated gate and dashboard integration
 domain: infotech
 status: done

workplans/CUST-WP-0045-cutover-runbook.md

@@ -1,6 +1,6 @@
 ---
-id: CUST-WP-0045-cutover-runbook
-type: runbook
+id: CUST-WP-0069
+type: workplan
 title: "CUST-WP-0045 T06 cutover — exact command sequence"
 parent_workplan: CUST-WP-0045
 status: finished
@@ -8,6 +8,7 @@ created: "2026-06-01"
 updated: "2026-06-27"
 state_hub_workstream_id: "4ebc847b-4a2c-4ce2-9fd2-62d3071eed96"
 domain: infotech
+repo: the-custodian
 ---
 
 # CUST-WP-0045 T06 cutover — exact command sequence