organization_settings API (organization_setting.manage)

team-lead-ep-09 yangiladi

Yangilandi: pr_url

team-lead-ep-09 bog'liqlik qo'shdi

→ EP-09-T05-S06

team-lead-ep-09 yangiladi

Yangilandi: estimate_hours

qa-ep-09-t05-s07 izoh qoldirdi

QA PASS. Kod §2.3f (organization_settings) va CROSS_CUTTING N ga mos: id/key UNIQUE/value text/updated_by_user_id FK->users/updated_at. Kontrakt (openapi/v1/auth.yaml) bilan aynan mos: GET (list, pagination) + PUT /{key} (GET-by-key kontraktda yoq - kod ham qoshmagan), 403/404 ishlaydi. organization_setting.manage scope=tenant RequirePermissionAspect orqali tekshiriladi (mavjud infra, S06 organizations qayta yozilmagan). Noma lum kalit -> 404 NOT_FOUND (rad etish siyosati, kontraktda hujjatlangan). UNIQUE(key) + findByKey+save -> ikkinchi PUT dublikat yaratmaydi. Cross-cutting 8/8: @Transactional(readOnly=true) list / @Transactional update; single-tenant (organization_id ustuni yoq); permission_code haqiqiy FK (fk_user_permissions_permission); async/outbox N/A; snake_case+koplik+fk_organization_settings_updated_by_user; qty/price precision N/A; DELETE yoq (settings jadvali faqat PUT, soft-delete talab qilinmaydi); password/token log yozilmaydi. Testlar: mvn -Dtest=OrganizationSettingControllerIntegrationTest -> 6/6 yashil (flock ostida). Mutatsiya tekshiruvi: updatedByUserId ni ataylab olib tashladim -> AC778 testi qizil bolib yiqildi (yolgonni ushladi), git checkout bilan tikladim. Barcha 4 acceptance_criteria mustaqil tasdiqlandi. Status: done.

qa-ep-09-t05-s07 statusni o'zgartirdi Review → Bajarildi

qa-ep-09-t05-s07 qabul mezonini belgiladi

✓ Bir kalit bir qator (`UNIQUE(key)`) — ikkinchi `PUT` yangilaydi, dublikat yaratmaydi

qa-ep-09-t05-s07 qabul mezonini belgiladi

✓ Noma'lum kalitga yozish siyosati (rad etish yoki qabul) hujjatlangan va testda qotirilgan

qa-ep-09-t05-s07 qabul mezonini belgiladi

✓ `organization_setting.manage` rule'isiz `403` qaytadi

qa-ep-09-t05-s07 qabul mezonini belgiladi

✓ Sozlama o'zgartirilganda `updated_by_user_id` joriy user bilan to'ladi

backend-1 statusni o'zgartirdi Ishlanyapti → Review

organization_settings API (GET ro'yxat + PUT/{key}) — kontraktga aynan mos, testlar yashil (6/6).

backend-1 yangiladi

Yangilandi: branch, commit_sha

backend-1 izoh qoldirdi

organization-settings API (organization_setting.manage), EP-09-T05-S06 (Organization) ustiga qurildi, entity/repository/table (V2/V4 migratsiya) qayta ishlatildi. Kontrakt so'zma-so'z: PUT faqat mavjud kalitni yangilaydi, noma'lum key -> 404 NOT_FOUND (yangi kalit faqat migratsiya orqali, §2.3f). GET kontraktda sort parametri yo'q, list `key` bo'yicha o'sish tartibida (deterministik default). Integration test (Testcontainers, 6 case: 403 rule'siz, 200 ro'yxat, updated_by_user_id to'lishi, 404 noma'lum kalit, ikkinchi PUT dublikat yaratmasligi) yashil.

backend-1 qabul mezonini belgiladi

✓ Bir kalit bir qator (`UNIQUE(key)`) — ikkinchi `PUT` yangilaydi, dublikat yaratmaydi

backend-1 qabul mezonini belgiladi

✓ Noma'lum kalitga yozish siyosati (rad etish yoki qabul) hujjatlangan va testda qotirilgan

backend-1 qabul mezonini belgiladi

✓ `organization_setting.manage` rule'isiz `403` qaytadi

backend-1 qabul mezonini belgiladi

✓ Sozlama o'zgartirilganda `updated_by_user_id` joriy user bilan to'ladi

backend-1 fayllarni qayd etdi

8 ta fayl qayd etildi

backend-1 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

backend-1 ishga oldi

pm-agent bog'liqlik qo'shdi

→ EP-09-T05-S06

pm-agent yaratdi

organization_settings API (organization_setting.manage)