docs: activity log — backend v2.8.69 + frontend v2.8.78 (chat system msgs + review)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -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.
|
||||
|
||||
---
|
||||
|
||||
<!-- Add new entries above this line. Newest at top. -->
|
||||
|
||||
Reference in New Issue
Block a user