`active` toggle — mobil kirish va yangi fakturaga biriktirish cheklovi

team-lead-pm bog'liqlik qo'shdi

→ EP-03-T02-S01

team-lead-pm yangiladi

Yangilandi: estimate_hours

team-lead-pm bog'liqlik qo'shdi

→ EP-03-T02-S01

team-lead-pm yangiladi

Yangilandi: estimate_hours

team-lead-pm bog'liqlik qo'shdi

→ EP-03-T02-S01

team-lead-pm yangiladi

Yangilandi: estimate_hours

finalize-ep-03 yangiladi

Yangilandi: pr_url

qa-ep-03-t02-s03 izoh qoldirdi

QA (qa-EP-03-T02-S03) — TEKSHIRILDI, verdikt: done. Spec: 01_suppliers.md #4.1 + §5 qoida 2 / qoida 14(c). Kontrakt: openapi/v1/suppliers.yaml 350-405. TESTLAR: SupplierToggleActiveTest 12/12 yashil (34.5s). Regressiya: SupplierCreateTest 13 + SupplierQueryTest 19 + SupplierToggleActiveTest 12 = 44/44 yashil, exit=0. S01/S02 buzilmagan. MEZONLAR (har biri alohida tekshirildi): - AC1704 — SupplierService.setActive users jadvaliga umuman tegmaydi (u yerda hech qanday JDBC/repo chaqiruvi yo'q). Test SupplierToggleActiveTest.java:182-199 HAQIQIY: real user yaratadi (insertUser), suppliers.user_id ni bog'laydi (linkSupplierToUser), deactivate OLDIN/KEYIN status va token_valid_after ni XOM SQL bilan solishtiradi. Qo'g'irchoq emas — mutatsiya bilan isbotlandi (quyida #3). - AC1705 — SupplierController da @DeleteMapping YO'Q; SupplierService da .delete/.deleteById/.deleteAll YO'Q; kontraktda ham /api/v1/suppliers/{id} uchun `delete:` yo'q (delete faqat documents/{documentId} va credentials da). Test DELETE -> 405/404 ekanini VA qator DB da omon qolganini tekshiradi. - AC1706 — ikkala endpoint @RequirePermission("supplier.toggle_active") (SupplierController.java:79,86); supplier.update ALOHIDA rule ekani 2 ta maxsus test bilan qoplangan. MUTATSIYA TEKSHIRUVI (4/4 o'ldirildi — testlar yolg'onni ushlay oladi): 1. toggle_active -> supplier.update: 9 fail, jumladan supplierUpdatePermissionAloneDoesNotAllowActivate/Deactivate "expected: 403 but was: 200". OK 2. @RequirePermission butunlay olib tashlandi: aynan 4 ta 403-testi fail, ortiqcha shovqinsiz. OK 3. deactivate da bog'langan user status='blocked' + token_valid_after=now() qilindi: AYNAN 1 fail — deactivateDoesNotChangeLinkedUserStatusOrTokenValidAfter, "expected: active but was: blocked". AC1704 testi HAQIQIY. OK 4. setActive idempotentligi buzildi (allaqachon shu holatda -> 409): aynan 2 idempotentlik testi fail. OK Har mutatsiya faqat tegilgan fayl bo'yicha qaytarildi; begona agent ishi (openapi/v1/suppliers.yaml, SupplierContract*) tegilmagan va joyida. §5 qoida 14(c) BAJARILMAGANI — TO'G'RI QAROR, defekt EMAS: spec'da qoida 14(c) ochiq "taklif — tasdiq kutilmoqda ... kontragent (ta'minotchi/mijoz) uchun TASDIQLANMAGAN" deb belgilangan; kontrakt ham deactivate description'da users holatiga ta'sirni VA'DA QILMAYDI. AC1704 aynan buning QO'LLANMAGANINI talab qiladi. KONTRAKT MOSLIGI: activate/deactivate ikkalasi 200 SupplierResponse; 401/403/404; idempotent 200 (allaqachon faol/nofaol bo'lsa ham). Maydon nomi/tip/status kodida chetga chiqish yo'q. CROSS-CUTTING: activate/deactivate ikkalasi @Transactional (yozuv — readOnly emas), SupplierService.java:98,113. Fizik DELETE yo'q. Multi-tenant mexanikasi qo'shilmagan (AR-1). Parol/token log'ga yozilmaydi. Bu commit'da migratsiya yo'q. GIGIYENA: 3a0f0cb — aynan 3 fayl (controller, service, test), +411 qator. openapi/ ga va erp/docs ga TEGILMAGAN. Begona agentning SupplierContract* / supplier_documents / V13 ishi commit'ga tushmagan.

qa-ep-03-t02-s03 statusni o'zgartirdi Review → Bajarildi

qa-ep-03-t02-s03 qabul mezonini belgiladi

✓ `supplier.toggle_active` rule'siz `403`; `supplier.update` bu amalni bermaydi (alohida rule)

qa-ep-03-t02-s03 qabul mezonini belgiladi

✓ Ta'minotchini fizik o'chirish yo'li API da yo'q (DELETE endpoint mavjud emas yoki 405)

qa-ep-03-t02-s03 qabul mezonini belgiladi

✓ `active=false` qilinganda bog'langan `users` qatori (status, token_valid_after) O'ZGARMAGAN bo'ladi — qoida 14(c) qo'llanmagani testi

coder-ep-03-t02-s03 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-03-t02-s03 yangiladi

Yangilandi: branch, commit_sha

coder-ep-03-t02-s03 qabul mezonini belgiladi

✓ `supplier.toggle_active` rule'siz `403`; `supplier.update` bu amalni bermaydi (alohida rule)

coder-ep-03-t02-s03 qabul mezonini belgiladi

✓ Ta'minotchini fizik o'chirish yo'li API da yo'q (DELETE endpoint mavjud emas yoki 405)

coder-ep-03-t02-s03 qabul mezonini belgiladi

✓ `active=false` qilinganda bog'langan `users` qatori (status, token_valid_after) O'ZGARMAGAN bo'ladi — qoida 14(c) qo'llanmagani testi

coder-ep-03-t02-s03 fayllarni qayd etdi

3 ta fayl qayd etildi

coder-ep-03-t02-s03 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-03-t02-s03 ishga oldi

pm-agent bog'liqlik qo'shdi

→ EP-03-T02-S01

pm-agent yaratdi

`active` toggle — mobil kirish va yangi fakturaga biriktirish cheklovi