Data-only push qabul qilish va ko'rsatish (qoida 27 filtri)

qa-1 statusni o'zgartirdi Review → Bajarildi

QA (qa-1): 4/4 mezon tasdiqlandi, mutatsiya bo'shlig'i test bilan yopildi (commit 80076ef).

qa-1 yangiladi

Yangilandi: branch, commit_sha

qa-1 izoh qoldirdi

QA (qa-1) — izolyatsiyalangan worktree'da to'liq tekshiruv. NATIJA: 4/4 mezon bajarilgan, barg `done`. MEZON-MEZON: * 5618 (dedupe, qoida 27/E6) ✅ — `push_message_handler.dart:40-41` (markIfNew -> !isNew ? return), persistent holat `shared_preferences_push_notification_deduper.dart:31-41`. Parser dedupe kalitsiz xabarni butunlay tashlaydi (`push_message_parser.dart:34`) — filtrni chetlab o'tish yo'li yo'q. * 5619 (foreground/background/terminated) ✅ — foreground `push_foreground_message_listener.dart:30-36`; background+terminated bitta top-level callback `push_background_handler.dart:25-31`, `main.dart:63` da ro'yxatdan o'tgan. * 5620 (ruxsat yo'q -> yiqilmaydi) ✅ — ikki qatlam: `flutter_local_notification_display.dart:75-98` (show ichida try/catch) + `push_message_handler.dart:43-52`. Inbox push'ga bog'liq emas (REST, alohida feature). * 5621 (analyze toza, to'plam yashil) ✅ — `flutter analyze`: No issues found; `flutter test`: 1036/1036 yashil. KONTRAKT DRIFTI (maydon darajasida, notifications.yaml @ 38e8f16) — drift YO'Q: * `POST /push-tokens` javob `200` (201 emas) — `push_token_api.dart:24-34` status tekshirmaydi, dio 2xx ni qabul qiladi; 201 kutilmaydi. * `audience` tanada YO'Q — `PushTokenRegisterRequest` da maydon strukturaviy ravishda yo'q (`push_token_register_request.dart:61-74`), JWT `aud` dan olinadi. * `DELETE /push-tokens/{device_id}` -> `204` (qator topilmasa ham) — `push_token_api.dart:39-45` `Future<void>`, tanani parse qilmaydi, 404 ni maxsus ishlamaydi. * Sxema maydonlari 1:1: token/platform(android|ios)/device_id/device_model?/app_version?; javobda `token` va `delete_after` YO'Q; `Audience` enum aynan 4 qiymat (employee|driver|customer|supplier), `web` yo'q. SPEC (10_notifications qoida 18/19/27): payload faqat event_code + notification_id + generik title/body; `tenant_slug` yo'q (qoida 19 bekor) — `PushMessage` klassi ortiqcha maydonga tur darajasida joy bermaydi, parser testi buni tasdiqlaydi. 🔴 MUTATSIYA TEKSHIRUVI (5 mutant, izolyatsiyalangan worktree): * MUT-A dedupe filtri olib tashlandi -> 3 test yiqildi (handler BACKGROUND/TERMINATED + foreground) ✅ o'ldi * MUT-B deduper diskdan o'qimaydi -> 4 test yiqildi ✅ o'ldi * MUT-C foreground obunasi yo'q -> 3 test yiqildi ✅ o'ldi * MUT-D `firebasePushBackgroundMessageHandler` tanasi `return;` -> 🔴 1027 testdan BITTASI HAM yiqilmadi (TIRIK QOLDI) * MUT-E `FlutterLocalNotificationDisplay.show` try/catch -> rethrow -> 🔴 TIRIK QOLDI Ya'ni mezon 5619 ning background/terminated KIRISH NUQTASI va mezon 5620 ning haqiqiy ijrochisi qamralmagan edi (kod to'g'ri, lekin uni hech narsa qo'riqlamasdi). Sabab: mavjud testlar faqat umumiy yadroni (`handleIncomingPushMessageData`) soxta bog'liqliklar bilan tekshirardi; `FlutterLocalNotificationDisplay` esa hech qanday testda ishlatilmasdi. QA 2 ta test fayli yozdi (9 test) — commit `80076ef`: * `test/core/push/push_background_handler_test.dart` — RemoteMessage.data haqiqatan uzatiladi, PERSISTENT (disk) deduper ishlatiladi, background dedupe, terminated cold-start, majburiy maydonsiz payload, otilmaslik. * `test/core/push/flutter_local_notification_display_test.dart` — test muhitida `FlutterLocalNotificationsPlatform.instance` ro'yxatdan o'tmagani "ruxsat yo'q / plagin sozlanmagan" holatini aynan takrorlaydi; show()/init() otilmasligi tekshiriladi. Qayta mutatsiya: MUT-D -> 3 yangi test yiqildi (boshqasi emas); MUT-E -> 3 yangi test yiqildi (init() testi to'g'ri ta'sirlanmadi). Ikkalasi ham endi o'ladi. Yakun: `flutter test` 1036/1036 yashil, `flutter analyze` toza, `git grep MUTANT HEAD` bo'sh, worktree o'chirildi.

worker-ep-13-t07 izoh qoldirdi

WORKER IZOHI (lead uchun, kelishuv talab qiladi): FCM data payload ining WIRE KALIT NOMLARI (notification_id / event_code / title / body) hech qanday muzlatilgan kontraktda YOQ — notifications.yaml faqat REST yollarni qamraydi, FCM payload ini emas. Backend FCM worker (EP-13-T02/T03) hali yozilmagan. Mobil klient bu nomlarni 10_notifications qoida 18 matnidan oldi (push_message_parser.dart boshida hujjatlandi). RISK: backend boshqa kalit nomi bilan yuborsa, push jimgina parse bo lmaydi va hech qanday test buni ushlamaydi (ikki repo, umumiy kontrakt yoq). Lead: backend push yuborish bargi shu AYNAN kalitlarni ishlatishi tekshirilsin yoki payload shakli spec ga yozilsin.

coder-ep-13-t07-s02 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-13-t07-s02 izoh qoldirdi

Data-only push qabul qilish/ko'rsatish tayyor. Yangi lib/core/push/*: push_message.dart (faqat 4 maydon — notification_id/event_code/title/body, qoida 18 taqig'i tur darajasida ham), push_message_parser.dart (xom data map -> PushMessage, majburiy maydon yo'q bo'lsa null), push_message_handler.dart (markaziy parse->dedupe->show), push_notification_deduper.dart + shared_preferences_push_notification_deduper.dart (persistent dedupe — SharedPreferences, ilova qayta ishga tushgach ham ishlaydi), local_notification_display.dart + flutter_local_notification_display.dart (yangi paket flutter_local_notifications ^22.3.0 qo'shildi), push_message_provider.dart + firebase_push_message_provider.dart (foreground oqimi), push_background_handler.dart (FirebaseMessaging.onBackgroundMessage top-level handler). main.dart S01 naqshiga mos wiring qilindi (Firebase best-effort init ichida). Arxitektura qarori: background va terminated FCM SDK darajasida BITTA callback orqali keladi (hujjatlashtirilgan xatti-harakat) — shuning uchun ikkalasi ham push_message_handler_test.dart da (background: bitta jarayon ichida ikkinchi chaqiruv; terminated/cold-start: YANGI deduper instansiyasi oldindan seed qilingan holat bilan) sinaldi, foreground alohida push_foreground_message_listener_test.dart da fake stream bilan. Dedupe persistensiyasi shared_preferences_push_notification_deduper_test.dart da SharedPreferences.setMockInitialValues + ikkinchi instansiya bilan real implementatsiya ustida tekshirildi (fake emas). FCM data payload wire kalitlari (notification_id/event_code/title/body) uchun OpenAPI kontrakt yo'q edi (FCM worker/payload backend tomonda hali yozilmagan, notifications.yaml faqat REST'ni qamraydi) — bu bo'shliq emas, muhandislik qarori sifatida push_message_parser.dart boshida hujjatlashtirdim (spec qoida 18 mazmunni aniq beradi, faqat kalit nomi tanlandi, notification_id so'zi spec matnidan aynan olindi). flutter analyze: 0 issue. flutter test (to'liq to'plam): 1027/1027 yashil (yangi 21 test shu ichida). Build (APK) urinilmadi — vazifa faqat analyze+test talab qildi, DevOps build rejimi board'da alohida comment sifatida topilmadi.

coder-ep-13-t07-s02 qabul mezonini belgiladi

✓ `flutter analyze` toza, to'liq test to'plami yashil

coder-ep-13-t07-s02 qabul mezonini belgiladi

✓ Notifikatsiya ruxsati berilmaganda ilova yiqilmaydi va inbox baribir ishlaydi

coder-ep-13-t07-s02 qabul mezonini belgiladi

✓ Foreground, background va yopiq ilova holatlarining uchalasida ham xabar ko'rsatiladi

coder-ep-13-t07-s02 qabul mezonini belgiladi

✓ Bir xil `notification_id` bilan ikki push kelganda foydalanuvchi bitta xabar ko'radi (E6)

coder-ep-13-t07-s02 fayllarni qayd etdi

21 ta fayl qayd etildi

coder-ep-13-t07-s02 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-13-t07-s02 ishga oldi

pm-agent yaratdi

Data-only push qabul qilish va ko'rsatish (qoida 27 filtri)