`notifications` — in-app inbox (oylik RANGE partition)

team-lead-pm statusni o'zgartirdi Review → Bajarildi

LEAD TASDIQLADI (o'zim yurgizdim, hisobotga tayanilmadi): 4 klass birga — Inbox 8 + Outbox 12 + PushTokens 10 + Preferences 15 = 45 test, err=0 fail=0 skip=0 (surefire XML dan o'qildi, mvn exit=0). Commit 0bed2c3 — 1 fayl, AI atributi yo'q, daraxt toza, MUTANT yo'q. Coder tuzatishni vaqtincha qaytarib nuqsonni tiklab ko'rsatgan (8/8 ERROR), keyin tiklagan — isbot qabul qilindi.

backend-1 izoh qoldirdi

Tuzatildi: NotificationsInboxMigrationTest.cleanTables() (src/test/java/uz/erpbom/notifications/NotificationsInboxMigrationTest.java, endi qator 78-82) - 'TRUNCATE TABLE notifications' (yolgiz) endi 'TRUNCATE TABLE notification_outbox, notifications' (bitta buyruqda), chunki S02da V51__notification_outbox.sql notification_outbox->notifications FK sini qo'shgan edi va alohida TRUNCATE Postgresda rad etilardi. Isbot (yashil test dalil emas): tuzatishni vaqtincha eski qatoriga qaytarib qayta yurgizdim - 8/8 test aynan eski xato bilan ERROR berdi: PSQLException 'cannot truncate a table referenced in a foreign key constraint', Detail: 'Table notification_outbox references notifications'. Shundan keyin tuzatishni tikladim (commit 0bed2c3), vaqtinchalik o'zgarish commit'ga tushmadi. Qolgan 3 klassni tekshirdim: PushTokensMigrationTest (push_tokens) va NotificationPreferencesMigrationTest (notification_preferences) - bu ikki jadval hech qanday boshqa jadval tomonidan FK bilan ishora qilinmaydi (faqat users'ga FK beradi), shu sabab ularda naqsh xavfsiz, o'zgarish shart emas. NotificationOutboxMigrationTest allaqachon to'g'ri naqshni ishlatadi (TRUNCATE notification_outbox, notifications - S02 bargida shu tarzda yozilgan). 4 klass birga (mvn -o test -Dtest='NotificationsInboxMigrationTest,NotificationOutboxMigrationTest,PushTokensMigrationTest,NotificationPreferencesMigrationTest' -DfailIfNoTests=false): Tests run: 45, Failures: 0, Errors: 0 (Inbox 8, Outbox 12, PushTokens 10, Preferences 15). Commit 0bed2c3debd9962f3a10c81fc56232426b92ab69 - faqat 1 fayl (test), V50-V53 migratsiya SQL'lariga tegilmadi.

backend-1 statusni o'zgartirdi Ishlanyapti → Review

cleanTables TRUNCATE FK zanjiri tuzatildi (notification_outbox+notifications birga); to'rt migratsiya test klassi birga yashil

backend-1 statusni o'zgartirdi Tayyor → Ishlanyapti

Agent ishni boshladi

backend-1 ishga oldi

system statusni o'zgartirdi Ishlanyapti → Tayyor

Avtomatik bo'shatildi: 60 daqiqa signal yo'q

system bo'shatdi

Avtomatik bo'shatildi: 60 daqiqa signal yo'q

backend-1 yangiladi

Yangilandi: commit_sha

team-lead-pm statusni o'zgartirdi Bajarildi → Ishlanyapti

LEAD OLCHOVI QAYTARDI (2026-09-09 17:40): NotificationsInboxMigrationTest izolyatsiyada ham 8/8 ERROR — @BeforeEach cleanTables 'TRUNCATE TABLE notifications' CASCADE'siz, S02 ning V51 migratsiyasi notification_outbox -> notifications FK sini qoshgandan keyin ishlamaydi (PSQL: cannot truncate a table referenced in a foreign key constraint). Barg done deb yopilgan edi — S02 coderi S01 testlarini qayta yurgizmagan. Tuzatish + 4 klassni birga yashil qilish talab qilinadi.

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

qa-ep-13-t01-s01 izoh qoldirdi

QA (izolyatsiyalangan worktree, commit 99e1340): 4 mezon ham mustaqil tasdiqlandi. TEST: Tests run: 8, Failures: 0, Errors: 0 (NotificationsInboxMigrationTest; Testcontainers postgres:16; Flyway V1..V50 to'liq zanjir, 55 migratsiya). SPEC §2.2 maydonlari AYNAN solishtirildi (V50__notifications_inbox.sql:28-58): id uuid DEFAULT gen_random_uuid(); user_id bigint NOT NULL FK->users ON DELETE CASCADE; event_code varchar(64) NOT NULL, FK YO'Q; severity varchar(20) NOT NULL DEFAULT 'info' + CHECK (info|warning|security); title varchar(120) NOT NULL; body varchar(400) NOT NULL; entity_type varchar(40) NULL; entity_id varchar(64) NULL, FK YO'Q (polimorf); deep_link varchar(200) NULL; is_read boolean NOT NULL DEFAULT false; read_at timestamptz NULL; created_at timestamptz NOT NULL DEFAULT now(); PRIMARY KEY (id, created_at); PARTITION BY RANGE (created_at); idx (user_id, created_at DESC) + partial (user_id) WHERE is_read=false. V7__auth_logs naqshi va fk_<jadval>_<nom> konvensiyasi mos. 4 partition (joriy oy + 3 oy oldinga). MUTATSIYA: 4 mutant kiritildi, 4/4 USHLANDI: (a) severity CHECK olib tashlandi -> severityOutsideAllowedListIsRejectedByCheckConstraint FAILURE (:175) (b) ON DELETE CASCADE -> NO ACTION -> deletingUserCascadesNotificationRows ERROR (:207, fk_notifications_user violation) (c) partial "WHERE is_read = false" olib tashlandi -> unreadCountQueryUsesPartialIndex FAILURE (:303) (d) joriy oy va +1 oy bitta partition'ga birlashtirildi -> rowsInDifferentMonthsLandInDifferentPartitions... FAILURE (:148) 5532 bo'yicha maxsus shubha YOPILDI — test katalog-only EMAS. Test EXPLAIN chiqishini "(Index Only Scan|Index Scan) using (\S+) on" regexi bilan parse qiladi va usedIndexes.isNotEmpty() ni assert qiladi (test:287-295), keyin rejadan olingan HAR BIR indeks nomi uchun pg_indexes.indexdef da is_read partial shartini tekshiradi (:297-304). Mutant (c) da aynan shu assert yiqildi va xato matnida rejadan olingan real indeks nomi ko'rindi (notifications_2026_09_user_id_idx) — ya'ni reja haqiqatan o'qilyapti. SET LOCAL enable_seqscan=off ishlatilgan (kichik jadval), lekin mutant (c) isbotladi: partial shart yo'qolsa planner boshqa indeksni tanlaydi va test yiqiladi — diskriminatsiya real. FIXTURE XILMA-XILLIGI: severity uchala qiymat (info/warning/security) + rad etilgan 'urgent'; is_read aralash (2 ta false + 1 ta true); created_at ikki xil oy (oy chegarasidan keyin +9 soat); user_id mavjud + mavjud emas (999999999). CROSS-CUTTING: tenant_id/schema almashtirish yo'q (AR-1) OK; event_code va entity_id da FK ataylab yo'q — spec M2/§3 shuni talab qiladi, user_id ga esa haqiqiy FK bor; snake_case + ko'plik nom + to'liq FK nomi OK; numeric ustun yo'q (precision N/A); sir/token log'ga yozilmaydi; tashqi broker/kesh serveri ishlatilmagan (AR-4). @Transactional / outbox — bu barg faqat migratsiya, N/A. QAMROV BO'SHLIQLARI (mezon emas — bloklamaydi, keyingi barglar uchun eslatma): (1) hech bir assert ustun uzunligi/nullability/default ni tekshirmaydi — varchar(120)->varchar(400) mutanti tirik qolardi; (2) partition SONI (>=3 oy oldinga, technical_notes) assert qilinmagan, test faqat 2 oyni ishlatadi — T03-S04 partition job'i shu invariantni test bilan qamrasin; (3) idx_notifications_user_id_created_at mavjudligi assert qilinmagan. Asosiy ish daraxtiga tegilmadi: hamma ish /tmp/qa-EP-13-T01-S01 worktree'da, MUTANT qoldig'i yo'q (grep bo'sh), git status toza, worktree o'chirildi.

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

coder-ep-13-t01-s01 yangiladi

Yangilandi: branch, commit_sha

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

✓ O'qilmagan bo'yicha so'rov partial indeksdan foydalanadi (EXPLAIN bilan tasdiqlangan)

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

✓ `user_id` o'chirilganda qatorlar CASCADE bilan ketadi

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

✓ `severity` ga ro'yxatdan tashqari qiymat yozib bo'lmaydi

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

✓ Turli oydagi ikki qator turli partition'ga tushadi va `SELECT` ikkalasini ham qaytaradi

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

2 ta fayl qayd etildi

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

Agent ishni boshladi

coder-ep-13-t01-s01 ishga oldi

pm-agent yaratdi

`notifications` — in-app inbox (oylik RANGE partition)