Skip to main content

Chatbot Sprint 1 (2026-Q3) — Jira reconciliation, pass 4 (2026-07-15)

Jira reconciliation — recheck (2026-07-15, pass 4)​

Full sprint:reconcile --team chatbot --json re-run, owed since pass 3's targeted Epic-relink fix. Sprint 21473 now holds 55 issues (up 1 from pass 2/3's 54 — the deterministic engine's count reflects the parent-field edits as re-parents, not new/removed issues). Worklist: 4 deterministic + 3 editorial findings. Code-evidence join checked 2 board-done issues: 0/2 code-corroborated (same 2 as pass 2 — no new done issues since).

Prior findings re-tested:

  • F-3 / F-17 (BOT-4602 Refiner Epic mis-links) — CONFIRMED FIXED. No coverage-gap or roster-mismatch row against BOT-4602, Farras Herdicho, or Samudra Linggar appeared this pass — and this time that absence is corroborated by a direct spot-check (below), not taken on faith per pass 2's mistake. The 7 re-parented issues (BOT-4574 + BOT-4610/4611/4612/4613/4614/4651) are reading clean.
  • F-1 coverage-gap (Google Calendar / BOT-4482) — RESOLVED, verified directly. Spot-check JQL (sprint = 21473 AND ("Epic Link" = BOT-4482 OR parent = BOT-4482)) returns 2 issues, both Tito Amanda (QA): BOT-4649 "QA Creation Testcases — Google Calendar Integration" and BOT-4643 "QA Test — Google Calendar OAuth & Booking Verification". The Epic is no longer at zero. However this exposes a narrower, real gap that survives the fix — see new finding below (Baghiz roster-mismatch).
  • F-2 coverage-gap (Impact Report / BOT-4568) — STILL OPEN. Still 1 non-dev issue, still 0 BE/FE implementation tasks.
  • F-6 roster-mismatch (Izzul QA rows unfiled) — STILL OPEN, now surfaced generically by the engine rather than by initiative name (no BOT-4602/BOT-4568/BOT-3351-specific QA issues for Izzul in sprint 21473).
  • F-8 (upstream engine norm() dotted-slug bug) — STILL OPEN, unverified from this repo (upstream qontak-docs issue).
  • F-14 (BOT-4618 code-evidence-gap) — STILL OPEN, unchanged: Won't Fix, no code trace (search still partial — qontak-designer/hub unchecked).
  • F-15 (BOT-4653 code-evidence-gap) — STILL OPEN, unchanged: Done, no code trace (search still partial — notification-service/qontak-designer unchecked).
  • F-16 (stale P3 plan text) — not machine-checked by the engine (doc-prose finding); still open per the sprint doc's own text pending the sprint-planner amend routed in pass 2.

New findings from the 2026-07-15 pull:

  • F-18 roster-mismatch (deterministic, new): Baghiz Firdausa shows 0 issues assigned in sprint 21473. Spot-checked directly: the Google Calendar Epic (BOT-4482) now has 2 QA issues (both Tito), but zero FE build issues — Baghiz's planned queue work (production FE exposure for Google Calendar row #2, AI Agent Impact Report FE foundation #3, AI Agent Testing FE/harness notes #4) has no Jira presence at all. This is a genuine gap, distinct from F-1: filing the QA test-case tasks did not also file Baghiz's FE build tasks. Owner: PM/TPM — file via sprint-jira-sync (sprint mode).
  • F-19 roster-mismatch (deterministic, new, informational): Dimas Fauzi Hidayat shows 0 issues assigned. Checked chatbot/delivery/roster.json directly — already documented there: "Non-engineering discipline (PM/TPM, DRI on every chatbot initiative)... assignment-drift/ off-plan-load findings against him route to a TPM read, not a staffing-mirror edit." This is the same class as pass-2/3's F-7 — expected, no action. The engine re-surfaces it every pass because its roster-mismatch check doesn't consult the _note field; not a bug to report upstream (the note itself says findings against him route to a read, which this is), just a recurring informational row. Folding into F-7 rather than treating as new drift.

This pass did NOT apply any staffing/coverage fix — F-18/F-2/F-6 route to sprint-jira-sync per the taxonomy; F-14/F-15 route to assignee/DRI board fixes; none of those are repo edits this skill makes unilaterally.

Downstream propagation worklist​

#FindingCanonical artifact to reconcileOwning tool / skill
1F-2 Impact Report 0 BE/FE dev work (still open)File BOT-4568-scoped BE/FE Tasks into sprint 21473sprint-jira-sync (sprint mode)
2F-6 Izzul QA rows unfiled (still open)File QA drafting Tasks under BOT-4602/BOT-4568/BOT-3351 for Izzulsprint-jira-sync
3F-8 engine false-positive (still open, upstream)No repo edit; report norm() gap to qontak-docsUpstream issue against sprint-reconcile.mjs
4F-14 BOT-4618 Won't Fix, no code trace (still open)Confirm code-free status or find the merge; DRI callassignee / DRI board fix
5F-15 BOT-4653 Done, no code trace (still open)Find the merge/PR reference or revert board statusassignee / DRI board fix
6F-16 stale P3 doc text (still open)Amend Initiative-index cell + Deviations prosesprint-planner (amend mode)
7F-18 Baghiz Firdausa 0 board presence (new)File Baghiz's FE build Tasks (Google Calendar prod exposure, Impact Report FE shell, AI Agent Testing FE notes) into sprint 21473sprint-jira-sync (sprint mode)

Always run npm run lint:delivery (DOCS_ROOT pointed at this repo) after any propagation edit.