Add durable delivery database core - #3
Closed
dakdevs wants to merge 1 commit into
Closed
Conversation
Member
Author
|
Superseded by #8, which is merged into main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
DeliveryStorefor atomic event recording, concurrent claims, ACK/NACK, heartbeat extension, and lease recoveryWhy
This implements the durable database core from PRD #1 before the Vercel ingress and CLI are wired to it. PostgreSQL is the source of truth, and all correctness-sensitive transitions use short atomic statements.
This is stacked on #2 and should be reviewed after the bootstrap PR.
Refs #1
Depends on #2
Validation
bun run db:generatereports no schema driftbun run lintbun run prettier:checkbun run typecheckbun test— 11 tests, including 10 real-PostgreSQL delivery testsbun run test:e2ebun run buildThe integration suite covers concurrent claim exclusion, tenant isolation, lease expiry and redelivery, stale-token rejection, retry scheduling, heartbeat extension, disabled hooks, and database-enforced webhook-event immutability.