Files
multica/server/migrations/120_comment_source_task_id.up.sql
Bohan Jiang e3a829f05e feat(daemon): disk-usage cross-root aggregation + migration FK/readiness fixes (MUL-3404) (#4290)
Bundles the MUL-3404 disk-usage feature with the two Preflight BLOCK fixes.

- feat(daemon): `disk-usage --all-profiles` aggregates across every workspace
  root (default + each ~/.multica/profiles/* root, incl. the Desktop app's),
  with a per-root breakdown and combined grand total; the cross-root hint now
  also fires when the current root is non-empty.
- fix(db): drop DB-level foreign keys/cascades from the new autopilot_subscriber
  and comment.source_task_id migrations (resolved in the app layer — autopilot
  delete now removes subscribers in a transaction); the autopilot_subscriber
  down-migration relabels reason='autopilot' to 'manual' instead of deleting.
- fix(server): readiness verifies every required migration is applied, not just
  the lexically-last one, so an out-of-order migration can't be masked.

MUL-3404.
2026-06-18 13:33:14 +08:00

9 lines
512 B
SQL

-- Trace pointer to the agent_task_queue row that produced this comment, used by
-- the "retry failed agent comment" affordance. No FK on source_task_id: the
-- referenced task can be GC'd independently of the comment it produced, and the
-- relationship is resolved in the application layer (a missing task simply means
-- the source is no longer retryable). Matches the repo rule that foreign keys
-- and cascades are handled by the app, not the database.
ALTER TABLE comment
ADD COLUMN source_task_id UUID;