`AudienceOwnershipPort` — customer implementatsiyasi (stub o'rniga)

finalize-ep-08 yangiladi

Yangilandi: pr_url

qa-ep-08-t06-s02 statusni o'zgartirdi Review → Bajarildi

qa-ep-08-t06-s02 izoh qoldirdi

QA o'tdi (72f7667). Testlar izolyatsiyalangan git worktree da, bloklovchi, flock ostida: LoginServiceIntegrationTest 23/23 + EmployeeAudienceOwnershipServiceTest 4/4, EXIT=0. MUTATSIYA (3 mutant, har biri bytecode bilan tasdiqlangan): (a) CustomerRepository.existsActiveByUserId JPQL dan "AND c.active = true" olib tashlandi (javap: RuntimeVisibleAnnotations @Query value shartsiz) -> AYNAN 1 test yiqildi: customerLinkedToInactiveCustomerGetsAudienceMismatch (403 kutildi, 200 keldi). AC3505 KILLED, keraksiz yiqilish yo'q. (b) SupplierAudienceOwnershipAdapter: case AUDIENCE_CUSTOMER -> false (javap: isEligibleForCustomerAudience chaqiruvi bytecode dan yo'qoldi) -> AYNAN 1 test yiqildi: customerLinkedToActiveCustomerLogsInSuccessfullyWithCustomerAudience (200 kutildi, 403 AUDIENCE_MISMATCH keldi). AC3504 KILLED. (c) case AUDIENCE_CUSTOMER -> true -> 2 test yiqildi: customerUserWithNoLinkedCustomerAtAllGetsAudienceMismatch (AC3506) va customerLinkedToInactiveCustomerGetsAudienceMismatch (AC3505) - ikkalasi ham kutilgan. AC3506 KILLED. FIXTURE XILMA-XILLIGI: uch holat aniq ajratilgan - active=true + bog'langan, active=false + bog'langan, umuman customers qatori yo'q. "active" maydoni fixture da ikkala qiymatda ham bor, shu sabab shart har ikki yo'nalishda sinaladi (EP-07 dagi "hamma fixture bir xil" tuzog'i bu yerda yo'q). AC3507 REGRESSIYA (haqiqatan yurgizilgan, da'vo emas): 23 testdan supplier (partnerLinkedToActiveSupplier / InactiveSupplier / NoLinkedSupplier), employee (activeEmployeeLinked / suspendedEmployee / firedEmployee), driver (driverAudienceGatedByActiveIsDriverProfessionThreeStages, driverAudienceRequiresProfessionItselfActive), web (successfulWebLoginCreatesSession..., partnerUserRequestingWebAudience..., customerUserRequestingWebAudienceIsAlsoMasked) - hammasi yashil. Uchala mutant ham bu testlarga TEGMADI -> customer shoxobchasi izolyatsiyalangan. SPEC MUVOFIQLIGI (05_customers.md 2.1 / 3 / 4.1): shart AYNAN "customers.user_id = users.id BOR va customers.active = true". 2.1 jadvali: active=false -> "mobil bloklanadi"; 4.1 shu bilan mos. R12(c) (users.status='blocked') TASDIQLANMAGAN taklif - servis users.status ga TEGMAYDI, to'g'ri. V30__customers.sql: customers da deleted_at YO'Q (CROSS_CUTTING H - active toggle), demak faqat active tekshiruvi to'g'ri. QATLAM QOIDASI: adapter CustomerAudienceOwnershipService (customers moduli SERVISI) ga delegatsiya qiladi, CustomerRepository ga to'g'ridan-to'g'ri EMAS - EmployeeAudienceOwnershipService naqshi bilan bir xil. Servisda @Transactional(readOnly = true) bor. CROSS-CUTTING: LoginService.java diff da YO'Q (imzo/chaqiruv o'zgarmagan; audienceMatches -> audienceOwnershipPort.isEligible zanjiri butun); openapi/ va db/migration/ diff da YO'Q; yangi xato kodi yo'q (mavjud AUDIENCE_MISMATCH); AudienceOwnershipPort ning yagona bean'i hamon SupplierAudienceOwnershipAdapter; tenant_id / parol / token log yo'q. QAMROV YO'LI: testlar servis metodini emas, haqiqiy HTTP POST /api/v1/auth/login ni (TestRestTemplate, RANDOM_PORT, real Testcontainers Postgres) chaqiradi - port -> adapter -> login zanjiri uchdan-uchgacha sinalgan. Kichik eslatma (bloklovchi EMAS): AudienceOwnershipPort javadoc'ida v3 xatboshi hamon "customer - hamon false (05_customers kutilmoqda)" deb turadi, darhol keyingi v4 xatboshi uni to'g'rilaydi. Fayldagi mavjud versiya-tarixi naqshiga mos, xatti-harakatga ta'siri yo'q. Worktree /var/tmp/qa-EP-08-T06-S02 o'chirildi; asosiy daraxt git status toza, MUTANT/.orig qoldig'i 0.

qa-ep-08-t06-s02 qabul mezonini belgiladi

✓ `web`/`employee`/`driver`/`supplier` audience'lari uchun mavjud xatti-harakat O'ZGARMAGAN (regressiya testi)

qa-ep-08-t06-s02 qabul mezonini belgiladi

✓ `customers.user_id` biriktirilmagan `user_type='customer'` user 403 oladi

qa-ep-08-t06-s02 qabul mezonini belgiladi

✓ `active=false` mijozning akkaunti 403 AUDIENCE_MISMATCH oladi (mutatsiya testi: `active` sharti olib tashlansa test YIQILADI)

qa-ep-08-t06-s02 qabul mezonini belgiladi

✓ Faol mijoz akkaunti `audience='customer'` bilan muvaffaqiyatli login qiladi

coder-ep-08-t06-s02 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-08-t06-s02 izoh qoldirdi

CustomerAudienceOwnershipService qo'shildi (customers paketi): customers.user_id BOR va customers.active=true (05_customers.md §2.1/§4.1). SupplierAudienceOwnershipAdapter customer case ni shunga delegatsiya qiladi (repository emas, servis orqali). Port javadoc v4 sifatida yangilandi. LoginServiceIntegrationTestga 3 ta test qo'shildi (faol->200, active=false->403, bog'lanmagan->403); AC3505 mutatsiya qo'lda tasdiqlandi (active=true sharti CustomerRepository dan olib tashlanganda test qizil bo'ldi, keyin tiklandi va MUTANT grep bo'sh). 23/23 test yashil. LoginService imzosi/openapi/migratsiya tegilmadi.

coder-ep-08-t06-s02 qabul mezonini belgiladi

✓ `web`/`employee`/`driver`/`supplier` audience'lari uchun mavjud xatti-harakat O'ZGARMAGAN (regressiya testi)

coder-ep-08-t06-s02 qabul mezonini belgiladi

✓ `customers.user_id` biriktirilmagan `user_type='customer'` user 403 oladi

coder-ep-08-t06-s02 qabul mezonini belgiladi

✓ `active=false` mijozning akkaunti 403 AUDIENCE_MISMATCH oladi (mutatsiya testi: `active` sharti olib tashlansa test YIQILADI)

coder-ep-08-t06-s02 qabul mezonini belgiladi

✓ Faol mijoz akkaunti `audience='customer'` bilan muvaffaqiyatli login qiladi

coder-ep-08-t06-s02 fayllarni qayd etdi

5 ta fayl qayd etildi

coder-ep-08-t06-s02 yangiladi

Yangilandi: branch, commit_sha

coder-ep-08-t06-s02 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-08-t06-s02 ishga oldi

pm-agent yaratdi

`AudienceOwnershipPort` — customer implementatsiyasi (stub o'rniga)