Record the HelixForge bot and private test channel.

provision apply registered @HelixForgeBot and channel 4427430639. The public channel stays held. The resolved file contains no token.

Assistant: grok
Assistant-Session: 01a10938-ab49-7280-877a-c06f64c06ddd

presence/resolved/hall-of-helix.yaml

@@ -0,0 +1,15 @@
+# Generated by `provision apply`. Committed, and free of secrets:
+# tokens, sessions and the redaction salt live in OpenBao.
+resolved:
+    campaign: hall-of-helix
+    spec_digest: sha256:9541e872967355cfb0ff51c7bf67d095e42062bb3406977ad86318d892d9298d
+    provisioned_at: 2026-10-07T23:08:37.147959627Z
+    bot:
+        username: HelixForgeBot
+        id: 8859371696
+        avatar_digest: sha256:10ea520f054574deecf4efd3a4655cc9558b88907dae71ab03724676d948c27e
+    channels:
+        test:
+            chat_id: 4427430639
+            admin_rights:
+                - post_messages

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

@@ -9,7 +9,7 @@ flavor: implementation
 owner: worsch
 topic_slug: fluid-telegram
 created: "2026-09-04"
-updated: "2026-10-05"
+updated: "2026-10-07"
 planning_priority: high
 planning_order: 1
 depends_on:
@@ -66,10 +66,8 @@ is and why it cannot be removed.
 
 ```task
 id: FT-WP-0001-T01
-status: wait
+status: done
 priority: high
-needs_human: true
-blocking_reason: "Founder accepted review-51834acb. The attended BotFather registration and OpenBao store have not been performed."
 state_hub_task_id: "a5449e86-3181-54b6-a0fe-e5c761b3e4ba"
 ```
 
@@ -84,7 +82,7 @@ reader encountering the bot cold should recognise it as HelixForge. That is now
 `bot.name` / `bot.about` / `bot.description` in the spec, where it is reviewable
 before it is applied.
 
-Close this task when `FT-WP-0002` T04 has run. See `docs/provisioning.md`.
+Done on 2026-10-07. `provision apply` registered @HelixForgeBot (id 8859371696), set the profile and avatar, and stored the token in OpenBao. The resolved record is `presence/resolved/hall-of-helix.yaml`.
 
 2026-10-03: human gate routed to hub decision 7f455718-66c9-4049-9aaf-1143aea39d34 (D6: Telegram operator session: register the bots, create the channels, bootstrap the user session) by CUST-WP-0075; resolving that decision raises C-40 here.
 
@@ -95,7 +93,7 @@ id: FT-WP-0001-T02
 status: wait
 priority: high
 needs_human: true
-blocking_reason: "Founder accepted review-94a73510. The attended private-then-public channel creation has not been performed."
+blocking_reason: "Private test channel 4427430639 exists and @HelixForgeBot may post there. The public channel stays held until a checked rendering exists."
 state_hub_task_id: "597ab1b7-5903-5a5d-a510-0a6946325404"
 ```
 
@@ -121,9 +119,7 @@ Close this task when `FT-WP-0002` T04 has run.
 
 ```task
 id: FT-WP-0001-T03
-status: wait
-needs_human: true
-blocking_reason: "The operator session is stored. The redaction salt is created when provision apply runs, and that live apply has not been run."
+status: done
 priority: high
 state_hub_task_id: "bbe5da73-e604-5dfe-b25f-fba802f67618"
 ```
@@ -136,7 +132,7 @@ It must never change: see `docs/observation.md` for why rotating it silently
 invalidates every longitudinal comparison. Making that a property of the tool
 rather than a note in a workplan is the whole reason the step moved.
 
-Close this task when `FT-WP-0002` T05 has run.
+Done on 2026-10-07. `provision apply` created the redaction salt at the empty OpenBao path and recorded that it is never rotated. The salt value is not in the repository.
 
 ## T04 — Record the intent and publish R-1
 
@@ -251,7 +247,7 @@ no basis, so this blocks T10.
 id: FT-WP-0001-T08
 status: wait
 depends_on: [FT-WP-0001-T07, FT-WP-0002-T01]
-blocking_reason: "The first private-channel post needs the consent basis and the operator session that creates the bot and channel."
+blocking_reason: "The bot and private test channel exist. The first private-channel post still waits on the recorded consent basis."
 priority: high
 state_hub_task_id: "5e5cd89a-e7b1-5aaf-9331-ece424afe5e3"
 ```