Skip to main content

CDP Sprint 1 (2026-Q3) — Jira reconciliation, pass 10 (2026-07-17)

Jira reconciliation — recheck (2026-07-17, pass 10)​

Tenth pass — full sprint:reconcile run (qontak-docs @ deffa6b, past both the 30d8080 discipline fix and the f41ad1a assignment-drift fix) + fresh token-safe digest of sprint 21382, followed by the step-6b progress computation and same-pass propagation. Sprint is day 10 of 14.

Flow vitals (jira:digest --vitals --since 2026-07-16): 73 → 78 issues (+5 net — new BE items TF-3517/3518/3519/3525/3526; the count grew, no pull-outs); 32 done / 18 WIP / 28 to-do; 10 issues done since 2026-07-16; oldest in-progress: TF-3284/3285/3286 (Ghozi, Export BE, created 23d ago — but all three are In Testing and updated today, so age reflects lane dwell, not abandonment).

Progress computation (step 6b — computed, code-corroborated)​

Discipline-days accounting (QA slices were credited via their own QA board items on earlier passes; BE/FE tasks credit their discipline column only — no double count):

InitiativeNewly done (joined)Days addedNew burnupEvidence
Customer Segmentation (TF-2544)TF-3399 = Task 2.1 (FE 1.0) · TF-3400 = Task 2.2 (FE 1.5)+2.54.0 / 8.5 known = 47% (was 18%)qontak-customer-fe PR #454 (39973b9), PR #457 (6836122)
Mention User (TF-3184)TF-3325/3326/3327 = BE Tasks 2.1/2.2/2.3 (0.5+2.0+1.5) · TF-3331/3382 = FE Tasks 2.7/2.8 (1.0+1.5)+6.511.0 / 34 = 32% (was 13%)contact-service PR #860 (df04e07a); qontak-customer-fe PR #458/#463, #460/#462
Legacy Migration: CRM Activity Logs (TF-3182)TF-3465 = Task 2 (BE 1.0)+1.02.0 / 24.5 known = 8% (was 4%)contact-service PR #861 (3a6be927)

All 7 credited issues corroborated via code:evidence (7/7 merged to default). Written same-pass to the three dated status/2026-07-17.md files → README progress_* caches → roadmap ## Portfolio progress & forecast.

Not credited (flagged, unresolved):

  • Export (TF-3181) — 2 done of 13: TF-3494 (QA test-case doc, code-free, no task-id) and TF-3512 ("Expose component ExportCustomerDrawer", no task-id token — cannot join to the breakdown; corroborated in code but 0-credited). Count-note only; stays 0%. Momentum note: Ghozi's whole BE chain Tasks 2.1–2.5 (TF-3284–3288) is In Testing, Jovi's CHAT report-page items (TF-3429/3430) in flight — a large burnup step is queued behind the testing lane.
  • Team Owner (TF-3185) — 1 done of 18 (TF-3491, QA doc, code-free). No repo task-breakdown (F-5) → count-note only, stays 0%. 4 of Azani's FE tasks in flight (2 In Testing).
  • Create Ticket (TF-3359) — 1 done of 1 (TF-3495, QA doc, code-free). Stays 0%; the board still has zero BE/FE implementation items (engine coverage-gap, part of F-1).
  • Mention User Mobile — 6 done Mobile items (TF-3290–3294, TF-3506) outside breakdown scope (F-7) → 0; TF-3292/3293 additionally have no code trace (plausibly code-free verification tasks — unstated). Phase-1 FE tasks 1.1–1.4 (7.0 FE d) have no board issues at all while the Phase-2 wiring built on them is Done — real progress invisible to the burnup; new F-17.
  • Customer Segmentation datamart hardening — now 5 done unpriced BE items (TF-3507/3508/3511 + new TF-3518/3519); F-8 scope grew this pass.
  • Buckets: TF-3477 (Adhoc) 4 board-done + TF-3478 READY TO DEPLOY; TF-3500 A4/TF-3499 done, tracker in-review pending Hendry's QA gate — engine emitted no bucket-tracker-drift row, so the trackers match; rollups stay engine---fix-owned.

Prior findings re-tested​

  • F-1 coverage-gap — STILL OPEN (8th pass): CALM Tasks 3–9 (TF-3466–3472) still absent; TF-3465 (Task 2) progressed READY TO DEPLOY → Done. Create Ticket web track (TF-3426/3427/3428) still absent (engine re-confirmed: TF-3359's single sprint issue is non-dev). Owner: TPM.
  • F-3 data-quality — STILL OPEN (8th pass): TF-3459 (Won't Fix duplicate of TF-3464) still on the board; 0-credited as always. Owner: TPM (Jira hygiene).
  • F-4 coverage-gap CEBE — ⛔ ESCALATED, STILL OPEN (8th pass): zero CEBE board items; no RFC file in cdp/customer-event-based-engine-cebe/rfcs/. 8 passes, zero movement — CEBE is de facto not being worked this sprint. Owner: Julio Jeffer / PM.
  • F-5 status-progress — ⛔ ESCALATED, STILL OPEN (8th pass): rfc-team-owner-field-and-team-permission.task-breakdown.md still missing in the repo while TEAM-S* Jira items exist; sprint now 10 of 14 days elapsed and Azani has 2 items In Testing that can never credit man-days without it. Owner: Ghozi / DRI.
  • F-6 assignment-drift engine false positive — ✅ RESOLVED pass 10: upstream fix landed (qontak-docs f41ad1a "kill assignment-drift name-match false positives"); this pass's worklist emits no assignment-drift row. Closed as fixed-upstream.
  • F-7 TF-3506 out-of-scope Mobile — ⛔ ESCALATED, STILL OPEN (3rd recheck): unchanged; now folded into the wider Mobile-scope call (6 done Mobile items, 0 credited). Owner: DRI/PM — retro-cost into the breakdown or declare out-of-band. Decision still pending after 3 rechecks.
  • F-8 scope-watch datamart hardening — ⛔ ESCALATED, STILL OPEN (3rd recheck), grew: 3 → 5 unpriced done BE items (added TF-3518/3519, both Done). The protected P1 commitment keeps absorbing silent scope. Owner: DRI — confirm in-scope + retro-cost.
  • F-10 off-plan-load Zhelia — STILL OPEN (2nd recheck → ⛔ ESCALATED): engine re-emitted the row (TF-3478 READY TO DEPLOY; not in roster.json, no capacity.md row). Second still-open recheck ⇒ escalate per the carry-forward rule. Owner: TPM — decision needed: add Zhelia to roster.json (discipline PM) or record as deliberately out-of-band management capacity in capacity.md; routed home = capacity.md either way.
  • F-16 epic-wiring-drift TF-3521 — STILL OPEN (residual sub-item): TF-3524 still the Epic's only sprint item (In Progress, Izzul); no volume growth, so no initiative folder/roadmap row yet. Owner: TPM (watch). Engine still emits the off-map row by design (the Deviations entry is the accepted repo-side home until/unless registered).

New findings​

  • F-17 status-progress (Mention User) — NEW: Phase-1 FE tasks 1.1–1.4 (7.0 FE days) have no board issues while the Phase-2 wiring that depends on them (2.7/2.8) is Done and merged. De facto complete, but uncreditable (no board+code join). Owner: TPM / Jovi — backfill the Phase-1 items (route: sprint-jira-sync) so ~7 FE days of real progress lands in the burnup.
  • F-18 engine limitation (informational) — the worklist's roster-mismatch row ("Izzul has a plan queue but 0 issues in sprint") is a knock-on of F-16: TF-3524 is assigned to Muhammad Izzul in sprint 21382, but its off-map Epic (TF-3521) excludes it from the engine's per-person coverage join. Not a real gap; report upstream to sprint-reconcile.mjs (count off-map-epic issues in per-assignee coverage). No repo action.
  • Blocked watch (no new id — feeds F-1's owner anyway): TF-3401 (Segmentation Task 2.3) moved In Progress → Blocked on OQ-FE-2 with the 07-21 commitment 4 days out — recorded in the 2026-07-17 status file's blockers.

Propagated this pass (same-pass, step 6b)​

  • customer-segmentation/delivery/status/2026-07-17.md — 47%, TF-3401 Blocked note, F-8 note.
  • notes-mention-user/delivery/status/2026-07-17.md — 32%, F-7/F-17 notes.
  • legacy-migration-crm-activity-logs/delivery/status/2026-07-17.md — 8%, F-1 note.
  • README progress_* caches (3) + roadmap ## Portfolio progress & forecast (3 rows).
  • Ledger rewritten in place in the sprint doc; prior pass file (pass 9) flipped to archived.
  • npm run lint:delivery run after the writes (see ledger note).