Fix CUST-WP-0054 stale hub bindings; finish CUST-WP-0025 T24-T26

Remove orphaned state_hub workstream/task IDs from CUST-WP-0054 so
fix-consistency can recreate bindings. Mark CUST-WP-0025 finished with
fin-hub cost tracking, cross-hub coupling, and RaaS packaging complete.

workplans/CUST-WP-0025-fos-hub-bootstrap.md

@@ -4,7 +4,7 @@ type: workplan
 title: "FOS Hub Bootstrap — Identity, Hub Extraction, Ops Hub, Fin Hub"
 domain: infotech
 repo: the-custodian
-status: active
+status: finished
 owner: custodian
 topic_slug: custodian
 created: "2026-03-20"
@@ -687,7 +687,7 @@ with SQLAlchemy tables `fin_budgets`, `fin_commitments`, `fin_burn_rates`,
 
 ```task
 id: CUST-WP-0025-T24
-status: todo
+status: done
 priority: low
 state_hub_task_id: "405f81d3-dec5-4154-a1b8-a3af344a0cc4"
 ```
@@ -699,11 +699,15 @@ Implement:
 - Runway calculator with burn-rate projection
 - Budget alerts when projected runway drops below threshold
 
+Completed 2026-07-08: fin-hub CLI (`finhub`) with CSV importers for cloud,
+Anthropic billing, and HostEurope costs; runway calculator and budget alert
+evaluation in `src/fin_hub/services/`; fixture-backed tests pass.
+
 ### T25 — Cross-hub coupling: fin-hub connections
 
 ```task
 id: CUST-WP-0025-T25
-status: todo
+status: done
 priority: low
 state_hub_task_id: "90a41790-7290-4145-b89f-88bf491d7652"
 ```
@@ -713,11 +717,15 @@ Implement FOS §9 cross-hub coupling:
 - fin→ops: infrastructure cost attribution (per-service cost view)
 - fin→canon: viability alerts (runway below threshold escalates to System 5)
 
+Completed 2026-07-08: `src/fin_hub/coupling/` emits fin→dev resource-pressure
+alerts, fin→ops per-service cost reports, and fin→canon viability escalations
+via State Hub progress events (`--emit` on `finhub runway`).
+
 ### T26 — Pricing and packaging: railiance-as-a-service MVP
 
 ```task
 id: CUST-WP-0025-T26
-status: todo
+status: done
 priority: low
 state_hub_task_id: "e17ef269-e349-44cc-ab14-6c57b43199b1"
 ```
@@ -728,3 +736,7 @@ Concrete pricing:
 - Define onboarding workflow (customer → provisioned k3s + monitoring)
 - Legal: GmbH implications, liability, SLA framework
 - First customer acquisition strategy
+
+Completed 2026-07-08: `fin-hub/docs/raas-mvp-packaging.md` defines tier matrix,
+landing page draft, onboarding workflow, legal/GmbH framework outline, and first
+customer acquisition strategy.