[JOY (JOY)]

Refs #85

Why

A back campaign's backers pay the creator's own bank account by VietQR once the campaign succeeds, so a back campaign must not be submitted, approved or go live without a usable receiving account. The database rule is DOS/DOS.Me#1549 (migration 20261106100000); this PR is the app side.

What

• Editor /me/campaigns/[id]: the "Tài khoản nhận tiền" section (M1 editor: bind the receiving account in the campaign editor and require it before review #32's picker, bound account, release) and the "Gửi duyệt" guard now show for back campaigns too. The section's intro says when backers pay (after success).
• submitForReview checks the account for both types before transition_campaign (which re-checks).
• lib/campaign-account.ts: checkSubmitAccount and loadEditorAccounts take the campaign type; swap requests are read for give only; submitUnusableAccount / submitAccountProblem take canSwap so a back campaign whose unusable account recorded money is told to contact Give (no swap exists for back, Replace a disabled receiving account on a live give campaign #55 is give-only).
• canAskRelease: a back campaign in changes_requested may release (matches the DB change, Recover a give campaign whose receiving account becomes unusable after approval #64 recovery for back).
• A live or suspended back campaign whose account is unusable is told to contact Give (no back swap yet, follow-up Recover a live or suspended back campaign whose receiving account became unusable #92).
• Wording: SUBMIT / release / binding messages and the accounts page no longer limit these rules to charity campaigns; the admin "waiting for account" queue explains it covers both types and shows each campaign's type badge.

Tests

• Vitest: 895 passed (new: back submit refused without an account / allowed with one / money-history wording; editor loads back accounts, no swap reads for back; back release allowed in changes_requested).
• turbo typecheck lint green, Prettier clean.
• Not checked in a running app (no local Supabase session).

Merge after (or with) DOS/DOS.Me#1549.

🤖 Generated with Claude Code

---

📌 TL;DR

Extends the receiving account validation and release logic to support "back" (reward-based) campaigns, ensuring they require a verified account before review and allowing account releases when changes are requested. Updates UI copy and error messages to distinguish between charity and reward-based campaigns, directing the latter to contact support for account swaps.

🎯 Type of Change

• 🚀 New feature
• 🐛 Bugfix
• 📚 Documentation

🔍 Changes Walkthrough

File	Summary of Changes
apps/web/src/app/admin/page.tsx	Updates admin dashboard copy to include "back" campaigns in the "waiting for account" section and adds a TypeBadge to distinguish campaign types.
apps/web/src/app/me/accounts/actions.test.ts	Updates tests to verify that releaseAccount now succeeds for "back" campaigns in changes_requested status.
apps/web/src/app/me/accounts/page.tsx	Generalizes UI copy for account binding/release rules to apply to all campaign types, not just charity.
apps/web/src/app/me/campaigns/[id]/page.tsx	Refactors the campaign editor to load account data for both "give" and "back" types. Updates error messages to direct "back" campaign organizers to contact support instead of using the swap feature.
apps/web/src/app/me/campaigns/actions.test.ts	Adds tests to ensure submitForReview blocks "back" campaigns without a valid account and handles unusable accounts correctly.
apps/web/src/app/me/campaigns/actions.ts	Modifies submitForReview to enforce account validation for all campaign types, passing the campaign type to the validation logic.
apps/web/src/lib/campaign-account.test.ts	Updates tests for loadEditorAccounts and submitAccountProblem to cover "back" campaign scenarios, including the absence of swap requests.
apps/web/src/lib/campaign-account.ts	Extends loadEditorAccounts, checkSubmitAccount, and submitAccountProblem to accept a type parameter. Logic now prevents swap requests for "back" campaigns and generates appropriate error messages.
apps/web/src/lib/campaigns.ts	Updates documentation comments to reflect that "back" campaigns are now included in the "waiting for account" logic.
apps/web/src/lib/errors.ts	Updates error message constants to provide specific guidance for "back" campaigns (contact support) vs. "give" campaigns (request swap).
apps/web/src/lib/receiving-accounts.test.ts	Updates test to confirm canAskRelease returns true for "back" campaigns in changes_requested status.
apps/web/src/lib/receiving-accounts.ts	Modifies canAskRelease to allow account releases for any campaign type (including "back") when the status is changes_requested.

📊 Architectural Flow

flowchart TD
    A[Organizer Submits Campaign] --> B{Check Campaign Type}
    B -->|Give| C[Validate Account & Check Swap Eligibility]
    B -->|Back| D[Validate Account & Disable Swap]
    C --> E{Account Usable?}
    D --> E
    E -->|No| F[Block Submission]
    F --> G{Has Transactions?}
    G -->|Yes & Give| H[Direct to Swap Request]
    G -->|Yes & Back| I[Direct to Contact Support]
    G -->|No| J[Direct to Release & Rebind]
    E -->|Yes| K[Allow Submission to Review]
    
    L[Organizer Requests Release] --> M{Status is changes_requested?}
    M -->|Yes| N{Type is defined?}
    N -->|Yes| O[Allow Release]
    N -->|No| P[Refuse Release]
    M -->|No| Q[Check Standard Release Rules]

Loading

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 45b8a673-ccb5-48a7-94f7-8a0bc152d517

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[dos]

⏱️ Code Review completed (12 eligible files · 37,182 chars · 3 model call(s) · 2 PR unit(s))

Whole diff with bounded context at base ffa6bb0 / head 614878f.

✅ CLEAN_PASS: Complete diff reviewed

Context investigation was bounded to the explicitly requested snapshot paths.

[dos]

⏱️ Code Review completed (12 eligible files · 37,727 chars · 3 model call(s) · 2 PR unit(s))

Whole diff with bounded context at base ffa6bb0 / head 573b41c.

✅ CLEAN_PASS: Complete diff reviewed

Context investigation was bounded to the explicitly requested snapshot paths.

[JOY (JOY)]

PO acceptance: merge at 573b41c. CI green, DOS Code Review CLEAN_PASS, Vitest 895. DB part DOS/DOS.Me#1549 merged.