AC4 — token tozalashning AVTOMATIK integratsiya testi

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

qa-ep-13-t08-s01 izoh qoldirdi

QA mustaqil tekshiruv (qa-EP-13-T08-S01) — QABUL QILINDI. Bazaviy yurish (flock ostida, main tree): PushTokenCleanupAc4IntegrationTest 3/3 + WorkReviewIntegrationTest 13/13 = Tests run: 16, Failures: 0, Errors: 0. Regressiya (uz.erpbom.notifications.**): Tests run: 215, Failures: 0, Errors: 0 — BUILD SUCCESS. 5626 — ikkala yo appRequestDelete... (qoida 22a, DELETE /push-tokens/{device_id}) va serverGuarantee... (qoida 22b+23, SessionRevocationService, HTTP DELETE yo) ALOHIDA test metodlarida. Assert FCM darajasida: RecordingPushSenderPort.requests() isEmpty (159-172 va 206-210 qatorlar) + outbox dead/no_token — ya worker haqiqatan yurgani isbotlanadi, faqat DB qatori emas. 5627 — MUTATSIYA QA tomonidan QAYTA otkazildi, izolyatsiyalangan worktree (/tmp/qa-EP-13-T08-S01-verify), har mutant javap bilan bytecode darajasida tasdiqlandi: M1 PushTokenService.delete tanasi boshatildi (javap: `0: return`) -> YIQILDI faqat (a) testi (PushTokenCleanupAc4IntegrationTest.java:161) + eski PushTokensControllerIntegrationTest#deleteRemovesRowImmediatelyAndIsIdempotent. Qolgan 225 test yashil. M2 scheduleDeferredCleanupForUser JPQL neytrallandi -> YIQILDI faqat (b) testi (:191) + SessionRevocationServiceIntegrationTest. Qolgan 224 yashil. M3 deleteByTokenAndUserIdNot JPQL neytrallandi -> YIQILDI faqat (c) testi + PushTokensControllerIntegrationTest#sameTokenOnSameDeviceMovesToNewUserAndOldRowIsGone. Qolgan 225 yashil. M4 (QA qoshimchasi, tavtologiya tekshiruvi) findEligibleForSend dagi delete_after qorigi neytrallandi -> (b) testi aynan FCM assertida yiqildi (:208, Expecting empty but was: [PushSendRequest[eventCode=auth.account_blocked, tokens=[fcm_ac4_server_guarantee_...]]]). Demak FCM-darajali assert tavtologiya emas, yolgonni ushlaydi. Fixture xilma-xilligi: uch testda user/device_id/token qiymatlari har xil (UUID suffiks), (c) da audience ham employee->driver farq qiladi; qotib qolgan qiymat yoq. 5628 — (c) testi: A registratsiya -> B ayni device_id + ayni token bilan registratsiya -> countPushTokensForUser(A)=0, A ning outbox qatori dead/no_token, FCM ga BITTA sorov (B uchun) va u aynan sharedToken bilan. AC11/UC4 3-qadam qoplangan. Flaki test (lead topshirigi): git diff f10a647^ f10a647 -- WorkReviewIntegrationTest.java faqat `erpbom.outbox.production.fixed-delay=3600000` property (+ izoh) qoshgan; @Disabled/@Ignore/assumeTrue YOQ, assert yumshatilmagan (pendingOutboxRow tekshiruvi 299/333 qatorlarda ozgarishsiz). Klass 3 marta ketma-ket yurgizildi: 13/13, 13/13, 13/13 — yashil. Tozalik: `grep -rn MUTANT src/` bosh, `git grep MUTANT HEAD` bosh, worktree ochirildi, asosiy ish daraxti toza (hech narsa yozilmadi/commit qilinmadi).

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

✓ B user kirgach ayni token faqat B qatorida bo'ladi (AC11)

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

✓ Token tozalash kodi olib tashlanganda aynan bu testlar yiqiladi, qolgan to'plam yashil qoladi

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

✓ Ikkala yo'l (ilova so'rovi va server kafolati) alohida testda qoplangan

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

coder-ep-13-t08-s01 yangiladi

Yangilandi: branch, commit_sha

coder-ep-13-t08-s01 izoh qoldirdi

AC4 avtomatik integratsiya testi yozildi: PushTokenCleanupAc4IntegrationTest (3 ta @Test - (a) DELETE /push-tokens/{device_id}, (b) SessionRevocationService server kafolati (qoida 22b/23, oyna yopilgach security xabar ham FCM stubga yetmaydi), (c) AC11/UC4 3-qadam qurilma qayta biriktirilishi). Har uch yolda RecordingPushSenderPort orqali FCM darajasida tekshirildi - mavjud testlar faqat DB qator darajasini tekshirardi, shu yetishmayotgan bogin yopildi. Mutatsiya (izolyatsiyalangan worktree, /tmp/qa-EP-13-T08-S01): 3 ta alohida mutatsiya (PushTokenService.delete boshatildi; PushTokenRepository.scheduleDeferredCleanupForUser va deleteByTokenAndUserIdNot AND 1=0 bilan no-op qilindi) - har birida FAQAT mos test qizil, qolgan 2/3 yashil qoldi. Diqqat: birinchi urinishda PushTokenCleanupAdapter.deletePushToken ni buzganda test ozgarmadi - chunki bu klass faqat auth.LogoutService orqali chaqiriladi, HTTP DELETE endpoint esa togridan-togri PushTokenService.delete ni chaqiradi; haqiqiy chaqiruv zanjirini tekshirib togri mutatsiya nuqtasiga otdim. Shu jarayonda testda @BeforeEach tozalov yoqligi (cross-test ifloslanish, worker butun jadvalni claim qilgani sababli) ham topildi va tuzatildi (alohida commit). LEAD topshirigi: WorkReviewIntegrationTest#terminalBrakRejectReleasesQtyClaimedForReclaim dagi ProductionOutboxWorker (fixedDelay 2s) poygasi erpbom.outbox.production.fixed-delay=3600000 bilan tuzatildi, 3 marta ketma-ket yashil tasdiqlandi (@Disabled ishlatilmadi, assert yumshatilmadi).

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

✓ B user kirgach ayni token faqat B qatorida bo'ladi (AC11)

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

✓ Token tozalash kodi olib tashlanganda aynan bu testlar yiqiladi, qolgan to'plam yashil qoladi

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

✓ Ikkala yo'l (ilova so'rovi va server kafolati) alohida testda qoplangan

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

2 ta fayl qayd etildi

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

Agent ishni boshladi

coder-ep-13-t08-s01 ishga oldi

pm-agent yaratdi

AC4 — token tozalashning AVTOMATIK integratsiya testi