docs(dashboard): require detail CSV exports
This commit is contained in:
@@ -46,6 +46,7 @@ Give a non-technical merchant a fast, trustworthy Persian RTL view of payment pe
|
||||
28. A deterministic insight is promoted into an actionable card only when at least 100 relevant sessions contribute and the comparison changes by at least 3 percentage points for a rate or 20 percent for an amount/count. Smaller changes remain available as metrics without an action claim.
|
||||
29. All merchant-facing values use Persian digits and monetary values use Rial only. Technical identifiers remain canonical and are directionally isolated.
|
||||
30. Light and dark modes are supported from the first release through the semantic token contract in `DESIGN.md`; system preference is the default and an explicit accessible user choice persists locally.
|
||||
31. Merchant-owned detail views that support operational handoff provide CSV export using the current authorized filters. Export never contains payer tokens, peer-level data, credentials, or fields absent from the corresponding authorized detail view.
|
||||
|
||||
## Frontend architecture baseline
|
||||
|
||||
@@ -66,6 +67,7 @@ Give a non-technical merchant a fast, trustworthy Persian RTL view of payment pe
|
||||
- Merchant-facing digits are Persian, money is labeled in Rial only, and technical identifiers remain uncorrupted in RTL layouts.
|
||||
- Light and dark modes both meet the documented contrast, focus, chart, state, and reduced-motion requirements at all acceptance viewports, with no first-paint theme flash.
|
||||
- Below-threshold comparisons never produce actionable insight language, while qualifying insight cards expose their numeric evidence and limitation.
|
||||
- Authorized CSV exports reconcile to the same filtered detail query shown in the dashboard, retain explicit Rial/date/status semantics, and remain tenant-isolated even when export parameters are manipulated.
|
||||
- Success views include `Paid` plus `Verified`, verification-completion views separate them, and unverified paid sessions are never styled or described as failures.
|
||||
- Paid volume and merchant fee values reconcile at session grain; fee totals remain unchanged when a session has additional attempts.
|
||||
- Retry recovery includes eventual `Paid` or `Verified`, and timing percentiles never treat missing values as zero.
|
||||
@@ -91,5 +93,5 @@ Give a non-technical merchant a fast, trustworthy Persian RTL view of payment pe
|
||||
- Approved analytics interface contract for the metric catalogue and cohort policy
|
||||
- Approved authentication/session API
|
||||
- OpenAPI/interface contract and error format
|
||||
- Delivery of the licensed Iran Yekan X Professional FaNum variable webfont
|
||||
- Approved private build/deployment injection path for the licensed Iran Yekan X Professional FaNum variable webfont
|
||||
- Static adapter fallback/routing behavior under the final Nginx configuration
|
||||
|
||||
Reference in New Issue
Block a user