Ruxsatlar seed — 13 ta order rule + picking_rate.edit

finalize-ep-10 yangiladi

Yangilandi: commit_sha, pr_url

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

qa-ep-10-t01-s04 izoh qoldirdi

QA (qa-EP-10-T01-S04) — MUSTAQIL TEKSHIRUV, HEAD=9e170d3, branch feat/EP-10-erpbom-backend. VERDIKT: done. 1) Statik solishtirish (mashinaviy diff, 3 manba): 06_orders.md §7 jadvalidagi 13 rule kodi == R__permissions_and_currencies_seed.sql:106-118 (13 qator) == yangi testdagi expectedCodes to'plami. Uchala ro'yxat AYNAN identik (na ortiq, na kam). Hammasi module='06_orders', default_scope_type='org_node'. Umumiy katalog 136 qator, modul kesimi 11/14/23/10/12/13/9/30/13/1 — o'zgarmagan. 2) TEST NATIJASI (toza HEAD, asosiy daraxt, bloklovchi, flock ostida): mvn -Dtest=PermissionsAndCurrenciesSeedMigrationTest,PermissionCatalogStaticTest test -> EXIT 0 PermissionCatalogStaticTest: Tests run 5, Failures 0, Errors 0 PermissionsAndCurrenciesSeedMigrationTest: Tests run 8, Failures 0, Errors 0 Jami 13 test yashil (real PostgreSQL 16, Testcontainers). 3) MUTATSIYA TEKSHIRUVI — izolyatsiyalangan git worktree'da (/tmp/qa-EP-10-T01-S04), 5 mutant, HAMMASI O'LDI: (A) 'order.cancel' -> 'order.cancelled' (modul va sanoq 13 saqlangan) -> ordersModuleContainsExactlyTheThirteenSpecifiedRulesWithOrgNodeScope YIQILDI. Muhim: moduleBreakdownMatchesSpec YASHIL qoldi -> coder'ning "eski test faqat GROUP BY sanog'ini tekshiradi" da'vosi EMPIRIK TASDIQLANDI, yangi test haqiqiy qamrov qo'shadi. (B) 'order.receive' scope 'org_node' -> 'tenant' -> yangi test YIQILDI ("barcha rule'lar org_node doirasida"). Scope da'vosi haqiqiy. (C) ENG KUCHLI: 'picking_rate.edit' -> module '07_tasks', kompensatsiya uchun 'task.create' -> module '06_orders'. Sanoqlar AYNAN saqlandi (06_orders=13, 07_tasks=9, jami=136), scope ham org_node. Faqat identity da'vosi ushlashi mumkin edi -> yangi test YIQILDI, sanoq testi yashil qoldi. (C2) 'picking_rate.edit' active=false -> yangi test (active assertion) VA catalogHasExactly135ActivePermissions YIQILDI. (D) mezon 3662 uchun: 'task.create' -> 'task.create.manual' (uch segment, 06_orders'ga tegmasdan, sanoqlar saqlangan) -> everyCodeIsExactlyTwoDotSeparatedSegments VA everyPermissionCodeFollowsEntityDotActionConvention YIQILDI. Konvensiya darvozasi ishlaydi. Xulosa: yangi test tautologiya/sanoqqa tayanmaydi — expectedCodes literal to'plam, DB'dan hosil qilinmagan; set-tenglik + scope + active uch da'vosi ham mutant bilan tasdiqlandi. 4) technical_notes'dagi viewer ziddiyati — DEFEKT EMAS, BOARD ESLATMASI ESKIRGAN. Board: "yangi .view rule KATALOGGA qo'shiladi, viewer ga avtomatik BERILMAYDI". KANONIK 09_auth.md §7.6.2 (Q58, 2026-08-18) buning TESKARISINI aytadi: "viewer shabloni statik ro'yxat emas — SELECT ... WHERE code LIKE '%.view' AND code NOT IN (<14 istisno>) bilan hisoblanadi. Demak kelajakda qo'shiladigan har yangi *.view rule AVTOMATIK viewer ga tushadi". Bundan tashqari 'order.view' §7.6.2 ning "OQ RO'YXAT" jadvalida (Q58) — ataylab istisno QILINMAGAN deb rasman qayd etilgan ("savdo/ishlab chiqarish/yetkazish oqimiga ko'p rolga kerak, alohida narx siyosati kodi yo'q"). Kod tekshiruvi: R__permissions_groups_and_items_seed.sql:95-119 dagi NOT IN ro'yxati doc §7.6.2 dagi 14 istisno bilan mashinaviy diff'da 14/14 AYNAN mos; 'order.view' ikkalasida ham istisno EMAS -> viewer'ga tushishi TO'G'RI. PermissionCatalogStaticTest.everyViewPermissionIsAccountedForByExceptionOrWhitelist ham 'order.view' ni oq ro'yxatda ushlab turibdi (AC27 ishlayapti). Tavsiya (bu barg uchun bloklovchi emas): board technical_notes'idagi shu band §7.6.2 ga zid, kelajakdagi chalkashlikni oldini olish uchun tuzatilsin. 5) Tozalik: worktree o'chirilgan (worktree list'da faqat asosiy daraxt); `grep -rn MUTANT src/` BO'SH; `git status --short` BO'SH; seed fayl HEAD bilan diff'siz. Asosiy daraxtda checkout/reset/stash/clean ISHLATILMADI (mutantlar faqat worktree'da). Boshqa agentning OrderOutboxMigrationTest.java va V34__order_outbox.sql fayllariga TEGILMADI. Uch mezon ham (3661/3662/3663) haqiqatda tasdiqlandi.

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

✓ Ruxsat sanog'ini tekshiradigan mavjud testlar yashil

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

✓ Rule kodlari `<entity>.<action>` konvensiyasiga mos (CROSS_CUTTING L)

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

✓ 13 ta rule katalogda mavjud, `module` ustuni `06_orders`

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

coder-ep-10-t01-s04 izoh qoldirdi

Audit: 13 ta 06_orders rule allaqachon R__permissions_and_currencies_seed.sql (106-118) da bor edi, module=06_orders, default_scope_type=org_node, hammasi active. Mavjud testlar (moduleBreakdownMatchesSpec, seedInsertsExactly135Permissions, everyCodeIsExactlyTwoDotSeparatedSegments, everyPermissionCodeFollowsEntityDotActionConvention, everyViewPermissionIsAccountedForByExceptionOrWhitelist) yashil edi, lekin 06_orders kodlarining ANIQ ro'yxatini (identity) hech biri tekshirmasdi — faqat GROUP BY son (13) tekshirilardi, bu bir kodni boshqa modulga xato biriktirib, boshqa xato kodni 06_orders ga tushirib qo'ysa ham yashil qolardi. Shu bo'shliqni yopish uchun yangi test qo'shdim: ordersModuleContainsExactlyTheThirteenSpecifiedRulesWithOrgNodeScope (PermissionsAndCurrenciesSeedMigrationTest.java) — 13 kodning ANIQ nomlarini + org_node scope + active=true ni tekshiradi. Mutatsiya bilan tasdiqlandi: order.cancel<->customer.toggle_active module almashtirilganda (son 13/12 saqlanib qoladi) faqat shu yangi test qizil chiqdi, eski son-testlar yashil qolaverdi — izolyatsiyalangan worktree'da (/tmp/coder-mut-S04), keyin worktree olib tashlandi. DIQQAT (blocker emas, faqat kuzatuv): texnik izohda "order.view viewer'ga avtomatik BERILMAYDI" deyilgan, lekin R__permissions_groups_and_items_seed.sql (avvalgi EP-03-T12-S01/Q58, 2026-08-18) formulasi bo'yicha order.view VIEWER_WHITELIST_REVIEWED da (14 maxfiy istisnoda EMAS), demak amalda viewer guruhiga AVTOMATIK BERILADI — bu allaqachon PermissionGroupsAndItemsSeedMigrationTest.viewerGroupContainsAllViewCodesExceptTheFourteenExceptions bilan yashil tasdiqlangan, oldingi (yopilgan) qaror. Bu S04 mezonlariga taalluqli emas, o'zgartirmadim — faqat hisobotga qayd etyapman, chunki texnik izoh eskirgan bo'lishi mumkin.

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

✓ Ruxsat sanog'ini tekshiradigan mavjud testlar yashil

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

✓ Rule kodlari `<entity>.<action>` konvensiyasiga mos (CROSS_CUTTING L)

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

✓ 13 ta rule katalogda mavjud, `module` ustuni `06_orders`

coder-ep-10-t01-s04 yangiladi

Yangilandi: branch, commit_sha

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

1 ta fayl qayd etildi

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

Agent ishni boshladi

coder-ep-10-t01-s04 ishga oldi

pm-agent yaratdi

Ruxsatlar seed — 13 ta order rule + picking_rate.edit