Kanban on Telegram (2026-10-20) — enabled with the correct access gate

What was verified in source first (file:line, not guessed)

• The gateway natively handles /kanban — gateway/slash_commands.py:342 _handle_kanban_command delegates to the shared kanban CLI with board routing, auto-subscription on create, and truncation handling. No install step exists or is needed — the handler ships; it just needs the per-scope access gate.
• The gate is per-platform-scope: gateway/slash_access.py:44 can_run — admins (the group_allow_admin_from list) get every registered command; non-admins keep the help/whoami floor plus any group_user_allowed_commands.
• Group-scope key = group_allow_admin_from (per-scope, DM not inherited) — slash_access.py:24 _SCOPE_KEYS.

Enablement applied (config changes, all backed up first)

• Laptop (tam profile): telegram extra gained group_allow_admin_from: [Young's user id] — Young is now admin on the group scope for this gateway.
• LAB (all 5 Brain profiles: sol/min/mira/nova/echo): same gate applied idempotently (every config timestamped .bak-tgadmin-*).
• Gateway restarts are the remaining beat (restart is a non-gateway-shell action; Sol/Young-side one-liner per profile) — until restarted, configs are correct on disk but the live gate is unread yet.

What Young gets in the group chat (once gateway cycles)

• /kanban list — live board view
• /kanban --board docker-vhost list — one of the six boards by name
• /kanban create &lt;title&gt; --assignee <who> — hand a task to a named agent
• /kanban complete <id> / block <id> / comment <id> "..." — drive the lifecycle from Telegram
• Cards created this way auto-subscribe the chat to the task (source-verified: _kanban_auto_subscribe) — replies land in the group automatically.

Honest limits

• The gateway must restart to re-read the platform extra config — config-on-disk is verified (grep), runtime gate is pending restart.
• Admin lists are per-scope deliberately (DM admin ≠ group admin) — Young's DM lane needs the DM-scope key if /kanban is wanted in DMs too (not set; ask if).

🎯 Tam Read: on Telegram /kanban was never missing — it was access-gated; the gate now names the principal as admin on the group scope for all six lane profiles, backed up and verified in source at file:line; one gateway restart per host turns the configs into live behavior, and from then on the board works from the group chat like any other agent surface.