docs: align dashboard payment semantics

DESIGN.md

@@ -1,7 +1,7 @@
 # Design System — ZarinPal Merchant Analytics
 
 - Status: Draft baseline for approval
-- Version: 0.1.9
+- Version: 0.2.0
 - Last updated: 2026-08-20
 - Direction: Persian-first RTL
 
@@ -84,7 +84,7 @@ Initial authenticated routes:
 1. ورود (login)
 2. پیشخوان (overview)
 3. عملکرد پرداخت (success, retries, failures, timing)
-4. کارمزد و درآمد (relative fee/cost analytics, clearly qualified)
+4. کارمزد و درآمد (real merchant fee amounts and rates in Rial)
 5. مقایسه با هم‌گروه‌ها (anonymized category/cohort benchmark)
 6. کیفیت داده / درباره شاخص‌ها (definitions, freshness, limitations)
 7. حساب کاربری / خروج
@@ -113,7 +113,8 @@ Navigation labels should describe merchant tasks, not internal database concepts
 - Charts have a textual summary and downloadable/visible data table when practical.
 - Zero, unavailable, suppressed, and not-yet-calculated are visually and linguistically distinct.
 - A ready section appears immediately without layout-shifting or blocking on unfinished siblings. Overall progress remains understandable without relying on animation.
-- Only source status `Verified` is presented as a confirmed successful payment. `Paid` is a separate operational state and is never merged into success or failure without a later approved metric-definition change.
+- Source statuses `Paid` and `Verified` both count as successful bank payments because funds were deducted. Keep them visually distinguishable: `Paid` means merchant verification is incomplete and is an actionable gap; `Verified` is finalized.
+- Present `fee_amount_rial` as the merchant's real fee, summed once per session. Never multiply it by retry attempts or label it as obfuscated/relative-only in the product.
 
 ## Motion
 
@@ -145,12 +146,12 @@ Navigation labels should describe merchant tasks, not internal database concepts
 
 | Version | Date | Decision |
 |---|---|---|
+| 0.2.0 | 2026-08-20 | Corrected payment lifecycle semantics from CTO guidance: `Paid` and `Verified` are bank-payment successes, `Paid` remains unverified, and session-level fees are real Rial amounts. |
 | 0.1.9 | 2026-08-20 | Added rate-limit UX, 15-second SSE heartbeat/recovery, one-hour replay, and failed-section-only manual retry. |
 | 0.1.8 | 2026-08-20 | Fixed the four parallel section ids, 30-day cache, idempotent start/SSE flow, and section timeout/retry behavior. |
 | 0.1.7 | 2026-08-20 | Moved analytics results to high-TTL Redis and defined partial, parallel section delivery through authenticated SSE. |
 | 0.1.6 | 2026-08-20 | Replaced time-based analytics freshness with lazy first-access calculation and revision-based merchant/cohort cache states; defined Saturday–Friday weeks. |
 | 0.1.5 | 2026-08-20 | Removed holiday/event reporting; limited period controls to daily, weekly, Jalali-month, and Persian-season views. |
-| 0.1.4 | 2026-08-20 | Kept `Paid` separate from confirmed `Verified` success. |
 | 0.1.2 | 2026-08-20 | Added the insufficient-data state and visibility threshold for anonymized peer comparisons. |
 | 0.1.1 | 2026-08-20 | Fixed merchant-facing time presentation to the Jalali calendar in `Asia/Tehran`, with explicit UTC API instants. |
 | 0.1.0 | 2026-08-20 | Established ZarinPal-inspired RTL foundation from supplied public/panel screenshots; fixed SvelteKit/Svelte/TypeScript/Tailwind stack; defined responsive shell, core components, accessibility, chart, and motion rules. |