mirror of
https://github.com/jjbrunton/Sauci.git
synced 2026-10-31 18:19:43 +00:00
jjbruntonandClaude Opus 5
ce0b188776
Completes the half-built dares feature: send a dare, respond, report done, confirm, and get a push notification on every transition. Backend (apps/api): - New `dares` domain with couple-shared premium entitlement, a free weekly send allowance, and server-enforced actor/state rules on every transition. - `submitted` status so the recipient reports completion and the sender confirms, rather than the sender guessing. - Notifications ride the existing operations outbox via a trigger on `sent_dares`. Push copy is generic; store compliance forbids dare text in a preview and a test asserts no payload leaks it. - Worker expiry sweep now covers `pending` as well as `active`/`submitted`; an invitation nobody opened previously stayed open forever. Fixes two latent defects: - Deleting any dare that had been sent aborted with a check violation, because `dare_id` is ON DELETE SET NULL while `sent_dares_dare_or_custom_check` required it. Dare text is now snapshotted at send time, which also keeps a couple's history stable across catalogue edits. - The free send allowance was raceable: concurrent requests all read the same count and every one succeeded. The count and insert are now serialized on the sender's profile row. Also ports `content_status` review metadata to the API catalogue, which had no store-safety gating at all, and mirrors the review decision already enforced on the legacy catalogue. Mobile: dares screen (active/send/history), send sheet with duration presets, home tile badging incoming dares, paywall on both proactive and 402 paths. Verified: lint, typecheck, 379 unit tests, build, 71 integration tests against local PostgreSQL. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
40 lines
1.5 KiB
Markdown
40 lines
1.5 KiB
Markdown
# Sauci documentation
|
|
|
|
This index separates maintained operational truth from implementation plans and
|
|
historical notes. Agents should load only the section relevant to their task.
|
|
|
|
## Maintained system documentation
|
|
|
|
- [System architecture](architecture/system.md)
|
|
- [Local full-stack development](development/local-stack.md)
|
|
- [Testing strategy](testing/strategy.md)
|
|
- [Database migration safety](operations/database-migrations.md)
|
|
- [Backend deployment and branching](operations/backend-deployments.md)
|
|
- [Agent routing and effort](agents/routing.md)
|
|
- [Learning promotion](agents/learnings.md)
|
|
- [Authentication](authentication.md)
|
|
- [Database schema](schema.md)
|
|
- [Couple pairing](couple-pairing.md)
|
|
- [Question selection](question-selection.md)
|
|
- [Match notifications](match-notifications.md)
|
|
- [Subscriptions](subscription-system.md)
|
|
- [Redemption codes](product/redemption.md)
|
|
- [Mobile release process](releasing.md)
|
|
- [Dares loop](dares-loop.md)
|
|
|
|
## Feature and implementation references
|
|
|
|
These contain useful history and acceptance details, but may describe planned or
|
|
partially implemented states. Confirm claims against current code.
|
|
|
|
- `admin-question-types-plan.md`
|
|
- [Universal catalogue safety plan](product/catalog-content-safety-plan.md)
|
|
- `content-balance-implementation.md`
|
|
- `dares-feature.md` (superseded by [Dares loop](dares-loop.md))
|
|
- `live-draw-feature-plan.md`
|
|
- `NEW_QUESTION_TYPES.md`
|
|
- `oversized-file-inventory.md`
|
|
- `pack-icons-admin-first.md`
|
|
- `data-retrieval-tasks.md`
|
|
- `release-notes.md`
|