Skip to main content

Pass 5 — 2026-07-15

Trigger: ad hoc request — "check chatbot active sprint, reconcile missing/incorrect story/epic link." Ran sprint:reconcile --team chatbot --json (sibling qontak-docs @ deffa6b) against live sprint 21473.

Flow vitals: sprint 21473 now 61 issues (pass 4: 55; pass 1 baseline: 22). 19 findings emitted (8 deterministic, 11 editorial).

Epic/Story wiring — the requested focus​

Genuinely new, real drift:

  • F-20 epic-wiring-drift (new) — BOT-4662 "26Q3 Chatbot - CRM Actions: Custom Fields" is a real Epic with 4 children (BOT-4668/4669/4670/4673), but it is untracked in the sprint doc — the plan still carries this as "Placeholder — CRM Deals Custom Field Support (Epic TBD)" for Baghiz (#1) and Agus (#2). This resolves the TBD: the Epic now exists. Owner: PM/TPM — confirm BOT-4662 is the canonical Epic for this initiative, then update the sprint doc's placeholder rows (Epic TBD → BOT-4662) and, once an initiative folder/README is created for it, set jira_epic: BOT-4662 there per the standard convention.
  • F-21 epic-wiring-drift — RESOLVED same-day: three of four orphan Tasks in sprint 21473 reparented via direct Jira edit and confirmed with a fresh read:
    • BOT-4587 [BE] Discuss Review PRD RDC AI Agent Refinement (Done) → BOT-4602 (P1 Autonomous AI Agent Refiner).
    • BOT-4655 [BE] Adjust list knowledge to expose knowledge name (Need Feedback/in progress) → BOT-3992 (P4 AI Agent Knowledge).
    • BOT-4656 [BE] Adjust list of ai agent to expose CID (Need Feedback/in progress) → BOT-3992 (P4 AI Agent Knowledge).
    • BOT-4658 [FE] Remove md-share MCP server from .mcp.json (Won't Fix) — left unparented: internal tooling cleanup, not tied to any product initiative.
  • F-22 epic-wiring-drift (recurring) — BOT-4554 "26Q3 Fast track" Epic still holds BOT-4084 ([BE] Support specialchars for interactive message on bot-preview, unassigned, To Do) — same issue previously logged as pass-4's F-10 ("not re-surfaced") ; it re-surfaced this pass because it's now inside sprint 21473. Not a chatbot initiative Epic in the tracked map — appears to be a genuine catch-all/off-plan bucket. Owner: PM/TPM — confirm BOT-4554 is an intentional off-plan/fast-track container (in which case no fix needed beyond noting it) or reparent BOT-4084 to a real initiative Epic.

Known false positives — do NOT reparent (re-confirmed this pass):

  • epic-wiring-drift (off-map) on BOT-4602 (5 issues), BOT-4609 (6 issues), and BOT-4482 (2 issues) — these are the sprint's own tracked Epics (P1 Refiner child Epic, QA BAU Epic, P9 Google Calendar child Epic respectively). The engine's initiative-index map only resolves single-Epic initiative READMEs; it doesn't yet know about umbrella child Epics or the non-initiative QA BAU Epic. Same documented gap as pass 3/4's SPRINT_EPIC_DRIFT advisory for BOT-4602/BOT-4482 — expected, not a real drift. Worth upstreaming to sprint-reconcile.mjs so it doesn't keep re-flagging tracked Epics as "untracked."

Other findings this pass (not the primary ask, logged for completeness)​

  • coverage-gap — AI Agent Impact Report (BOT-4568): still only 1 non-dev issue, 0 BE/FE (matches ledger F-2, still open).
  • assignment-drift — engineering-q3-2026 README missing Baghiz Firdausa as an implementor/qa (now Jira-assigned there).
  • roster-mismatch — Izzul and Dimas Fauzi Hidayat both show 0 issues in sprint 21473 against their plan queues (Izzul: partial recurrence of F-6; Dimas: informational F-7/F-19 pattern, PM/TPM planning work is expected to have no board presence).
  • status-progress — AI Agent Testing now 4 done / 3 in-progress of 12 sprint issues, but 0/4 done issues code-corroborated — progress_pct should stay at 0% (extends F-13).
  • code-evidence-gap — 5 done-on-board issues with no merged-code trace in chatbot/chatbot-fe (partial repo coverage): BOT-3949, BOT-4616, BOT-4617, BOT-4618 (extends F-14), BOT-4653 (extends F-15).

Applied this pass​

  • F-21 reparented: BOT-4587 → BOT-4602, BOT-4655 → BOT-3992, BOT-4656 → BOT-3992 (direct Jira parent field edit, each confirmed with a fresh read). BOT-4658 confirmed intentionally unparented (tooling cleanup, not product work) — left as-is.

Not applied this pass — still needs a PM/TPM call​

  • F-20: confirm BOT-4662 as the canonical CRM Custom Fields Epic and update the sprint doc's placeholder rows.
  • F-22: confirm whether BOT-4554 ("26Q3 Fast track") is an intentional off-plan container, or reparent BOT-4084 to a real initiative Epic.