From 9823194125af62fbc81c3c86a2b30dbbb7c913b7 Mon Sep 17 00:00:00 2001 From: moojttaba Date: Wed, 3 Jun 2026 22:23:03 +0330 Subject: [PATCH] =?UTF-8?q?docs:=20activity=20log=20=E2=80=94=20backend=20?= =?UTF-8?q?v2.8.69=20+=20frontend=20v2.8.78=20(chat=20system=20msgs=20+=20?= =?UTF-8?q?review)?= 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 | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/09 - Audits/Activity Log.md b/09 - Audits/Activity Log.md index 302cd1b..ece6d21 100644 --- a/09 - Audits/Activity Log.md +++ b/09 - Audits/Activity Log.md @@ -1038,4 +1038,23 @@ handleVerify still refreshes after a successful confirm). --- +### 2026-06-03 — backend v2.8.69 + frontend v2.8.78 — chat system messages + post-delivery review + +**Chat both-sides (round 2 — real root cause):** support welcome/greeting and +group "chat created" messages are authored on the backend with +`chat.metadata.createdBy` (the buyer) as senderId, so they rendered as the +buyer's own. Backend (v2.8.69): `sendSystemMessage` now takes an optional +senderId and createSupportChat passes the support user's id. Frontend (v2.8.78): +any `messageType:'system'` message renders as a neutral centred note regardless +of sender — robust fix for all system messages. +**Post-delivery seller review (frontend v2.8.78):** buyer viewing a +delivery/delivered/seller_paid/completed request sees a star + comment prompt +(TelegramReviewPrompt). Seller resolved from the request's selected offer +(getOffers → selectedOfferId → sellerId); submits createReview({subjectType: +'seller', subjectId, rating, comment, purchaseRequestId}); 409 → "already +reviewed" handled gracefully. +**Verification:** backend + frontend tsc clean. + +--- +