docs: prepare ops-hub bootstrap handoff

workplans/HF-WP-0001-establish-ops-hub-first-extension.md

@@ -365,7 +365,7 @@ Output: `Confirmed Bootstrap Path` section in this workplan.
 
 ```task
 id: HF-WP-0001-T02
-status: todo
+status: blocked
 priority: high
 state_hub_task_id: "8e9bd9b2-54fc-49a4-8bb8-11c8577be48d"
 ```
@@ -388,13 +388,22 @@ fields as an Inter-Hub API/model gap.
 Done when: `ops-hub` appears in `/Hubs` and `/api/v2/hub-registry` after
 authentication, and a human can tell that it is the VSM Operations hub.
 
+Blocked until: an authenticated Inter-Hub admin session or deployment-side
+migration is available.
+
+Prepared artifacts:
+
+- `wiki/OpsHubBootstrapRunbook.md`
+- `wiki/ops-hub-manifest.draft.json`
+- `wiki/ops-hub-bootstrap.sql`
+
 ---
 
 ### T03 — Activate the ops-hub capability manifest
 
 ```task
 id: HF-WP-0001-T03
-status: todo
+status: blocked
 priority: high
 state_hub_task_id: "55f5aeed-21c3-4a83-bc78-f90f92c7d597"
 ```
@@ -421,13 +430,18 @@ Validation:
 
 Done when: the manifest status is `active` and no type conflicts remain.
 
+Blocked until: the `ops-hub` row exists in Inter-Hub and an authenticated
+operator or migration can create and activate the manifest.
+
+Prepared artifact: `wiki/ops-hub-manifest.draft.json`.
+
 ---
 
 ### T04 — Create ops-hub API consumer and key
 
 ```task
 id: HF-WP-0001-T04
-status: todo
+status: blocked
 priority: high
 state_hub_task_id: "ad08e729-8562-4a02-8bf6-dcdfebe430c8"
 ```
@@ -444,13 +458,17 @@ Store the key only in the operator secret store or local env file, never in Git.
 Done when: `POST /api/v2/token` can exchange the static key for a short-lived
 access token and `GET /api/v2/hub-registry` works with that token.
 
+Blocked until: an authenticated operator creates the API key and stores the
+full static key outside Git. The SQL fallback intentionally creates only the
+consumer row, not the one-time visible secret.
+
 ---
 
 ### T05 — Seed first governed ops widgets
 
 ```task
 id: HF-WP-0001-T05
-status: todo
+status: blocked
 priority: high
 state_hub_task_id: "d303884d-d1f6-4fd0-a4ec-97afe6162164"
 ```
@@ -478,6 +496,13 @@ migration and record that as an API gap.
 Done when: the widgets appear under `ops-hub` and can accept interaction events
 and annotations.
 
+Blocked until: `ops-hub` and its active manifest exist in Inter-Hub.
+
+Prepared artifacts:
+
+- `wiki/ops-hub-widgets.seed.json`
+- `wiki/ops-hub-bootstrap.sql`
+
 ---
 
 ### T06 — Build the first ops inventory artifact
@@ -517,7 +542,7 @@ Output: `wiki/OpsHubInventory.md`.
 
 ```task
 id: HF-WP-0001-T07
-status: todo
+status: blocked
 priority: medium
 state_hub_task_id: "ed3e0396-b16d-40c2-9519-e755ad6241eb"
 ```
@@ -544,6 +569,10 @@ Suggested event:
 Done when: the Gitea registry readiness event is visible in Inter-Hub and
 traceable back to the Railiance workplan.
 
+Blocked until: the `ops-endpoint-gitea-registry` widget exists, the
+`ops-endpoint-verified` event type is active, and an ops-hub API key is
+available to the operator.
+
 ---
 
 ### T08 — Define the ops-hub readiness gate model for ThreePhoenix migration
@@ -604,7 +633,7 @@ needed.
 
 ```task
 id: HF-WP-0001-T10
-status: todo
+status: in_progress
 priority: high
 target_repo: inter-hub
 state_hub_task_id: "7fa54508-7add-4885-8913-12edaadc4d92"
@@ -641,6 +670,9 @@ Recommended Inter-Hub improvements:
 Done when: the next VSM hub can be created from a script using documented API
 calls and without direct DB access.
 
+Linked Inter-Hub workplan:
+`inter-hub/workplans/IHUB-WP-0019-vsm-hub-bootstrap-api.md`.
+
 ## Initial Acceptance Criteria
 
 This workplan is complete when: