@capybara-hq/kernel 0.1.0-rc.20 → 0.1.0-rc.22

package/src/migrations/0113_scheduled_tasks.sql

@@ -0,0 +1,108 @@
+-- Scheduled tasks (spec 2026-11-11-scheduled-tasks-design.md §4).
+-- A task belongs to its org; the creator, agent and target conversation carry no foreign key: when
+-- they go, the fire job pauses the task with a reason (creator_inactive / agent_gone /
+-- conversation_gone) instead of the row vanishing.
+CREATE TABLE IF NOT EXISTS scheduled_tasks (
+  id text PRIMARY KEY,
+  org_id text NOT NULL REFERENCES orgs(id) ON DELETE CASCADE,
+  account_id text NOT NULL,
+  agent_id text NOT NULL,
+  name text NOT NULL,
+  prompt text NOT NULL,
+  -- { kind: 'cron', expr, timeZone } or { kind: 'once', at, timeZone }; timeZone is an IANA name
+  trigger jsonb NOT NULL,
+  mode text NOT NULL CHECK (mode IN ('new', 'conversation', 'chat')),
+  -- conversation mode only
+  conversation_id text,
+  -- chat mode only: { connectionId, chatId, chatType }
+  chat jsonb,
+  -- null = the agent's defaults
+  model jsonb,
+  effort text,
+  -- null = the default pick for new conversations
+  device_id text,
+  status text NOT NULL DEFAULT 'active' CHECK (status IN ('active', 'paused', 'ended')),
+  pause_reason text CHECK (pause_reason IN ('creator', 'admin', 'failures', 'creator_inactive',
+    'agent_gone', 'target_gone', 'conversation_gone', 'org_disabled', 'expired',
+    'invalid_schedule')),
+  paused_by text,
+  -- null when not active; jitter included
+  next_run_at timestamptz,
+  jitter_seconds integer NOT NULL DEFAULT 0,
+  expires_at timestamptz,
+  consecutive_failures integer NOT NULL DEFAULT 0,
+  created_at timestamptz NOT NULL DEFAULT now(),
+  updated_at timestamptz NOT NULL DEFAULT now(),
+  deleted_at timestamptz
+);
+
+-- the scanner's due query
+CREATE INDEX IF NOT EXISTS scheduled_tasks_due_idx ON scheduled_tasks (next_run_at)
+  WHERE status = 'active' AND deleted_at IS NULL;
+-- a creator's list and the per-member cap
+CREATE INDEX IF NOT EXISTS scheduled_tasks_account_idx ON scheduled_tasks (org_id, account_id)
+  WHERE deleted_at IS NULL;
+
+-- One row per tick (and per trial run). scheduled_for is the tick before jitter.
+CREATE TABLE IF NOT EXISTS scheduled_task_runs (
+  id text PRIMARY KEY,
+  task_id text NOT NULL REFERENCES scheduled_tasks(id) ON DELETE CASCADE,
+  org_id text NOT NULL REFERENCES orgs(id) ON DELETE CASCADE,
+  scheduled_for timestamptz NOT NULL,
+  fired_at timestamptz,
+  trial boolean NOT NULL DEFAULT false,
+  -- a person's "run now" (trial or not), outside the schedule: it runs even while the task is paused
+  manual boolean NOT NULL DEFAULT false,
+  conversation_id text,
+  run_id text,
+  status text NOT NULL DEFAULT 'pending'
+    CHECK (status IN ('pending', 'running', 'completed', 'failed', 'skipped')),
+  skip_reason text CHECK (skip_reason IN ('missed', 'overlap', 'rate_limited', 'queue_paused',
+    'removed', 'device_offline', 'creator_inactive', 'agent_gone', 'target_gone',
+    'conversation_gone', 'org_disabled', 'unsupported_target', 'task_deleted', 'task_paused')),
+  error text,
+  -- tool keys refused for lack of a grant (§7)
+  missing_grants jsonb NOT NULL DEFAULT '[]'::jsonb,
+  -- when the scanner's repair last found this started run still in flight (rotates its rechecks)
+  rechecked_at timestamptz
+);
+
+-- the exactly-once guard: one scheduled run per tick (trial runs are free of it)
+CREATE UNIQUE INDEX IF NOT EXISTS scheduled_task_runs_tick_uq ON scheduled_task_runs (task_id, scheduled_for)
+  WHERE NOT trial;
+-- the scanner's repair of lost fire jobs (pending runs never fired)
+CREATE INDEX IF NOT EXISTS scheduled_task_runs_pending_idx ON scheduled_task_runs (scheduled_for)
+  WHERE status = 'pending';
+-- a task's history and its latest run
+CREATE INDEX IF NOT EXISTS scheduled_task_runs_task_idx ON scheduled_task_runs (task_id, scheduled_for DESC);
+-- the org's maxRunsPerHour count
+CREATE INDEX IF NOT EXISTS scheduled_task_runs_fired_idx ON scheduled_task_runs (org_id, fired_at)
+  WHERE fired_at IS NOT NULL;
+
+-- A task's "always allow" grants: the shape and meaning of conversation_tool_grants (a grant stops
+-- applying when spec_hash changes or the connector is not the same one).
+CREATE TABLE IF NOT EXISTS scheduled_task_grants (
+  task_id text NOT NULL REFERENCES scheduled_tasks(id) ON DELETE CASCADE,
+  tool_key text NOT NULL,
+  spec_hash text NOT NULL,
+  connector_id text,
+  created_at timestamptz NOT NULL DEFAULT now(),
+  PRIMARY KEY (task_id, tool_key)
+);
+
+-- Marks a run as unattended and links it to its task run; inherited by the runs that descend from
+-- it without a person (sub-agents, wakes caused by an unattended run).
+ALTER TABLE runs ADD COLUMN IF NOT EXISTS scheduled_task_run_id text;
+-- Set on the conversations a new-mode task creates.
+ALTER TABLE conversations ADD COLUMN IF NOT EXISTS scheduled_task_id text;
+CREATE INDEX IF NOT EXISTS conversations_scheduled_task_idx ON conversations (scheduled_task_id)
+  WHERE scheduled_task_id IS NOT NULL;
+-- The schedule marker of a queued task message (ScheduleMarker); null for a person's message.
+ALTER TABLE conversation_queue ADD COLUMN IF NOT EXISTS schedule jsonb;
+-- A group chat run's delivery whose thread is not bound yet (§8): the account its thread row gets
+-- once outbound has the run's first post (thread key = that message's id); null afterwards.
+ALTER TABLE channel_deliveries ADD COLUMN IF NOT EXISTS pending_thread_account_id text;
+-- The chats a person can point a chat task at (`GET …/schedules/chat-targets`) and the fire's
+-- thread checks read their thread rows by account; anonymous visitors' rows (no account) never.
+CREATE INDEX IF NOT EXISTS channel_threads_account_idx ON channel_threads (account_id, connection_id)
+  WHERE account_id IS NOT NULL;

package/src/migrations/0114_network_asks.sql

@@ -0,0 +1,23 @@
+-- Network asks (network ask-to-allow spec §6.1): an approval of kind 'network' asks the device owner
+-- to allow domains a command was refused. `detail` holds the hosts, the command, the kept command
+-- result and, once decided, what took effect. A network ask shares the (run_id, call_id, attempt)
+-- numbering of its call with the call's tool approvals: it takes the next attempt after them, and
+-- is only asked after the command ran, so no tool approval of the call can follow it.
+ALTER TABLE approvals ADD COLUMN IF NOT EXISTS kind text NOT NULL DEFAULT 'tool';
+ALTER TABLE approvals DROP CONSTRAINT IF EXISTS approvals_kind_check;
+ALTER TABLE approvals ADD CONSTRAINT approvals_kind_check CHECK (kind IN ('tool', 'network'));
+ALTER TABLE approvals ADD COLUMN IF NOT EXISTS detail jsonb;
+
+-- A message from the run's starter skips a pending network ask (spec §6.7). Widening the inline
+-- CHECK of 0010 (PG's default name approvals_status_check), like 0108 did for questions.
+ALTER TABLE approvals DROP CONSTRAINT IF EXISTS approvals_status_check;
+ALTER TABLE approvals ADD CONSTRAINT approvals_status_check
+  CHECK (status IN ('pending', 'approved', 'denied', 'expired', 'cancelled', 'skipped'));
+
+-- Run grants and the per-run caps read the network asks of a run tree.
+CREATE INDEX IF NOT EXISTS approvals_network_run_idx ON approvals (run_id) WHERE kind = 'network';
+
+-- What the machine's program reported in its hello (spec §5.4): the features it supports and a
+-- summary of its local network policy, refreshed by each `policy` operation.
+ALTER TABLE device_machines ADD COLUMN IF NOT EXISTS features text[] NOT NULL DEFAULT '{}';
+ALTER TABLE device_machines ADD COLUMN IF NOT EXISTS local_policy jsonb;

package/src/migrations/0115_network_requests.sql

@@ -0,0 +1,28 @@
+-- Org-layer network requests (network ask-to-allow spec §5.3, plan decision P-D6): a member asks the
+-- org admins to add hosts to the org's sandbox egress allowlist. A `network_allowlist` request names
+-- no item, entry or agent; `detail` holds what it asks for ({ hosts, conversationId, agentId }).
+-- Expand-only: the new column is nullable and the dropped checks are added back, wider, in this file.
+
+ALTER TABLE catalog_requests ADD COLUMN IF NOT EXISTS detail jsonb;
+
+-- capybara:allow-destructive the check is added back with `network_allowlist` in the next statement; existing rows satisfy it
+ALTER TABLE catalog_requests DROP CONSTRAINT IF EXISTS catalog_requests_kind_check;
+ALTER TABLE catalog_requests ADD CONSTRAINT catalog_requests_kind_check
+  CHECK (kind IN ('access', 'import', 'enable', 'connector_setup', 'network_allowlist'));
+
+-- capybara:allow-destructive the check is added back with the network_allowlist branch in the next statement; existing rows satisfy its other branches
+ALTER TABLE catalog_requests DROP CONSTRAINT IF EXISTS catalog_requests_target_check;
+ALTER TABLE catalog_requests ADD CONSTRAINT catalog_requests_target_check
+  CHECK (
+    kind = 'import' AND entry_name IS NOT NULL
+    OR kind = 'connector_setup' AND agent_id IS NOT NULL
+      AND item_id IS NULL AND entry_name IS NULL
+    OR kind = 'network_allowlist' AND detail IS NOT NULL
+      AND item_id IS NULL AND agent_id IS NULL AND entry_name IS NULL
+    OR kind NOT IN ('import', 'connector_setup', 'network_allowlist') AND item_id IS NOT NULL
+  );
+
+-- `detail` is a JSON object when set.
+ALTER TABLE catalog_requests DROP CONSTRAINT IF EXISTS catalog_requests_detail_check;
+ALTER TABLE catalog_requests ADD CONSTRAINT catalog_requests_detail_check
+  CHECK (detail IS NULL OR jsonb_typeof(detail) = 'object');

package/src/migrations/0116_skills_default_on.sql

@@ -0,0 +1,37 @@
+-- Skills are on by default and pinning is gone (spec 2026-11-12-skills-default-on-design.md §4,
+-- §5): an agent stores only what it turns off (`disabledSkills`), not selected (`skills.orgSkills`)
+-- or pinned (`skills.pinned`) skills. Every stored agent version, older ones included (a rollback
+-- reads the same shape), becomes "nothing turned off"; `skills` stays only while it still holds
+-- something (`writePolicy`). Idempotent: rows already rewritten match neither statement.
+UPDATE agent_versions
+SET definition = CASE
+    WHEN ((definition -> 'skills') - 'orgSkills' - 'pinned') = '{}'::jsonb
+      THEN definition - 'skills'
+    ELSE jsonb_set(definition, '{skills}', (definition -> 'skills') - 'orgSkills' - 'pinned')
+  END
+WHERE jsonb_typeof(definition -> 'skills') = 'object'
+  AND ((definition -> 'skills') ? 'orgSkills' OR (definition -> 'skills') ? 'pinned');
+
+UPDATE agent_versions
+SET definition = definition || jsonb_build_object('disabledSkills', '[]'::jsonb)
+WHERE NOT definition ? 'disabledSkills';
+
+-- Org-made agent templates (saved from an agent by an org admin: no plugin, no catalog item) lose
+-- `selectedSkills`: with skills on by default there is nothing to select. Templates from plugin
+-- packages keep what the package wrote (the kernel's template reader drops the field).
+UPDATE agent_template_versions AS v
+SET definition = v.definition - 'selectedSkills'
+FROM agent_templates AS t
+WHERE t.id = v.template_id
+  AND t.plugin_name IS NULL
+  AND t.catalog_item_id IS NULL
+  AND v.definition ? 'selectedSkills';
+
+UPDATE platform_agent_template_versions AS v
+SET definition = v.definition - 'selectedSkills'
+FROM platform_agent_templates AS t
+WHERE t.id = v.template_id
+  AND t.plugin_name IS NULL
+  AND t.catalog_item_id IS NULL
+  AND v.object_prefix IS NULL
+  AND v.definition ? 'selectedSkills';

package/src/migrations/0117_sandbox_tiers.sql

@@ -0,0 +1,11 @@
+-- Sandbox tiers (sandbox dev tiers spec §7.2, §12). A cloud device's own tier: null follows the
+-- org's default. A local device keeps its tier in its machine's policy.json, never here.
+ALTER TABLE devices ADD COLUMN IF NOT EXISTS tier text;
+ALTER TABLE devices DROP CONSTRAINT IF EXISTS devices_tier_check;
+ALTER TABLE devices ADD CONSTRAINT devices_tier_check CHECK (tier IN ('strict', 'dev', 'open'));
+
+-- The limits in force on the device's instance, `{ tier, egress }`, written by the fenced create
+-- (or the file system create, for a provider whose limits apply there) and by an applied
+-- `update`. Null (instances made before this migration) differs from every effective tier, so
+-- the first use after the upgrade applies the new one.
+ALTER TABLE device_instances ADD COLUMN IF NOT EXISTS instance_limits jsonb;