thinkwork-cli 0.13.1 → 1.0.0

package/dist/drizzle/0283_agents_agentcore_runtime_dispatch.sql

@@ -0,0 +1,13 @@
+-- THINK-585 U6 (KTD3): per-agent AgentCore Runtime dispatch flag.
+-- When true AND the stage kill-switch (AGENTCORE_RUNTIME_DISPATCH_ENABLED
+-- runtime-config key) is on, chat turns dispatch through the
+-- agentcore-runtime-dispatch Lambda to the Bedrock AgentCore Runtime with a
+-- per-thread session instead of the Pi Lambda. Additive + default false —
+-- safe to apply ahead of code deploy.
+--
+-- Hand-rolled (drizzle meta journal is not in use for this change);
+-- apply with: psql "$DATABASE_URL" -f drizzle/0283_agents_agentcore_runtime_dispatch.sql
+-- creates-column: public.agents.agentcore_runtime_dispatch
+
+ALTER TABLE public.agents
+  ADD COLUMN IF NOT EXISTS agentcore_runtime_dispatch boolean NOT NULL DEFAULT false;

package/dist/drizzle/0284_user_brain_claims.sql

@@ -0,0 +1,69 @@
+-- User brain claims (THINK-625): per-(tenant, user) Company Brain
+-- authorization, the write side of the user-claims/v1 manifest published to
+-- `user-claims/<tenantId>/latest.json` in the brain-artifacts bucket.
+--
+-- Ships three things that must land together, because the publisher is
+-- useless without the safety interlock and the audit row cannot be written
+-- without the widened event-type constraint:
+--   1. the user_brain_claims table,
+--   2. tenant_settings.brain_user_claims_enabled (default false),
+--   3. the tenant_policy_events event_type CHECK widened to accept
+--      'user_brain_claims' (renamed to _v2 so drift is detectable).
+--
+-- Hand-rolled (partial-index-free but with a NULL-vs-empty array column the
+-- generator flattens; mirrors the 0274/0281/0282 convention). Not registered
+-- in meta/_journal.json.
+-- Apply via: psql "$DATABASE_URL" -f drizzle/0284_user_brain_claims.sql
+-- creates: public.user_brain_claims
+-- creates: public.uq_user_brain_claims_tenant_user
+-- creates: public.idx_user_brain_claims_tenant
+-- creates-column: public.tenant_settings.brain_user_claims_enabled
+-- creates-constraint: public.tenant_policy_events.tenant_policy_events_event_type_allowed_v2
+
+CREATE TABLE IF NOT EXISTS public.user_brain_claims (
+  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
+  tenant_id uuid NOT NULL REFERENCES public.tenants(id) ON DELETE CASCADE,
+  user_id uuid NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
+  -- '[]' = PUBLIC graph only; ARRAY['*'] = every group.
+  security_groups text[] NOT NULL DEFAULT ARRAY[]::text[],
+  -- KB is grant-only: '[]' = no KB at all; ARRAY['*'] = every collection.
+  kb_collections text[] NOT NULL DEFAULT ARRAY[]::text[],
+  kb_bundles jsonb NOT NULL DEFAULT '{}'::jsonb,
+  default_kb_bundle text,
+  -- NULL is DISTINCT from '{}': NULL = the Brain surface default applies,
+  -- '{}' = no tools at all. Never coalesce one into the other.
+  tool_allowlist text[],
+  is_operator boolean NOT NULL DEFAULT false,
+  kb_trace boolean NOT NULL DEFAULT false,
+  -- false still publishes an entry (disabled: true) so the Brain fails
+  -- closed rather than falling back to legacy group grants.
+  enabled boolean NOT NULL DEFAULT true,
+  notes text,
+  created_at timestamptz NOT NULL DEFAULT now(),
+  updated_at timestamptz NOT NULL DEFAULT now(),
+  updated_by_user_id uuid
+);
+
+CREATE UNIQUE INDEX IF NOT EXISTS uq_user_brain_claims_tenant_user
+  ON public.user_brain_claims (tenant_id, user_id);
+
+CREATE INDEX IF NOT EXISTS idx_user_brain_claims_tenant
+  ON public.user_brain_claims (tenant_id);
+
+-- Per-tenant enable flag. Default false everywhere: claims rows are
+-- editable with no publish until an operator flips this on.
+ALTER TABLE public.tenant_settings
+  ADD COLUMN IF NOT EXISTS brain_user_claims_enabled boolean NOT NULL DEFAULT false;
+
+-- Widen the audited event types. The old constraint is dropped and a
+-- freshly-named one created so `pnpm db:migrate-manual` can prove the
+-- widened version is actually present in the target database.
+ALTER TABLE public.tenant_policy_events
+  DROP CONSTRAINT IF EXISTS tenant_policy_events_event_type_allowed;
+
+ALTER TABLE public.tenant_policy_events
+  DROP CONSTRAINT IF EXISTS tenant_policy_events_event_type_allowed_v2;
+
+ALTER TABLE public.tenant_policy_events
+  ADD CONSTRAINT tenant_policy_events_event_type_allowed_v2
+  CHECK (event_type IN ('sandbox_enabled','compliance_tier','user_brain_claims'));

package/dist/drizzle/0285_tenant_mcp_twin_keys_trusted_subsystem.sql

@@ -0,0 +1,30 @@
+-- Trusted-subsystem marker on tenant_mcp_twin_keys (THINK-626) — the write
+-- side of the `trustedSubsystem` field in key manifest v2
+-- (twin-mcp-keys/v2; reader is company-brain brain-mcp/src/auth.ts).
+--
+-- true lets the key assert `on_behalf_of` per tools/call — running the call
+-- under the named signed-in human's user-claims entry instead of under the
+-- key's own grants. It is NOT a grant and it can never widen anyone: the
+-- asserted user's grants come from the user-claims manifest, and a tenant
+-- that publishes none refuses the assertion. It belongs only on keys the
+-- platform itself holds (the Pi runtime's provisioned "default" connector
+-- key), never on one handed to a customer's client — hence default false
+-- and no backfill for user-minted rows.
+--
+-- Hand-rolled (mirrors the 0274/0281/0282 convention; not registered in
+-- meta/_journal.json).
+-- Apply via: psql "$DATABASE_URL" -f drizzle/0285_tenant_mcp_twin_keys_trusted_subsystem.sql
+-- creates-column: public.tenant_mcp_twin_keys.trusted_subsystem
+
+ALTER TABLE public.tenant_mcp_twin_keys
+  ADD COLUMN IF NOT EXISTS trusted_subsystem boolean NOT NULL DEFAULT false;
+
+-- The platform-provisioned connector key ("default") is the ThinkWork Pi
+-- runtime's own key — the one and only principal that may speak for a
+-- signed-in human. Grandfather every active one; re-provisioning would set
+-- the same flag anyway. User-minted keys stay false.
+UPDATE public.tenant_mcp_twin_keys
+   SET trusted_subsystem = true
+ WHERE name = 'default'
+   AND revoked_at IS NULL
+   AND trusted_subsystem = false;

package/dist/drizzle/0286_brain_analytics_key.sql

@@ -0,0 +1,26 @@
+-- Analytics-channel visibility flag on Brain principals (THINK-656 D4) —
+-- the write side of the `analyticsKey` field in both published manifests:
+-- user-claims/v1 (per-user entries) and twin-mcp-keys/v2 (key entries).
+-- Reader is company-brain brain-mcp/src/auth.ts, which parses literal true
+-- only: `analyticsKey: true` lets the principal's brain_ask loop consult
+-- the mart_analytics briefing tools. Tool VISIBILITY only, never a data
+-- grant — the marts hold the tenant's own data and every query still runs
+-- under the account's env gates (ANALYTICS_ENABLED et al.).
+--
+-- Default TRUE by decision (Eric, 2026-08-08): every user and key gets the
+-- analytics channel unless an operator turns it off per row. There is no
+-- console UI for the flag yet; the column is the future toggle. The NOT
+-- NULL DEFAULT true also backfills every existing row, which matches the
+-- 2026-08-07 go-live hand-edits this migration makes durable.
+--
+-- Hand-rolled (mirrors the 0274/0281/0282/0284/0285 convention; not
+-- registered in meta/_journal.json).
+-- Apply via: psql "$DATABASE_URL" -f drizzle/0286_brain_analytics_key.sql
+-- creates-column: public.tenant_mcp_twin_keys.analytics_key
+-- creates-column: public.user_brain_claims.analytics_key
+
+ALTER TABLE public.tenant_mcp_twin_keys
+  ADD COLUMN IF NOT EXISTS analytics_key boolean NOT NULL DEFAULT true;
+
+ALTER TABLE public.user_brain_claims
+  ADD COLUMN IF NOT EXISTS analytics_key boolean NOT NULL DEFAULT true;

package/dist/drizzle/0287_brain_subject.sql

@@ -0,0 +1,25 @@
+-- Brain-pool subject on Brain principals (THINK-625 backfill gap) — the
+-- write side of the `subject` field in user-claims/v1.
+--
+-- The manifest published `users.cognito_sub` as `subject`, but that column
+-- is the user's sub in THIS product's Cognito pool. The Brain MCP has its
+-- OWN end-user pool, and a federated (Google/Microsoft) sign-in there mints
+-- a DIFFERENT sub — so the published subject never matched the Brain access
+-- token, claims resolution fell closed to emptyGrants(), and an HR user's
+-- payroll ask was refused (TEI, 2026-08-12). Access tokens carry no email
+-- claim, so the reader's email fallback cannot save the mismatch.
+--
+-- This column holds the sub the user's Brain tokens actually carry. It is
+-- captured at the ONE place the product ever sees a Brain token: the
+-- mcp-oauth callback (skills.ts), which decodes the access token it just
+-- exchanged and republishes the manifest. The manifest publisher prefers
+-- brain_subject over users.cognito_sub; NULL (never captured) keeps
+-- today's fallback byte-identical.
+--
+-- Hand-rolled (mirrors the 0274/0281/0282/0284/0285/0286 convention; not
+-- registered in meta/_journal.json).
+-- Apply via: psql "$DATABASE_URL" -f drizzle/0287_brain_subject.sql
+-- creates-column: public.user_brain_claims.brain_subject
+
+ALTER TABLE public.user_brain_claims
+  ADD COLUMN IF NOT EXISTS brain_subject text;

package/dist/drizzle/0288_multi_lane_identities.sql

@@ -0,0 +1,25 @@
+-- Multi-lane identity enrollment (Eric 2026-08-15: "I need all three" —
+-- email, Google AND Microsoft sign-in for one person).
+--
+-- uq_user_auth_identities_cognito_sub allowed ONE enrollment per Cognito
+-- subject, total. But a Cognito user with linked providers carries one sub
+-- across lanes (password + Microsoft on the same sub), so whichever lane
+-- enrolled first consumed the slot and every other lane admitted to
+-- "No tenant assigned". Admission already matches per-connection
+-- (auth-admission.ts: identity.authProviderResourceId === route.connectionId);
+-- the index was the only thing forcing one lane per person.
+--
+-- One row per (subject, connection) from now on. The invariant that one
+-- Cognito subject maps to ONE product user is no longer carried by this
+-- index — the writers enforce it (cross-user guard in auto-link, enrollment
+-- consume, and invite).
+--
+-- Hand-rolled (mirrors the 0274..0287 convention; not registered in
+-- meta/_journal.json).
+-- Apply via: psql "$DATABASE_URL" -f drizzle/0288_multi_lane_identities.sql
+-- drops: public.uq_user_auth_identities_cognito_sub
+-- creates: public.uq_user_auth_identities_sub_connection
+
+DROP INDEX IF EXISTS public.uq_user_auth_identities_cognito_sub;
+CREATE UNIQUE INDEX IF NOT EXISTS uq_user_auth_identities_sub_connection
+  ON public.user_auth_identities (cognito_issuer, cognito_sub, auth_provider_resource_id);