Netting — ProductionOrderIntakePort chaqiruvi (R3, R13)

finalize-ep-10 yangiladi

Yangilandi: commit_sha, pr_url

qa-ep-10-t04-s04 statusni o'zgartirdi Review → Bajarildi

qa-ep-10-t04-s04 izoh qoldirdi

QA (qa-EP-10-T04-S04) — a2ecce9 mustaqil tekshirildi: AC3698/3699/3700 ✅ done. 2(a) REQUIRES_NEW/self-deadlock — XAVF YO'Q, empirik. Netting PORTINING O'ZI tashqi (apply) tranzaksiyasida: OrderReservationApplyPoster.java:299-306 -> ProductionOrderIntakePortImpl.java:64 (@Transactional REQUIRED) va :84 (readOnly REQUIRED) — ikkalasi ham QO'SHILADI. REQUIRES_NEW faqat SetAssemblyShortagePreviewGateway.java:50 da (preview). preview() (SetAssemblyService.java:207-264) FAQAT qulflamaydigan SELECT: findByWarehouseIdAndProductVariantIdAndCondition + findFifoBatches (StockBatchRepository.java:20-31 javadoci: "FOR UPDATE shart emas"). QA probe: tashqi tranzaksiya HAM komponent (semi_finished) HAM set (finished) stock qatorini FOR UPDATE bilan ushlab turgan holatda apply() -> netting yo'li 577ms/279ms da tugadi, netting qatori yozildi — 55P03 yo'q, osilish yo'q. Coder'ning 'ambient transaction poisoning' sababi texnik jihatdan to'g'ri (participating @Transactional advice setRollbackOnly qiladi). Eslatma (defekt emas, arxitektura): REQUIRES_NEW ochiq yozuvchi tranzaksiya ichida IKKINCHI ulanish oladi; DB_POOL_MAX_SIZE=15 (application.yml:32) — 15 ta parallel finished-netting apply() da pool ochligi nazariy mumkin. 2(b) 'Ochiq sikl' ta'rifi TO'LIQ. V24__production_runs.sql:60-61 CHECK = ('in_progress','completed','cancelled'); 07_tasks.md §4.1a (351-356) ayni shu. 'planned'/'draft'/'paused' YO'Q — in_progress yagona terminal bo'lmagan status. production_outbox (V28:95-96) = pending/processing/sent/failed; pending+processing sanaladi, 'sent' esa production_runs tomonidan sanaladi (ikki marta hisoblash yo'q), 'failed' terminal — sanalmasligi to'g'ri. Ta'rif spec'ga tayanadi, coder taxmini EMAS. 2(c) '02 qoida 13' havolasi HAQIQIY. 02_products.md:713-719: 'Tovar2 alohida ishlab chiqarish taski EMAS — u 03_warehouse ombor operatsiyasi; 07_tasks faqat Tovar1 ishlab chiqaradi.' 06 R14 p.3 (556-557) bilan mos. Dekompozitsiya semi_finished komponent uzatadi (preview from-warehouse = requireSemiFinishedWarehouse). MUTATSIYA (izolyatsiyalangan worktree /tmp/qa-EP-10-T04-S04, javap bilan bytecode tasdiqlangan; worktree remove --force bajarildi, asosiy daraxt toza, grep MUTANT bo'sh): - M1 yalpi qty (remaining=getQty()) -> O'LDI, 7 test (jumladan ...WithNoOpenCycle_requestsNettedDeficit 15.0000) - M2 openRequestedQty=ZERO -> O'LDI, 4 test (qo'sh sikl ochildi) - M3 outbox qismi olib tashlandi -> O'LDI, 2 test - M6 production_runs status filtri kengaytirildi -> O'LDI (...WithCompletedProductionRun_requestsFullDeficitAgain) - M5 netQty ichki 0-chegarasi (max/<=0 -> <0) -> O'LDI, 2 test (kamomad AYNAN 0 da port chaqirilmasligi qoplangan) - M4 tashqi 'remaining<=0 continue' (OrderReservationApplyPoster.java:236-238) -> TIRIK QOLDI. Coder'ning 'ichki himoya qoplaydi' da'vosi TASDIQLANDI, EKVIVALENT mutant: (a) semi_finished yo'lda netQty=max(rawDeficit-openQty,0)<=0 -> port chaqirilmaydi; (b) finished yo'lda SetAssemblyPreviewRequest qty faqat @DecimalMin (bean-validation, kontroller qatlami) — record konstruktorida tekshiruv YO'Q, shu sabab preview(qty=0) portlamaydi va har komponentda shortageQty=0. Coder SINAMAGAN chekka holat — ko'p qatorli finished buyurtma, bitta qator TO'LIQ band — men alohida probe bilan sinadim: M4 QO'YILGAN holda ham tranzaksiya qulamadi, ortiqcha netting qatori yozilmadi (probe asl kodda ham yashil). Ya'ni haqiqiy bo'shliq EMAS; yagona farq — 2 ta ortiqcha SELECT. FIXTURE XILMA-XILLIGI: to'g'ridan-to'g'ri semi_finished netting yo'lida kerak/bor juftligi 6 testda BIR XIL (20-5). Lekin openQty operandi farqlanadi (0/10/15-outbox/15-run) va Tovar2 yo'li boshqa raqamlar beradi (6-2=4). 20≠5≠15≠0 bo'lgani uchun ayirish mutanti (M1) 7 test bilan o'ldi — arifmetika haqiqatan qotirilgan. Kuzatuv: kelgusi ishda to'g'ridan-to'g'ri yo'lga ikkinchi kombinatsiya (mas. 7-0, 9-8) qo'shilsa yaxshi. TESTLAR (bloklovchi, flock ostida, surefire XML'dan): OrderOutboxWorkerTest 23/0F/0E (S03 dan keyin 14 edi -> +9 yangi, KAMAYMAGAN; R10 to'sig'i testlari joyida: qaRepro_*, twoOrdersCompete*, outboxProcessingOrderScrambled*, concurrentProcessReceived*). 07 regressiyasi: ProductionOutboxWorkerTest 5, WorkReviewProductionInIntegrationTest 4, ProductionOrderIntakePortTest 7 — hammasi 0F/0E. SetAssemblyCreate 9 / ListAndGet 10 / Preview 10 / Reverse 10, StockReservationServiceTest 6 — 0F/0E. REGRESSIYA: git show --numstat a2ecce9 = 703 qo'shildi / 0 O'CHIRILDI — 07 ning mavjud kodi bir qator ham o'zgarmagan; buildDedupKey (create_from_order:order:{orderId}:{variantId}:{qty}) va enqueueIfAbsent (ON CONFLICT WHERE status IN pending/processing) o'zgarmagan (EP-07 AC3208 saqlangan). git diff b441b81..HEAD -- openapi/ db/migration/ = BO'SH. CROSS-CUTTING: 1 @Transactional ✓ · 2 tenant_id/schema qo'shilmagan ✓ · 3 migratsiya yo'q ✓ · 4 outbox biznes yozuv bilan bir tranzaksiyada, tashqi broker yo'q ✓ · 5 snake_case/ko'plik ✓ · 6 qty numeric(18,4) (QTY_ZERO scale 4, Command setScale(4)) ✓ · 7 DELETE yo'q ✓ · 8 log'da sir yo'q ✓. Kichik nomuvofiqlik (defekt emas): commit xabari '11 ta yangi test' deydi, aslida 9 ta.

qa-ep-10-t04-s04 qabul mezonini belgiladi

✓ Chaqiruv 06 ning holat o'zgarishi bilan bitta tranzaksiyada (yangi tranzaksiya chegarasi ochilmaydi)

qa-ep-10-t04-s04 qabul mezonini belgiladi

✓ Ochiq sikl bor bo'lsa u hisobga olinadi va ikkinchi sikl OCHILMAYDI (R13)

qa-ep-10-t04-s04 qabul mezonini belgiladi

✓ Port `qty` sifatida NETTING QILINGAN kamomadni oladi (20 kerak - 5 bor = 15), yalpi miqdorni EMAS

coder-ep-10-t04-s04 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-10-t04-s04 yangiladi

Yangilandi: branch, commit_sha

coder-ep-10-t04-s04 qabul mezonini belgiladi

✓ Chaqiruv 06 ning holat o'zgarishi bilan bitta tranzaksiyada (yangi tranzaksiya chegarasi ochilmaydi)

coder-ep-10-t04-s04 qabul mezonini belgiladi

✓ Ochiq sikl bor bo'lsa u hisobga olinadi va ikkinchi sikl OCHILMAYDI (R13)

coder-ep-10-t04-s04 qabul mezonini belgiladi

✓ Port `qty` sifatida NETTING QILINGAN kamomadni oladi (20 kerak - 5 bor = 15), yalpi miqdorni EMAS

coder-ep-10-t04-s04 fayllarni qayd etdi

7 ta fayl qayd etildi

coder-ep-10-t04-s04 statusni o'zgartirdi Tayyor → Ishlanyapti

Agent ishni boshladi

coder-ep-10-t04-s04 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

coder-ep-10-t04-s04 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-10-t04-s04 ishga oldi

pm-agent yaratdi

Netting — ProductionOrderIntakePort chaqiruvi (R3, R13)