release: promote protected payments to staging - #5
SourceSenseiTheRealOne wants to merge 65 commits into
Conversation
# Conflicts: # README.md # context/architecture.md # context/stack.md # frontend/.env.example # frontend/README.md # frontend/src/app/[locale]/page.tsx # frontend/src/features/landing/components/landing-shell.test.tsx # frontend/src/features/landing/components/landing-shell.tsx
## Summary - restrict listing approval and payment operations to the exact verified administrator while retaining durable Go roles - add Stripe Checkout/Connect payments with server-owned amounts, signed idempotent webhooks, payouts, refunds, disputes, tax and invoice configuration - add localized payment, payout, legal and administration surfaces plus the compact discovery filter control ## Verification - Go full tests, focused race tests, vet and build - real local PostgreSQL checkout/webhook/admin-list integration test - frontend verify: 43 files / 110 tests, lint, typecheck, production build, audit - authenticated local runtime: listing queue resolved and payment admin BFF returned the durable empty queue ## Deployment - source promotion only; no Heroku deployment - production payment activation remains blocked until exposed credentials are rotated and provider-side activation gates are complete
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closing without merge: squash-history divergence made this direct environment PR report 558 files and conflicts, while the actual tree delta is 59 paths. Replacing it with a target-based exact-tree promotion. |
1 participant
Promotes the green sole-admin moderation and protected-payment source from development to staging. Same source scope as PR #4. No Heroku deployment or live Stripe activation.