@app-vitals/agent-admin 0.0.1 → 0.1.1

package/prisma/migrations/20260906000000_add_session_follow_notification_prefs_alert_state/migration.sql

@@ -0,0 +1,47 @@
+-- Session follow/notification-prefs/alert-state models (SES-6.1).
+-- Three additive tables; no changes to existing tables.
+
+-- CreateTable
+CREATE TABLE "SessionFollow" (
+    "id" TEXT NOT NULL,
+    "userEmail" TEXT NOT NULL,
+    "sessionSlug" TEXT NOT NULL,
+    "muted" BOOLEAN NOT NULL DEFAULT false,
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "SessionFollow_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateTable
+CREATE TABLE "UserNotificationPrefs" (
+    "userEmail" TEXT NOT NULL,
+    "autoFollowSessions" BOOLEAN NOT NULL DEFAULT true,
+    "reminderHourLocal" INTEGER NOT NULL DEFAULT 9,
+    "autoFollowSince" TIMESTAMP(3),
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "UserNotificationPrefs_pkey" PRIMARY KEY ("userEmail")
+);
+
+-- CreateTable
+CREATE TABLE "SessionAlertState" (
+    "id" TEXT NOT NULL,
+    "userEmail" TEXT NOT NULL,
+    "sessionSlug" TEXT NOT NULL,
+    "lastAlertedAt" TIMESTAMP(3),
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "SessionAlertState_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE INDEX "SessionFollow_sessionSlug_idx" ON "SessionFollow"("sessionSlug");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "SessionFollow_userEmail_sessionSlug_key" ON "SessionFollow"("userEmail", "sessionSlug");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "SessionAlertState_userEmail_sessionSlug_key" ON "SessionAlertState"("userEmail", "sessionSlug");

package/prisma/migrations/20260911000000_backfill_auto_follow_since/migration.sql

@@ -0,0 +1,16 @@
+-- Backfill the auto-follow opt-in boundary for pre-existing prefs rows.
+--
+-- `UserNotificationPrefs.autoFollowSessions` defaults to true and a row is
+-- created just by loading the session settings page, so every row that existed
+-- before session-alert-sweeper.ts shipped sits in the null ("no boundary")
+-- cohort. Without this backfill the sweeper's first tick after deploy would
+-- auto-follow every currently-waiting session for those users and immediately
+-- push each one — the pre-existing-backlog burst the boundary exists to
+-- prevent.
+--
+-- Data-only: no schema change. Stamping `now()` means "auto-follow starts
+-- here", so only sessions that start waiting after the deploy are
+-- auto-followed. Explicit follows are untouched.
+UPDATE "UserNotificationPrefs"
+SET "autoFollowSince" = CURRENT_TIMESTAMP
+WHERE "autoFollowSince" IS NULL;

package/prisma/migrations/20260923115814_add_last_heartbeat_at_to_agent_cron_run/migration.sql

@@ -0,0 +1,2 @@
+-- AlterTable
+ALTER TABLE "AgentCronRun" ADD COLUMN     "lastHeartbeatAt" TIMESTAMP(3);

package/prisma/migrations/20260924120000_add_trial_expiry_fields_to_agent/migration.sql

@@ -0,0 +1,6 @@
+-- AddColumn: trialExpiresAt, trialExpiryWarnedAt TIMESTAMP(3) to Agent (additive, nullable, no backfill)
+-- ATE-1.1: trial expiry tracking. Both columns default to NULL — trialExpiresAt
+-- is user-settable via PATCH /agents/:id; trialExpiryWarnedAt is written
+-- internally by ATE-2.1's warning check.
+ALTER TABLE "Agent" ADD COLUMN     "trialExpiresAt" TIMESTAMP(3);
+ALTER TABLE "Agent" ADD COLUMN     "trialExpiryWarnedAt" TIMESTAMP(3);

package/prisma/migrations/20260929000000_add_agent_phase_methodology/migration.sql

@@ -0,0 +1,21 @@
+-- PMC-1.1: per-phase subagent-type override table. Additive; no changes to
+-- existing tables. `phase` is constrained to the six-value pipeline-phase
+-- enum (prd | plan-session | review | patch | deploy | dev-task) at the
+-- service/route layer (Zod), not here.
+
+-- CreateTable
+CREATE TABLE "AgentPhaseMethodology" (
+    "id" TEXT NOT NULL,
+    "agentId" TEXT NOT NULL,
+    "phase" TEXT NOT NULL,
+    "subagentType" TEXT,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "AgentPhaseMethodology_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE UNIQUE INDEX "AgentPhaseMethodology_agentId_phase_key" ON "AgentPhaseMethodology"("agentId", "phase");
+
+-- AddForeignKey
+ALTER TABLE "AgentPhaseMethodology" ADD CONSTRAINT "AgentPhaseMethodology_agentId_fkey" FOREIGN KEY ("agentId") REFERENCES "Agent"("id") ON DELETE CASCADE ON UPDATE CASCADE;

package/prisma/migrations/20260929120000_add_agent_policy_fields/migration.sql

@@ -0,0 +1,15 @@
+-- AddColumn: autoPostReviews, allowSelfReview, minConfidence, maxFindings,
+-- cleanupMergedWorktrees, cleanupAfterDays to Agent (additive, NOT NULL with
+-- defaults, no backfill UPDATE needed)
+-- APM-1.1: DB mirrors of the 6 real fields currently living only in each
+-- agent's own state/agent-policy.md. Every existing row gets the documented
+-- default via the column default below; a separate standalone script
+-- (agent/scripts/backfill-agent-policy.ts) later overwrites a given agent's
+-- row with its file's real values, same as patchAuthorAllowlist's original
+-- addition — a fresh column needs no in-migration backfill UPDATE.
+ALTER TABLE "Agent" ADD COLUMN     "autoPostReviews" BOOLEAN NOT NULL DEFAULT true;
+ALTER TABLE "Agent" ADD COLUMN     "allowSelfReview" BOOLEAN NOT NULL DEFAULT false;
+ALTER TABLE "Agent" ADD COLUMN     "minConfidence" INTEGER NOT NULL DEFAULT 75;
+ALTER TABLE "Agent" ADD COLUMN     "maxFindings" INTEGER NOT NULL DEFAULT 5;
+ALTER TABLE "Agent" ADD COLUMN     "cleanupMergedWorktrees" BOOLEAN NOT NULL DEFAULT true;
+ALTER TABLE "Agent" ADD COLUMN     "cleanupAfterDays" INTEGER NOT NULL DEFAULT 14;

package/prisma/migrations/20261005000000_add_agent_github_installations_snapshot/migration.sql

@@ -0,0 +1,21 @@
+-- CreateTable: AgentGitHubInstallationsSnapshot — one row per agent, holding
+-- the agent's most recently reported GitHub App installations. agentId is
+-- unique so PUT /agents/:id/github-installations can upsert a single row.
+-- Additive only.
+
+-- CreateTable
+CREATE TABLE "AgentGitHubInstallationsSnapshot" (
+    "id" TEXT NOT NULL,
+    "agentId" TEXT NOT NULL,
+    "reportedAt" TIMESTAMP(3) NOT NULL,
+    "installations" JSONB NOT NULL,
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+
+    CONSTRAINT "AgentGitHubInstallationsSnapshot_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE UNIQUE INDEX "AgentGitHubInstallationsSnapshot_agentId_key" ON "AgentGitHubInstallationsSnapshot"("agentId");
+
+-- AddForeignKey
+ALTER TABLE "AgentGitHubInstallationsSnapshot" ADD CONSTRAINT "AgentGitHubInstallationsSnapshot_agentId_fkey" FOREIGN KEY ("agentId") REFERENCES "Agent"("id") ON DELETE CASCADE ON UPDATE CASCADE;

package/prisma/migrations/20261008000000_add_cron_run_telemetry/migration.sql

@@ -0,0 +1,50 @@
+-- Run telemetry for the prompt-audit patrol (all additive, nullable):
+--   * AgentCronRun gains the first-turn context baseline (the measured
+--     always-loaded context per run), turn/tool-call counts, and the
+--     always-loaded-context fingerprint + versions that group runs by what
+--     the model was given.
+--   * AgentCronRunSkillUsage holds per-skill / per-subagent token
+--     attribution rows, one per [cronRunId, kind, name].
+-- Older agent builds simply never set these; nothing is backfilled.
+
+-- AlterTable
+ALTER TABLE "AgentCronRun"
+  ADD COLUMN "baselineModel" TEXT,
+  ADD COLUMN "baselineContextTokens" INTEGER,
+  ADD COLUMN "baselineInputTokens" INTEGER,
+  ADD COLUMN "baselineCacheCreationTokens" INTEGER,
+  ADD COLUMN "baselineCacheReadTokens" INTEGER,
+  ADD COLUMN "turns" INTEGER,
+  ADD COLUMN "toolCalls" INTEGER,
+  ADD COLUMN "contextFingerprint" TEXT,
+  ADD COLUMN "pluginVersion" TEXT,
+  ADD COLUMN "claudeCodeVersion" TEXT;
+
+-- CreateIndex
+CREATE INDEX "AgentCronRun_contextFingerprint_idx" ON "AgentCronRun"("contextFingerprint");
+
+-- CreateTable
+CREATE TABLE "AgentCronRunSkillUsage" (
+    "id" TEXT NOT NULL,
+    "cronRunId" TEXT NOT NULL,
+    "kind" TEXT NOT NULL,
+    "name" TEXT NOT NULL,
+    "invocations" INTEGER NOT NULL DEFAULT 0,
+    "turns" INTEGER NOT NULL DEFAULT 0,
+    "inputTokens" INTEGER NOT NULL DEFAULT 0,
+    "outputTokens" INTEGER NOT NULL DEFAULT 0,
+    "cacheReadTokens" INTEGER NOT NULL DEFAULT 0,
+    "cacheCreationTokens" INTEGER NOT NULL DEFAULT 0,
+    "invokeContextDelta" INTEGER,
+
+    CONSTRAINT "AgentCronRunSkillUsage_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE UNIQUE INDEX "AgentCronRunSkillUsage_cronRunId_kind_name_key" ON "AgentCronRunSkillUsage"("cronRunId", "kind", "name");
+
+-- CreateIndex
+CREATE INDEX "AgentCronRunSkillUsage_kind_name_idx" ON "AgentCronRunSkillUsage"("kind", "name");
+
+-- AddForeignKey
+ALTER TABLE "AgentCronRunSkillUsage" ADD CONSTRAINT "AgentCronRunSkillUsage_cronRunId_fkey" FOREIGN KEY ("cronRunId") REFERENCES "AgentCronRun"("id") ON DELETE CASCADE ON UPDATE CASCADE;

package/prisma/migrations/20261008010000_add_account_models/migration.sql

@@ -0,0 +1,48 @@
+-- SSP-1.2: Account, AccountMember, AccountInvite + nullable Agent.accountId.
+-- Additive only: existing Agent rows keep accountId = NULL.
+CREATE TABLE "Account" (
+    "id" TEXT NOT NULL,
+    "name" TEXT NOT NULL,
+    "status" TEXT NOT NULL DEFAULT 'active',
+    "maxAgents" INTEGER NOT NULL DEFAULT 0,
+    "plan" TEXT,
+    "trialExpiresAt" TIMESTAMP(3),
+    "trialExpiryWarnedAt" TIMESTAMP(3),
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "Account_pkey" PRIMARY KEY ("id")
+);
+
+CREATE TABLE "AccountMember" (
+    "id" TEXT NOT NULL,
+    "accountId" TEXT NOT NULL,
+    "email" TEXT NOT NULL,
+    "role" TEXT NOT NULL,
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+
+    CONSTRAINT "AccountMember_pkey" PRIMARY KEY ("id")
+);
+
+CREATE TABLE "AccountInvite" (
+    "id" TEXT NOT NULL,
+    "accountId" TEXT NOT NULL,
+    "email" TEXT NOT NULL,
+    "invitedBy" TEXT NOT NULL,
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "acceptedAt" TIMESTAMP(3),
+
+    CONSTRAINT "AccountInvite_pkey" PRIMARY KEY ("id")
+);
+
+ALTER TABLE "Agent" ADD COLUMN "accountId" TEXT;
+
+CREATE UNIQUE INDEX "AccountMember_email_key" ON "AccountMember"("email");
+CREATE UNIQUE INDEX "AccountMember_accountId_email_key" ON "AccountMember"("accountId", "email");
+CREATE INDEX "AccountInvite_email_idx" ON "AccountInvite"("email");
+CREATE UNIQUE INDEX "AccountInvite_accountId_email_key" ON "AccountInvite"("accountId", "email");
+CREATE INDEX "Agent_accountId_idx" ON "Agent"("accountId");
+
+ALTER TABLE "Agent" ADD CONSTRAINT "Agent_accountId_fkey" FOREIGN KEY ("accountId") REFERENCES "Account"("id") ON DELETE RESTRICT ON UPDATE CASCADE;
+ALTER TABLE "AccountMember" ADD CONSTRAINT "AccountMember_accountId_fkey" FOREIGN KEY ("accountId") REFERENCES "Account"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+ALTER TABLE "AccountInvite" ADD CONSTRAINT "AccountInvite_accountId_fkey" FOREIGN KEY ("accountId") REFERENCES "Account"("id") ON DELETE CASCADE ON UPDATE CASCADE;

package/prisma/migrations/20261008020000_add_cron_lockdown_disabled_at/migration.sql

@@ -0,0 +1,3 @@
+-- Records which crons the trial-expiry lockdown disabled (additive, nullable)
+-- so they can be restored without touching crons the user disabled manually.
+ALTER TABLE "AgentCronJob" ADD COLUMN "lockdownDisabledAt" TIMESTAMP(3);

package/prisma/migrations/20261009000000_chat_token_usage_bigint/migration.sql

@@ -0,0 +1,7 @@
+-- Widen daily chat token counters to BIGINT: accumulated per-model daily sums
+-- overflow INT4 (SQLSTATE 22003) — see Sentry VITALS-OS-5T.
+ALTER TABLE "AgentChatTokenUsageDailyByModel"
+    ALTER COLUMN "inputTokens" TYPE BIGINT,
+    ALTER COLUMN "outputTokens" TYPE BIGINT,
+    ALTER COLUMN "cacheReadTokens" TYPE BIGINT,
+    ALTER COLUMN "cacheCreationTokens" TYPE BIGINT;

package/prisma/migrations/20261010000000_add_cron_run_command_variant/migration.sql

@@ -0,0 +1,2 @@
+-- Records which slash-command variant a loop dispatch ran (additive, nullable).
+ALTER TABLE "AgentCronRun" ADD COLUMN "commandVariant" TEXT;

package/prisma/migrations/20261019000000_add_agent_anthropic_identity/migration.sql

@@ -0,0 +1,9 @@
+-- PAI-1.1: owner and Anthropic identity columns on Agent (additive, nullable).
+ALTER TABLE "Agent" ADD COLUMN "ownerEmail" TEXT;
+ALTER TABLE "Agent" ADD COLUMN "anthropicIdentityName" TEXT;
+ALTER TABLE "Agent" ADD COLUMN "anthropicServiceAccountId" TEXT;
+ALTER TABLE "Agent" ADD COLUMN "anthropicFederationRuleId" TEXT;
+ALTER TABLE "Agent" ADD COLUMN "k8sServiceAccountName" TEXT;
+
+-- CreateIndex
+CREATE UNIQUE INDEX "Agent_anthropicIdentityName_key" ON "Agent"("anthropicIdentityName");

package/prisma/migrations/20261025000000_add_agent_ask/migration.sql

@@ -0,0 +1,23 @@
+-- COS-31.1: AgentAsk audit table for agent-to-agent asks (additive only).
+-- CreateTable
+CREATE TABLE "AgentAsk" (
+    "id" TEXT NOT NULL,
+    "fromAgentId" TEXT NOT NULL,
+    "toAgentId" TEXT NOT NULL,
+    "threadId" TEXT,
+    "depth" INTEGER NOT NULL,
+    "waitMs" INTEGER NOT NULL,
+    "ttlSeconds" INTEGER NOT NULL,
+    "status" TEXT NOT NULL,
+    "callerLabel" TEXT NOT NULL,
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "repliedAt" TIMESTAMP(3),
+
+    CONSTRAINT "AgentAsk_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE INDEX "AgentAsk_toAgentId_createdAt_idx" ON "AgentAsk"("toAgentId", "createdAt");
+
+-- CreateIndex
+CREATE INDEX "AgentAsk_fromAgentId_createdAt_idx" ON "AgentAsk"("fromAgentId", "createdAt");

package/prisma/migrations/migration_lock.toml

@@ -0,0 +1,3 @@
+# Please do not edit this file manually
+# It should be added in your version-control system (e.g., Git)
+provider = "postgresql"

package/prisma/schema/coding.prisma

@@ -0,0 +1,85 @@
+// Shipwright — Admin Service Schema: coding-owned models (AEP-3.4)
+//
+// Part of the admin Prisma multi-file schema (prisma/schema/). These models
+// belong to the coding feature surface and are isolated here so the coding
+// code can later be extracted. They share the single `db` datasource and
+// generator declared in schema.prisma, so the generated client and the
+// migrations are unchanged by this split.
+//
+// Coding-owned columns that live on the shared Agent model (schema.prisma)
+// and are grouped/commented there: reviewAuthorAllowlist, patchAuthorAllowlist,
+// autoPostReviews, allowSelfReview, minConfidence, maxFindings.
+
+// ─── Agent Work Queue Snapshot ────────────────────────────────────────────────
+// One row per agent, holding the agent's most recently pushed work-queue
+// snapshot (its ranked view of pending tasks/PRs across pipeline phases).
+// POST /agents/:id/work-queue upserts this single row, overwriting any prior
+// snapshot — there is no history, only the latest state.
+
+model AgentWorkQueueSnapshot {
+  id         String   @id @default(cuid())
+  agentId    String   @unique
+  agent      Agent    @relation(fields: [agentId], references: [id], onDelete: Cascade)
+  computedAt DateTime
+  items      Json     // RankedWorkItem[]
+  createdAt  DateTime @default(now())
+}
+
+// ─── Agent Phase Methodology ──────────────────────────────────────────────────
+// Per-phase subagent-type override. Each row records which subagent type
+// (e.g. a custom Specialty name) should handle one pipeline phase — prd,
+// plan-session, review, patch, deploy, or dev-task — for a given agent,
+// overriding that phase's default methodology. `subagentType` is nullable:
+// a row with a null value (or the absence of a row) means "use the default".
+// The `phase` value is constrained to the six-value enum at the service/route
+// layer (Zod), not here — Postgres/Prisma has no native enum-column
+// requirement in this schema style (mirrors AgentTool.pattern / AgentCronJob
+// validation living at the service layer). The unique constraint on
+// [agentId, phase] makes upsert-based writes idempotent (one override row per
+// phase per agent), mirroring AgentTool's [agentId, pattern] and AgentPlugin's
+// [agentId, name].
+
+model AgentPhaseMethodology {
+  id           String   @id @default(cuid())
+  agentId      String
+  agent        Agent    @relation(fields: [agentId], references: [id], onDelete: Cascade)
+  phase        String
+  subagentType String?
+  updatedAt    DateTime @updatedAt
+
+  @@unique([agentId, phase])
+}
+
+// ─── Session Follow ───────────────────────────────────────────────────────────
+// Records that a user is "following" a planning session (identified by its
+// slug) so they can receive reminders/notifications about it. `muted` lets a
+// user stay following (kept in listByUser) while suppressing alerts, distinct
+// from unfollowing (row deleted entirely). The unique constraint on
+// [userEmail, sessionSlug] makes follow() idempotent via upsert.
+model SessionFollow {
+  id          String   @id @default(cuid())
+  userEmail   String
+  sessionSlug String
+  muted       Boolean  @default(false)
+  createdAt   DateTime @default(now())
+  updatedAt   DateTime @updatedAt
+
+  @@unique([userEmail, sessionSlug])
+  @@index([sessionSlug])
+}
+
+// ─── Session Alert State ─────────────────────────────────────────────────────
+// Tracks the last time a user was alerted about a given session, so a
+// reminder job can avoid re-alerting the same user/session pair within a
+// cooldown window. The unique constraint on [userEmail, sessionSlug] allows
+// upsert semantics (one state row per user per session).
+model SessionAlertState {
+  id            String    @id @default(cuid())
+  userEmail     String
+  sessionSlug   String
+  lastAlertedAt DateTime?
+  createdAt     DateTime  @default(now())
+  updatedAt     DateTime  @updatedAt
+
+  @@unique([userEmail, sessionSlug])
+}