[apple050620312]

Summary

• Recover safely from find-or-create uniqueness races without masking unrelated database failures.
• Add a migration that deduplicates existing rows and enforces unique member and custom-domain constraints.
• Expand and index event names for operational queries.
• Flush buffered analytics and close HTTP sessions during shutdown.
• Generate runtime configuration safely, bound database startup waits, and make migrations explicit and fail-closed.
• Keep the database private to the Compose network and add a one-shot migration service.

Priority

P2 — improves correctness, rollout safety, and recovery under concurrent multi-worker operation.

Validation

• Migration imports successfully.
• Compose migration topology and private database assertions pass.
• Runtime imports and all Python AST parsing checks pass.

[Kyrela]

Recover safely from find-or-create uniqueness races without masking unrelated database failures.

The ORM is not async, and I closed #112, so it doesn't bring anything here.

Add a migration that deduplicates existing rows and enforces unique member and custom-domain constraints.

Yeah this one is obvious I should have done it from the start.

Expand and index event names for operational queries.

The "expand" part is wrong (and thus dangerous as it can fail), but same, I should have indexed it like this from the start

Flush buffered analytics and close HTTP sessions during shutdown.

Yeah I tought of this, but decided I didn't really care. But it's technically just an improvement, except, this has some problems like a fail-loop that blocks analytics entierely.

Generate runtime configuration safely

Not bad, but a bit overkill.

bound database startup waits

Useless as restart: unless-stopped is used.

make migrations explicit and fail-closed

fail-closed is good, but "explicit" (if it means making migrations opt-in) is obviously a bad idea, except for multi-instances work proposed in #112

Keep the database private to the Compose network

Yeah, that makes sense.

add a one-shot migration service

See above

Also, the migrations files were manually created and therefore don't have any id.