`push_tokens` — qurilma registri (`audience`, `delete_after`)

qa-ep-13-t01-s03 statusni o'zgartirdi Review → Bajarildi

qa-ep-13-t01-s03 izoh qoldirdi

QA (qa-EP-13-T01-S03) — izolyatsiyalangan worktree, commit 03f1df5. VERDIKT: done. Spec §2.3 jadvali AYNAN mos (11/11 ustun, ortiqcha ustun/cheklov YO'Q): token varchar(255)+UNIQUE(token) DB bo'ylab, audience varchar(16) CHECK IN (employee,driver,customer,supplier) — 'web' YO'Q, platform varchar(10) CHECK (android|ios), device_id varchar(128) NOT NULL, device_model varchar(80), app_version varchar(20), delete_after timestamptz NULL, last_seen_at/created_at NOT NULL DEFAULT now(), user_id bigint FK->users(id) ON DELETE CASCADE, UNIQUE(user_id,device_id,audience). Partitsiya YO'Q (test relkind='r' ni tasdiqlaydi) — talab bo'yicha to'g'ri. tenant_id/schema ajratish yo'q (AR-1), nomlash snake_case + ko'plik, fk_push_tokens_user repo konvensiyasiga mos. KONTRAKT (openapi/v1/notifications.yaml, MUZLATILGAN, tegilmadi): PushTokenRegisterRequest har maydoni uchun DB ustuni bor va tur/uzunlik mos — token(255)->varchar(255), platform enum->CHECK, device_id(128)->varchar(128), device_model(80), app_version(20). audience tanada ataylab yo'q (JWT aud) — DB'da bor. PushTokenResponse 8 maydonining hammasi DB'da qoplangan. Drift YO'Q. TESTLAR: mvn -Dtest=PushTokensMigrationTest test -> Tests run: 10, Failures: 0, Errors: 0 (Testcontainers postgres:16, real migratsiya zanjiri V1..V52). MUTATSIYA: 6 mutant, 5/5 majburiysi ushlandi (har biri target/classes da kuchga kirgani tasdiqlangan): (a) UNIQUE(token) olib tashlandi -> sameTokenCannotBeWrittenForSecondUser YIQILDI [5537] (b) UNIQUE dan faqat audience olib tashlandi -> sameDeviceCanHoldRowsForDifferentAudiencesOfSameUser YIQILDI [5538] (c) CHECK ro'yxatiga 'web' qo'shildi -> webAudienceIsRejectedByCheckConstraint YIQILDI [5539] (d) ON DELETE CASCADE -> NO ACTION: deletingUserCascadesPushTokenRows YIQILDI (e) platform CHECK yechildi -> platformOutsideAllowedListIsRejectedByCheckConstraint YIQILDI Uchala mezon (5537/5538/5539) mustaqil tasdiqlandi. FIXTURE XILMA-XILLIGI — yaxshi: audience 4 xil qiymat, platform android+ios, delete_after NULL va NOT NULL, device_id/token har testda turlicha. Qotib qolgan fixture yo'q. 🟡 IZOH (bloklamaydi, mezonlarga kirmaydi — keyingi bargga): 6-mutant `delete_after timestamptz` -> `date` 10 testdan TIRIK o'tdi (target/classes da mutatsiya kuchga kirgani tasdiqlangan). Sabab: delete_after yoziladi, lekin hech bir testda QAYTA O'QILMAYDI, shuning uchun ustun TURI qo'riqlanmagan. Qoida 23 (now() + 5 daqiqa oynasi) `date` da yarim tunga qirqilib ketardi va jim yurardi. Servis/worker bargida (delete_after yozadigan T-barg) round-trip assert qo'shilsin: yozilgan Instant aynan qaytib o'qilsin. DB kodi TO'G'RI (timestamptz) — bu faqat test qamrovi qarzi.

coder-ep-13-t01-s03 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-13-t01-s03 yangiladi

Yangilandi: branch, commit_sha

coder-ep-13-t01-s03 qabul mezonini belgiladi

✓ `audience = 'web'` qiymati CHECK bilan rad etiladi

coder-ep-13-t01-s03 qabul mezonini belgiladi

✓ Bitta user + qurilma + auditoriya uchun ikkinchi qator yozilmaydi

coder-ep-13-t01-s03 qabul mezonini belgiladi

✓ Ayni `token` ikkinchi user'ga yozilmoqchi bo'lsa `UNIQUE(token)` buni to'sadi (UC4 3-qadam mantiqi servis qatlamida)

coder-ep-13-t01-s03 fayllarni qayd etdi

2 ta fayl qayd etildi

coder-ep-13-t01-s03 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-13-t01-s03 ishga oldi

pm-agent yaratdi

`push_tokens` — qurilma registri (`audience`, `delete_after`)