`NotificationOutboxWorker` — qoida 34 claim/lease + holat mashinasi

qa-ep-13-t03-s01 statusni o'zgartirdi Review → Bajarildi

qa-ep-13-t03-s01 izoh qoldirdi

QA (qa-EP-13-T03-S01) — QABUL QILINDI. Tekshirilgan commit 0120b98, QA test commit'i 92081cf. O'LCHANGAN DALIL — butun notification to'plami birga (mvn -o test -Dtest='Notification*Test,PushTokens*Test,AdminSecurityNotification*Test', target/surefire-reports oldin o'chirilgan): Tests run: 89, Failures: 0, Errors: 0, Skipped: 0 — 8 klass (poydevor 77/7 edi, +12 yangi test). MEZONLAR — har biri kod darajasida + mutatsiya bilan tasdiqlandi (izolyatsiyalangan git worktree /tmp/qa-EP-13-T03-S01, HEAD=0120b98, yakunda o'chirildi): * 5557 — NotificationOutboxRepository.java:122 `FOR UPDATE SKIP LOCKED`; test qulfni ATAYLAB commit qilinmagan alohida JDBC ulanishida ushlab turadi (timing'ga bog'liq emas), ikki sikl bo'ylab FCM ga jami 2 so'rov (har qatorga 1). * 5558 — claim SQL'da `status='sending' AND next_attempt_at <= now()` (repo:119); test next_attempt_at = now()-6min (qayta olinadi) va now()+4min (OLINMAYDI) juftligi bilan tekshiradi. * 5559 — NotificationOutboxWorker.java:247 `return security || "active".equals(user.status())`; bloklangan user: task.available -> dead/recipient_ineligible, auth.account_blocked -> sent, FCM ga faqat 1 so'rov. Qo'shimcha: soft-delete'da (qoida 5 b) security xabari HAM o'ladi. * 5560 — worker:161 `!catalog.exists(...)` -> markDeadImmediate('unknown_event'), FCM ga umuman ketmaydi. * 5561 — claim SQL sent/dead ni umuman tanlamaydi; test claim=0 va qatorlarning TO'LIQ snapshot'ini (SELECT *) solishtiradi. MUTATSIYA: 6 mutant sinaldi, 5 tasi darhol o'ldi: 1) SKIP LOCKED olib tashlandi -> 5557 testi claim'da qulfda abadiy blokda qoladi (500 s'da terminate; javap: bytecode'da 'SKIP LOCKED' 0 marta) = o'ldi; 2) lease reclaim sharti olib tashlandi -> sendingRowWithExpiredLease...:192 FAILURE; 3) katalog tekshiruvi olib tashlandi -> unknownEventCodeDies...:266 FAILURE; 4) qoida 6 security istisnosi olib tashlandi -> blockedUserWorkEventDies...:224 FAILURE; 5) terminal qo'riqchi (status IN (...,'sent','dead')) -> sentAndDeadRowsAreNeverTouchedAgain:300 FAILURE. 6) 🔴 TIRIK QOLDI: LEASE_DURATION 5 daqiqa -> 5 soat mutanti 12 testlik to'plamdan o'tib ketdi (javap bilan tasdiqlandi: bytecode'da Duration.ofHours) — hech bir assert qoida 34 dagi lease chegarasining KATTALIGIGA tegmagan edi. Kod TO'G'RI (5 daqiqa), qamrov teshigi edi -> QA testni kuchaytirdi (92081cf, FAQAT test fayli): claim'dan keyin `next_attempt_at - now()` TO'LIQ DB tomonida o'lchanadi (240..300 s) — test JVM'i va Postgres konteyneri soatlari farqiga ham, kalendar (oy/kun) chegarasiga ham bog'liq emas. Mutant endi o'ladi. Ikkinchi kuchaytirish: unknownEvent... testidagi "qayta urinilmaydi" da'vosi claim'ning lease YON-TA'SIRI bilan isbotlanardi (5-mutant shu testdan tirik o'tib faqat 5561 da o'lgan edi) — endi next_attempt_at ataylab o'tgan zamonga tushiriladi, mutant ikkala testda o'ladi. FIXTURE XILMA-XILLIGI ✓: severity info+security; status pending/sending/sent/failed/dead; attempt_count 0/1/3/4; user active/blocked/deleted_at; token delete_after NULL va kelajakdagi qiymat. Bitta qiymatga tayangan shoxobcha topilmadi. KALENDAR ✓: ClockConfig bean, Java tomonidagi HAR vaqt qarori clock.instant() dan (sent_at, last_error_at, F1 next_attempt_at, delete_after filtri); claim/lease `now()` SQL ichida (spec shu ko'rinishda beradi). O'tgan OYGA created_at yozadigan INSERT YO'Q (V51 partition xavfi yo'q) — testdagi Clock.fixed(2026-01-31T23:59) faqat Java-side backoff'ga ta'sir qiladi, created_at DEFAULT now(). CHEGARA ✓: app.notifications.worker.enabled=false — application.yml + dev + prod (uchchalasi); fixed-delay default 1000 ms (qoida 38). S01 da FCM/HTTP klienti YO'Q (grep: RestTemplate/WebClient/HttpClient/okhttp/fcm.googleapis — 0), faqat PushSenderPort + NoopPushSenderPort seam. CROSS-CUTTING ✓: claim/markSent/markFailedRetry/markDead* — hammasi @Transactional(REQUIRES_NEW), FCM chaqiruvi qulfdan TASHQARIDA (CROSS_CUTTING F.10); tenant_id/schema almashtirish yo'q (AR-1); migratsiya (V50–V53) va openapi/ TEGILMAGAN (git show --stat 0120b98); push_tokens fizik DELETE — qoida 16 talab qiladi; log'da token QIYMATI yo'q (faqat token_count). 📌 NON-BLOCKING KUZATUV (S02/S03 uchun, bu bargni bloklamaydi): finalize UPDATE'larida (markSent/markDead*/markFailedRetry) `AND status='sending'` qo'riqchisi YO'Q — kafolat faqat claim SQL'ida. Bitta instansda (AR-5, @Scheduled fixedDelay bitta thread) xavf yo'q, lekin IKKINCHI instans qo'shilganda bitta qatorni ishlash 5 daqiqadan oshsa nazariy `dead -> sent` (spec §4 da TAQIQ) mumkin. Spec 'naqsh ikkinchi instans uchun tayyor' deydi — S03/kelajakdagi ikkinchi instans ishida finalize'ga status sharti qo'shilsa arzon yopiladi.

qa-ep-13-t03-s01 qabul mezonini belgiladi

✓ `sent` yoki `dead` qatorni qayta ishlashga urinish holatni o'zgartirmaydi

qa-ep-13-t03-s01 qabul mezonini belgiladi

✓ Katalogda yo'q `event_code` `dead`/`unknown_event` bo'ladi va qayta urinilmaydi

qa-ep-13-t03-s01 qabul mezonini belgiladi

✓ Bloklangan foydalanuvchiga ish xabari `dead`/`recipient_ineligible`, xavfsizlik xabari esa yuboriladi (AC5)

qa-ep-13-t03-s01 qabul mezonini belgiladi

✓ Lease muddati o'tgan `sending` qator keyingi siklda qayta olinadi (qo'lda `next_attempt_at` ni o'tkazib tekshiriladi)

qa-ep-13-t03-s01 qabul mezonini belgiladi

✓ Ikki parallel worker sikli bir vaqtda ishga tushirilganda bir qator FCM ga bir marta ketadi (AC14, E13)

coder-ep-13-t03-s01 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-13-t03-s01 izoh qoldirdi

NotificationOutboxWorker yozildi — AbstractOutboxWorker EXTENDS qilinmadi (ustun shakli mos emas: attempt_count/sending/dead vs attempts/locked_at/processing), qoida 34 SQL o'zi NotificationOutboxRepository ichida. PushSenderPort porti bilan chegaralandi (FCM klienti EP-13-T03-S02); NoopPushSenderPort ATAYLAB transient failure qaytaradi, shu sabab app.notifications.worker.enabled=false HAMMA profilda (application.yml + dev + prod) — S02 real klient tayyor bo'lganda yoqiladi. Clock bean qo'shildi (common/config/ClockConfig) — F1 backoff va push_tokens delete_after filtri Java tomonida endi test bilan boshqariladi. Retry backoff to'liq jadvali+jitter va circuit breaker ATAYLAB S03 uchun seam (NotificationRetryBackoff) qoldirildi. Qoida 5(c) (huquq qayta tekshiruvi) worker sathida TEKSHIRILMAYDI — notification_outbox/katalogda permission_code maydoni yo'q, bu S01 mezonlari doirasidan tashqari ma'lum cheklov (kod qarzi). Test: Notification*Test+PushTokens*Test+AdminSecurityNotification*Test birga 89/89 yashil (0 fail/0 err).

coder-ep-13-t03-s01 yangiladi

Yangilandi: branch, commit_sha

coder-ep-13-t03-s01 qabul mezonini belgiladi

✓ `sent` yoki `dead` qatorni qayta ishlashga urinish holatni o'zgartirmaydi

coder-ep-13-t03-s01 qabul mezonini belgiladi

✓ Katalogda yo'q `event_code` `dead`/`unknown_event` bo'ladi va qayta urinilmaydi

coder-ep-13-t03-s01 qabul mezonini belgiladi

✓ Bloklangan foydalanuvchiga ish xabari `dead`/`recipient_ineligible`, xavfsizlik xabari esa yuboriladi (AC5)

coder-ep-13-t03-s01 qabul mezonini belgiladi

✓ Lease muddati o'tgan `sending` qator keyingi siklda qayta olinadi (qo'lda `next_attempt_at` ni o'tkazib tekshiriladi)

coder-ep-13-t03-s01 qabul mezonini belgiladi

✓ Ikki parallel worker sikli bir vaqtda ishga tushirilganda bir qator FCM ga bir marta ketadi (AC14, E13)

coder-ep-13-t03-s01 fayllarni qayd etdi

15 ta fayl qayd etildi

coder-ep-13-t03-s01 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-13-t03-s01 ishga oldi

pm-agent yaratdi

`NotificationOutboxWorker` — qoida 34 claim/lease + holat mashinasi