bazilion 0.2.1 → 0.3.0

package/dist/migrations/0003_agent_telegram.sql

@@ -0,0 +1,40 @@
+-- Telegram integration columns. Step 1 of the docs/telegram.md plan adds the
+-- schema only; the bot singleton, polling loop, and routing helpers land in
+-- subsequent steps. None of these columns are populated yet — they sit empty
+-- until the live bot in Step 2 starts persisting topic ids on first traffic.
+--
+-- agents.telegram_topic_id        — forum-topic message_thread_id; one topic per
+--                                   agent. Partial unique index below allows
+--                                   multiple NULLs (unbound agents) but enforces
+--                                   one-to-one once an id is written.
+-- agents.telegram_topic_name_locked — sticky bit set when a human renames the
+--                                   topic in Telegram; once set, bazilion stops
+--                                   propagating agent/group renames to that topic.
+-- agents.telegram_icon_emoji      — per-agent override of the profile-derived
+--                                   custom-emoji sticker id. Lookup at topic
+--                                   creation: agents.* → profiles.* → null.
+--                                   Survives topic delete + recreate, unlike
+--                                   a customization that only lived in Telegram.
+-- groups.telegram_icon_color      — Telegram's 6-color enum slot allocated to
+--                                   this group on first-traffic. Red is reserved
+--                                   for the service chat, so groups round-robin
+--                                   over the remaining 5.
+-- profiles.telegram_icon_emoji    — curated default sticker id from
+--                                   getForumTopicIconStickers, per built-in
+--                                   profile. Seeded for built-ins, NULL for
+--                                   custom profiles (which render color-only).
+
+ALTER TABLE agents ADD COLUMN telegram_topic_id INTEGER;
+ALTER TABLE agents ADD COLUMN telegram_topic_name_locked INTEGER NOT NULL DEFAULT 0;
+ALTER TABLE agents ADD COLUMN telegram_icon_emoji TEXT;
+
+ALTER TABLE groups ADD COLUMN telegram_icon_color INTEGER;
+
+ALTER TABLE profiles ADD COLUMN telegram_icon_emoji TEXT;
+
+-- Partial unique index: enforces one-to-one mapping between agents and topic
+-- ids without blocking many unbound agents (SQLite treats NULLs as distinct
+-- in unique indexes, but being explicit avoids surprise if that ever changes).
+CREATE UNIQUE INDEX IF NOT EXISTS idx_agents_telegram_topic_id
+  ON agents(telegram_topic_id)
+  WHERE telegram_topic_id IS NOT NULL;

package/dist/migrations/0004_agent_mirror_mode.sql

@@ -0,0 +1,17 @@
+-- Per-agent Telegram outbound-mirror verbosity.
+--
+-- 'minimal' (default): mirror only the assistant's final message text to
+--                      the agent's bound forum topic. Cleanest conversation
+--                      feel; what most operators want.
+-- 'verbose':           also mirror short tool-call summary lines so the
+--                      topic shows the agent's reasoning steps. Helpful
+--                      while iterating on a misbehaving agent; noisy in
+--                      steady state.
+--
+-- The column has no effect on agents without a bound topic. Step 6 picks
+-- the value up when materializing each ChatFrame; Step 7's CLI + web UI
+-- surfaces let operators flip it per-agent.
+
+ALTER TABLE agents
+  ADD COLUMN telegram_mirror_mode TEXT NOT NULL DEFAULT 'minimal'
+  CHECK (telegram_mirror_mode IN ('minimal','verbose'));

package/dist/migrations/0005_group_topic_name_format.sql

@@ -0,0 +1,15 @@
+-- Per-group Telegram forum-topic name template.
+--
+-- NULL (default): bazilion composes topic names the built-in way — bare
+--   agent.name for the `default` group, "<group.slug> › <agent.name>" for every
+--   other group (see lib/telegram/naming.ts:topicNameFor).
+-- Non-NULL: an explicit template rendered with the tokens {agent.name},
+--   {group.name}, {group.slug}. Must contain {agent.name} so each agent in the
+--   group still gets a distinct topic title. Validated on write
+--   (lib/telegram/naming.ts:validateTopicNameFormat).
+--
+-- Changing the template re-renders every bound, non-locked topic in the group
+-- via editForumTopic (lib/telegram/topic-rename.ts:syncGroupTopicNames). Topics
+-- a human has renamed (telegram_topic_name_locked = 1) are left untouched.
+
+ALTER TABLE groups ADD COLUMN telegram_topic_name_format TEXT;

package/dist/migrations/0006_telegram_acl.sql

@@ -0,0 +1,18 @@
+-- Per-user Telegram allowlist (Phase 7).
+--
+-- Bootstrap model: TOFU (trust-on-first-use). While this table is empty the
+-- bot is open; the first user to message it is auto-added as 'owner' and
+-- enforcement begins immediately after. Scope: FLAT — an allowlisted user can
+-- do everything (commands + agent chat); anyone not on the list is ignored.
+--
+-- role: 'owner' can manage the allowlist (/allow, /deny) and cannot be removed;
+-- 'member' can use the bot but not manage who else can. At least one owner must
+-- always remain (enforced in the repo + routes).
+
+CREATE TABLE IF NOT EXISTS telegram_allowed_users (
+  user_id   INTEGER PRIMARY KEY,
+  username  TEXT,
+  label     TEXT,
+  role      TEXT NOT NULL DEFAULT 'member' CHECK (role IN ('owner','member')),
+  added_at  INTEGER NOT NULL
+);

package/dist/worker.js

@@ -418,6 +418,36 @@ var SERVICES = [
         placeholder: "https://searxng.example.com"
       }
     ]
+  },
+  // --- External integrations (chat bridges, etc) ---
+  // Each integration has its own dedicated /config/integrations/* page with
+  // workflow-specific UI (preflight health, setup wizard, …). The fields
+  // here exist so the keys are allowlisted in the config/secrets stores and
+  // surfaced through the generic `PUT /api/config/fields/:envVar` endpoint.
+  // Daemon-managed internal state keys (watermarks, derived topic ids) live
+  // in repos/config.ts:INTERNAL_CONFIG_KEYS instead, since the user never
+  // edits them.
+  {
+    id: "telegram",
+    displayName: "Telegram",
+    category: "integration",
+    hint: "Forum-supergroup bot for talking to your agents from a phone",
+    fields: [
+      {
+        envVar: "TELEGRAM_BOT_TOKEN",
+        kind: "secret",
+        label: "Bot token",
+        placeholder: "1234567890:ABC...",
+        description: "Get one from @BotFather \u2192 /newbot. Disable Privacy Mode in Bot Settings."
+      },
+      {
+        envVar: "TELEGRAM_CHAT_ID",
+        kind: "config",
+        label: "Supergroup chat ID",
+        placeholder: "-1001234567890",
+        description: "Numeric id of the forum-enabled supergroup the bot is admin in."
+      }
+    ]
   }
 ];
 var FIELD_INDEX = (() => {
@@ -431,9 +461,19 @@ var FIELD_INDEX = (() => {
 })();
 
 // ../daemon/src/core/repos/config.ts
-var CONFIG_KEYS = SERVICES.flatMap(
-  (s) => s.fields.filter((f) => f.kind === "config").map((f) => f.envVar)
-);
+var INTERNAL_CONFIG_KEYS = [
+  // Telegram (step 2+): polling watermark + derived topic/message ids.
+  "TELEGRAM_LAST_UPDATE_ID",
+  "TELEGRAM_SERVICE_TOPIC_ID",
+  "TELEGRAM_DIRECTORY_MESSAGE_ID",
+  // Phase 5: proposed new chat id after a migrate_to_chat_id event, pending
+  // operator confirmation via POST /api/config/telegram/reconnect.
+  "TELEGRAM_MIGRATED_CHAT_ID"
+];
+var CONFIG_KEYS = [
+  ...SERVICES.flatMap((s) => s.fields.filter((f) => f.kind === "config").map((f) => f.envVar)),
+  ...INTERNAL_CONFIG_KEYS
+];
 var CONFIG_KEY_SET = new Set(CONFIG_KEYS);
 
 // ../daemon/src/core/repos/messages.ts