docs: sync documentation with latest codebase state

- Update Activity Log with 108 missing commits (48 backend + 60 frontend)
- Update version references: backend v2.8.79, frontend v2.8.94
- Update migration count: 18 migrations (0000-0017)
- Update Telegram Mini App Flow to v2.8.94
- Update Payment Flow - Scanner to 2026-06-05
- Update all architectural and database references

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>

02 - Data Models/Postgres Runtime Cutover Status.md

@@ -4,14 +4,14 @@ tags: [data-model, postgres, migration, runtime-status]
 aliases: [Postgres Status, PG Cutover Status, Mongo vs Postgres Runtime]
 created: 2026-05-31
 updated: 2026-06-03
-source: backend integrate-main-into-development@14d164c + deployment main@8764fdf
+source: backend integrate-main-into-development@41087c7 + deployment main@8764fdf
 ---
 
 # Postgres Runtime Cutover Status
 
-> **Current branch:** backend `integrate-main-into-development` at `14d164c`, version `2.8.56`; dev deployment `main` at `8764fdf`.
+> **Current branch:** backend `integrate-main-into-development` at `41087c7`, version `2.8.79`; dev deployment `main` at `8764fdf`.
 >
-> **Bottom line:** the codebase is in **active dual-write phase**. All 11 repository domains in the factory now have Drizzle schemas, Drizzle repos, and dual-write wrappers (except Chat and ReleaseHold, which have Drizzle repos but no dual-write counterpart). 18 Drizzle migrations (0000–0017) have landed, covering every table in scope. Dev deployment defaults nine PG-capable stores to Postgres: auth-owned users/Telegram auth, confirmation-threshold config/history, user addresses, categories, level config, shop settings, reviews, notifications, and the oracle payment_quotes path. Code-level defaults remain `mongo` outside those deployment overrides. Repository factory normalizes `postgres` and `pg` as equivalent mode tokens. The unmounted legacy marketplace router is detached. As of `2.8.54–2.8.56`, the `guard` user role is in PG schema, chat routes are fixed, notifications deliver in real time, and PG response serialization/id resolution in marketplace is corrected. Reads are still Mongo-authoritative across all dual-write domains — read cutover is the remaining gate for each domain. Chat normalization (participants/messages stored as JSONB blobs, not relational child tables) remains an open blocker for full Chat cutover.
+> **Bottom line:** the codebase is in **active dual-write phase**. All 11 repository domains in the factory now have Drizzle schemas, Drizzle repos, and dual-write wrappers (except Chat and ReleaseHold, which have Drizzle repos but no dual-write counterpart). 18 Drizzle migrations (0000–0017) have landed, covering every table in scope. Dev deployment defaults nine PG-capable stores to Postgres: auth-owned users/Telegram auth, confirmation-threshold config/history, user addresses, categories, level config, shop settings, reviews, notifications, and the oracle payment_quotes path. Code-level defaults remain `mongo` outside those deployment overrides. Repository factory normalizes `postgres` and `pg` as equivalent mode tokens. The unmounted legacy marketplace router is detached. As of `2.8.79`, the `guard` user role is in PG schema, chat routes are fixed, notifications deliver in real time, PG response serialization/id resolution in marketplace is corrected, and seller shop lookup is tolerant of uuid/legacy id formats. Reads are still Mongo-authoritative across all dual-write domains — read cutover is the remaining gate for each domain. Chat normalization (participants/messages stored as JSONB blobs, not relational child tables) remains an open blocker for full Chat cutover.
 
 ## Schema and Repository Coverage
 
@@ -158,12 +158,29 @@ The backend code defaults every store flag below to `mongo`. Dev deployment over
 
 Estimated overall: **schema and infrastructure phase complete; write-seam phase substantially complete; read cutover and backfill execution remain for every domain.**
 
-## Recent Progress Since Last Update (2.8.37 → 2.8.56)
+## Recent Progress Since Last Update (2.8.37 → 2.8.79)
 
 - **2.8.38–2.8.46:** Complete dual-write repos for all remaining domains; Drizzle migrations pipeline finalized; TTL scheduler added; shop lookup bug-fixed.
 - **2.8.47:** Seeds made Postgres-capable and idempotent for PG-only boot (`MONGO_CONNECT_MODE=never`).
 - **2.8.48–2.8.49:** Fresh-DB PG migrate + seed path corrected; 0013/0014 migrations made valid for a fresh `drizzle-kit migrate` run.
 - **2.8.50:** Admin user counts routed through postgres-capable stores; admin user management works end-to-end under PG.
+- **2.8.51–2.8.53:** PG response serialization and id resolution in marketplace purchase-request paths corrected; user creation and purchase request unblocked.
+- **2.8.54:** Guard user role added across auth and user management; migration 0017 adds guard to user_role enum.
+- **2.8.55:** Chat routes fixed and notifications deliver in real time.
+- **2.8.56:** Seller shop lookup made tolerant of uuid/legacy id formats.
+- **2.8.57–2.8.60:** Telegram Mini App in-shell shop, account tab parity, shopping cart.
+- **2.8.61:** Direct-transfer checkout option for non-web3 users.
+- **2.8.62–2.8.64:** Points level boundary fixes, legacy 24-hex user id support, seller ratings from real published reviews.
+- **2.8.65:** Chat participant names populated on Postgres path, participant canonicalization.
+- **2.8.66–2.8.69:** Telegram: product-style template cards, in-shell template detail, web-app-parity templates, settings/addresses in-shell, theme/dark mode, solar-style icons, avatar upload, achievements.
+- **2.8.70:** Telegram in-shell settings and addresses, theme from central config.
+- **2.8.71–2.8.73:** Telegram: solar-style icons, avatar URL fixes, inline email verify, web links keep app alive, remove escrow-states.
+- **2.8.74:** Telegram chat own-message detection, read-only email field.
+- **2.8.75:** Self-contained email-change flow with visible code entry.
+- **2.8.76:** Telegram send-code always reveals verify panel.
+- **2.8.77:** Telegram keep email code panel mounted after sending.
+- **2.8.78:** Telegram system messages neutral + post-delivery seller review.
+- **2.8.79:** Request template maxUsage made truly optional; template creation 500 fix.
 - **2.8.51–2.8.53:** PG response serialization and id resolution corrected in marketplace; user creation and purchase request creation unblocked from PG FK constraint errors.
 - **2.8.54:** `guard` user role added to `user_role` enum (migration 0017); guard role support across auth and user management.
 - **2.8.55:** Chat routes fixed; notifications delivered in real time alongside chat.