vmall/openspec/changes/archive/2026-09-24-add-wallet-settlement/specs/frontend-mall/spec.md at 9904696e76a897fb7a39b0a94a198320c93973ec

Files

T

james 9904696e76 feat: wave 2 migration (P3, P5, P7 openspec changes)

Implements, verifies, and archives the three remaining Wave 2 changes from
openspec/MIGRATION-PLAN.md.

- add-wallet-settlement (P3): demo recharge, guarded withdrawal freeze and
  one-time admin review, paginated own fund entries, idempotent per-shop
  weekly/monthly settlement statements with commission rate and one-time
  payout confirmation.
- add-merchant-onboarding (P5): personal/enterprise applications with one live
  application per user, guarded review with mandatory rejection reason, and
  transactional shop + owner provisioning returning one-time credentials;
  mall onboarding/status pages and an admin review console.
- add-membership-messaging (P7): platform member levels, append-only growth
  accrual on order completion with guarded one-way leveling, order/shipment/
  refund system messages with unread/read state and soft deletion, plus the
  mall header unread badge.

Backend: migrations 0019-0023, new wallet, settlement, merchant_onboarding,
membership and messaging modules, event hooks in order/fulfillment/aftersale,
and integration suites for each. Shared contract extended and all three
frontends updated; code indexes, domain docs, backend guidelines and the
migration tracker synced.

Verification: cargo test -p vmall-api green twice consecutively; mall, admin
and shop-admin builds pass; browser smoke on every new surface; openspec
validate --all --strict green (33 passed).

The three changes share the @vmall/shared contract, the mall mock adapter and
per-app locale/nav files, so they are committed together to keep every commit
buildable.

2026-09-25 15:25:29 +00:00

1.4 KiB

Raw Blame History

ADDED Requirements

Requirement: Buyer wallet surface

The mall SHALL render a buyer-center wallet page driven by the selected API adapter through @vmall/shared: available and frozen balance with currency, paginated fund entries, a clearly labeled demo recharge form, and a withdrawal request form. Balances and entries SHALL reflect backend state after each action rather than local-only state. The wallet SHALL be a mall API domain with fixed-adapter fallback methods and LIVE_PICKS wiring following the established per-domain adapter pattern.

Scenario: wallet page loads live state

WHEN a signed-in buyer opens the wallet page
THEN balances and the first page of fund entries render from the shared wallet contract

Scenario: demo recharge updates balance

WHEN the buyer submits a demo recharge
THEN the visible available balance reflects the credit without a reload and the form is visibly marked simulated

Scenario: withdrawal freezes visibly

WHEN the buyer submits a withdrawal request
THEN the visible summary shows available decreased and frozen increased by the requested amount, and the request appears in the withdrawal list as pending

Scenario: fixed adapter remains functional

WHEN the wallet domain is configured to fixed data
THEN the wallet page behaves deterministically through the same shared client methods

1.4 KiB Raw Blame History