Tasdiqlash — accrual + `salary_monthly` xarajati (64a)

finalize-ep-12 yangiladi

Yangilandi: pr_url

pm-agent yangiladi

Yangilandi: estimate_hours

pm-agent yangiladi

Yangilandi: estimate_hours

qa-ep-12-t05-s03 statusni o'zgartirdi Review → Bajarildi

qa-ep-12-t05-s03 izoh qoldirdi

QA (izolyatsiyalangan worktree, df18d16). Baza: PayrollRunServiceTest — Tests run: 43, Failures: 0, Errors: 0. SPEC (Q65 = A) MUVOFIQLIGI — kod darajasida tasdiqlandi: - approve() sharti PayrollRunService.java:759 `line.getSalaryComponent().signum() > 0` (hodim TURI emas) — qoida 51/64a. - accrueLedgerWageAccrual :822 `line.getSalaryComponent().negate()` — ledger AYNAN -salary_component. - accrueExpenseSalaryMonthly :862 `line.getSalaryComponent()` — xarajat AYNAN salary_component. - salary_component = 0 -> accrueMonthlyLine umuman chaqirilmaydi (nol summali yozuv YO`Q, AC40). - piece_component hech qayerda accrual/xarajatga kirmaydi; accrued_amount faqat F7 to`lov hisobida qoladi. Kontrakt (openapi/v1/finance.yaml approvePayrollRun) matni kod bilan bir xil: shart, summa manbai, nol-yozuv taqiqi. AC39 (aralash hodim) ALOHIDA tasdiqlandi — approveAccrues...Ac39 testi: salary 2 380 952,38 / piece 125 000 -> xarajat 2 380 952,38, ledger -2 380 952,38, balans -2 380 952,38 (125 000 uchun payroll HECH NARSA yozmaydi), accrued_amount butun sikl davomida 2 505 952,38. Fixture`da salary_component != accrued_amount — almashtiruvchi mutant tirik qolmaydi. MUTATSIYA TEKSHIRUVI — 7/7 O`LDI (har biri kompilyatsiya bo`ldi, BUILD FAILURE = test yiqildi): - M1 xarajat getSalaryComponent->getAccruedAmount: 1 fail (AC39(a):1103) - M2 ledger getSalaryComponent->getAccruedAmount: 1 fail (AC39(b):1095) - M3 approve sharti > 0 -> >= 0: 3 fail (AC40 gate) - M4 approve sharti butunlay olib tashlandi: 3 fail - M5a `if (alreadyActive)` -> `if (!alreadyActive)`: 3 fail - M5b ledger idempotentligi signum() > 0 -> < 0: 2 fail - M6 returnToCalculated teskari yozuv chaqiruvi olib tashlandi: 2 fail (AC4663) FIXTURE XILMA-XILLIGI: salary_component 0 (AC40) va >0; piece_component 0 (legacy 4 000 000) va >0 (125 000 / 90 000); aralash hodim; approved->calculated->approved to`liq sikli (yozuv soni 1->2->3, reversalOfEntryId zanjiri) qamralgan. CROSS-CUTTING: approve/returnToCalculated @Transactional; tenant_id yo`q (AR-1); expense kategoriyasi FK (category_id) orqali; snake_case + ko`plik; salary_component numeric(18,2) NOT NULL DEFAULT 0 (V46) -> NPE yo`q; fizik DELETE yo`q — faqat teskari yozuv; token/parol log`ga chiqmaydi. EmployeeService BUZILMAGAN: commit faqat 2 faylga tegadi (PayrollRunService + test); EmployeeService.java o`zgarmagan, hasActiveMonthlyProfession EmployeeService.java:355 da QOLGAN va kompilyatsiya yashil. Kichik kuzatuv (defekt emas, bu barg doirasidan tashqari): Q65 dan keyin bu metodning main-kodda chaqiruvchisi qolmadi (PayrollRunService:115 da faqat javadoc matni) — kelajakda tozalash yoki boshqa chaqiruvchi paydo bo`lishi mumkin. Worktree tozalandi: grep -rn MUTANT src/ bo`sh, git diff df18d16 bo`sh, worktree o`chirildi. Asosiy ish daraxtiga tegilmadi.

qa-ep-12-t05-s03 qabul mezonini belgiladi

✓ Ikki marta tasdiqlashda yozuvlar takrorlanmaydi

qa-ep-12-t05-s03 qabul mezonini belgiladi

✓ Run qaytarilganda accrual va xarajat teskari yozuv bilan bekor qilinadi

qa-ep-12-t05-s03 qabul mezonini belgiladi

✓ Tasdiqda har oylikbay qatorga `salary_monthly` xarajat qatori tug'iladi; ishbay qatorlarda YO'Q (08 AC31)

coder-ep-12-t05-s03 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-12-t05-s03 yangiladi

Yangilandi: commit_sha

coder-ep-12-t05-s03 qabul mezonini belgiladi

✓ Ikki marta tasdiqlashda yozuvlar takrorlanmaydi

coder-ep-12-t05-s03 qabul mezonini belgiladi

✓ Run qaytarilganda accrual va xarajat teskari yozuv bilan bekor qilinadi

coder-ep-12-t05-s03 qabul mezonini belgiladi

✓ Tasdiqda har oylikbay qatorga `salary_monthly` xarajat qatori tug'iladi; ishbay qatorlarda YO'Q (08 AC31)

coder-ep-12-t05-s03 fayllarni qayd etdi

2 ta fayl qayd etildi

coder-ep-12-t05-s03 statusni o'zgartirdi Tayyor → Ishlanyapti

Agent ishni boshladi

coder-ep-12-t05-s03 ishga oldi

team-lead-pm statusni o'zgartirdi Bloklangan → Tayyor

Q65 = A javobi keldi — ikki komponentli qator; blok olib tashlandi.

team-lead-pm izoh qoldirdi

✅ JAVOB KELDI (2026-09-07, §5 sikli) — Q65 = A: 04 TO'G'RI, 08 ARALASH HODIMNI QO'LLAYDI. SPEC YANGILANDI. Qator endi IKKI KOMPONENTLI (§2.12a): 🆕 salary_component — F7 proratsiyasi (oylik_maosh × worked_days/working_days_total); maoshi yo'q hodimda 0 🆕 piece_component — Σ wage_entries.amount (04 §2.6, bonus bilan); ishbayi yo'q hodimda 0 accrued_amount — endi HOSILA: salary_component + piece_component 🔴 ENG MUHIM QOIDA (qoida 51/64a endi HODIM TURIGA emas, KOMPONENTGA bog'langan): · Ledger `wage_accrual` accrual'i = AYNAN `salary_component` · `salary_monthly` xarajat yozuvi = AYNAN `salary_component`, shart: `salary_component > 0` · `piece_component` ni payroll HECH QACHON accrual qilmaydi va xarajatga yozmaydi — uni 04/07 ish tasdiqlanganda va qoida 64b (picking) oqimi ALLAQACHON hisobga olgan · `accrued_amount` MAJBURIYAT/XARAJAT MANBAI EMAS — u faqat F7 to'lov hisobiga kiradi ⚠️ Lead tuzatishi: savol variantining matnida 'ledger majburiyati ikkalasining yig'indisi' deb yozilgan edi — bu qoida 51 bilan zid va aynan sen topgan ikki marta sanashni qaytarardi. Shuning uchun majburiyat ham `salary_component` ga bog'landi. Spec'da shunday yozilgan. Yangi qabul mezonlari (spec §12): AC39 (aralash hodim ikki marta sanalmaydi — 2 380 952,38 xarajat va accrual, 125 000 uchun payroll hech narsa yozmaydi, accrued_amount 2 505 952,38), AC40 (sof ishbayda nol summali yozuv ham YO'Q), AC41 (F7 ishorasi — Q64). 📌 DB: `payroll_run_lines` ga ikki ustun kerak. V46 shu BRANCHDA yangi (main'da yo'q) — joyida tahrirlash xavfsiz, checksum xavfi nol. Xohlasang yangi V ham yozishing mumkin. ⚠️ KONTRAKT HALI TUZATILMAGAN: (1) F7 formulasi matni (Q64), (2) `payroll_run_lines` sxemasiga ikki maydon (Q65). Lead ikkalasini T03 worker'i repo'ni bo'shatgach bitta tuzatishda yopadi. Sen kontraktga TEGMA. Barg `ready` ga qaytarildi.

team-lead-pm izoh qoldirdi

✅ LEAD DA'VONI MUSTAQIL TASDIQLADI (2026-09-07) — "oylikbay qator" ta'rifi ikki modulda ZID. O'lchov: - 04_employees.md 24-qator: "Bir hodim bir vaqtda IKKALASINI HAM olishi mumkin — oylik + ishbay QO'SHILADI". - 04_employees qoida 7 (463-qator): "Oylik + ishbay birga: hodim bir vaqtda oylik maosh (agar belgilangan) VA ...". - 08_finance qoida 64a / AC31 (2486-qator) esa xarajat yozuvini FAQAT "oylikbay" qatorga bog'laydi; §8.4 4-qadam (2210-qator): "approved → oylikbaylarga wage_accrual ledger yozuvi (ishbay TAKRORLANMAYDI — qoida 51)". Ya'ni 08 hodimni "oylikbay YOKI ishbay" deb modellashtiradi, 04 esa ikkalasini BIRGA ruxsat etadi. Worker probe'i oqibatni ko'rsatdi: aralash hodimda ishbay ikki marta (majburiyat + xarajat, qoida 51/46 buziladi); sof ishbay + maoshli hodimda maosh xarajatga umuman tushmaydi. 🔴 Foydalanuvchiga uzatildi. Javob kelmaguncha "oylikbay qator" ta'rifini O'ZINGDAN aniqlama.

qa-ep-12-t05-s03 statusni o'zgartirdi Review → Bloklangan

AC4662: "oylikbay qator" tarifi spec (qoida 64a/§4.4/F7) va 04_employees (qoida 6/7/8/9 — oylik+ishbay BIRGA) orasida yopilmagan. Probe: (A) hamma kasbi piece_rate + hodim darajasida maosh 3 000 000 -> approve dan keyin 0 ledger/0 expense (oylik maosh xarajatga umuman tushmaydi); (B) aralash hodim -> ledger -3 125 000 va expense 3 125 000, yani ishbay 125 000 ikki marta (qoida 51/46 buziladi). Javob kontrakt matniga ham tegadi (finance.yaml 4728-4738: amount = accrued_amount). Batafsil — oldingi izoh.

qa-ep-12-t05-s03 izoh qoldirdi

QA (qa-EP-12-T05-S03) — commit 247cc7f, izolyatsiyalangan worktree (/tmp/qa-EP-12-T05-S03, yakunda olib tashlandi). TESTLAR: PayrollRunServiceTest — Tests run: 32, Failures: 0, Errors: 0 (mvn, 45-52s). FinanceContractOperationCoverageTest — QIZIL (kutilgan), yetim ro'yxatida approve/return-to-calculated YO'Q (qolgani: pay=S04, accounting-periods, reconciliations, me/finance). Kontrakt maydon darajasida: PayrollRunReturnRequest(reason, @NotBlank, @Size(255)) = finance.yaml sxemasi; controller yo'llari + @RequirePermission("payroll.approve") = kontrakt/§7; 409 INVALID_STATUS_TRANSITION va PERIOD_CLOSED testlar bilan qoplangan. MUTATSIYA (har biri ALOHIDA, javap bilan bytecode tasdig'i bilan): O'LDI: M1 hasActiveMonthlyProfession->true (1 fail) · M2 ->false (2) · M3b alreadyActive=latest.isPresent() (1) · M4 ledger teskari yozuvini o'tkazib yuborish (1) · M5 expense teskari yozuvini o'tkazib yuborish (1) · M6 resolvePeriodEnd -> davr boshi (1) · M7 §4.4 holat qo'riqchisi (2) · M8 source_type='expense_invoices' (2). TIRIK M3a — PayrollRunService.java:757-760 (`alreadyActive`) + :729 (ledger `signum() > 0`) dedup'ini BUTUNLAY olib tashlash 32 testni yashil qoldiradi. Sabab: AC4664 amalda faqat §4.4 status guard bilan qo'riqlanadi (M7 o'ldiradi), bu ikki shoxobcha erishib bo'lmaydigan himoya qatlami. Nuqson emas, lekin "idempotent" da'vosi testsiz. TIRIK M6b — PayrollRunService.java:761 xarajat qatorining entry_date ini davr BOSHIga o'zgartirish HECH BIR testni yiqitmaydi, holbuki qoida 64a `entry_date` = davr oxiri deb talab qiladi (ledger tarafda assert bor, expense tarafda YO'Q). Blok yechilgach test qo'shilsin. 4(b) TESKARI YOZUV NAQSHI — TEKSHIRILDI, SPEC'GA MOS. Probe: 3 ta to'liq approve->return sikli -> ledger SUM=0.00, expense SUM=0.00, kontragent balansi 0.00 (har siklda; bekor qilingan run moliyaviy iz qoldirmaydi). Qator soni chiziqli (+2/+2 har sikl — insert-only jurnal, §2.2/qoida 2/10), unique kalit buzilmaydi: V38 qisman indeks (WHERE reversal_of_entry_id IS NULL) reversal qatorlarini chiqaradi, V42 faqat AKTIV qatorga qo'llanadi. E'tirof: qayta tasdiqda ledger qatori "reversal'ning reversal'i" bo'lgani uchun reversal_of_entry_id ORIGINAL'ga emas oxirgi qatorga ishora qiladi — V38 majburlagan, summa va audit izi to'g'ri. === BLOK SABABI — 4(a): "oylikbay qator" ta'rifi spec'da yopilmagan; ikkala talqin ham hozirgi kodda MOLIYAVIY XATO beradi (real DB probe bilan o'lchandi) === (A) "Alisher" holati (04_employees qoida 8/9: hamma kasbi piece_rate, LEKIN hodim darajasida oylik maosh bor; koderning O'Z fixture'i calculateAddsMonthlyAndPieceRateComponentsForMixedWageEmployee aynan shu shakl): maosh 3 000 000 (20/20 kun) + ishbay 125 000 -> accrued_amount = 3 125 000. approve dan keyin: ledger 0 qator, expense 0 qator, balans 0.00. Ya'ni 3 000 000 oylik maosh NA majburiyat sifatida tan olinadi, NA expense_entries ga tushadi -> qoida 64a/AC31 buziladi, F9 foydasi shu summaga oshib ketadi. Sabab: EmployeeService.java:337 mezoni (faol `monthly` KASB) bu hodimga false qaytaradi, PayrollRunService.java:666 esa shu mezon bilan butun qatorni o'tkazib yuboradi. (B) Aralash hodim (faol monthly kasb + shu davrda ishbay wage_entries): ledger = -3 125 000 (PayrollRunService.java:727), expense = 3 125 000 (:762). Qoida 51 va §4.4 izohi ("payroll-run FAQAT oylikbay proratsiyasini accrual qiladi") bo'yicha ledger -3 000 000 bo'lishi kerak edi -> 125 000 IKKINCHI marta majburiyat. Qoida 46 bo'yicha ishlab chiqarish ishbayi expense_entries ga umuman kirmaydi (COGS ichida), picking ishbayi esa qoida 64b bilan ALOHIDA picking_wage yozuvini oladi -> xarajatda ham 125 000 ikki marta. Bu koderning xatosi EMAS: qoida 64a va MUZLATILGAN kontrakt (openapi/v1/finance.yaml 4728-4738) aynan `amount = accrued_amount` deydi, §2.12a/F7 esa accrued_amount = oylik proratsiya + Σ wage_entries. Spec hodimni "oylikbay YOKI ishbay" deb modellashtiradi, 04_employees (qoida 6/7/8/9, Q2 Alisher, §6.2) esa ikkalasi BIRGA bo'lishini ochiq ruxsat etadi. Ya'ni bu holat spec'da qoplanmagan. PM ga 2 savol (08_finance §5 qoida 64a + §4.4 + kontrakt tavsifi BIRGA tuzatilishi kerak): 1) Qator qachon "oylikbay" sanaladi — (a) hodimda faol `monthly` kasb bor (hozirgi kod), (b) `worked_days` kiritilgan (§2.12a mezoni), yoki (c) F7 oylik komponenti > 0? (a) Alisherni tashlab yuboradi, (b)/(c) uni qamrab oladi. 2) Aralash qatorda wage_accrual va salary_monthly summasi — butun `accrued_amount` mi yoki FAQAT oylik komponentmi? Qoida 51 + 46 dan "faqat oylik komponent" chiqadi, lekin qoida 64a va muzlatilgan kontrakt matni `accrued_amount` deb yozilgan — javob kontraktni ham o'zgartiradi. Mezonlar: AC4663 ✓ (teskari yozuv — kod + probe bilan), AC4664 ✓ (status guard + sikl testi), AC4662 ✗ -> is_met=false (yuqoridagi (A)/(B)).

qa-ep-12-t05-s03 qabul mezonini belgiladi

✗ Tasdiqda har oylikbay qatorga `salary_monthly` xarajat qatori tug'iladi; ishbay qatorlarda YO'Q (08 AC31)

qa-ep-12-t05-s03 qabul mezonini belgiladi

✓ Ikki marta tasdiqlashda yozuvlar takrorlanmaydi

qa-ep-12-t05-s03 qabul mezonini belgiladi

✓ Run qaytarilganda accrual va xarajat teskari yozuv bilan bekor qilinadi

coder-ep-12-t05-s03 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-12-t05-s03 izoh qoldirdi

approve/return-to-calculated qoshildi (PayrollRunService/Controller). Oylikbay mezoni worked_days EMAS - EmployeeService#hasActiveMonthlyProfession (professions.wage_type=monthly, ADR-001 sec2.3 servis orqali; EmployeeProfessionRepository+1 metod). Ledger tarafda expense_entriesdagi reversed_by_entry_id yoq (V38) - approve->return->approve siklida LedgerEntryService#reverse ENG SONGGI qatorga qollaniladi (reversalning reversali), expense tarafda esa record() qayta chaqiriladi (3-qator naqshi). Test: PayrollRunServiceTest (32/32 yashil, 9 tasi yangi) - AC4662/4663/4664 uchtasi ham bitta uzluksiz sikl testida (mixed oylikbay+ishbay). Mutant isboti: approve() dagi hasActiveMonthlyProfession shartini if(true)ga almashtirdim - ishbay qatorga ham yozuv tushib test qizardi (2ta assertion), tikladim, grep MUTANT boш. FinanceContractOperationCoverageTest hali QIZIL (NORMAL) - approve/return-to-calculated ROYXATDAN CHIQDI, qolgan 15ta (pay, accounting-periods, reconciliations, me/finance) boshqa barglar qamrovi.

coder-ep-12-t05-s03 qabul mezonini belgiladi

✓ Ikki marta tasdiqlashda yozuvlar takrorlanmaydi

coder-ep-12-t05-s03 qabul mezonini belgiladi

✓ Run qaytarilganda accrual va xarajat teskari yozuv bilan bekor qilinadi

coder-ep-12-t05-s03 qabul mezonini belgiladi

✓ Tasdiqda har oylikbay qatorga `salary_monthly` xarajat qatori tug'iladi; ishbay qatorlarda YO'Q (08 AC31)

coder-ep-12-t05-s03 yangiladi

Yangilandi: branch, commit_sha

coder-ep-12-t05-s03 fayllarni qayd etdi

8 ta fayl qayd etildi

coder-ep-12-t05-s03 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-12-t05-s03 ishga oldi

team-lead-pm yangiladi

Yangilandi: estimate_hours

pm-agent yaratdi

Tasdiqlash — accrual + `salary_monthly` xarajati (64a)