bazilion 0.2.1 → 0.4.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/migrations/0007_mcp_servers.sql

@@ -0,0 +1,30 @@
+-- MCP (Model Context Protocol) servers.
+--
+-- Each row is one configured server the daemon connects to as an MCP client.
+-- Tools discovered on it (`tools/list`) are namespaced `mcp__<name>__<tool>`
+-- and injected into agent turns. v0.4.0 scopes servers globally — every agent
+-- sees the tools of every enabled server.
+--
+-- Transports:
+--   stdio — local subprocess (`command` + JSON `args`); inherits the daemon's
+--           merged secrets env, so a server needing e.g. GITHUB_TOKEN picks it
+--           up from the normal secrets table.
+--   http  — Streamable-HTTP endpoint at `url`.
+--   sse   — SSE endpoint at `url`.
+--
+-- Bearer auth for http/sse is NOT stored here: the token lives in the encrypted
+-- `secrets` table under key `MCP_TOKEN_<id>`; `has_auth` records whether one is
+-- set so the UI/API can show it without decrypting.
+
+CREATE TABLE IF NOT EXISTS mcp_servers (
+  id          TEXT PRIMARY KEY,
+  name        TEXT NOT NULL UNIQUE,
+  transport   TEXT NOT NULL CHECK (transport IN ('stdio','http','sse')),
+  command     TEXT,
+  args        TEXT NOT NULL DEFAULT '[]',
+  url         TEXT,
+  has_auth    INTEGER NOT NULL DEFAULT 0,
+  enabled     INTEGER NOT NULL DEFAULT 1,
+  created_at  INTEGER NOT NULL,
+  updated_at  INTEGER NOT NULL
+);