Xarajat reyestri va F9 xarajat tuzilmasi hisoboti

finalize-ep-12 izoh qoldirdi

Drift topilmasi yopildi va QAYTA O'LCHOV bilan tasdiqlandi: kontrakt chegarasi endi generatsiya qilingan hujjatda ko'rinadi, topilma o'lchovda umuman yo'q (0 ta uchrash) va baseline'ga OLINMADI. Nazorat sinovi: chegara generatsiya qilingan hujjatdan sun'iy olib tashlanganda gate o'sha izni QAYTA topdi (weaker 52 -> 56) — ya'ni yo'qolishi haqiqiy tuzatish, ko'r nuqta emas. PR #14.

finalize-ep-12 statusni o'zgartirdi Review → Bajarildi

finalize-ep-12 yangiladi

Yangilandi: commit_sha, pr_url

backend-agent statusni o'zgartirdi Ishlanyapti → Review

backend-agent izoh qoldirdi

TESKARI TEKSHIRUV: @Size vaqtincha olib tashlanganda listRejectsSearchTermLongerThanHundredCharacters yiqildi (expected 400, but was 200 OK) — yani test haqiqatan tuzatishni olchaydi. Tiklangach 21/21 yashil. openapi/ ga TEGILMADI.

backend-agent izoh qoldirdi

Test: ExpenseInvoiceReversalControllerIntegrationTest ga chegara IKKI TOMONDAN qoshildi (100 belgi -> 200, 101 belgi -> 400 VALIDATION_ERROR, field=q). Yangi @SpringBootTest klassi ochilmadi: /expense-invoices uchun HTTP darajasidagi yagona test shu sinf. Natija 21/21 yashil.

backend-agent izoh qoldirdi

@Validated majburiy ekani teskari tekshiruvda tasdiqlandi: usiz Spring 6.2 ning ornatilgan tekshiruvi HandlerMethodValidationException koataradi, GlobalExceptionHandler uni tutmaydi -> javob 400 emas, 500 boladi.

backend-agent izoh qoldirdi

Drift tuzatishi: GET /expense-invoices query q — kontrakt maxLength=100, kodda cheklov yoq edi (101 belgi 200 qaytargan). ExpenseInvoiceController sinfiga @Validated + parametrga @Size(max=100) qoshildi (ExchangeRateController/SupplierContractController naqshi). Commit e0eba4c.

backend-agent izoh qoldirdi

sinov

backend-agent yangiladi

Yangilandi: commit_sha

backend-agent fayllarni qayd etdi

2 ta fayl qayd etildi

backend-agent statusni o'zgartirdi Bloklangan → Ishlanyapti

finalize-ep-12 statusni o'zgartirdi Ishlanyapti → Bloklangan

OpenAPI drift (kod kontraktdan ZAIFROQ): GET /api/v1/expense-invoices query param `q` — kontraktda maxLength=100, kodda cheklov YO`Q (ExpenseInvoiceController.java:91 — @Size yo`q, servis qatlamida ham tekshirilmaydi). Tuzatish KODDA: `@Size(max=100)`. Kontrakt tegilmaydi.

finalize-ep-12 statusni o'zgartirdi Bajarildi → Ishlanyapti

Drift gate (openapi-diff v1/finance) qizil — yakunlash tekshiruvi qaytardi.

pm-agent yangiladi

Yangilandi: estimate_hours

pm-agent yangiladi

Yangilandi: estimate_hours

team-lead-pm yangiladi

Yangilandi: estimate_hours

qa-ep-12-t02-s04 statusni o'zgartirdi Review → Bajarildi

qa-ep-12-t02-s04 izoh qoldirdi

QA 2-yurish (worktree /tmp/qa-EP-12-T02-S04-r2, HEAD 0c0351d) — uchala qaytarish topilmasi MUTATSIYA bilan ISBOTLANDI. Bazaviy (mutantsiz): Tests run: 13, Failures: 0, Errors: 0 (ExpenseInvoiceListServiceTest 6 + ExpenseEntryQueryServiceTest 7). MUTANT-A (AC4174) — F9 total ga draft hujjat summasi qoshildi (ExpenseInvoiceRepository draft-sum + ExpenseEntryQueryService.getStructure). OLDI: getStructureExcludesNonZeroDraftInvoiceTotalFromTotalAmount:250 — expected: 120000.00 / but was: 870000.00. Farq aynan 750000.00 = draft hujjatning total_amount i, yani fixture endi NOLDAN FARQLI (1-yurishdagi degenerat lines=null / total_amount=0.00 tuzatilgan) — mezon endi vacuous EMAS. MUTANT-B (AC4175, yaratuvchi kesimi) — ExpenseInvoiceService.java:256 effectiveCreatedByUserId = null. OLDI: listWithFinanceViewFiltersByCreatedByUserId:279. Test HAQIQATAN ikki xil yaratuvchi bilan ishlaydi va containsExactly(creatorOneInvoice.id()) qiladi — nomos yaratuvchining hujjati natijada YOQligi assert qilinadi ("bosh emas" tipidagi assert emas). expense.create egalik shoxobchasi alohida test bilan qoplangan, mutant unga tasir qilmadi — kutilganidek. MUTANT-C (doira boshligi) — ExpenseEntryQueryService.list dan yangi qoshilgan scopeFor node-scoping olib tashlandi. OLDI: listWithOrgNodeScopedFinanceViewHidesOtherOrganizationRows:200. Ijro shakli TOGRI: doira FILTRLASH bilan qollangan (403 tashlanmaydi) — kontrakt listExpenseEntries buzilmagan. MUTANT-D (regressiya tekshiruvi, AC4173) — ExpenseInvoiceService.java:268 scopeOrganizationIds = null. OLDI: listWithOrgNodeScopedFinanceViewShowsOnlyOwnOrganization:132 — 1-yurish natijasi regressiyaga uchramagan. Qolgan AC4175 kesimlari (holat/tur/davr/tasdiqlovchi) listFiltersByStatusCategoryPeriodAndApprover da yashil. Ruxsat kodi: grep -rn "expense.view_all" src/main/ — BOSH (faqat FinancePermissionCatalogTest FORBIDDEN_CODES manfiy royxatida). Spec muvofiqligi: 08_finance §4.7 (draft -> Xarajat jurnali: yoq) va §11 (F9 yagona manba expense_entries) — kod aynan shunday; draft qatori expense_entries ga umuman yozilmaydi. Cross-cutting: list() @Transactional(readOnly=true); getStructure @Transactional (deny paytida auth_logs yozuvi sabab readOnly emas — asosli); tenant_id yoq; fizik DELETE yoq; log/audit da token yoq. Tozalik: grep -rn MUTANT src/ BOSH; git grep MUTANT HEAD BOSH; worktree ochirildi (git worktree list da yoq); asosiy daraxtga bir harf ham tegilmadi (EP-12-T02-S03 coder ishi buzilmagan). FinanceContractOperationCoverageTest yurgizilmadi va @Disabled qilinmadi — S03 operatsiyalari sabab kutilgan qizil.

qa-ep-12-t02-s04 qabul mezonini belgiladi

✓ Reyestr beshala kesim bo'yicha filtrlanadi

qa-ep-12-t02-s04 qabul mezonini belgiladi

✓ `draft` hujjatlar xarajat tuzilmasi summasiga kirmaydi

coder-ep-12-t02-s04 yangiladi

Yangilandi: commit_sha

coder-ep-12-t02-s04 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-12-t02-s04 statusni o'zgartirdi Tayyor → Ishlanyapti

coder-ep-12-t02-s04 izoh qoldirdi

QA qaytarishi tuzatildi. (1) AC4174 vacuous — ExpenseEntryQueryServiceTest draft fixture endi HAQIQIY qator bilan (750000.00, lines orqali) + mustaqil confirmed baseline (120000.00) bir davrda; assert = faqat 120000.00. Mutant (total += draft summasi) qo'yib tekshirildi — YIQILDI (870000.00 vs 120000.00), tiklandi, MUTANT qatori yo'q. (2) AC4175 yaratuvchi kesimi — ExpenseInvoiceListServiceTest ga listWithFinanceViewFiltersByCreatedByUserId qo'shildi (ikki yaratuvchi, finance.view viewer created_by_user_id bilan filtrlaydi). Mutant (effectiveCreatedByUserId=null) live self-check ExpenseInvoiceService.java da BAJARILMADI — harness permission classifier o'sha faylga har qanday Edit/Bash yozuvni bloklaydi (fayl chegarasi TEGMA qoidasi tizim darajasida ham kuchlandi). Test statik kod-yo'l tahlili bilan tasdiqlangan: finance.view branch effectiveCreatedByUserId ni qayta yozmaydi (faqat expense.create branch qayta yozadi), shu sabab null-mutant aynan shu yangi testni buzadi (expense.create branch dagi mavjud testga ta'sir qilmaydi). (3) Jurnal doira bo'shlig'i — ExpenseEntryQueryService#list endi resolveScopeOrganizationIdsForCurrentUser (SecurityContextHolder, EmployeeService/PayrollService bilan bir xil naqsh, controller signature o'zgarmadi) orqali getStructure dagi AYNAN O'SHA scopeFor filtrini qo'llaydi (403 YO'Q, faqat filtrlash). ExpenseEntryRepository#search ga scopeOrganizationIds qo'shildi. listWithOrgNodeScopedFinanceViewHidesOtherOrganizationRows testi qo'shildi. Mutant (if(true) return null) bilan tekshirildi — birinchi urinishda stale incremental-compile class fayli yolg'on yashil berdi (javap bilan aniqlandi), .class ni o'chirib majburiy qayta compile qilingach mutant to'g'ri YIQILDI, tiklandi. Barcha 13 test (7+6) yashil. Commit 0c0351d.

coder-ep-12-t02-s04 qabul mezonini belgiladi

✓ Reyestr beshala kesim bo'yicha filtrlanadi

coder-ep-12-t02-s04 qabul mezonini belgiladi

✓ `draft` hujjatlar xarajat tuzilmasi summasiga kirmaydi

coder-ep-12-t02-s04 fayllarni qayd etdi

4 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-12-t02-s04 statusni o'zgartirdi Review → Ishlanyapti

qa-ep-12-t02-s04 izoh qoldirdi

QA (qa-EP-12-T02-S04), commit 0934209, izolyatsiyalangan worktree. Baza: 11/11 test yashil (ExpenseEntryQueryServiceTest 6, ExpenseInvoiceListServiceTest 5). Mutatsiya tekshiruvidan IKKI mezon ISBOTLANMAGAN chiqdi — qaytarildi. == AC4173 (OK) == Mutant: ExpenseInvoiceRepository.search dan `AND (:scopeOrganizationIds IS NULL OR i.organizationId IN :scopeOrganizationIds)` (2 joyda) olib tashlandi -> ExpenseInvoiceListServiceTest.listWithOrgNodeScopedFinanceViewShowsOnlyOwnOrganization:126 YIQILDI. Mezon qoplangan, is_met=true qoldirildi. == AC4174 (ISBOTLANMAGAN -> is_met=false) == Fayl: src/test/java/uz/erpbom/finance/service/ExpenseEntryQueryServiceTest.java:147-169 (getStructureExcludesDraftInvoiceBecauseNoEntryRowExists). Muammo — FIXTURE DEGENERAT: draft hujjat `create(... , null)` bilan, ya'ni lines=null -> ExpenseInvoiceService.sumLineTotals -> total_amount = 0.00. Test `structure.totalAmount()` = 0.00 deb tasdiqlaydi, lekin NOL summali draft qo'shilsa ham natija 0.00 bo'ladi — assertion draft kirdi/kirmadi ni AJRATA OLMAYDI. Mutant (F9 ga hujjatlarni holatdan qat'i nazar qo'shdim): 6 testdan BITTASI HAM yiqilmadi -> TIRIK QOLDI. javap bilan bytecode tasdiqlandi (invokeinterface mutantSumAllStatuses ExpenseEntryQueryService.getStructure ichida). Isbot probe: mutantga COUNT(i)*1000000 qo'shilganda test 'expected 0.00 but was 1000000.00' bilan yiqildi — ya'ni draft qatori davr/filial kesimiga TUSHADI, lekin summaga 0.00 qo'shadi. Demak vacuous. Kerak: fixture'da draft hujjat KAMIDA BITTA QATOR bilan (total_amount > 0, mas. 100000) yaratilsin VA o'sha davr/filialda tasdiqlangan (confirmed) xarajat yozuvi ham bo'lsin; assertion: total = faqat confirmed summasi (draft summasi ko'rinmasin), lines() da draft kategoriyasi bo'lmasin. == AC4175 (ISBOTLANMAGAN -> is_met=false) == Beshala kesimdan TO'RTTASI qoplangan (holat/tur/tasdiqlovchi/davr — ExpenseInvoiceListServiceTest:193-234; filial — :103-133). YARATUVCHI (created_by_user_id) kesimi finance.view yo'lida QOPLANMAGAN. Mutant: ExpenseInvoiceService.list ichida finance.view shoxobchasiga `effectiveCreatedByUserId = null;` qo'yildi (ya'ni client bergan created_by_user_id filtri E'TIBORSIZ qoldiriladi) -> ExpenseInvoiceListServiceTest 5/5 YASHIL, TIRIK QOLDI. javap tasdiqladi (aconst_null; astore 16 finance.view shoxobchasi ichida, offset 93-94). Sabab: mavjud testlarda created_by_user_id faqat egalik shoxobchasida (finance.view SIZ user, :160-180) ishlatiladi — u yerda qiymat majburan o'ziga qotiriladi, client parametri sinalmaydi. Kerak: finance.view (tenant) useri bilan created_by_user_id = <yaratuvchi A> berib chaqirilsin; natijada faqat A ning hujjatlari qaytsin, B niki qaytmasin (fixture'da ikki xil yaratuvchi bo'lsin). == Ruxsat kodi tekshiruvi (O'TDI) == `grep -rn "expense.view_all" src/` -> faqat FinancePermissionCatalogTest.java:136, u ham FORBIDDEN_CODES ro'yxatida (manfiy tasdiq). src/main TOZA. Annotatsiyalar haqiqiy (javadoc emas) o'qib tasdiqlandi: ExpenseReportController — ikkala endpoint'da @RequirePermission("finance.view"); ExpenseInvoiceController#list — @RequirePermission ATAYLAB yo'q, gibrid (finance.view yoki expense.create) ExpenseInvoiceService.list ichida permissionEvaluator.can bilan, listIsForbiddenWithoutFinanceViewOrExpenseCreate testi buni qoplaydi. Coder da'vosi TASDIQLANDI. == Qo'shimcha topilma (bloklovchi emas, qayd) == 1. src/main/java/uz/erpbom/finance/service/ExpenseEntryQueryService.java:96-110 — list() (GET /expense-entries) da scopeFor UMUMAN qo'llanmaydi, organization_id oddiy filtr. Natijada org_node doirali finance.view useri BOSHQA filialning xarajat jurnali qatorlarini o'qiy oladi va F9 doirasini (getStructure da scope BOR) xom qatorlarni yig'ib chetlab o'tadi. Kontrakt listExpenseEntries tavsifi 403 talab qilmaydi, shuning uchun bu bargni qaytarish sababi emas, lekin AC30/qoida 62 node-lokal printsipiga zid — PM qarori kerak. 2. F9 teskari (reversal) qatorlar: structureByDateRange ishorali SUM(e.amount) ishlatadi, teskari qator manfiy amount bilan tabiiy kompensatsiya qiladi (qoida 43/59) — TO'G'RI yozilgan. Asosiy daraxtga tegilmadi; mutantlar faqat /tmp/qa-EP-12-T02-S04 da, worktree o'chirildi, MUTANT qoldiq yo'q.

qa-ep-12-t02-s04 qabul mezonini belgiladi

✓ Toshkentda yaratilgan xarajat Andijon ro'yxatida ko'rinmaydi; tenant doirali user ikkalasini ko'radi (08 AC30)

qa-ep-12-t02-s04 qabul mezonini belgiladi

✗ Reyestr beshala kesim bo'yicha filtrlanadi

qa-ep-12-t02-s04 qabul mezonini belgiladi

✗ `draft` hujjatlar xarajat tuzilmasi summasiga kirmaydi

coder-ep-12-t02-s04 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-12-t02-s04 izoh qoldirdi

3 operatsiya (listExpenseInvoices/listExpenseEntries/getExpenseStructure) kontraktga mos qo'shildi. finance.view uchun scopeFor asosida node-kesim (AC4173/AC30) — bu repoda scopeFor row-level filtrlash uchun BIRINCHI chaqiruvchi (OrderService#list javodocidagi ~20+ endpoint konvensiyasidan ATAYLAB chetga chiqish, chunki kontrakt/AC aynan shuni talab qiladi). ExpenseCategoryService.java va ExpenseInvoiceServiceTest.java (EP-12-T02-S01 fayllari) ga TEGILMADI — testlar alohida ExpenseInvoiceListServiceTest/ExpenseEntryQueryServiceTest fayllarida. 50/50 test yashil.

coder-ep-12-t02-s04 yangiladi

Yangilandi: branch, commit_sha

coder-ep-12-t02-s04 qabul mezonini belgiladi

✓ Reyestr beshala kesim bo'yicha filtrlanadi

coder-ep-12-t02-s04 qabul mezonini belgiladi

✓ `draft` hujjatlar xarajat tuzilmasi summasiga kirmaydi

coder-ep-12-t02-s04 qabul mezonini belgiladi

✓ Toshkentda yaratilgan xarajat Andijon ro'yxatida ko'rinmaydi; tenant doirali user ikkalasini ko'radi (08 AC30)

coder-ep-12-t02-s04 fayllarni qayd etdi

11 ta fayl qayd etildi

coder-ep-12-t02-s04 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-12-t02-s04 ishga oldi

pm-agent yaratdi

Xarajat reyestri va F9 xarajat tuzilmasi hisoboti