@stackbone/cli 0.7.0 → 0.8.0

package/migrations/0114_memory_person_id.sql

@@ -0,0 +1,16 @@
+-- STA3-33: Studio and the box address a person by this opaque per-agent id
+-- instead of the phone or email in user_id, which leaked into URLs and logs.
+-- It lives on the revision row because an erase bumps the revision and keeps
+-- the row, so a person who is deleted and comes back keeps the same id.
+
+ALTER TABLE stackbone_platform.memory_user_revisions
+  ADD COLUMN person_id uuid NOT NULL DEFAULT gen_random_uuid(),
+  ADD CONSTRAINT memory_user_revisions_person_id_key UNIQUE (person_id);
+
+-- A person with facts or calls but no revision row yet has no id to open.
+INSERT INTO stackbone_platform.memory_user_revisions (agent_id, user_id, revision)
+SELECT agent_id, user_id, 0 FROM (
+  SELECT agent_id, user_id FROM stackbone_platform.memory_facts
+  UNION SELECT agent_id, user_id FROM stackbone_platform.memory_calls
+) AS people
+ON CONFLICT (agent_id, user_id) DO NOTHING;

package/migrations/0115_memory_erased_person_keeps_no_identifier.sql

@@ -0,0 +1,31 @@
+-- STA3-35: an erase keeps the revision row as a tombstone, so an add that
+-- snapshotted before the erase still fails its revision check and cannot write
+-- the erased memory back. The tombstone kept the phone or email in user_id; it
+-- now keeps only the opaque person_id, so user_id is nullable and person_id is
+-- the key. UNIQUE (agent_id, user_id) stays the lookup the SDK's
+-- ON CONFLICT (agent_id, user_id) infers, and Postgres treats NULLs as
+-- distinct, so an agent can hold many erased rows.
+
+ALTER TABLE stackbone_platform.memory_user_revisions
+  DROP CONSTRAINT memory_user_revisions_pkey;
+ALTER TABLE stackbone_platform.memory_user_revisions
+  ALTER COLUMN user_id DROP NOT NULL,
+  ADD CONSTRAINT memory_user_revisions_pkey PRIMARY KEY (person_id),
+  DROP CONSTRAINT memory_user_revisions_person_id_key,
+  ADD CONSTRAINT memory_user_revisions_agent_id_user_id_key UNIQUE (agent_id, user_id);
+
+-- People erased before this change. Only an erase deletes memory_calls, and
+-- every committed add writes a call with its revision bump, so a row with no
+-- facts and no calls on its own agent is an erased tombstone. The rule holds
+-- only here: once adds claim the row at snapshot, a failed add can leave such
+-- a row for a live person.
+UPDATE stackbone_platform.memory_user_revisions AS revisions
+SET user_id = NULL
+WHERE NOT EXISTS (
+    SELECT 1 FROM stackbone_platform.memory_facts AS facts
+    WHERE facts.agent_id = revisions.agent_id AND facts.user_id = revisions.user_id
+  )
+  AND NOT EXISTS (
+    SELECT 1 FROM stackbone_platform.memory_calls AS calls
+    WHERE calls.agent_id = revisions.agent_id AND calls.user_id = revisions.user_id
+  );

package/migrations/0116_rag_hybrid_search.sql

@@ -0,0 +1,14 @@
+-- STA3-57: lexical + hybrid search, opt-in per collection.
+ALTER TABLE stackbone_platform.rag_collections
+  ADD COLUMN IF NOT EXISTS hybrid_enabled boolean NOT NULL DEFAULT false,
+  ADD COLUMN IF NOT EXISTS number_format text NOT NULL DEFAULT 'eu'
+    CONSTRAINT rag_collections_number_format_check CHECK (number_format IN ('eu', 'us'));
+
+-- Nullable: ingest writes the terms only while the collection has hybrid on
+-- (STA3-57 D11). The terms are normalised in TypeScript, so no `unaccent` (D6).
+ALTER TABLE stackbone_platform.rag_chunks
+  ADD COLUMN IF NOT EXISTS lexical tsvector;
+
+-- Built under the migrator's advisory lock, like the 1536 index in 0103.
+CREATE INDEX IF NOT EXISTS rag_chunks_lexical_gin
+  ON stackbone_platform.rag_chunks USING gin (lexical);

package/migrations/0117_rag_extract_fields.sql

@@ -0,0 +1,3 @@
+ALTER TABLE stackbone_platform.rag_collections
+  ADD COLUMN IF NOT EXISTS extract_enabled boolean NOT NULL DEFAULT false,
+  ADD COLUMN IF NOT EXISTS extract_fields jsonb NOT NULL DEFAULT '[]';

package/migrations/0118_voice_outbound_calls.sql

@@ -0,0 +1,29 @@
+-- 0118_voice_outbound_calls.sql — the answered outbound calls a workflow placed
+-- (`placeCall`, STA3-56) whose `onEnd` workflow has not started yet.
+--
+-- A row is written when the callee answers and deleted once `onEnd` has started,
+-- so the table holds only live calls and the phone number never outlives the
+-- call. It lives in Postgres, not in the box's memory, because the fallback that
+-- starts `onEnd` for a worker that never posts its completion must also cover a
+-- box that restarted mid-call.
+--
+-- `claimed_at` is the once-only guard: whoever sets it from NULL (the worker's
+-- `/complete` or the sweep) starts `onEnd`. A claim older than the sweep's
+-- reclaim window belongs to a box that died between the claim and the start, and
+-- may be taken again. `room_gone_at` is when the sweep first saw the LiveKit room
+-- gone; the sweep gives the worker a grace period after it before it ends the
+-- call as `failed`.
+--
+-- `context` is what the workflow passed to `placeCall`, opaque to the box and
+-- never logged.
+CREATE TABLE IF NOT EXISTS stackbone_platform.voice_outbound_calls (
+    session_key   text        PRIMARY KEY,
+    room          text        NOT NULL,
+    agent         text        NOT NULL,
+    to_number     text        NOT NULL,
+    context       jsonb       NOT NULL,
+    on_end        text        NOT NULL,
+    answered_at   timestamptz NOT NULL,
+    room_gone_at  timestamptz NULL,
+    claimed_at    timestamptz NULL
+);

package/migrations/0119_voice_call_metrics.sql

@@ -0,0 +1,20 @@
+-- 0119_voice_call_metrics.sql — the latencies of each answered turn of a voice call,
+-- as LiveKit measured them in the voice worker (STA3-56).
+--
+-- The worker sends them once, with the transcript, in the call's `/complete`; the
+-- box writes one row per call and never updates it. It is keyed by the call's
+-- session id, the same one `voice_recordings` uses, so a screen that shows a call
+-- finds its recording and its latencies by one id. A second `/complete` of the same
+-- call shares the first one's result, so the row cannot be written twice; the
+-- insert still skips a conflict rather than fail a completion over a duplicate.
+--
+-- `turns` is the worker's array as the box validated it
+-- (`voiceCallTurnMetricsSchema`): numbers only, no transcript text and nothing that
+-- names the caller, which is why the memory erase does not touch this table.
+CREATE TABLE IF NOT EXISTS stackbone_platform.voice_call_metrics (
+    session_id   uuid        PRIMARY KEY,
+    agent        text        NOT NULL,
+    session_key  text        NOT NULL,
+    turns        jsonb       NOT NULL,
+    created_at   timestamptz NOT NULL DEFAULT now()
+);

package/migrations/0120_run_steps_voice.sql

@@ -0,0 +1,19 @@
+-- 0120_run_steps_voice.sql — a `voice` step: one phase of how long a voice turn made
+-- its caller wait (STA3-56).
+--
+-- The voice worker measures each answered turn with LiveKit (end of turn, speech to
+-- text, the agent's first token, speech synthesis, and the whole wait) and sends the
+-- numbers once, in the call's `/complete`. The box then writes them as steps on the
+-- run that answered the turn, so the run's trace shows them on the same time axis
+-- as its `model_call`: a `Wait` parent and one child per phase. Their times come
+-- from the run's own start, the box's clock, so a worker clock that drifts never
+-- moves them.
+ALTER TABLE stackbone_platform.run_steps
+    DROP CONSTRAINT IF EXISTS run_steps_type_check;
+
+ALTER TABLE stackbone_platform.run_steps
+    ADD CONSTRAINT run_steps_type_check
+        CHECK (type IN (
+            'workflow_step', 'model_call', 'connection', 'hook',
+            'tool_call', 'agent', 'guardrail', 'voice'
+        ));

package/migrations/0121_model_routing.sql

@@ -0,0 +1,28 @@
+-- 0121_model_routing.sql — the OpenRouter provider routing an operator picked
+-- for one model key of one deep agent (`provider: { sort }` on its model calls).
+--
+-- Addressed like `model_selections` (0073), by (owner_kind, owner_name, key), but
+-- its own table: `model_selections.model_id` is NOT NULL, and an agent that runs
+-- on the model its code names still needs a routing row. No row means the code's
+-- `modelRouting`, and with none written there, OpenRouter's default routing.
+--
+-- `sort` carries NO CHECK, for the reason 0073 has none on `owner_kind`: a box
+-- running an older build must be able to store a value it cannot apply, and the
+-- SDK ignores a sort it does not know.
+CREATE TABLE IF NOT EXISTS stackbone_platform.model_routing (
+    owner_kind  text        NOT NULL,
+    owner_name  text        NOT NULL,
+    key         text        NOT NULL,
+    sort        text        NOT NULL,
+    updated_by  text,
+    updated_at  timestamptz NOT NULL DEFAULT now(),
+    PRIMARY KEY (owner_kind, owner_name, key)
+);
+
+-- The voice settings leaf `fastModelRouting` is retired: provider routing now
+-- belongs to the agent's model keys. The settings schema is strict, so a stored
+-- override still holding the key would fail every read of that agent's settings.
+-- It never reached production, so the value is dropped rather than carried over.
+UPDATE stackbone_platform.voice_settings
+   SET overrides = overrides - 'fastModelRouting'
+ WHERE overrides ? 'fastModelRouting';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stackbone/cli",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "license": "UNLICENSED",
   "type": "module",
   "bin": {