bazilion 0.2.0 → 0.3.0

package/dist/migrations/0001_init.sql

@@ -0,0 +1,179 @@
+-- Bazilion initial schema (consolidated, post-IPC + secrets-in-DB cleanup).
+--
+-- The daemon is the sole owner of `~/.bazilion/`. All state — entity
+-- metadata, inbox, scheduler, web tokens, encrypted secrets, plaintext
+-- config — lives in this single SQLite file. The only other file at the
+-- bazilion home root is `auth.json`: a tiny bootstrap shared by the daemon
+-- (which uses its `token` as the PBKDF2 seed for the `secrets` table) and
+-- the CLI (which uses the same token as its loopback bearer).
+--
+-- On-disk layout owned by the daemon:
+--   ~/.bazilion/bazilion.db
+--   ~/.bazilion/groups/<slug>/        — group root, mounted as cwd; may be a
+--                                       symlink for "agents working on my
+--                                       existing project tree" use cases
+--                  /memory/           — qmd index for the group (shared by
+--                                       all member agents)
+--   ~/.bazilion/agents/<id>/          — agent's private home (NEVER inside
+--                                       the group tree, so the cwd-rooted
+--                                       coding tools can't see/clobber it)
+--                  /sessions/*.jsonl  — pi transcripts
+--   ~/.bazilion/profiles/<id>/        — profile templates
+--   ~/.bazilion/skills/<name>/        — installed skills
+--   ~/.bazilion/logs/                 — daemon logs
+
+-- Groups are collaboration contexts: one filesystem root, one USER.md, one
+-- roster of member agents. The id IS the slug IS the directory name under
+-- `~/.bazilion/groups/`. No `path` column — paths derive from id.
+-- `user_md` is read-only context about the human (edited via web UI; never
+-- exposed as a file the agent could clobber via `edit`/`write`).
+CREATE TABLE groups (
+  id          TEXT PRIMARY KEY,
+  name        TEXT NOT NULL,
+  user_md     TEXT NOT NULL DEFAULT '',
+  created_at  INTEGER NOT NULL
+);
+
+-- Profiles are agent templates. `dir` is the on-disk directory for the
+-- profile's SOUL.md / IDENTITY.md / etc. master files, derived from id.
+-- `skills_mode = 'all'` attaches every installed skill at spawn;
+-- `'selected'` attaches only those listed in `profile_default_skills`.
+CREATE TABLE profiles (
+  id            TEXT PRIMARY KEY,
+  name          TEXT NOT NULL,
+  dir           TEXT NOT NULL,
+  default_model TEXT NOT NULL,
+  skills_mode   TEXT NOT NULL DEFAULT 'selected' CHECK (skills_mode IN ('all','selected')),
+  created_at    INTEGER NOT NULL,
+  updated_at    INTEGER NOT NULL
+);
+
+CREATE TABLE profile_default_skills (
+  profile_id  TEXT NOT NULL REFERENCES profiles(id) ON DELETE CASCADE,
+  skill_name  TEXT NOT NULL,
+  PRIMARY KEY (profile_id, skill_name)
+);
+
+-- Agents have exactly one group. `dir` is the agent's private home,
+-- ~/.bazilion/agents/<id>/ — strictly outside the group tree so that
+-- pi's coding tools (rooted at the group dir) can't reach into it.
+-- `reasoning_level` feeds pi-ai's streamSimple `reasoning` option;
+-- 'medium' is the sensible default.
+CREATE TABLE agents (
+  id              TEXT PRIMARY KEY,
+  profile_id      TEXT NOT NULL REFERENCES profiles(id),
+  name            TEXT NOT NULL,
+  model_override  TEXT,
+  status          TEXT NOT NULL CHECK (status IN ('idle','running','archived')),
+  dir             TEXT NOT NULL,
+  reasoning_level TEXT NOT NULL DEFAULT 'medium',
+  group_id        TEXT NOT NULL REFERENCES groups(id) ON DELETE RESTRICT,
+  created_at      INTEGER NOT NULL,
+  archived_at     INTEGER
+);
+
+CREATE TABLE agent_skills (
+  agent_id    TEXT NOT NULL REFERENCES agents(id) ON DELETE CASCADE,
+  skill_name  TEXT NOT NULL,
+  attached_at INTEGER NOT NULL,
+  PRIMARY KEY (agent_id, skill_name)
+);
+
+-- Periodic / scheduled wake-up triggers. The scheduler picks rows whose
+-- next-fire time has elapsed and kicks off a turn with `message` as the
+-- user input.
+--
+-- kind='interval' → interval_sec holds seconds between fires (cron_expr NULL)
+-- kind='cron'     → cron_expr holds a 5-field cron expression (interval_sec NULL)
+--
+-- last_fired_at is bumped *before* the run kicks off so a daemon restart
+-- mid-fire doesn't double-trigger.
+CREATE TABLE agent_triggers (
+  id             TEXT PRIMARY KEY,
+  agent_id       TEXT NOT NULL REFERENCES agents(id) ON DELETE CASCADE,
+  kind           TEXT NOT NULL CHECK (kind IN ('interval','cron')),
+  interval_sec   INTEGER,
+  cron_expr      TEXT,
+  message        TEXT NOT NULL,
+  enabled        INTEGER NOT NULL DEFAULT 1,
+  last_fired_at  INTEGER,
+  created_at     INTEGER NOT NULL
+);
+CREATE INDEX agent_triggers_agent ON agent_triggers(agent_id);
+CREATE INDEX agent_triggers_enabled ON agent_triggers(enabled) WHERE enabled = 1;
+
+-- Inter-agent inbox. The scheduler's auto-deliver loop polls
+-- `messages_to_unread` to fan out wakeup turns; the messaging tools insert
+-- here when one agent sends another a message.
+CREATE TABLE messages (
+  id            TEXT PRIMARY KEY,
+  from_agent_id TEXT NOT NULL REFERENCES agents(id),
+  to_agent_id   TEXT NOT NULL REFERENCES agents(id),
+  reply_to      TEXT REFERENCES messages(id),
+  payload       TEXT NOT NULL,
+  created_at    INTEGER NOT NULL,
+  read_at       INTEGER
+);
+CREATE INDEX messages_to_unread ON messages(to_agent_id) WHERE read_at IS NULL;
+
+-- Per-skill import provenance. Skills live on disk under ~/.bazilion/skills/<name>/;
+-- this table records where each was imported from and when.
+CREATE TABLE skill_meta (
+  name         TEXT PRIMARY KEY,
+  source       TEXT,
+  imported_at  INTEGER
+);
+
+-- Per-client web tokens. Each row stores SHA-256(token) hex; the plaintext
+-- is returned exactly once at creation time and never persisted in this
+-- table. The CLI's bootstrap token is one row here — its plaintext lives
+-- in `~/.bazilion/auth.json` so both the daemon (PBKDF2 seed for the
+-- secrets table) and the CLI (loopback bearer) can read it.
+-- `revoked_at` is a soft-delete marker to keep audit trail intact.
+CREATE TABLE web_tokens (
+  id            TEXT PRIMARY KEY,
+  label         TEXT NOT NULL,
+  token_hash    TEXT NOT NULL UNIQUE,
+  created_at    INTEGER NOT NULL,
+  last_used_at  INTEGER,
+  revoked_at    INTEGER
+);
+CREATE INDEX web_tokens_active ON web_tokens(token_hash) WHERE revoked_at IS NULL;
+
+-- Curated list of models per provider. Drives the model dropdowns in
+-- profile creation and agent spawn/edit forms.
+CREATE TABLE provider_models (
+  provider   TEXT    NOT NULL,
+  model      TEXT    NOT NULL,
+  added_at   INTEGER NOT NULL,
+  PRIMARY KEY (provider, model)
+);
+CREATE INDEX idx_provider_models_provider ON provider_models (provider);
+
+-- Admin-toggled enabled state per provider.
+CREATE TABLE provider_state (
+  provider_id TEXT    NOT NULL PRIMARY KEY,
+  enabled     INTEGER NOT NULL DEFAULT 0,
+  updated_at  INTEGER NOT NULL
+);
+
+-- Encrypted secrets. AES-256-GCM envelopes (salt+iv+tag+data hex JSON),
+-- one row per env-var-shaped key (`ANTHROPIC_API_KEY`, `OPENAI_CODEX_OAUTH`, …).
+-- The encryption key is derived from the bootstrap web token (PBKDF2-SHA256,
+-- 100k iterations) — same crypto as the previous file-based secrets.enc,
+-- now atomic with the rest of the DB.
+CREATE TABLE secrets (
+  key         TEXT PRIMARY KEY,
+  envelope    TEXT NOT NULL,
+  updated_at  INTEGER NOT NULL
+);
+
+-- Plaintext config. Same env-var-shaped keys as secrets, but for values
+-- that don't need confidentiality (server URLs, region slugs, project IDs).
+-- The application layer enforces a CONFIG_KEYS allowlist on writes so a
+-- typo can't put a secret in this table.
+CREATE TABLE config (
+  key         TEXT PRIMARY KEY,
+  value       TEXT NOT NULL,
+  updated_at  INTEGER NOT NULL
+);

package/dist/migrations/0002_profile_groups.sql

@@ -0,0 +1,39 @@
+-- Profile groups — preconfigured team templates. A ProfileGroup captures
+-- the recipe for a team (ordered slots, each pointing at a Profile with
+-- optional per-slot overrides) so an operator can replay it with a single
+-- spawn call instead of clicking through agent-create N times per project.
+--
+-- Strictly additive: the single-profile `POST /api/agents` spawn path is
+-- untouched. Profile groups bundle existing primitives (profiles, groups,
+-- agents), they don't replace them.
+--
+-- Spawn semantics live in apps/daemon/src/core/profile-group/spawn.ts.
+-- See docs/backlog/todo/BAZ-002-profile-groups.md for the full spec.
+
+CREATE TABLE profile_groups (
+  id              TEXT PRIMARY KEY,        -- slug, e.g. "platform-team"
+  name            TEXT NOT NULL,           -- display name
+  user_md         TEXT,                    -- optional starter USER.md; seeded only into a freshly-created target group (pre-existing groups are left alone — see Decision #5)
+  created_at      INTEGER NOT NULL,
+  updated_at      INTEGER NOT NULL
+);
+
+-- Member ordering uses an explicit `position` column rather than insertion
+-- order so the spawn loop is deterministic and rollback can identify which
+-- members succeeded. PK includes position so the same template can have
+-- multiple members pointing at the same profile (e.g. "two reviewers" —
+-- duplicate agent_name values are intentionally accepted; the spawn op
+-- auto-suffixes collisions with `-2`, `-3`, ... at spawn time).
+--
+-- `ON DELETE RESTRICT` on profile_id prevents deleting a profile that a
+-- profile-group member still references; the existing single-profile delete
+-- keeps working unchanged because it never had a referrer before.
+CREATE TABLE profile_group_members (
+  profile_group_id TEXT NOT NULL REFERENCES profile_groups(id) ON DELETE CASCADE,
+  position         INTEGER NOT NULL,
+  profile_id       TEXT NOT NULL REFERENCES profiles(id) ON DELETE RESTRICT,
+  agent_name       TEXT NOT NULL,          -- e.g. "planner", "reviewer"
+  model_override   TEXT,                   -- nullable; falls back to profile.default_model
+  reasoning_level  TEXT,                   -- nullable; falls back to spawn default 'medium'
+  PRIMARY KEY (profile_group_id, position)
+);

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

@@ -32,7 +32,7 @@ import { existsSync as existsSync4, readdirSync } from "fs";
 import { join as join3 } from "path";
 
 // ../daemon/src/core/db/client.ts
-import { DatabaseSync } from "sqlite";
+import { DatabaseSync } from "node:sqlite";
 
 // ../daemon/src/core/db/migrate.ts
 import { readdirSync as readdirSync2, readFileSync as readFileSync3 } from "fs";
@@ -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