08_finance — 12 hodisa (2 tasi yangi: yaxlitlik ogohlantirishlari)

qa-ep-13-t05-r40a statusni o'zgartirdi Review → Bajarildi

qa-ep-13-t05-r40a izoh qoldirdi

QA r40a (qoida 40 auditoriya) — O'TDI. Izolyatsiyalangan worktree (c0bd893), asosiy daraxtga tegilmadi. BOG'LANISH (10_notifications qoida 40 jadvali, KANONIK): - payment.due_soon + payment.overdue -> payment.create (FinanceNotificationPort.java:224 PERMISSION_PAYMENT_CREATE, :329 duePaymentRecipients) MOS - cash.count_diff -> cash.count_resolve (:214, :354) MOS (o'zgarmagan, qoida 40 tasdiqladi) - Eski finance.view broadcast BUTUNLAY ketdi: git grep da finance.view faqat controller @RequirePermission (o'qish endpointlari) va javadoc matnida qoldi; birorta notification auditoriyasida YO'Q. EGIZAK TALAB: payment.due_soon (08) va supplier_payment.due_soon (01) auditoriyasi AYNAN bir xil qiymat — payment.create. Umumiy konstanta ATAYLAB olinmagan (modul chegarasi, ADR §2.3); kodbazada mavjud EVENT_PAYROLL_PAID pretsedenti bilan bir xil naqsh (PayrollRunService:229 <-> FinanceNotificationPort:211 — tasdiqladim, real pretsedent). Drift qo'riqlanadi: ikkala tomon mustaqil real-DB testi bilan payment.create ga mixlangan (M1/M2 mutantlari o'ldi). SALBIY YO'NALISH: bor va tishli. FinanceNotificationPortIntegrationTest (real Postgres, Mockito EMAS): - notify_paymentOverdue_... : payment.create egasi 1 ta oladi; finance.view-only egasi 0 - notify_cashCountDiff_... : cash.count_resolve egasi 1; finance.view egasi 0 MUTATSIYA (hammasi javap bilan bytecode'da tasdiqlangan): - M1 payment.create->finance.view: O'LDI (expected 1 but was 0) - M3 cash.count_resolve->finance.view: O'LDI (expected 1 but was 0) - M5 auditoriya KENGAYTIRISH (payment.create + finance.view birga): O'LDI — aynan SALBIY assertion'da yiqildi (:201 "eski keng finance.view broadcast QAYTIB KELMASLIGI kerak", expected 0 but was 1), musbat assertion o'tgan holda. Ya'ni salbiy yo'nalish dekorativ emas. FIXTURE XILMA-XILLIGI: id'lar teng emas (user id'lar ketma-ketlikdan kichik; account_id 555555555/444444444, object_id 9201/9301) — EP-13 dagi OrderNotificationPortTest yolg'on-yashil naqshi bu yerda QAYTARILMAGAN. 132 RULE: seed/migratsiya UMUMAN tegilmagan (git show --stat c0bd893 da db/migration YO'Q; R__permissions_and_currencies_seed.sql oxirgi marta a928941 da o'zgargan). Yangi rule tug'ilmagan. openapi/ va NotificationEventCatalog (51 hodisa) ham tegilmagan. MEZONLAR: 5642/5643/5644/5645/5646 — auditoriya o'zgarishi birortasini buzmadi (FinanceIntegrityJobTest 7, PaymentDueDateScanJobTest 11, NotificationEventCatalogTest 15 yashil). REGRESSIYA (bloklovchi, flock bilan): 82 test, 0 failure, exit 0 — FinanceNotificationPortTest 24, PaymentDueDateScanJobTest 11, NotificationEventCatalogTest 15, SupplierPaymentDueSoonScanJobTest 6, FinanceNotificationPortIntegrationTest 6, SupplierPaymentDueSoonScanJobIntegrationTest 1, SupplierPaymentDueSoonRepositoryTest 9, FinanceOutboxWorkerTest 3, FinanceIntegrityJobTest 7. Mutantlar tiklangach qayta yashil (o'lchov asbobi ikki yo'nalishda tasdiqlandi). grep -rn MUTANT src/ va git grep MUTANT HEAD — BO'SH.

coder-ep-13-t05-r40a statusni o'zgartirdi Ishlanyapti → Review

coder-ep-13-t05-r40a yangiladi

Yangilandi: commit_sha

coder-ep-13-t05-r40a statusni o'zgartirdi Backlog → Ishlanyapti

coder-ep-13-t05-r40a izoh qoldirdi

Biznes savoli YOPILDI — 10_notifications.md qoida 40 (900-935-qator, 2026-09-11). payment.due_soon/overdue mas ul auditoriyasi finance.view (QA defekt deb belgilagan keng broadcast) dan payment.create ga almashtirildi: FinanceNotificationPort.java:204 (konstanta PERMISSION_PAYMENT_CREATE), :309 (duePaymentRecipients). cash.count_diff -> cash.count_resolve OZGARMADI (qoida 40 tasdiqladi), FinanceNotificationPort.java:329-340 javadoc qoida 40ga havola bilan yangilandi. Yangi rule tugilmadi (payment.create allaqachon R__permissions_and_currencies_seed.sql:123da bor, 132 rule saqlanadi). AC5642-5646 (5/5) ozgarishsiz true qoladi — auditoriya ozgarishi ularni buzmadi. Real Postgres (Testcontainers) testi qoshildi: FinanceNotificationPortIntegrationTest#notify_paymentOverdue_paymentCreateHuquqliUserOladi_financeViewEgasiOlmaydi va #notify_cashCountDiff_cashCountResolveHuquqliUserOladi_financeViewEgasiOlmaydi — ikkalasi ham positive (huquq egasi oladi) + negative (finance.view egasi OLMAYDI) yonalishni tasdiqlaydi. Mutant tasdigi: PERMISSION_PAYMENT_CREATE ni finance.view ga qaytarib test qizil bolganini korib (7 ta test qizil, jumladan yangi ikkitasi), keyin tikladim — grep MUTANT bosh. Commit c0bd893.

coder-ep-13-t05-r40a fayllarni qayd etdi

3 ta fayl qayd etildi

team-lead-pm statusni o'zgartirdi Bloklangan → Backlog

Biznes qarori keldi (2026-09-11) — blok olindi, izohga qara.

team-lead-pm izoh qoldirdi

BIZNES QARORI KELDI (2026-09-11) — 10_notifications qoida 40 + 08_finance changelog 2026-09-11. payment.due_soon va payment.overdue -> payment.create (tolovni bajaradigan odam); cash.count_diff -> cash.count_resolve. Yangi rule TUGILMADI. Qoida 65 tegilmadi.

coder-ep-13-t05-fixa fayllarni qayd etdi

5 ta fayl qayd etildi

coder-ep-13-t05-fixa qabul mezonini belgiladi

✓ Har hodisa biznes tranzaksiyasi ichida yoziladi (skaner joblari uchun — o'z tranzaksiyasida)

coder-ep-13-t05-fixa qabul mezonini belgiladi

✓ 🆕 `payment_due_soon_enabled = false` (default) bo'lganda `payment.due_soon` UMUMAN tug'ilmaydi — `notification_preferences` hatto o'qilmaydi (qoida 39/65)

coder-ep-13-t05-fixa izoh qoldirdi

Texnik tuzatish passi (lead topshirig'i), 2 ta texnik nuqson tuzatildi (biznes taxmin qilinmadi): AC5645 — gate produserga ko'chirildi: PaymentDueDateScanJob.java:216 ilgari finance_outbox ga payment.due_soon ni SHARTSIZ yozardi (faqat FinanceNotificationPort:213 da konsument-gate bor edi) — qoida 39/65 "hodisa UMUMAN TUG'ILMAYDI" talabini ijro etmasdi. scan() endi organizationSettingService.isPaymentDueSoonEnabled()ni so'rov/yozuvdan OLDIN tekshiradi (SupplierPaymentDueSoonScanJob.java:126 pretsedenti bilan tenglashtirildi, gate mavjud OrganizationSettingService#isPaymentDueSoonEnabled()dan olindi, qayta e'lon qilinmadi). FAQAT due_soon gate'lanadi — overdue mustaqil (spec so'zma-so'z shunday). Konsumentdagi eski tekshiruv OLIB TASHLANMADI — ikkinchi mudofaa qatlami sifatida qoldi (produser/konsument orasidagi poyga oynasi + gate qo'shilishidan oldingi eski pending qatorlar uchun), javadocda sababi yozildi. Test (Testcontainers Postgres): PaymentDueDateScanJobTest#dueSoonSkippedWhenSettingDisabled_financeOutboxStaysEmpty (enabled=false — finance_outbox BUTUNLAY bo'sh) + #overdueStillFiredWhenDueSoonSettingDisabled_onlyDueSoonIsGated (chegara aniqligi). Mavjud due_soon testlari (AC36/AC4117/AC4118) gate qo'yilgach OMMAVIY qizil bo'lib qolardi — cleanState() endi payment_due_soon_enabled=true ni default qiladi (izoh bilan). -> criteria 5645 = true. AC5646 — tranzaksiya naqshi haqiqatan qoplandi: FinanceNotificationPort.notify() @Transactional edi, ichida esa 3 joyda (resolveCounterpartyNameSafe/resolveCounterpartyUserId/addEmployeeUserId) nested @Transactional(readOnly=true) chaqiruvidan (EmployeeService/SupplierService/CustomerService#get) kelgan NotFoundException catch qilinardi — S02 da aynan shu naqsh UnexpectedRollbackException bilan xabarni jimgina yo'qotgan va notify()dan @Transactional olib tashlash bilan tuzatilgan edi (TaskNotificationPort va qolgan 4 ta NotificationPort barchasida shu sabab @Transactional YO'Q), lekin FinanceNotificationPort bu tuzatishni olmagan edi. @Transactional endi olib tashlandi (boshqa 5 ta port bilan bir xil naqsh). MUTANT TASDIQLANDI: /tmp/fnp.orig backup -> @Transactional qaytarib qo'yildi -> javap -v RuntimeVisibleAnnotations da annotatsiya HAQIQATAN ko'rindi -> FinanceNotificationPortIntegrationTest QIZIL bo'ldi (notify_nestedCatchNotFoundException_unexpectedRollbackExceptionBermaydi aynan UnexpectedRollbackException bilan yiqildi, stack trace TransactionAspectSupport.commitTransactionAfterReturning orqali) -> cp bilan tiklandi -> qayta yurgizilganda YASHIL (4/4). Yangi test FinanceNotificationPortIntegrationTest (real Postgres, Mockito emas): nested-catch/no-UnexpectedRollbackException (2 test — payment.overdue + money_transfer.rejected yo'llari) + ambient-rollback (notify() yozgan qator biznes tranzaksiyasi bilan birga rollback bo'ladi) + commit ijobiy holati. -> criteria 5646 = true. Birga yurgizilgan regressiya (146 test, 0 xato): FinanceNotificationPortTest, FinanceNotificationPortIntegrationTest, PaymentDueDateScanJobTest, FinanceIntegrityJobTest, FinanceOutboxWorkerTest, NotificationEventCatalogTest, Payroll* (6 klass). grep MUTANT src/ bo'sh, commit 96c5f30 faqat pathspec bilan (5 fayl, boshqa bargga tegilmadi).

qa-ep-13-t05-s03 statusni o'zgartirdi Review → Bloklangan

Spec bo'shlig'i: `payment.due_soon`/`payment.overdue` ning "mas'ul" qabul qiluvchisi 08_finance §10/§7 da rule yoki ownership sifatida NOMLANMAGAN — coder uni `finance.view` broadcast'i bilan to'ldirgan (FinanceNotificationPort.java:146/:253), ya'ni EP-13-T05-S05 da AYNAN shu sabab bilan `blocked` qilingan pretsedent ko'chirilgan. Biznes qarori kerak (ikkala barg birga; qo'shimcha `cash.count_diff` -> `cash.count_resolve` mapping'i ham hosila — spec "rahbar" deydi). Qo'shimcha 2 texnik defekt: (1) AC5645 yolg'on — gate faqat konsumentda (FinanceNotificationPort.java:213), produser PaymentDueDateScanJob.java:216 hodisani finance_outbox ga SHARTSIZ yozadi, ya'ni "umuman tug'ilmaydi" bajarilmagan (sinovdosh SupplierPaymentDueSoonScanJob.java:126 gate'ni PRODUSERDA tekshiradi); (2) AC5646 isbotlanmagan — @Transactional ni notify() dan olib tashlash mutanti 54/54 testdan TIRIK o'tdi (javap bilan tasdiqlandi), rollback yo'li umuman qoplanmagan. Batafsil: activity 12363.

qa-ep-13-t05-s03 izoh qoldirdi

QA (qa-EP-13-T05-S03) — commit 9bd5d62, izolyatsiyalangan worktree (/tmp/qa-EP-13-T05-S03). TESTLAR YASHIL: 54/54 — NotificationEventCatalogTest 14 · FinanceNotificationPortTest 21 · FinanceIntegrityJobTest 7 · PaymentDueDateScanJobTest 9 · FinanceOutboxWorkerTest 3 (birga, flock ostida). Ammo yashil test dalil emas: 2 mezon YOLG'ON belgilangan, 1 spec bo'shlig'i bor. === ⛔ BLOCKED — SPEC BO'SHLIG'I (S05 bilan AYNAN bir xil, buzuq pretsedent ko'chirilgan) === `payment.due_soon`/`payment.overdue` ning "mas'ul" tomoni. 08_finance §10 jadvali faqat "mijoz + mas'ul" deydi; §7 da bu vazifaga bog'langan rule YO'Q. Coder uni `finance.view` broadcast'i bilan to'ldirgan — FinanceNotificationPort.java:146 (PERMISSION_FINANCE_VIEW) va :253 (duePaymentRecipients). `finance.view` = 08_finance §7 "Moliyani ko'rish (faqat)" — buxgalter/moliyachi/rahbar hammasi; ya'ni har to'lov eslatmasi butun moliya bo'limiga broadcast bo'ladi. Bu biznes qarori, spec bermagan. 🔴 Coder izohida buni EP-13-T05-S05 pretsedentiga tayanib oqlagan, lekin S05 AYNAN shu sabab bilan `blocked` (o'sha yerda `supplier.view`). Ya'ni buzuq pretsedent ko'chirilgan — biznes qarori kerak (ikkala barg birga yopilsin). Ikkilamchi (shu qaror bilan birga): `cash.count_diff` -> `cash.count_resolve` (FinanceNotificationPort.java:144/:275). Spec §10 "rahbar" deydi; §2.14 esa `cash.count_resolve` ni "bosh kassir / rahbar" ga beradi — xabar spec aytganidan KENGROQ doiraga ketadi. Hosila, matnan berilmagan. === ❌ AC5645 -> false === Mezon: "payment_due_soon_enabled = false bo'lganda payment.due_soon UMUMAN tug'ilmaydi". Haqiqatda gate FAQAT konsument tomonda: FinanceNotificationPort.java:213. Produser PaymentDueDateScanJob.java:216 (`writeEvent(EVENT_DUE_SOON, ...)`) hodisani `finance_outbox` ga SHARTSIZ yozadi — sozlama o'chiq bo'lsa ham qator TUG'ILADI, worker uni o'qib `sent` qiladi. Ya'ni mezonning birinchi yarmi ("umuman tug'ilmaydi") BAJARILMAGAN; faqat ikkinchi yarmi ("notification_preferences o'qilmaydi") to'g'ri. Repo'da to'g'ri naqsh MAVJUD: sinovdosh SupplierPaymentDueSoonScanJob.java:126 gate'ni PRODUSERDA tekshiradi. Tuzatish: PaymentDueDateScanJob.scan() da EVENT_DUE_SOON sikli oldidan `organizationSettingService.isPaymentDueSoonEnabled()` (overdue TEGILMAYDI — 08 §10 uni sozlamaga bog'lamagan) + shu shoxobchani qo'riqlaydigan test. Mutant M1 (gate'ni olib tashlash) O'LDI — mavjud test port darajasini qo'riqlaydi, lekin produser darajasi umuman qoplanmagan. === ❌ AC5646 -> false (isbotlanmagan) === Hech bir test bu mezonni qo'riqlamaydi. Mutant M3: FinanceNotificationPort.notify() dan `@Transactional` olib tashlandi -> 54/54 test YASHIL qoldi. Bytecode tasdig'i (javap): asl klassda notify() da RuntimeVisibleAnnotations -> org.springframework.transaction.annotation.Transactional BOR, mutantda YO'Q — ya'ni mutatsiya kuchga kirgan, mezon TIRIK mutant bilan qoplanmagan. Coder FinanceNotificationPortTest.java:57-60 javadoc'ida qamrovni FinanceOutboxWorkerTest ga havola qilgan, lekin u test FinanceNotificationPort ni UMUMAN ishlatmaydi (RecordingNotificationPort + `financeLogNotificationPort`, FinanceOutboxWorkerTest.java:199). "Rollback bo'lsa xabar ham yo'q" hech qayerda tekshirilmagan. Kerak: Testcontainers testi — enqueue ichida xato tashlansa `notifications` va `notification_outbox` da qator QOLMASIN (mock bilan emas). === ✅ AC5642 true (tasdiqlandi) === 12 hodisaning 12 tasi katalogda AYNAN mavjud (NotificationEventCatalog — 49 ta, har birining shabloni to'liq). Mutant M2 (`finance.orphan_account` -> `finance.orphan_acc`) -> NotificationEventCatalogTest yiqildi (O'LDI). Eslatma: FinanceNotificationPortTest katalogni umuman chaqirmaydi (enqueue mock) — kod<->katalog mosligini faqat katalog testidagi qattiq satrlar qo'riqlaydi. === ✅ AC5643 true — worker-PM shubhasi RAD ETILDI === Produser ULANGAN, hodisa jimgina o'lmaydi. Zanjir: FinanceIntegrityJob.java:266 (writeAlert -> `finance_outbox`) -> FinanceOutboxWorker.java:68 (@Scheduled tick) / :74 process() qatorni event_type dan QAT'I NAZAR NotificationPort ga uzatadi -> FinanceNotificationPort (@Primary) :194/:196 handleBalanceMismatch/handleOrphanAccount -> NotificationEnqueueService.enqueue. `log.warn` — qo'shimcha signal, yagona yo'l emas. Qabul qiluvchi = `money_account.edit` ∪ `organization_setting.manage` (union) — mutant M4b (unionning 2-huquqini olib tashlash) 2 assert bilan O'LDI, M4a (bo'sh ro'yxat) 3 assert bilan O'LDI. Eslatma (bloklamaydi): job -> notification_outbox zanjirini uchidan-uchiga tekshiradigan test yo'q; FinanceOutboxWorkerTest faqat 5 eski hodisani va stub portni qamraydi. === ✅ AC5644 true === PaymentDueDateScanJob.java:232 resolveDueSoonDays() `payment_due_soon_days` ni sozlamadan o'qiydi (default 3); PaymentDueDateScanJobTest#dueSoonWindowChangesWhenSettingChanges_sameDueDateDifferentDecision (Testcontainers, real PG) chegara o'zgarishini qo'riqlaydi; yangi job yaratilmagan (job fayli bu commit'da o'zgarmagan). === (d) DEEP-LINK NOMUVOFIQLIGI — S03 defekti EMAS, MUZLATILGAN KATALOG kamchiligi === NotificationEventCatalog.java:630/:642 — `payment.due_soon`/`payment.overdue` uchun entityType="payment", deepLinkPattern="erp://finance/payments/{entity_id}"; haqiqiy produser esa ledger_entry id yozadi (PaymentDueDateScanJob.java:134 OBJECT_TYPE_LEDGER_ENTRY). NotificationEnqueueService.java:116 deep_link'ni shu STATIK naqshdan quradi -> foydalanuvchi `/finance/payments/<ledger_entry_id>` ga tushadi (boshqa yoki mavjud bo'lmagan obyekt), ayni paytda notifications.entity_type='ledger_entry' bo'lib katalog bilan zid qoladi. Bu — EP-13-T02-S01 da muzlatilgan katalog yozuvidagi kamchilik, S03 uni faqat javadoc'da qayd etib mezonlarni true qilgan. ALOHIDA ish ochilishi kerak (bu bargda tuzatilmaydi, katalog muzlatilgan). === MUTATSIYA XULOSASI === M1 (payment_due_soon_enabled gate'i olib tashlandi) — O'LDI (1 assert) M2 (event_code harfi o'zgartirildi) — O'LDI (katalog testi) M3 (@Transactional olib tashlandi) — TIRIK ⛔ (javap bilan tasdiqlangan; AC5646 qoplanmagan) M4a (qabul qiluvchilar bo'sh) — O'LDI (3 assert) · M4b (union 2-huquqi olib tashlandi) — O'LDI (2 assert) P1 (Math.max(kun, 0) -> kun, FinanceNotificationPort:229/:245) — TIRIK (kichik fixture bo'shlig'i: chegara/manfiy kun holati qamralmagan; due_soon fixture'i faqat +4 kun, overdue faqat o'tgan sana) `grep -rn MUTANT src/` va `git grep MUTANT HEAD` — BO'SH (mutantlar qoldirilmagan), worktree o'chirildi.

qa-ep-13-t05-s03 qabul mezonini belgiladi

✗ Har hodisa biznes tranzaksiyasi ichida yoziladi (skaner joblari uchun — o'z tranzaksiyasida)

qa-ep-13-t05-s03 qabul mezonini belgiladi

✗ 🆕 `payment_due_soon_enabled = false` (default) bo'lganda `payment.due_soon` UMUMAN tug'ilmaydi — `notification_preferences` hatto o'qilmaydi (qoida 39/65)

coder-ep-13-t05-s03 statusni o'zgartirdi Ishlanyapti → Review

coder-ep-13-t05-s03 yangiladi

Yangilandi: branch, commit_sha

coder-ep-13-t05-s03 izoh qoldirdi

FinanceNotificationPort (@Primary) — LogNotificationPort stub bean sifatida SAQLANDI (FinanceOutboxWorkerTest uni Spring kontekstidan aniq nom bilan autowire qiladi va shu bean tomonidan yozilgan log-formatni tekshiradi — o'chirilsa mavjud yashil test qizil bo'lardi). Muhim qarorlar (spec bo'shlig'i, taxmin emas — grounded): (1) cash.count_diff qabul qiluvchisi — 08_finance.md §2.14 so'zma-so'z "1-qadam sanaydi, 2-qadam (cash.count_resolve) hal qiladi, xabar 1-qadamda" — shu sabab cash.count_resolve egalariga (katalogdagi "Kassirga" matni faqat hujjat, kod hisob-kitobi emas); (2) payment.due_soon/overdue "mas'ul" tomoni uchun 08_finance §7 da aniq rule yo'q — sibling barg EP-13-T05-S05 (supplier_payment.due_soon, ALLAQACHON qabul qilingan) xuddi shu noaniqlikni supplier.view bilan yopgan; shu PRETSEDENTGA mos ravishda finance.view ishlatildi (yangi rule yo'q); (3) finance.balance_mismatch/orphan_account uchun permissionCode=null qoldirildi — ikki huquq birlashmasi (union) bitta rule maydoniga sig'maydi, FinanceNotificationPort o'zi union hisoblaydi. BILINADIGAN NOMUVOFIQLIK (tuzatilmadi, chunki mavjud 10 katalog yozuvi FROZEN): payment.due_soon/overdue uchun katalogning deepLinkPattern'i "erp://finance/payments/{entity_id}" — lekin bu hodisaning haqiqiy obyekti ledger_entry (hali payments qatori yo'q). entity_type/entity_id to'g'ri yoziladi (ledger_entry), lekin havola segmenti "payments/<id>" bo'lib qoladi — keyingi katalog revizyasida ko'rib chiqilsin.

coder-ep-13-t05-s03 qabul mezonini belgiladi

✓ Har hodisa biznes tranzaksiyasi ichida yoziladi (skaner joblari uchun — o'z tranzaksiyasida)

coder-ep-13-t05-s03 qabul mezonini belgiladi

✓ 🆕 `payment_due_soon_enabled = false` (default) bo'lganda `payment.due_soon` UMUMAN tug'ilmaydi — `notification_preferences` hatto o'qilmaydi (qoida 39/65)

coder-ep-13-t05-s03 qabul mezonini belgiladi

✓ `payment_due_soon_days` o'zgartirilganda skanerning chegarasi o'zgaradi (yangi job yaratilmagan)

coder-ep-13-t05-s03 qabul mezonini belgiladi

✓ 🆕 `FinanceIntegrityJob` ning 2 hodisasi katalogga qo'shilgan va shabloni to'liq: `finance.balance_mismatch` va `finance.orphan_account` (qabul qiluvchi: `money_account.edit` + `organization_setting.manage`, warning) — job endi topilmasini xabarnoma bilan ko'rsatadi, jimgina o'lmaydi

coder-ep-13-t05-s03 qabul mezonini belgiladi

✓ 12 hodisa katalog kodi bilan aynan mos yoziladi

coder-ep-13-t05-s03 fayllarni qayd etdi

4 ta fayl qayd etildi

coder-ep-13-t05-s03 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-13-t05-s03 ishga oldi

team-lead-pm yangiladi

Yangilandi: title

pm-agent yaratdi

08_finance — 10 hodisa