Amortizatsiya — F5, catch-up va xarajat qatori

finalize-ep-12 yangiladi

Yangilandi: pr_url

pm-agent yangiladi

Yangilandi: estimate_hours

pm-agent yangiladi

Yangilandi: estimate_hours

team-lead-pm yangiladi

Yangilandi: estimate_hours

qa-ep-12-t04-s02 statusni o'zgartirdi Review → Bajarildi

qa-ep-12-t04-s02 izoh qoldirdi

QA qayta tekshiruv (eb8eaa1, izolyatsiyalangan worktree). AC4187 endi MUTATSIYADAN O'LDI. Mutant: FixedAssetDepreciationService.java:219 setPeriodId(periodId) -> accountingPeriodRepository.findByPeriodYearAndPeriodMonth(month).map(getId).orElse(periodId) (ya'ni yozuv oyining o'z davri, aks holda joriy davr). javap bilan bytecode tasdiqlandi: processAsset ichida findByPeriodYearAndPeriodMonth -> Optional.map -> Optional.orElse -> setPeriodId. Natija QIZIL: FixedAssetDepreciationServiceTest:237 expected 6L but was 5L (mart davri o'rniga fevral davri). Mutant cp .orig bilan tiklandi; git status toza, grep MUTANT src/ bo'sh, .orig qolmadi. Da'vo FARQLOVCHI: test:221 insertPeriod(2026,2) fevral davrini HAQIQATAN yaratadi (mutant uni id=5 deb topdi - eng kuchli dalil), test:237-238 ikkala da'vo ham bor: isEqualTo(marchPeriodId) VA isNotEqualTo(februaryPeriodId). Boshqa 3 mezon buzilmagan - baseline yashil: Tests run: 9, Failures: 0, Errors: 0 (ServiceTest 6/6, ControllerTest 3/3, mvn -o -Dtest=FixedAssetDepreciationServiceTest,FixedAssetDepreciationControllerTest test, BUILD SUCCESS). AC4185 = depreciatesFullMonthRegardlessOfAcquisitionDay (10-iyul -> iyul to'liq 8000000.00) + depreciatesDisposalMonthFullyThenStopsAfterwards (mart to'liq, aprelga yozuv yo'q). AC4186 = createsDepreciationAndExpenseEntryTogetherThenSkipsSilentlyOnSecondRun (expense_entries source_ref_id orqaga bog'lash, is_cash=false, 2-yurish 0 qator, count o'zgarmadi, accumulated ikkilanmadi). AC4188 = fullyDepreciatesOverUsefulLifeThenStopsAtCap (60 x 8000000.00, 61-oy yo'q, book_value=0) + lastMonthAbsorbsRoundingRemainder (yaxlitlash qoldig'i oxirgi oyda). 4/4 -> done.

qa-ep-12-t04-s02 qabul mezonini belgiladi

✓ Ikki oy o'tkazib yuborilgan aktivda catch-up 2 ta alohida qator yozadi va ikkalasining `period_id` si joriy davr bo'ladi

coder-ep-12-t04-s02 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-12-t04-s02 izoh qoldirdi

QA qaytargan AC4187 mutatsiya bo'shligi yopildi: catch-up testida fevral uchun ham accounting_periods qatori qo'shildi va februaryRow.period_id endi isEqualTo(marchPeriodId).isNotEqualTo(februaryPeriodId) bilan tasdiqlanadi. setPeriodId(periodId) ni "yozuv oyining o'z davri"ga almashtiruvchi mutant qo'lda kiritilib QIZIL ekani tasdiqlandi (expected 6L but was 5L), so'ng tiklandi. grep MUTANT bo'sh, .orig fayl yo'q. Kod (FixedAssetDepreciationService.java) o'zgarmadi. 9/9 test yashil (FixedAssetDepreciationServiceTest + FixedAssetDepreciationControllerTest).

coder-ep-12-t04-s02 yangiladi

Yangilandi: commit_sha

coder-ep-12-t04-s02 qabul mezonini belgiladi

✓ Ikki oy o'tkazib yuborilgan aktivda catch-up 2 ta alohida qator yozadi va ikkalasining `period_id` si joriy davr bo'ladi

coder-ep-12-t04-s02 fayllarni qayd etdi

1 ta fayl qayd etildi

coder-ep-12-t04-s02 ishga oldi

qa-ep-12-t04-s02 statusni o'zgartirdi Review → Ishlanyapti

qa-ep-12-t04-s02 izoh qoldirdi

QA (worktree 375f86ab, izolyatsiyalangan). Kod TO'G'RI, testlar yashil (6+3), ExpenseEntryService regressiyasi YO'Q (108 test: ExpenseEntry/ExpenseInvoice/FinanceIntegrity/FinanceExpense/FinanceProductionLoss/FinanceSupplierLedger/CashCount/FixedAssetService — hammasi 0 failure). Lekin AC4187 MUTATSIYA bilan qoplanmagan — qaytaraman. === AC4187 TIRIK MUTANT === Fayl: src/main/java/uz/erpbom/finance/service/FixedAssetDepreciationService.java:219 (`depreciation.setPeriodId(periodId)`). Mutant: period_id ni joriy davr o'rniga YOZUV OYINING o'z davri qilib qo'ydim (fallback bilan): setPeriodId(accountingPeriodRepository.findByPeriodYearAndPeriodMonth(month.getYear(), month.getMonthValue()).map(AccountingPeriod::getId).orElse(periodId)) Natija: FixedAssetDepreciationServiceTest 6/6 O'TDI va FixedAssetDepreciationControllerTest 3/3 O'TDI — mutant BUTUN 9 testdan tirik chiqdi. javap bilan tasdiqlandi (bytecode'da findByPeriodYearAndPeriodMonth chaqiruvi bor), ya'ni yolg'on xulosa emas. SABAB — FIXTURE TESHIGI: FixedAssetDepreciationServiceTest.java:215-217 da fevral ATAYLAB `accounting_periods` qatorisiz qoldirilgan. Shuning uchun `februaryRow.getPeriodId() == marchPeriodId` da'vosi FARQLOVCHI emas — noto'g'ri implementatsiya (period_id ni o'z oyi bo'yicha izlash — aynan eng ehtimolli xato) ham SHU qiymatni yozadi, chunki fevral davri mavjud emas. Xuddi shu teshik ControllerTest:128 (iyul davri yo'q) va fullyDepreciatesOverUsefulLifeThenStopsAtCap (faqat 2031-07 davri bor) da ham bor. TUZATISH (test, kod emas): catchesUpTwoSkippedMonthsWithCurrentClosingPeriodId da mart yurishidan OLDIN fevral uchun ham davr qatori yaratilsin, lekin runForPeriod U BILAN CHAQIRILMASIN: long februaryPeriodId = insertPeriod(2026, 2); // davr bor, lekin hech qachon yopilmagan long marchPeriodId = insertPeriod(2026, 3); ... runForPeriod(marchPeriodId, userId); assertThat(februaryRow.getPeriodId()).isEqualTo(marchPeriodId); assertThat(februaryRow.getPeriodId()).isNotEqualTo(februaryPeriodId); // <-- farqlovchi da'vo Shundan keyin yuqoridagi mutant YIQILADI. === O'LDIRILGAN MUTANTLAR (6/7) — bu mezonlar HAQIQATAN qoplangan === M1 salvage_value ayirilmadi -> lastMonthAbsorbsRoundingRemainder:291 yiqildi M3 idempotentlik existsBy olib tashlandi -> 2 test DataIntegrityViolation (uq_fixed_asset_depreciations_...) — idempotentlik DB unikal indeksiga ham tayanadi, faqat exists() ga emas: poyga xavfsiz M4 qoida 29 break olib tashlandi -> fullyDepreciates...:251 yiqildi (61-oyga yozuv tushdi) M5 linkSourceRef chaqirilmadi -> createsDepreciationAndExpenseEntry...:181 yiqildi (source_ref_id) M6 sold/written_off tekshiruvi olib tashlandi -> depreciatesDisposalMonthFully...:148 yiqildi M7 yaxlitlash qoldig'i qirqilmadi -> lastMonthAbsorbs...:294 yiqildi === TEKSHIRILGAN VA TOZA === - Fixture xilma-xilligi YAXSHI: 480000000/60/0, 1200000/12/0, 2400000/24/0, 1300000/6/salvage=300000 — salvage>0 va bo'linmaydigan baza qamralgan; summalar isEqualByComparingTo bilan (qism satr solishtiruvi yo'q). - Yaxlitlash: 5*166666.67 + 166666.65 = 1000000.00 AYNAN base ga teng (test:297). - Ikki bosqichli yozuv (expense_entries avval source_ref_id=null, keyin linkSourceRef) — runForPeriod @Transactional, linkSourceRef REQUIRED bilan qo'shiladi: yetim qator qolmaydi. `uq_expense_entries_source_type_source_ref_id_active` partial indeksi (WHERE source_ref_id IS NOT NULL) buzilmaydi — null bosqichi indeksga tushmaydi, har amortizatsiya id unikal. - ExpenseEntryService o'zgarishi SOF QO'SHIMCHA (yangi linkSourceRef + javadoc); record/reverse/expenseStructureByPeriod tegilmagan. - Kontrakt: FixedAssetDepreciationResponse ning 11 required maydoni ham DTO da bor, nom/tip mos; BigDecimal->String (JacksonConfig ToStringSerializer), sort period_year/period_month + default desc/desc, 403/404 test bilan. - Cross-cutting: @Transactional (list readOnly=true), tenant_id yo'q, FK to'liq nomdan, numeric(18,2), insert-only audit (fizik DELETE yo'q), log'da parol/token yo'q.

qa-ep-12-t04-s02 qabul mezonini belgiladi

✗ Ikki oy o'tkazib yuborilgan aktivda catch-up 2 ta alohida qator yozadi va ikkalasining `period_id` si joriy davr bo'ladi

qa-ep-12-t04-s02 qabul mezonini belgiladi

✓ F5 misolidagi 60 oylik jadval (8 000 000/oy) test bilan tasdiqlangan

qa-ep-12-t04-s02 qabul mezonini belgiladi

✓ Oy yopilganda amortizatsiya VA xarajat qatori tug'iladi; ikkinchi marta yopilsa takrorlanmaydi (08 AC10)

qa-ep-12-t04-s02 qabul mezonini belgiladi

✓ 10-iyulda olingan aktivga iyul oyi TO'LIQ yoziladi (ulush yo'q); sotilgan oy ham to'liq (08 AC16)

coder-ep-12-t04-s02 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-12-t04-s02 yangiladi

Yangilandi: branch, commit_sha

coder-ep-12-t04-s02 izoh qoldirdi

Keyingi task uchun uzatma (EP-12-T05/T06, davr yopilishi): amortizatsiya dvigateli mavjud, lekin REST/period.close orqali HALI ULANMAGAN. Chaqiruvchi klass·metod: uz.erpbom.finance.service.FixedAssetDepreciationService#runForPeriod(Long periodId, Long actingUserId) — @Transactional, davr yopilishini bajaruvchi kod (AccountingPeriodService#closeAccountingPeriod yoki uning muqobili) davr status closed bo'lishidan oldin (yoki bitta tranzaksiyada birga) shu metodni SHU periodId bilan chaqirishi kerak (Q32 = A, qoida 47). Metod barcha fixed_assets ni ko'rib chiqadi, yetishmagan oylarni catch-up bilan to'ldiradi, har yozuv bilan expense_entries (depreciation) qatorini birga yozadi va fixed_assets.accumulated_depreciation cache ini yangilaydi. Idempotent — bir xil periodId bilan qayta chaqirish xavfsiz (yangi qator yo'q). Rule/endpoint YO'Q — 7-bo'limda qo'lda ishga tushirish rule kodi ta'riflanmagan (T00 izohi p.3), shu sabab faqat servis metodi sifatida qoldirildi.

coder-ep-12-t04-s02 qabul mezonini belgiladi

✓ F5 misolidagi 60 oylik jadval (8 000 000/oy) test bilan tasdiqlangan

coder-ep-12-t04-s02 qabul mezonini belgiladi

✓ Ikki oy o'tkazib yuborilgan aktivda catch-up 2 ta alohida qator yozadi va ikkalasining `period_id` si joriy davr bo'ladi

coder-ep-12-t04-s02 qabul mezonini belgiladi

✓ Oy yopilganda amortizatsiya VA xarajat qatori tug'iladi; ikkinchi marta yopilsa takrorlanmaydi (08 AC10)

coder-ep-12-t04-s02 qabul mezonini belgiladi

✓ 10-iyulda olingan aktivga iyul oyi TO'LIQ yoziladi (ulush yo'q); sotilgan oy ham to'liq (08 AC16)

coder-ep-12-t04-s02 fayllarni qayd etdi

8 ta fayl qayd etildi

coder-ep-12-t04-s02 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-12-t04-s02 ishga oldi

contract-ep-12 izoh qoldirdi

EP-12-T00 (kontrakt) eslatmasi — QISMAN bo'shliq, blok EMAS: amortizatsiya kontraktda FAQAT asosiy yo'l orqali yuritiladi — POST /api/v1/accounting-periods/{id}/close (Q32 = A, §4.5 6-qadam; catch-up va idempotentlik shu yerda). Qoida 28/47 dagi "+ qo'lda hisoblash tugmasi" uchun §7 da rule YO'Q, shu sababli alohida endpoint YOZILMADI (rule to'qilmadi). Agar qo'lda tugma kerak bo'lsa — savol erp/ §5 sikliga: yangi rule (mas. fixed_asset.depreciate) kerakmi yoki period.close egasiga beriladimi? Barg asosiy qamrovda (yopish orqali amortizatsiya + expense_entries qatori) bloksiz bajariladi.

pm-agent yaratdi

Amortizatsiya — F5, catch-up va xarajat qatori