mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-23 18:17:44 +02:00
e3a829f05e
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.
24 lines
1.2 KiB
SQL
24 lines
1.2 KiB
SQL
-- Template list of workspace members auto-subscribed to every issue spawned
|
|
-- by the autopilot. Members-only for now (broaden the CHECK to expand).
|
|
-- No foreign keys or cascades — autopilot existence and workspace membership
|
|
-- are both enforced in the application layer (the autopilot delete handler
|
|
-- removes these rows in the same transaction; membership is checked at the API
|
|
-- boundary via isWorkspaceEntity), per the repo rule. Mirrors issue_subscriber's
|
|
-- app-level user_id handling.
|
|
CREATE TABLE autopilot_subscriber (
|
|
autopilot_id UUID NOT NULL,
|
|
user_type TEXT NOT NULL CHECK (user_type IN ('member')),
|
|
user_id UUID NOT NULL,
|
|
created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
|
|
PRIMARY KEY (autopilot_id, user_type, user_id)
|
|
);
|
|
|
|
-- Reverse-lookup index for "which autopilots auto-subscribe this member?";
|
|
-- the PK can't answer that since autopilot_id is its leading column.
|
|
CREATE INDEX idx_autopilot_subscriber_user
|
|
ON autopilot_subscriber (user_type, user_id);
|
|
|
|
ALTER TABLE issue_subscriber DROP CONSTRAINT issue_subscriber_reason_check;
|
|
ALTER TABLE issue_subscriber ADD CONSTRAINT issue_subscriber_reason_check
|
|
CHECK (reason IN ('creator', 'assignee', 'commenter', 'mentioned', 'manual', 'autopilot'));
|