feat: savings allocations

internal/db/migrations/00012_create_allocations_table.sql

@@ -0,0 +1,21 @@
+-- +goose Up
+-- +goose StatementBegin
+CREATE TABLE allocations (
+    id TEXT PRIMARY KEY NOT NULL,
+    account_id TEXT NOT NULL REFERENCES accounts(id) ON DELETE CASCADE,
+    name TEXT NOT NULL,
+    amount TEXT NOT NULL,
+    target_amount TEXT,
+    sort_order INTEGER NOT NULL DEFAULT 0,
+    created_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    updated_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    UNIQUE (account_id, name)
+);
+
+CREATE INDEX idx_allocations_account_id ON allocations (account_id, sort_order);
+-- +goose StatementEnd
+
+-- +goose Down
+-- +goose StatementBegin
+DROP TABLE allocations;
+-- +goose StatementEnd

internal/db/migrations/00013_index_allocation_audit_logs.sql

@@ -0,0 +1,15 @@
+-- +goose Up
+-- +goose StatementBegin
+-- Mirror of idx_space_audit_logs_account_id but for allocation.* actions, so
+-- the account-scoped activity feed can OR-merge the two prefixes without a
+-- sequential scan over space_audit_logs.
+
+CREATE INDEX idx_space_audit_logs_allocation_account_id
+    ON space_audit_logs ((metadata->>'account_id'), created_at DESC)
+    WHERE action LIKE 'allocation.%';
+-- +goose StatementEnd
+
+-- +goose Down
+-- +goose StatementBegin
+DROP INDEX IF EXISTS idx_space_audit_logs_allocation_account_id;
+-- +goose StatementEnd