V27 — `wage_entries.work_id` -> `works` haqiqiy FK

finalize-ep-07 yangiladi

Yangilandi: pr_url

unknown-agent statusni o'zgartirdi Review → Bajarildi

unknown-agent izoh qoldirdi

[lead] Regressiya yopildi — commit 55e076d. Lead MUSTAQIL o'lchovi (coder hisobotiga tayanmasdan, HEAD 55e076d): 1) `mvn -Dtest='uz.erpbom.employees.**'` -> run=254, failures=0, errors=0, exit 0 (ilgari 6 klass qizil, 22 xato). 2) `mvn -Dtest='uz.erpbom.tasks.**'` -> run=214, failures=0, errors=0, exit 0 (regressiya yo'q). 3) Qamrov kamaymagani tekshirildi: commit diff'ida `@Disabled`/`@Ignore`/`assertTrue(true)`/`assumeTrue` YO'Q; 546 qo'shildi / 65 o'chirildi. O'chirilganlar aynan sun'iy `work_id` literallari (1001L, 2001L, 910_001L...) — ular haqiqiy `production_run->task->work` zanjiri bilan almashtirilgan. 4) Yagona o'chirilgan assertion — `workIdColumnHasNoForeignKeyConstraint` ("wage_entries.work_id da FK BO'LMASLIGI kerak (07_tasks epicida qo'shiladi)"). Bu V27 dan keyin ta'rifan yolg'on; o'rniga ijobiy assertion (`...HasForeignKeyToWorksSinceV27`) qo'yilgan. Yumshatish emas, tuzatish. Yopish asosi: 3/3 mezon + yuqoridagi o'lchovlar. Eslatma — S04 ning birinchi QA verdikti employees to'plamini yurgizmagani uchun regressiya o'tib ketgan edi; kelgusida FK/migratsiya bargida bog'liq modul to'plami majburiy yurgizilsin.

backend-1 izoh qoldirdi

Regressiya tuzatildi: V27 fk_wage_entries_work fixture regressiyasi. 6 test faylida (WageEntriesMigrationTest, WageAccrualServiceTest, WageAccrualPortTest, PayrollControllerIntegrationTest, EmployeePayrollSelfControllerIntegrationTest, EmployeeProfessionServiceTest) barcha wage_entries fixturelari endi haqiqiy production_run->task->work (yoki picking task) zanjiri orqali real works.id ishlatadi. Bitta eskirgan assertion tuzatildi (workIdColumnHasNoForeignKeyConstraint -> workIdColumnHasForeignKeyToWorksSinceV27, AC2825 V27 bilan supersede bo'ldi). WageAccrualPort javodocidagi notogri AC2900 izohi (confirmed_qty=0 da work confirmed bolishi mumkin) togrilandi -> rejected/terminal brak (07_tasks R22-c/F7); xatti-harakat ozgarmadi, faqat matn. Natija: uz.erpbom.employees.** 252/252 yashil (0 failure/0 error), uz.erpbom.tasks.** 213/213 yashil (0 failure/0 error). Commit: 55e076d.

backend-1 statusni o'zgartirdi Ishlanyapti → Review

unknown-agent yangiladi

Yangilandi: commit_sha

unknown-agent statusni o'zgartirdi Bajarildi → Ishlanyapti

unknown-agent izoh qoldirdi

[lead] REOPEN — S04 regressiya qoldirgan. V27 (4c59cf1) `fk_wage_entries_work` FK sini qo'shgan (spec bo'yicha TO'G'RI), lekin 04_employees ning mavjud test fixture'lari `works` da yo'q `work_id` qiymatlarini (8101, 9201, 9401...) kiritadi -> FK violation. Lead mustaqil o'lchovi (HEAD b4f044f, `mvn -Dtest='uz.erpbom.employees.**'`): 6 test klassi qizil, jami 22 xato — WageAccrualServiceTest (8), WageAccrualPortTest (3), WageEntriesMigrationTest (1F+3E), PayrollControllerIntegrationTest (4), EmployeePayrollSelfControllerIntegrationTest (2), EmployeeProfessionServiceTest (1). Kod nuqsoni EMAS — fixture qarzi: har bir fixture wage_entry yaratishdan oldin haqiqiy `works` qatorini yaratishi (yoki work_id=NULL qoldirishi, agar ustun nullable bo'lsa) kerak. S04 QA verdikti employees to'plamini yurgizmagani uchun o'tib ketgan. S04 `done` -> `ready` ga qaytarildi; tuzatilib QA'dan o'tgach yopiladi.

qa-ep-07-t01-s04 statusni o'zgartirdi Ishlanyapti → Bajarildi

qa-ep-07-t01-s04 izoh qoldirdi

QA (qa-EP-07-T01-S04) — mustaqil tekshiruv, oldingi is_met belgilariga tayanilmadi. Test: mvn -Dtest=WageEntriesWorkFkMigrationTest test -> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 (38.79 s). 3181 — V27:44 `ALTER TABLE wage_entries ADD CONSTRAINT fk_wage_entries_work FOREIGN KEY (work_id) REFERENCES works (id)`, ON DELETE klauzulasi YO'Q. Test katalog darajasida tekshiradi (pg_constraint: conname + confrelid::regclass = 'works' + confdeltype in ('a','r')), shunchaki insert urinishi bilan emas. Qo'shimcha: DELETE FROM works bog'liq wage_entries borida 23503 bilan rad etiladi (RESTRICT xatti-harakati isbotlangan). 3182 — uq_wage_entries_work_id (V23:70) V27 dan keyin ham bor: test pg_indexes.indexdef ni o'qib CREATE UNIQUE INDEX + (work_id) ni tasdiqlaydi, ayni paytda dublikat work_id insert'i rad etilishi ham tekshiriladi. V28/V29 bu FK/indeksga tegmaydi (grep bilan tasdiqlandi). 3183 — uch shoxobcha ham avtomatlashtirilgan: (a) bo'sh wage_entries — to'liq zanjir flyway_schema_history.success; (b) yetim work_id — alohida schema'da mustaqil Flyway V26 gacha, qator qo'yiladi, keyin V27; (c) ma'lumot bor schema — V27 o'tadi va qator saqlanadi. Oldingi QA e'tirozi ('avtomatlashtirib bo'lmaydi' javadoc) yopilgan. MUTATSIYA SINOVI (V27 SQL ataylab buzilib, target/classes da buzilish borligi tasdiqlanib, keyin git checkout bilan tiklandi): - A) DO $$ ... RAISE EXCEPTION ... END $$; bloki olib tashlandi -> migrationRejectsOrphanWorkIdWithExactValueInMessage YIQILDI: expected P0001 but was 23503. Ya'ni SQLSTATE assert'i aynan oldingi yolg'on-yashil holatni ushlaydi (xabardagi yetim qiymat PG ning o'z 23503 matnida ham bor, shu sabab faqat qiymat tekshiruvi yetarli emas edi). - B) FK nomi fk_wage_entries_work_MUTANT ga o'zgartirildi + uq_wage_entries_work_id tushirildi -> 3 ta test YIQILDI: fkWorkIdReferencesWorksTableWithoutCascade, uniqueWorkIdIndexStillExists, duplicateWorkIdIsStillRejectedByUniqueConstraint. Survived test yo'q. Tiklashdan keyin qayta yurgizildi — 9/9 yashil, git status toza. Cross-cutting: tenant_id ustuni qo'shilmagan (AR-1) · haqiqiy FK, 'varchar kod + ilova nazorati' emas (AR-10) · snake_case, jadval ko'plikda · V27 API yuzasiga tegmaydi, openapi/ ga tegilmadi. Kichik kuzatuv (bloklamaydi, tuzatish talab qilinmaydi): (1) confdeltype in ('a','r') — 'a' (NNO ACTION, klauzulasiz) va 'r' (aniq ON DELETE RESTRICT) ikkalasini ham qabul qiladi; joriy SQL da klauzula yo'q, semantik farq faqat deferred constraint'da, CASCADE/SET NULL rad etiladi. (2) wageEntryWithUnknownWorkIdIsRejected dagi hasMessageContaining('fk_wage_entries_work') prefiks bo'lgani uchun B mutatsiyasida yiqilmadi — aniq nom tekshiruvi pg_constraint testida qamrab olingan. Verdikt: done.

qa-ep-07-t01-s04 qabul mezonini belgiladi

✓ Migratsiya bo'sh `wage_entries` da ham, ma'lumot bor bazada ham o'tadi (yetim qator bo'lsa migratsiya aniq xabar bilan yiqiladi)

qa-ep-07-t01-s04 qabul mezonini belgiladi

✓ Mavjud `UNIQUE(work_id)` indeksi o'zgarmaydi va tushirilmaydi

qa-ep-07-t01-s04 qabul mezonini belgiladi

✓ `fk_wage_entries_work` FOREIGN KEY (`work_id`) REFERENCES `works` (`id`) — ON DELETE klauzulasiz (RESTRICT)

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

Regressiya qayta ochildi — V27 FK ikki mavjud testni yiqitdi; fixture tuzatilishi kerak (izohga qara).

team-lead-pm izoh qoldirdi

🔴 QAYTA OCHILDI (team-lead-pm, 2026-08-25) — regressiya, EP-07 yakunlanishidan OLDIN yopilishi shart. TOPILMA (EP-07-T03 worker'i aniqladi): `feat/EP-07-erpbom-backend` branch'ida ikkita BEGONA test qizil — `EmployeeProfessionServiceTest#unassigningProfession...` va `WageAccrualServiceTest` — sabab `fk_wage_entries_work` buzilishi. TASHXIS (lead tekshirdi): V27 (shu barg) `wage_entries.work_id -> works` HAQIQIY FK qo'shadi. Migratsiya spec'ga MOS (07_tasks #3: works 1-1 wage_entries, UNIQUE FK) va tuzatilmasligi kerak. Muammo — 04_employees modulining mavjud testlari: ular `wage_entries` qatorini `works` da mavjud bo'lmagan `work_id` bilan yaratadi (V23 vaqtida FK yo'q edi, shuning uchun ishlardi). BAJARILISHI KERAK: o'sha ikki testning fixture'ini tuzat — avval haqiqiy `works` qatori yaratilsin, keyin `wage_entries`. Migratsiyaga yoki FK ta'rifiga TEGILMASIN. Boshqa modul testi bo'lgani uchun minimal, faqat fixture darajasidagi o'zgarish. Qamrov: bu EP-07 kiritgan regressiya, shuning uchun EP-07 ichida yopiladi (Faza D dan oldin).

qa-ep-07-t01-s04 statusni o'zgartirdi Review → Bajarildi

qa-ep-07-t01-s04 izoh qoldirdi

QA 2-o'tish (mustaqil qayta tekshiruv). Baseline 9/9 yashil (avval 7). 3183 teshigi YOPILDI — uchala mutatsiya O'LDIRILDI: (a) V27:20-37 DO $$ yetim blokini BUTUNLAY o'chirish -> migrationRejectsOrphanWorkIdWithExactValueInMessage YIQILDI (SQLSTATE kutilgan P0001, olingan 23503). Bu o'tgan safar omon qolgan mutatsiya edi. (b) RAISE EXCEPTION xabaridan yetim work_id ro'yxatini (%, orphan_ids) olib tashlash -> o'sha test YIQILDI: xabar "777777" ni o'z ichiga olmadi. Demak test faqat "exception tashlandi" emas, xato MATNINI tekshiradi. (c) FK ga ON DELETE CASCADE qo'shish -> 2 test YIQILDI (fkWorkIdReferencesWorksTableWithoutCascade: confdeltype=c; deletingWorkReferencedByWageEntryIsRejectedByRestrict). Har mutatsiyadan keyin SQL git checkout bilan tiklandi; git diff 4c59cf1 -- V27__wage_entries_work_fk.sql BO'SH (migratsiya o'zgarmagan, faqat test fayli). 3183 ikkala yarmi qoplangan: (i) yetim -> target("26") schema harnessi bilan aniq xabar; (ii) to'ldirilgan schema -> V27 o'tadi va qator saqlanadi (migrationSucceedsAndPreservesRowsOnPopulatedSchema). work_id IS NULL yarmi qo'llanilmaydi — V23:46 da work_id bigint NOT NULL. 3181/3182 regressiyasiz (4+2 test yashil). Javadoc'dagi eski "avtomatlashtirib bo'lmaydi" izohi olib tashlangan.

qa-ep-07-t01-s04 qabul mezonini belgiladi

✓ Migratsiya bo'sh `wage_entries` da ham, ma'lumot bor bazada ham o'tadi (yetim qator bo'lsa migratsiya aniq xabar bilan yiqiladi)

coder-ep-07-t01-s04 yangiladi

Yangilandi: commit_sha

coder-ep-07-t01-s04 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-07-t01-s04 statusni o'zgartirdi Tayyor → Ishlanyapti

coder-ep-07-t01-s04 qabul mezonini belgiladi

✓ Migratsiya bo'sh `wage_entries` da ham, ma'lumot bor bazada ham o'tadi (yetim qator bo'lsa migratsiya aniq xabar bilan yiqiladi)

coder-ep-07-t01-s04 fayllarni qayd etdi

1 ta fayl qayd etildi

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

qa-ep-07-t01-s04 statusni o'zgartirdi Review → Ishlanyapti

qa-ep-07-t01-s04 izoh qoldirdi

QA (qa-EP-07-T01-S04) — V27 tekshiruvi. Migratsiyaning O'ZI to'g'ri, ammo 3183 mezoni TESTDA umuman qamralmagan -> qaytarilyapti. [OK] 3181 — jonli PG16 bazada MUSTAQIL tasdiqlandi (V1..V26 qo'lda qo'llab, keyin V27): pg_constraint fk_wage_entries_work, conrelid=wage_entries(work_id) -> confrelid=works(id), confdeltype='a' (NO ACTION, 'c'/CASCADE EMAS), confupdtype='a', convalidated=t. [OK] 3182 — uq_wage_entries_work_id V23 dagi ta'rifidek turibdi: pg_constraint contype='u', pg_get_constraintdef = 'UNIQUE (work_id)'; pg_indexes = 'CREATE UNIQUE INDEX uq_wage_entries_work_id ON public.wage_entries USING btree (work_id)'. Nomi ham, ustuni ham o'zgarmagan, tushirilmagan. MUTATSIYA TEKSHIRUVI (baseline: 7/7 yashil, mvn exit 0): (a) FK ga ON DELETE CASCADE qo'shildi -> O'LDIRILDI. 2 failure: fkWorkIdReferencesWorksTableWithoutCascade (WageEntriesWorkFkMigrationTest.java:106), deletingWorkReferencedByWageEntryIsRejectedByRestrict (:158). (c) constraint nomi fk_we_work_mutated ga o'zgartirildi -> O'LDIRILDI. 2 failure: :98 va wageEntryWithUnknownWorkIdIsRejected (:124). (b) V27__wage_entries_work_fk.sql:20-38 dagi DO $$ ... RAISE EXCEPTION yetim tekshiruv bloki BUTUNLAY o'chirildi -> **OMON QOLDI**: mvn exit 0, 7/7 test yashil. Har uch mutatsiyadan keyin fayl `git checkout --` bilan tiklandi; `git diff 4c59cf1 -- V27...sql` BO'SH (bayt-ma-bayt bir xil). [X] 3183 — QAMROV DEFEKTI. Yetim blokni o'chirsa ham birorta test yiqilmaydi, ya'ni mezonning "yetim qator bo'lsa aniq xabar bilan yiqiladi" qismi himoyalanmagan. Buni WageEntriesWorkFkMigrationTest.java:39-42 javadoc'ining o'zi tan oladi: "bu holat alohida qo'lda sinab ko'rilgan, chunki toza Testcontainers bazasida yetim qator hosil qilib bo'lmaydi". Bu ASOS NOTO'G'RI — men buni amalda bajardim: toza PG16 ga V1..V26 qo'llab, wage_entries ga yetim qatorlar (work_id=777777, 888888) qo'yib V27 ni yurgizdim, migratsiya kutilgan xabar bilan yiqildi: ERROR: V27: wage_entries.work_id da works jadvalida mavjud bo'lmagan qiymat(lar) topildi: 777777, 888888. FK qo'shishdan oldin bu yetim wage_entries qatorlarini tuzating. Demak xatti-harakat to'g'ri, faqat REGRESSIYA TESTI yo'q. BAJARILISHI KERAK: 1. Flyway'ni V26 da to'xtatadigan test harnessi qo'sh (Flyway.configure()...target("26").load().migrate(), yoki spring.flyway.target=26 bilan alohida test klassi). So'ng yetim wage_entries qatori INSERT qil (work_id = works da yo'q qiymat), so'ng target("27") bilan migrate qil -> FlywayException KUTILSIN va xato matni yetim work_id QIYMATINI o'z ichiga olishi assert qilinsin (faqat SQLSTATE 23503 yoki "constraint violated" YETARLI EMAS — mezon "aniq xabar" deydi). 2. Shu harnessda 3183 ning ikkinchi yarmi ham yopilsin: MA'LUMOT BOR bazada (haqiqiy works ga ishora qilgan wage_entries qatori mavjud holatda) V27 muvaffaqiyatli o'tishi. Hozirgi 7 testning HAMMASI V27 allaqachon BO'SH wage_entries ustida qo'llangan bazada ishlaydi — "ma'lumot bor bazada ham o'tadi" hech qayerda tekshirilmagan. 3. Yangi test qo'shilgach, (b) mutatsiyasini qayta yurgizib O'LDIRILGANINI tasdiqla. TUZATISH SHART EMAS (tasdiq uchun): `work_id IS NOT NULL` filtri to'g'ri — NOT NULL ni tushirib NULL work_id qatori qo'yilgan bazada V27 muvaffaqiyatli o'tdi, NULL yetim deb hisoblanmadi. V27 SQL fayliga o'zgartirish KIRITILMADI (QA kod tuzatmaydi).

qa-ep-07-t01-s04 qabul mezonini belgiladi

✗ Migratsiya bo'sh `wage_entries` da ham, ma'lumot bor bazada ham o'tadi (yetim qator bo'lsa migratsiya aniq xabar bilan yiqiladi)

qa-ep-07-t01-s04 qabul mezonini belgiladi

✓ Mavjud `UNIQUE(work_id)` indeksi o'zgarmaydi va tushirilmaydi

qa-ep-07-t01-s04 qabul mezonini belgiladi

✓ `fk_wage_entries_work` FOREIGN KEY (`work_id`) REFERENCES `works` (`id`) — ON DELETE klauzulasiz (RESTRICT)

coder-ep-07-t01-s04 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-07-t01-s04 yangiladi

Yangilandi: branch, commit_sha

coder-ep-07-t01-s04 qabul mezonini belgiladi

✓ Migratsiya bo'sh `wage_entries` da ham, ma'lumot bor bazada ham o'tadi (yetim qator bo'lsa migratsiya aniq xabar bilan yiqiladi)

coder-ep-07-t01-s04 qabul mezonini belgiladi

✓ Mavjud `UNIQUE(work_id)` indeksi o'zgarmaydi va tushirilmaydi

coder-ep-07-t01-s04 qabul mezonini belgiladi

✓ `fk_wage_entries_work` FOREIGN KEY (`work_id`) REFERENCES `works` (`id`) — ON DELETE klauzulasiz (RESTRICT)

coder-ep-07-t01-s04 fayllarni qayd etdi

2 ta fayl qayd etildi

coder-ep-07-t01-s04 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-07-t01-s04 ishga oldi

pm-agent yaratdi

V27 — `wage_entries.work_id` -> `works` haqiqiy FK