diff --git a/workplans/FT-WP-0001-telegram-identity-and-hall-channel.md b/workplans/FT-WP-0001-telegram-identity-and-hall-channel.md
index 98ecb93..c8a825a 100644
--- a/workplans/FT-WP-0001-telegram-identity-and-hall-channel.md
+++ b/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-07"
+updated: "2026-10-08"
 planning_priority: high
 planning_order: 1
 depends_on:
@@ -280,6 +280,15 @@ it to the private channel, and confirm by looking at it:
 The second bullet is the one that needs a person. Everything else can be
 automated; whether a condensation is fair to the person it describes cannot.
 
+2026-10-08: first publish-path check. The outlet's own test post
+(`hoh-test-2026-10-08-outlet-parametrization`, `subject_consent: not-required`,
+reviewed by tegwick) went to the private channel through a short-lived local
+adapter (`scripts/send-post.sh` inside the attended OpenBao login): HTTP 201,
+published 10:10:19 +02:00. Fixed on the way: channel ids are now emitted in
+Bot API form (`-100<id>`). This is not T08: T08 still needs a post composed
+from one entry, which waits on the T07 consent basis. The rendering in the
+channel still needs a person's look before T02's public channel.
+
 ## T09 — Implement both delivery forms as R-2 and R-3
 
 ```task