Add fake payment lifecycle API

[tarunag10]

Summary

• add in-memory fake payment records with send/list/get/complete/cancel lifecycle routes
• support retry-safe sends with either an idempotency_key body field or Idempotency-Key header
• preserve default middleware payment state across requests with a shared in-memory DB
• document the payment endpoints in the README

/claim #1

Tests

• npx bun test tests/routes/payments-default-middleware.test.ts tests/routes/payments.test.ts
• npx bun test
• npx bun run build
• npx tsc --noEmit
• npx biome check README.md lib/db/schema.ts lib/db/db-client.ts lib/middleware/with-db.ts lib/payments/route-schemas.ts routes/payments tests/routes/payments.test.ts tests/routes/payments-default-middleware.test.ts
• git diff --check

AI-assisted with Codex; I reviewed the diff and kept the PR scoped to the bounty API.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e83051cf05

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Scope default DB instance per app context

Move DB initialization out of module scope: creating defaultDb once at import time makes all routes that rely on withDb share state across the entire process, so separate Winterspec bundles or test runs in the same process can see each other’s payments/things and become order-dependent. This introduces cross-instance data bleed rather than just per-request persistence.

Useful? React with 👍 / 👎.

[tarunag10]

Hi @seveibar, just following up on this Algora claim for #1.

I noticed the bounty issue is now closed, but my claim is still pending on Algora. Could you confirm whether PR #25 is still eligible for review/reward, or whether another implementation was selected?

Happy to make any changes if there is still a path forward. Thanks.