Dry-run oldindan ko'rish — komponent ehtiyoji va maksimal set soni

finalize-ep-04 yangiladi

Yangilandi: commit_sha, pr_url

worker-ep-04-t14 statusni o'zgartirdi Ishlanyapti → Bajarildi

worker-ep-04-t14 statusni o'zgartirdi Tayyor → Ishlanyapti

Agent ishni boshladi

worker-ep-04-t14 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

worker-ep-04-t14 statusni o'zgartirdi Bloklangan → Ishlanyapti

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

🔴 BLOK SABABI EPIC DARAJASIDA: bu barg o'z doirasini (dry-run preview) TO'G'RI bajargan. Blok shu bargga qo'yildi, chunki SetAssemblyController aynan shu bargda yaratilgan va yetishmayotgan GET'lar o'sha klassga tegishli; PM Board'da ota-item statusi bolalardan hisoblanadi, shuning uchun drift faqat barg orqali ko'rsatiladi. FINALIZE DRIFT (EP-04, implementatsiya<->kontrakt). Muzlatilgan kontraktda (openapi/v1/warehouse.yaml) e'lon qilingan 2 operatsiya kodda YO'Q: - GET /api/v1/set-assemblies (yaml 2103-qator) - GET /api/v1/set-assemblies/{id} (yaml 2279-qator) DALIL: springdoc /v3/api-docs (HEAD c884b47 dan qurilgan ilova) da bu yo'llar yo'q; SetAssemblyController da faqat 3 ta @PostMapping bor (preview/create/reverse). SABAB: SetAssemblyController izohi (37-qator) "Ro'yxat/kartochka (GET) — T07 ning boshqa bargasida shu klassga qo'shiladi" deydi, lekin bunday barg board'da HECH QACHON yaratilmagan (T07 = S01..S03, hammasi done). Ya'ni kamchilik backlog qamrovida, bu bargning bajarilishida emas. TA'SIRI: erpbom-web SetAssemblyListView va SetAssemblyDetailView shu ikki endpointni chaqiradi (src/modules/warehouse/api/set-assemblies.api.ts:82 va :92) — real backend'da 404 bo'ladi. NEGA SEZILMAGAN: prism mock (:4010) muzlatilgan kontraktni serve qilib turgan edi; finalize paytida o'chirildi. TUZATISH KODDA (kontrakt muzlatilgan, unga TEGILMAYDI): GET ro'yxat + kartochka uchun yangi barg ochilsin. NATIJA: erpbom-backend PUSH QILINMADI, PR ochilmadi.

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

🔴 BLOK SABABI EPIC DARAJASIDA: bu barg o'z doirasini (dry-run preview) TO'G'RI bajargan. Blok shu bargga qo'yildi, chunki SetAssemblyController aynan shu bargda yaratilgan va yetishmayotgan GET'lar o'sha klassga tegishli; PM Board'da ota-item statusi bolalardan hisoblanadi, shuning uchun drift faqat barg orqali ko'rsatiladi. FINALIZE DRIFT (EP-04, implementatsiya<->kontrakt). Muzlatilgan kontraktda (openapi/v1/warehouse.yaml) e'lon qilingan 2 operatsiya kodda YO'Q: - GET /api/v1/set-assemblies (yaml 2103-qator) - GET /api/v1/set-assemblies/{id} (yaml 2279-qator) DALIL: springdoc /v3/api-docs (HEAD c884b47 dan qurilgan ilova) da bu yo'llar yo'q; SetAssemblyController da faqat 3 ta @PostMapping bor (preview/create/reverse). SABAB: SetAssemblyController izohi (37-qator) "Ro'yxat/kartochka (GET) — T07 ning boshqa bargasida shu klassga qo'shiladi" deydi, lekin bunday barg board'da HECH QACHON yaratilmagan (T07 = S01..S03, hammasi done). Ya'ni kamchilik backlog qamrovida, bu bargning bajarilishida emas. TA'SIRI: erpbom-web SetAssemblyListView va SetAssemblyDetailView shu ikki endpointni chaqiradi (src/modules/warehouse/api/set-assemblies.api.ts:82 va :92) — real backend'da 404 bo'ladi. NEGA SEZILMAGAN: prism mock (:4010) muzlatilgan kontraktni serve qilib turgan edi; finalize paytida o'chirildi. TUZATISH KODDA (kontrakt muzlatilgan, unga TEGILMAYDI): GET ro'yxat + kartochka uchun yangi barg ochilsin. NATIJA: erpbom-backend PUSH QILINMADI, PR ochilmadi.

qa-ep-04-t07-s01 statusni o'zgartirdi Review → Bajarildi

qa-ep-04-t07-s01 qabul mezonini belgiladi

✓ Resepti yo'q yoki `finished` bo'lmagan variant uchun dry-run 400 beradi

qa-ep-04-t07-s01 qabul mezonini belgiladi

✓ Yetmaslik holatida javob qaysi komponent yetmagani, kerak/mavjud/band miqdorlari bilan qaytadi

qa-ep-04-t07-s01 qabul mezonini belgiladi

✓ Maksimal set soni `min ⌊mavjud/resept⌋` formulasi bo'yicha to'g'ri qaytadi (band qoldiq chegiriladi)

qa-ep-04-t07-s01 qabul mezonini belgiladi

✓ Dry-run hech qanday qator yozmaydi (stock/batches/movements diff bo'sh)

coder-ep-04-t07-s01 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-04-t07-s01 yangiladi

Yangilandi: commit_sha

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Yetmaslik holatida javob qaysi komponent yetmagani, kerak/mavjud/band miqdorlari bilan qaytadi

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Maksimal set soni `min ⌊mavjud/resept⌋` formulasi bo'yicha to'g'ri qaytadi (band qoldiq chegiriladi)

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Dry-run hech qanday qator yozmaydi (stock/batches/movements diff bo'sh)

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Resepti yo'q yoki `finished` bo'lmagan variant uchun dry-run 400 beradi

coder-ep-04-t07-s01 fayllarni qayd etdi

2 ta fayl qayd etildi

coder-ep-04-t07-s01 ishga oldi

qa-ep-04-t07-s01 izoh qoldirdi

QA (qa-EP-04-T07-S01) — QAYTARILDI: 3/4 mezon o'tdi, AC2504 yiqildi + 1 test bo'shligi. TEST NATIJASI (o'zim yurgizdim, flock ostida): `mvn -o -Dtest=SetAssemblyPreviewTest test` -> Tests run: 9, Failures: 0, Errors: 0 (BUILD SUCCESS, 43s). O'TGAN MEZONLAR (kod darajasida tekshirildi): * AC2501 — SetAssemblyService.java:76 `@Transactional(readOnly = true)`, butun oqimda birorta `save()`/`@Modifying` yo'q; qulflovchi `findForUpdate` o'rniga oddiy o'qish (StockRepository.findByWarehouseIdAndProductVariantIdAndCondition). Test stock/stock_batches/stock_movements/set_assemblies qator sonini VA qty_on_hand ni oldin/keyin solishtiradi. * AC2502 — SetAssemblyService.java:111 `qty_on_hand - qty_reserved`, :129 `divide(recipe, 0, FLOOR)` (min_i floor). MUTATSIYA bilan isbotlandi: (a) `availableQty = qtyOnHand` (band chegirilmasa) -> previewSubtractsReservedQtyFromAvailability yiqildi (expected 20.0000, was 25.0000); (b) FLOOR -> CEILING -> previewMatchesWorkedExampleFromSpec yiqildi (expected 10.0000, was 11.0000). Ikkala mutatsiya ham tiklandi. * AC2503 — :112 `shortageQty = max(0, required - available)`, javobda component_variant_id/required_qty/available_qty/reserved_qty/shortage_qty/is_sufficient; test manba misolidagi raqamlar bilan (kerak 20, mavjud 14, yetmaydi 6) tekshiradi, can_assemble=false va estimated_total_cost=null. * Kontrakt: yo'l `/api/v1/set-assemblies/preview`, `set_assembly.create` rule, maydon nomlari va tiplari openapi/v1/warehouse.yaml (SetAssemblyPreviewRequest/Response, SetAssemblyComponentRequirement) bilan mos — chetlanish topilmadi. YIQILGAN — AC2504 ("resepti yo'q YOKI finished bo'lmagan variant -> 400"): SetAssemblyService.java:79-80 — `product_type != finished` bo'lganda `SET_RECIPE_MISSING` (409) tashlanadi, :82-83 resept yo'qligida ham aynan shu kod. 1) "Resepti yo'q" shoxi uchun 409 SET_RECIPE_MISSING — QABUL QILINADI: muzlatilgan kontrakt (warehouse.yaml:2766 SetAssemblyConflict) buni aynan 409 deb belgilagan, AC matnidagi "400" kontraktdan ustun emas. Bu shox bo'yicha da'vo yo'q. 2) `product_type != finished` shoxi — DEFEKT: kontraktda bu holat uchun kod YO'Q, ya'ni 409 ga majburlovchi hech narsa yo'q; endpoint kontraktida `400 ValidationError` (warehouse.yaml:2268) e'lon qilingan va repo'da tayyor mexanizm bor (uz.erpbom.common.exception.ValidationException -> 400 VALIDATION_ERROR). Hozirgi xatti-harakat AC2504 dagi 400 talabidan chetga chiqadi VA xabari yolg'on: Tovar1 (semi_finished) SKU tanlansa foydalanuvchi "Bu Tovar2 uchun faol resept versiyasi topilmadi" (SetAssemblyService.java:194-196) xabarini oladi, holbuki Tovar1 da faol resept BOR — foydalanuvchi resept qidirib vaqt yo'qotadi. Kutilgan: `product_type != finished` -> 400 VALIDATION_ERROR, xabar/`fields` da sabab aniq (mas. product_variant_id: "Tovar2 (product_type = finished) bo'lishi shart"); resept yo'qligi 409 SET_RECIPE_MISSING bo'lib qoladi. Testda previewRejectsVariantThatIsNotFinishedType shunga moslansin (hozir SetAssemblyPreviewTest.java:325 CONFLICT kutadi). TEST BO'SHLIGI (tuzatilishi shart) — "FAOL recipe_version tanlanishi" isbotlanmagan: MUTATSIYA OMON QOLDI (javap bilan tasdiqlandi — target/classes dagi klass haqiqatan yangilangan): RecipeVersionService.findActive ichidagi `findByProductVariantIdAndActiveTrue(productVariantId)` -> `findByProductVariantIdAndVersionNumber(productVariantId, 1)` ga almashtirildi, `mvn -o -Dtest=SetAssemblyPreviewTest test` -> 9/9 YASHIL. Sabab: birorta fixture nofaol versiya yaratmaydi (SetAssemblyPreviewTest.java:552 insertActiveRecipeVersion doim active=true, version_number=1). Ya'ni "nofaol/eski versiya bo'yicha hisoblash" regressiyasi test to'rida ushlanmaydi, holbuki task tavsifi "joriy FAOL recipe_versions" deydi (03_warehouse.md 8.9-A p.2, 9 "resept o'zgardi"). Kerak: bitta test — bir variant uchun v1 (active=false, boshqa/ko'proq komponent miqdori) + v2 (active=true) yaratilsin, javobdagi recipe_version_id = v2 va required_qty/max_sets AYNAN v2 miqdorlari bo'yicha chiqsin. Mutatsiya tiklandi, ishchi daraxt toza. Ikkinchi darajali (majburiy emas, lekin tavsiya): birorta test `condition = 'defective'` qator kiritmaydi — "faqat good qoldiq hisobga olinadi" (8.9-A p.2, qoida 26) da'vosi ham to'rda ushlanmaydi; shu bir qator fixture bilan yopiladi. Status -> in_progress. AC2501/2502/2503 = met, AC2504 = not met.

qa-ep-04-t07-s01 statusni o'zgartirdi Review → Ishlanyapti

qa-ep-04-t07-s01 qabul mezonini belgiladi

✗ Resepti yo'q yoki `finished` bo'lmagan variant uchun dry-run 400 beradi

qa-ep-04-t07-s01 qabul mezonini belgiladi

✓ Yetmaslik holatida javob qaysi komponent yetmagani, kerak/mavjud/band miqdorlari bilan qaytadi

qa-ep-04-t07-s01 qabul mezonini belgiladi

✓ Maksimal set soni `min ⌊mavjud/resept⌋` formulasi bo'yicha to'g'ri qaytadi (band qoldiq chegiriladi)

qa-ep-04-t07-s01 qabul mezonini belgiladi

✓ Dry-run hech qanday qator yozmaydi (stock/batches/movements diff bo'sh)

coder-ep-04-t07-s01 fayllarni qayd etdi

9 ta fayl qayd etildi

coder-ep-04-t07-s01 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-04-t07-s01 yangiladi

Yangilandi: branch, commit_sha

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Resepti yo'q yoki `finished` bo'lmagan variant uchun dry-run 400 beradi

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Yetmaslik holatida javob qaysi komponent yetmagani, kerak/mavjud/band miqdorlari bilan qaytadi

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Maksimal set soni `min ⌊mavjud/resept⌋` formulasi bo'yicha to'g'ri qaytadi (band qoldiq chegiriladi)

coder-ep-04-t07-s01 qabul mezonini belgiladi

✓ Dry-run hech qanday qator yozmaydi (stock/batches/movements diff bo'sh)

coder-ep-04-t07-s01 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-04-t07-s01 ishga oldi

pm-agent yaratdi

Dry-run oldindan ko'rish — komponent ehtiyoji va maksimal set soni