feat(digest): first run is a complete setup chain (v3.4.11)

.claude/plugins/onebrain/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "onebrain",
-  "version": "3.4.10",
+  "version": "3.4.11",
   "description": "OneBrain — Your AI Thinking Partner",
   "author": {
     "name": "OneBrain Contributors"

.claude/plugins/onebrain/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "onebrain",
-  "version": "3.4.10",
+  "version": "3.4.11",
   "description": "OneBrain — Your AI Thinking Partner",
   "namespace": "onebrain",
   "skills": "./skills/",

.claude/plugins/onebrain/skills/digest/SKILL.md

@@ -76,6 +76,14 @@ user the note path, and remind them it is theirs to edit.
    confirm with the ✓/✗ state from `onebrain schedule list`. On skip: mention
    `/schedule-add` works any time later. Never re-offer when a `/digest` entry
    already exists in the schedule block.
+6. **Telegram offer (only when it can work):** if the telegram channel tools are
+   available in this session AND `notifications.telegram_chat_id` is not set, run
+   the **Notification Offer** flow from `schedule-add/SKILL.md` — user sends the
+   bot one message, the incoming channel tag carries `chat_id`, write it to
+   `onebrain.yml` and confirm with a test send. If the telegram tools are absent,
+   say nothing about Telegram (vault-log delivery is the normal path). This makes
+   the first `/digest` conversation a complete setup: sections → schedule →
+   delivery channel, no second command required.
 
 ## Step 1: Gather (per section present in config)
 

CHANGELOG.md

@@ -1,5 +1,5 @@
 ---
-latest_version: 3.4.10
+latest_version: 3.4.11
 released: 2026-07-30
 ---
 
@@ -11,6 +11,10 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 > **Versioning:** Plugin version is tracked in `plugin.json`. Bump when ANY harness config changes — skills, agents, hooks, INSTRUCTIONS, Gemini settings, slash commands, etc.
 > For CLI binary changes, see the [`onebrain-ai/onebrain-cli`](https://github.com/onebrain-ai/onebrain-cli/blob/main/CHANGELOG.md) repository.
 
+## v3.4.11 — 2026-07-30 — /digest first run is a complete setup chain
+
+- The interview now closes with the Telegram Notification Offer (shared with `/schedule-add`) when the telegram tools are present and no `notifications.telegram_chat_id` is set — sections → schedule → delivery channel in one conversation, no second command. Vaults without the telegram channel hear nothing about it.
+
 ## v3.4.10 — 2026-07-30 — /digest interview ends with a schedule offer
 
 - The first-run interview now closes by offering to schedule the digest ("ทุกเช้า กี่โมง?", default 08:30) — writes the `onebrain.yml` entry and runs `onebrain schedule register` in the same flow, confirming with the truthful ✓/✗ state. Skipping points at `/schedule-add`; the offer never repeats once a `/digest` entry exists. Closes the gap where a user who just chose their sections had to know a second command to get the daily run.