From 5b43a9b783dc294179cb03d8a91f9ad6ea4250bf Mon Sep 17 00:00:00 2001 From: moojttaba Date: Thu, 4 Jun 2026 01:09:33 +0330 Subject: [PATCH] =?UTF-8?q?docs:=20activity=20log=20=E2=80=94=20frontend?= =?UTF-8?q?=20v2.8.81=20(in-shell=20checkout)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.8 (1M context) --- 09 - Audits/Activity Log.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/09 - Audits/Activity Log.md b/09 - Audits/Activity Log.md index 41f5d77..70f68ff 100644 --- a/09 - Audits/Activity Log.md +++ b/09 - Audits/Activity Log.md @@ -1139,4 +1139,21 @@ dedups correctly for both parties. --- +### 2026-06-04 — frontend v2.8.81 — in-shell checkout (Mini App no longer hands off to web) + +Cart «ادامه و پرداخت» previously navigated the Telegram WebView to the web +checkout (taking over the Mini App). New TelegramCheckoutView keeps it in-shell: +order summary + delivery-address picker (reuses saved addresses; "add address" +opens the in-shell addresses manager) → places the order via +convertTemplatesToRequests({paymentConfirmed:false}) so requests are created in +`pending_payment` (escrow model — NO on-chain/web3 transaction needed inside the +Mini App). Cart cleared on success and the shell jumps to Requests, where the +buyer completes the escrow payment. New 'checkout' shell overlay + cart `clear()` +on the cart hook. Verified the deferred path exists (status 'pending_payment' +when paymentConfirmed is false) rather than requiring batch-convert's +paymentConfirmed:true on-chain flow. +**Verification:** tsc + eslint clean. + +--- +