Skip to main content

Pass 6 — 2026-07-16

Trigger: /sprint-resync "Chatbot's active Sprint". Ran sprint:reconcile --team chatbot --json (sibling qontak-docs @ deffa6b, past pinned SYSTEM_REF f41ad1a) against live sprint 21473, then jira:digest --vitals --since 2026-07-15 --epic-map and targeted getJiraIssue reads on BOT-4500, BOT-4554, BOT-4662 to resolve the engine's off-map-parent rows to real Epic identities.

Flow vitals: sprint 21473 now 67 issues (pass 5: 61; pass 1 baseline: 22). WIP 34, 14 done since 2026-07-15. Oldest in-progress: BOT-3941 (Farras Herdicho, 100 days old) and BOT-4188 (Farras Herdicho, 59 days) — outside this resync's scope but worth a separate look; both untouched since creation per updatedDaysAgo: 0.

Status of prior findings (by id):

  • F-1 (coverage-gap, Google Calendar) — RESOLVED (pass 4). No change.

  • F-2 (coverage-gap, AI Agent Impact Report BOT-4568) — STILL OPEN, 6th check (since pass 1). Board still carries exactly 1 issue under BOT-4568 (BOT-4645, "QA Creation Testcases", Tito Amanda, In Testing) — 0 BE/FE implementation tasks. Escalating: six consecutive passes with no board movement on the FE/BE track and no owner response is past the second-recheck threshold. Owner: Dimas Fauzi Hidayat (PM/TPM). Decision needed: either file the BE/FE Tasks via sprint-jira-sync now, or formally descope Sprint 1 outcome target 3 ("P2 ... has a buildable FE shell") to planning-only. Routed to a dated status/ risk entry (draft below, pending confirmation) since this affects a named Sprint 1 outcome target.

  • F-3 (Epic-wiring, BOT-4574→BOT-4602) — RESOLVED (pass 3, confirmed pass 4). Re-checked this pass via epic-map: BOT-4574 and its 8 sub-tasks (BOT-4579–4586) all still resolve under BOT-4602. No regression.

  • F-4/F-12 (Eko Aprianto + Samudra Linggar README staffing) — RESOLVED (pass 4). No change.

  • F-5 (BOT-4621 unassigned/unsprinted) — not re-surfaced. No change.

  • F-6 (roster-mismatch, Izzul initiative-specific QA drafting rows unfiled) — SUPERSEDED. The current sprint doc's Izzul queue carries exactly one row (QA BAU), and it is filed (BOT-4637, "Automation coverage", In Progress). The finding's original premise — separate per-initiative QA drafting rows for Izzul beyond BAU — no longer matches the plan text (superseded by the same-day staffing amendments that also removed other per-person rows). The engine's roster-mismatch: Izzul row this pass is the same known false positive as before (below), not a live recurrence of F-6.

  • F-7 / F-19 (Dimas Fauzi Hidayat 0 issues) — informational, unchanged. Expected per roster.json _note.

  • F-8 (engine normName() false positives) — RESOLVED (pin bumped to f41ad1a). No change.

  • F-9 (AI Agent Testing task breakdown "Jira only") — RESOLVED (pass 5, was a stale premise).

  • F-10 (BOT-4084 off-plan) — superseded by F-22 (below), no independent status.

  • F-13 (AI Agent Testing progress stays 0%) — extends cleanly: now 4 done / 5 in-progress of 12 (WIP grew 3→5), still 0/4 done issues code-corroborated, so progress_pct correctly stays 0%. No status/ edit needed — informational, continues.

  • F-14 (code-evidence-gap, BOT-3949/4616/4617/4618, AI Agent Testing) — STILL OPEN, 5th check (since pass 2). Re-verified via code:evidence join inside sprint:reconcile: all four remain Won't Fix / no trace in chatbot/chatbot-fe (partial — qontak-designer/hub still not searched). Escalating: five checks with no board-status correction or explicit code-free confirmation. Owner: assignee/DRI (the four issues' assignees — check board for current owner) + Dimas Fauzi Hidayat (TPM) to force a decision. Needed: either confirm each is genuinely code-free (docs/config/no-op) and state so explicitly, or correct the board status. Routed to a dated status/ entry for AI Agent Testing (draft below).

  • F-15 (code-evidence-gap, BOT-4653, engineering-q3-2026) — STILL OPEN, 5th check (since pass 2). Still Done on board, no trace in chatbot/chatbot-fe (partial — notification-service /qontak-designer not searched). Escalating on the same basis as F-14. Owner: assignee/DRI. Routed to a dated status/ entry for engineering-q3-2026 (draft below; bucket progress is story-count based, so this is a risk note, not a man-day deduction).

  • F-16 (stale P3 plan text) — RESOLVED (pass 5). No change.

  • F-17 (BOT-4610–4614/4651 reparented) — RESOLVED (pass 3, confirmed pass 4). Re-checked via epic-map: BOT-4651 still resolves under BOT-4602. No regression.

  • F-18 (roster-mismatch, Baghiz Firdausa 0 issues) — RESOLVED, pass 6, verified directly. Baghiz now has 5 board issues: BOT-4661 (engineering-q3-2026 Ruby/Rails upgrade, In Review — this is Story A3, see F-15 sibling note below) and BOT-4680/4681/4682/4683 (all In Progress, under Epic BOT-4662 — see F-20). His planned Impact Report (#3) and AI Agent Testing (#4) queue items still have no board presence, but the "0 issues" premise is resolved.

  • F-20 (epic-wiring-drift, BOT-4662 "26Q3 Chatbot - CRM Actions: Custom Fields") — STILL OPEN, 2nd check — ESCALATING per the aging rule. Read BOT-4662's Jira description directly (the engine only classifies it "off-map," it doesn't read issue bodies): "BE + FE adjustment to add pipeline-scoped custom fields to the create deal / create ticket AI Agent actions. PRD: chatbot/qontak-action/prds/crm-actions-custom-fields.md. RFC: chatbot/qontak-action/rfcs/crm-actions-custom-fields.md." This resolves what the Epic is, and it is materially more advanced than "untracked":

    • The PRD (crm-actions-custom-fields.md, status draft), both RFCs (BE + FE), and both task-breakdowns already exist in the repo under chatbot/qontak-action/, fully estimated (BE 6d, FE 7d).
    • The PRD's own jira_epic: BOT-3350 (the already-shipped "Qontak CRM + Chat actions" Epic) does not match the live board Epic (BOT-4662, created 2026-07-15) that all 10 sprint issues actually hang from.
    • BOT-4662 is not declared in qontak-action/README.md's ## Jira Epics child-Epic family table (only BOT-3350, BOT-4341, and a TBD Send-WhatsApp-Flow row are listed).
    • The board shows real, substantial progress: BE — 3 Done (BOT-4669, BOT-4673, and one more), 2 Ready-to-Deploy, 1 Ready-to-Merged (Agus); FE — 4 In Progress (Baghiz, BOT-4680/4681/4682/ 4683). Eko Aprianto holds 5 of the 6 BE tasks (3 already Done) with zero mention in the sprint plan for this work at all.
    • The sprint doc still frames all of this as "Placeholder — CRM Deals Custom Field Support (Epic TBD)... do not start build until confirmed" for Baghiz (#1) and Agus (#2) only — directly contradicted by the board.
    • The roadmap's P10 "Qontak Action" row still reads "Visible backlog only... not projected into Sprint 01" — also contradicted.

    Owner: Dimas Fauzi Hidayat (PM/TPM). Decision needed, all in one pass: (1) confirm BOT-4662 as the canonical child Epic for this work (vs. BOT-3350), (2) add it to the qontak-action README's Jira-Epics family table and correct the PRD's jira_epic field, (3) replace the sprint doc's two "Placeholder — Epic TBD" rows with the real initiative/Epic/task-breakdown links, (4) add Eko Aprianto (+ confirm Baghiz/Agus) to qontak-action staffing (README has no implementors: field yet), (5) correct the roadmap P10 row. Not applied this pass — this is a registration decision, not a mechanical mirror fix. Routed to a dated status/ entry for qontak-action (draft below).

  • F-21 (BOT-4587/4655/4656 reparented) — RESOLVED (pass 5). Correction to the pass-5 record: BOT-4658 was described as "left unparented." Direct lookup this pass shows it is parented — to BOT-4500 ("Q3 2026 - Code Readiness," an Epic, not a chatbot product initiative). The interpretation in pass 5 ("internal tooling cleanup, not tied to any product initiative") was correct; the specific fact ("unparented") was stale/imprecise. No action needed — noting the correction so the next pass doesn't re-derive it. BOT-4500 joins the known-false-positive list below.

  • F-22 (epic-wiring-drift, BOT-4084 under BOT-4554 "26Q3 Fast track") — STILL OPEN, recurring (informational since pass 4, formal since pass 5). Unchanged: unassigned, To Do, sole child of BOT-4554. Not escalating yet (only its 2nd appearance as a numbered finding). Owner: PM/TPM — confirm BOT-4554 is an intentional off-plan/fast-track container or reparent.

New findings from the 2026-07-16 pull:

  • F-24 (assignment-drift, deterministic) — ai-agent-knowledge/README.md implementors list (eko.aprianto, samudra.linggar) is missing Farras Herdicho, who is Jira-assigned to BOT-4655/BOT-4656 (the two Tasks F-21 reparented here from BOT-4602). Applied this pass: added farras.herdicho to the README implementors:, the roadmap Implementors column, and a capacity.md row noting the allocation as unconfirmed/split with Eko's existing 8 BE days (the repo captures staffing, it does not invent an effort split — that's a DRI call).
  • F-25 (assignment-drift / bucket-tracker-drift, deterministic) — engineering-q3-2026 README implementors list was missing Baghiz Firdausa, who is Jira-assigned to BOT-4661. Tracing the issue further: BOT-4661 ("[FE] Upgrade pdfjs-dist + patch pdf-cover.vue worker init", In Review) is the real Jira Task for tracker Story A3 (SCA remediation, pdfjs-dist CVE-2024-4367) — which the README ## Stories table still carried as DRI: TBD, FE: TBD, Status: backlog, Jira Story: TBD, while the board already had it at in-review. Applied this pass: updated the A3 tracker row (DRI/FE → Baghiz, Status → in-review, Jira Story → BOT-4661), added baghiz.firdausa to README implementors: + roadmap Implementors + roadmap Adhoc/Interrupt-lane row + capacity.md. This tripped BUCKET_EXPEDITE_UNJUSTIFIED (A3 is 🔴 Expedite and now in-flight with no ## Expedite log row) — added a retroactive log row with the known CVE justification; Authorized by is left TBD pending DRI/TPM confirmation, matching the same convention already used for A1. Also noted: A3's own RFC (sca-pdfjs-dist-upgrade.md) is still draft with DRI/reviewers/approvers all TBD despite the build being nearly complete — flagged, not fixed (a process/governance gap, not a mirror-drift one). lint:delivery clean after all of the above (0 errors, pre-existing 78 advisory warnings unrelated to this pass).

Known false positives — do not action (re-confirmed + one addition this pass):

  • epic-wiring-drift (off-map) on BOT-4602 (6 issues, up from 5 — new: BOT-4608, Farras' planned rollout-flag task), BOT-4609 (6 issues), BOT-4482 (2 issues) — unchanged rationale from pass 3–5: these are the sprint's own tracked child/QA-BAU Epics; the engine's initiative-index map doesn't resolve umbrella child Epics or the non-initiative QA BAU Epic.
  • BOT-4500 ("Q3 2026 - Code Readiness", 1 issue: BOT-4658) — new this pass: confirmed via direct lookup to be a legitimate non-initiative internal-tooling Epic (see F-21 correction above). Add to the standing false-positive list.
  • Also noted, not a false positive but out of scope: QQ-2175 (cross-project key, parented to BOT-4609) is a new item in sprint 21473 this pass — legitimate QA BAU work filed under a different Jira project's key; no action.

What this pass does NOT fix (captures, never estimates): F-2/F-14/F-15/F-20's underlying board gaps are not filed, corrected, or registered by this pass — only escalated with a named owner and a proposed status/ routing (drafts below, pending confirmation before being written). F-22 remains open, one check short of its own escalation threshold.

Downstream propagation worklist (this pass)​

#FindingCanonical artifact to reconcileOwning tool / skillApplied?
F-24assignment-driftai-agent-knowledge/README.md + roadmap + capacity.mdhand-edit + lint:delivery✅ applied this pass
F-25assignment-drift / bucket-tracker-driftengineering-q3-2026/README.md (implementors + Story A3 row + Expedite log) + roadmap + capacity.mdhand-edit + lint:delivery (CHECK GROUP J)✅ applied this pass
F-2coverage-gap (escalated)ai-agent-impact-report/delivery/status/<date>.md risk entrysprint-jira-sync (file Tasks) or TPM descopeproposed, not yet written
F-14code-evidence-gap (escalated)ai-agent-testing/delivery/status/<date>.md risk entryassignee/DRI board fixproposed, not yet written
F-15code-evidence-gap (escalated)engineering-q3-2026/delivery/status/<date>.md risk entryassignee/DRI board fixproposed, not yet written
F-20epic-wiring-drift / initiative-registration gap (escalated)qontak-action/README.md (Jira-Epics family table, implementors:), PRD jira_epic, sprint doc placeholder rows, roadmap P10 row, qontak-action/delivery/status/<date>.mdjira-alignment-check (D1–D6) + PM/TPM registration decisionproposed, not yet written
F-22epic-wiring-driftboard fix or confirm off-planjira-alignment-check / PM/TPMnot applied — recurring, not yet escalated