Jason Woltje 92de2f282f fix(database): resolve migration failures and schema drift ...

Root cause: migration 20260129235248_add_link_storage_fields dropped the
personalities table and FormalityLevel enum, but migration
20260208000000_add_missing_tables later references personalities in a FK
constraint, causing ERROR: relation "personalities" does not exist on any
fresh database deployment.

Fix 1 — 20260208000000_add_missing_tables:
  Recreate FormalityLevel enum and personalities table (with current schema
  structure) at the top of the migration, before the FK constraint.

Fix 2 — New migration 20260215100000_fix_schema_drift:
  - Create missing instances table (Federation module, never migrated)
  - Recreate knowledge_links unique index (dropped, never recreated)
  - Add 7 missing @@unique([id, workspaceId]) composite indexes
  - Add missing agent_tasks.agent_type index

Verified: all 27 migrations apply cleanly on a fresh PostgreSQL 17 database
with pgvector.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-15 14:42:06 -06:00

..

api

fix(database): resolve migration failures and schema drift

2026-02-15 14:42:06 -06:00

coordinator

fix(#374): add pip.conf to coordinator Docker build for private registry

2026-02-15 12:05:04 -06:00

orchestrator

fix(#367): migrate Node.js 20 → 24 LTS

2026-02-13 15:20:01 -06:00

web

merge: resolve conflicts with develop (M10-Telemetry + M12-MatrixBridge)

2026-02-15 12:31:08 -06:00