repo.work.assign_missing_identifiers

source: repo-manager
reason: deterministic projection registration

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1116572@bnt-lap001
Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400

workplans/FLUID-WP-0001-statehub-bootstrap.md

@@ -9,6 +9,7 @@ owner: codex
 topic_slug: custodian
 created: "2026-09-04"
 updated: "2026-09-04"
+state_hub_workstream_id: "b5c231e1-9d06-5772-95a7-01cc0bf62051"
 ---
 
 # Bootstrap State Hub integration
@@ -21,6 +22,7 @@ Fluid interface for telegram messaging and interaction platform.
 id: FLUID-WP-0001-T01
 status: todo
 priority: high
+state_hub_task_id: "f106ac45-c90b-5115-a0de-e986839b19f9"
 ```
 
 Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
@@ -32,6 +34,7 @@ Replace generated placeholders with repo-specific facts where needed.
 id: FLUID-WP-0001-T02
 status: todo
 priority: high
+state_hub_task_id: "1e3f26fe-4a1a-5f96-8dd6-962dd844402e"
 ```
 
 Identify the repo's install, test, lint, build, and run commands. Add or refine
@@ -44,6 +47,7 @@ changes confidently.
 id: FLUID-WP-0001-T03
 status: todo
 priority: medium
+state_hub_task_id: "2428db4a-c6ad-547d-acf3-9163ea17ae20"
 ```
 
 Create the first implementation workplan for the repository's most important

workplans/FT-WP-0001-telegram-identity-and-hall-channel.md

@@ -17,6 +17,7 @@ related_repos:
   - fluid-core
   - helix-forge
   - hall-of-helix
+state_hub_workstream_id: "a660ed65-700e-5b54-8d91-a556b73518f0"
 ---
 
 # FT-WP-0001 — Telegram identity and the Hall of Helix channel
@@ -39,6 +40,7 @@ adapter.
 id: FT-WP-0001-T01
 status: todo
 priority: high
+state_hub_task_id: "a5449e86-3181-54b6-a0fe-e5c761b3e4ba"
 ```
 
 **Human step.** Register the HelixForge bot through BotFather (Canon BOT-01).
@@ -56,6 +58,7 @@ briefly. Consistent with `HF-WP-0002` (bao.coulomb.social).
 id: FT-WP-0001-T02
 status: todo
 priority: high
+state_hub_task_id: "597ab1b7-5903-5a5d-a510-0a6946325404"
 ```
 
 **Human step.** Create the **private test channel first**, then the public
@@ -72,6 +75,7 @@ public channel until the rendering has been seen by a person.
 id: FT-WP-0001-T03
 status: todo
 priority: high
+state_hub_task_id: "bbe5da73-e604-5dfe-b25f-fba802f67618"
 ```
 
 `openssl rand -hex 32`, stored in OpenBao beside the token, injected as
@@ -84,6 +88,7 @@ rotating it silently invalidates every longitudinal comparison.
 id: FT-WP-0001-T04
 status: todo
 priority: high
+state_hub_task_id: "13a92a96-2f87-5de2-a69c-7edc21f3a0c7"
 ```
 
 ```bash
@@ -103,6 +108,7 @@ only, and a revision signed with one stops verifying after a restart.
 id: FT-WP-0001-T05
 status: todo
 priority: high
+state_hub_task_id: "c89782da-9896-5957-b729-7c35165a0067"
 ```
 
 Implement the three operations in `contracts/r1.openapi.yaml` against the
@@ -120,6 +126,7 @@ hypotheses and can only be honest if the adapter refuses.
 id: FT-WP-0001-T06
 status: todo
 priority: high
+state_hub_task_id: "317bef32-e82e-586a-8947-8cbb330f6c98"
 ```
 
 The first real test. Publish a single hall entry to the private channel and
@@ -136,6 +143,7 @@ confirm, by looking at it:
 id: FT-WP-0001-T07
 status: todo
 priority: medium
+state_hub_task_id: "6a91ea08-8814-58f3-8297-a7ca63405294"
 ```
 
 R-2 implements `H-tg-teaser`, R-3 implements `H-tg-serial`. Both are
@@ -148,6 +156,7 @@ change. Verify both against the private channel before either sees a subscriber.
 id: FT-WP-0001-T08
 status: todo
 priority: medium
+state_hub_task_id: "5e5cd89a-e7b1-5aaf-9331-ece424afe5e3"
 ```
 
 Point the production adapter at the public channel and publish the existing
@@ -163,6 +172,7 @@ experiment, which is why `E-tg-length` names R-2 as control rather than R-1.
 id: FT-WP-0001-T09
 status: todo
 priority: low
+state_hub_task_id: "649e7df6-6c07-5cc8-a022-d1eadcdb7236"
 ```
 
 Start `E-tg-length` once the channel has roughly 100 subscribers. Before then
@@ -180,6 +190,7 @@ amendments rather than discovering it as a disappointment.
 id: FT-WP-0001-T10
 status: todo
 priority: low
+state_hub_task_id: "b469b9b8-a1a8-5f76-a1bb-dd51dd4d2ce5"
 ```
 
 Record the hypothesis outcome, resolve the competition group, and promote the