Skip to main content

Chatbot Sprint 01 — Jira reconciliation pass 09 (2026-07-23)

Jira reconciliation — recheck (2026-07-23, pass 09)​

Fresh pull since pass 8. Flow vitals: 73 → 85 issues (+12 net — CRM/QACF FE follow-ons, AI-Testing FE port, more fast-track bugs, framework-upgrade tasks); 28 WIP, 47 done (25 resolved since 2026-07-20 — throughput stays high). Oldest in-progress: BOT-3942 ([BE] API webhook result of validation, Eko Aprianto), created 2026-04-07 — 107 days old, still the pre-sprint carryover worth a deliberate close-or-descope. Engine run: sprint:reconcile --team chatbot --digest (sibling qontak-docs at 7bfdc11); digest pulled via MCP, 85 issues, single page. Code-evidence join: chatbot + chatbot-fe fetched 2026-07-23; notification-service, qontak-designer, hub have no usable local checkout (verdicts PARTIAL to that extent).

Status of prior findings (by id):

  • F-2 (coverage-gap, AI Agent Impact Report) — STILL OPEN, ⛔ ESCALATED (8th pass). BOT-4568 still has exactly 1 sprint issue (BOT-4645, QA) and 0 BE/FE tasks. Eight passes with no board movement — the audit has no further observe-only lever. Escalation home this pass: accepted-risk restated in ai-agent-impact-report/delivery/status/2026-07-23.md, and the decision is now formally owed: Dimas Fauzi Hidayat must either file the BE/FE Tasks via sprint-jira-sync before sprint close (2026-07-27) or descope Sprint-1 outcome target 3 in a decisions/ ADR. No further re-log without one of those.
  • F-14 (code-evidence-gap, AI Agent Testing Won't Fix set) — STILL OPEN, ⛔ ESCALATED (7th pass). BOT-3949, BOT-4616, BOT-4617, BOT-4618 still Won't Fix, still no trace on chatbot origin/master (re-grepped after fetch 2026-07-23). Escalation home: the descope decision + the effort_total_days shrink is restated in ai-agent-testing/delivery/status/2026-07-23.md — owner assignee/DRI + Dimas Fauzi Hidayat; testing progress_pct correctly stays 0% until it lands.
  • F-15 (code-evidence-gap, BOT-4653) — STILL OPEN, ⛔ ESCALATED (7th pass). Still Done, still no trace in chatbot/chatbot-fe (PARTIAL: notification-service unchecked). Owner unchanged (assignee Eko Aprianto / DRI).
  • F-26 (code-evidence-gap, QACF BOT-4669/BOT-4673) — STILL OPEN, ⛔ ESCALATED (2nd pass). Manual join (engine went silent — see engine note below): BOT-4670/4671/4672 ARE merged to chatbot origin/master (PRs #2394/#2397/#2395); BOT-4669 (Task 2, AdditionalFieldNormalizer) and BOT-4673 (Task 6, node-registry seed) have zero trace in chatbot or chatbot-fe (any ref). Gap is specific, not a search artifact. Owner: Eko Aprianto.
  • F-27 (code-evidence-gap, Knowledge BOT-4655/BOT-4656) — STILL OPEN (2nd pass). Still no trace in chatbot/chatbot-fe; off-breakdown → 0 md either way. Owner: Farras Herdicho.
  • F-28 (epic-wiring-drift, orphan BOT-4698) — RESOLVED. BOT-4698 is now parented to Epic BOT-4620 and Done. (Note: the parent it landed under is the engineering-bucket Ruby/Rails Epic — see F-30, unrelated to this orphan's closure.)
  • F-29 (off-plan-load, fast-track Epic BOT-4554) — STILL OPEN, ⛔ ESCALATED (2nd pass) — GREW. Now 4 mid-sprint bugs: BOT-4690 (Done), BOT-4700 (Done, now Farras), BOT-4693 (In Progress, Agus), BOT-4726 (In Progress, Farras — new this pass). Still no plan queue rows, no Expedite-intake record; committed load landing on the two busiest BEs. Owner: Dimas Fauzi Hidayat — adhoc intake gate or an accepted off-plan-load note.
  • F-30 (forecast-at-risk / plan-drift) — STILL OPEN, ⛔ ESCALATED. A1 Ruby/Rails Phase-1 is still being built despite the plan's "discovery only, build not authorized": BOT-4698 now Done under BOT-4620, and engineering tasks BOT-4628/BOT-4650 continue. Owner: Dimas Fauzi Hidayat — authorize retroactively (update A1 status/plan/capacity) or stop; risk entry stands in engineering-q3-2026/delivery/status/2026-07-20.md.

New findings from the 2026-07-23 pull:

  • F-31 (epic-wiring-drift, orphans — deterministic): four sprint Tasks, all Ready-to-Test, with no parent Epic — BOT-4724 ([FE] Replace ActionMultiSelectField, Baghiz), BOT-4727 ([FE] field-array element support, Baghiz), BOT-4697 (Port AI Testing feature to chatbot-fe, Linggar), BOT-4732 (Testing detail modal + shadow-mode gate, Linggar). Likely intended parents: BOT-4724/4727 → the CRM/QACF family (BOT-4662); BOT-4697/4732 → an AI-Testing Epic (BOT-3351 or its FE-port sibling). Real work hidden under no Epic. Board fix → jira-alignment-check (parent each; the FE-port pair also needs the correct AI-Testing Epic confirmed).

  • F-32 (code-evidence-gap, engineering bucket): BOT-4650 ("Fix subscription feature-flag gating…") is board-Done with no trace in chatbot/chatbot-fe; BOT-4628 ([BE] Task 6 — CI gates) is Won't Fix with code only on an unmerged branch (origin/BOT-4628-be-task-6-ci-gates-…). Both contribute 0 md. Note the provenance mismatch: tracker A4 (BOT-4696) claims it was "reconstructed from BOT-4650 code changes", yet no such code is reachable — informational, flag to DRI. Owner: assignee/DRI.

  • F-33 (assignment-drift, deterministic): Eko Aprianto is assigned live-sprint issues under ai-agent-testing (BOT-3942, In Progress) and engineering-q3-2026 (BOT-4653, Done) but is absent from both READMEs' implementors. Applied to ai-agent-testing only (README + roadmap + capacity 3-place mirror) — a normal initiative with a free implementors list. Not applied to engineering-q3-2026: that bucket derives implementors from its per-story tracker owners, and BOT-4653 is the code behind story A4 (tracker owner Linggar), so Eko is a code author, not a story owner there — adding him fired BUCKET_IMPLEMENTORS_DRIFT (extra: eko). Recorded here informationally.

  • status-progress (info — the step-6b computations):

    • Autonomous AI Agent (P1 Refiner): unchanged at 12.5 / 24.5 md (51%) — engine flagged no drift; README cache still matches jira-implied. No write.
    • CRM Deals Custom Fields (qontak-action): BE 3.0 of 5.0 breakdown md corroborated done — Task 3 (BOT-4670, 1d), Task 4 (BOT-4671, 1.5d), Task 5 (BOT-4672, 0.5d) all merged; Task 1 (BOT-4668) Won't Fix; Tasks 2/6 (BOT-4669/4673) withheld as F-26. FE 6/6 tasks board-Done (BOT-4680–4683/4699/4722), corroboration deferred (chatbot-fe not exhaustively joined this pass). README effort_total_days: TBD blocks any progress_pct — evidence parked in qontak-action/delivery/status/2026-07-23.md; baseline sizing still owed by DRI/PM. This initiative is engine-blind (see engine note) so this manual join is the only corroboration path until BOT-4662 is registered as a resolvable child Epic.
    • AI Agent Testing: count-based only — 9 of 15 board issues done, 5 code-corroborated; man-days stay 0 pending the F-14 descope call and the BOT-4654 ≈ Task 2.1 join (F-13).
    • AI Agent Knowledge: 0 md — BOT-4655/4656 done but off-breakdown + no code trace (F-27).

  • Identity / engine corrections:

    • Engine limitation (report upstream to sprint-reconcile.mjs): the code-evidence join is scoped to issues under a team's resolvable initiative Epics, so off-map umbrella-child Epics are excluded — QACF (BOT-4662) done issues get no code-evidence verdict at all. That is why F-26 disappeared from the engine's gap list this pass despite the gap being real (confirmed by manual grep). Consequence: all QACF progress must be hand-joined until BOT-4662 is resolvable.
    • New off-map parents are genuine non-initiative Epics, not mis-wiring (verified via getJiraIssue): BOT-4674 = "AI Agent - Appointment" (Epic, To Do; child BOT-4731, Eko) and BOT-3972 = "26Q2 QA Automation & Delivery" (Epic, Done; child BOT-4461, Izzul). Added to the known off-map set — not actionable.
    • Re-confirmed false positives (unchanged): untracked-Epic rows BOT-4602/4609/4482/4500/4662 (umbrella children / non-initiative — engine resolves only the top-level jira_epic); the two roster-mismatch rows — Muhammad Izzul has BOT-4461 In Progress (engine queue-join bug) and Dimas Fauzi Hidayat is the known no-board-tasks PM/TPM.

  • A3 bucket flip is now code-corroborated (resolves the pass-7/8 human-hold caveat): A3 = pdfjs SCA remediation (BOT-4661), not Ruby/Rails, so independent of F-30. BOT-4661 is merged to chatbot-fe origin/main (PR #1556). sprint:reconcile --fix promoted A3 → done and the roadmap / README rollup to 1 of 4 (25%).

This pass does NOT fix: F-2 (Dimas — file or descope by close; ADR owed), F-14/F-15/F-26/F-27/F-32 (named assignees — board/code truth), F-29 (adhoc intake / accepted-load — Dimas), F-30 (Dimas — authorize or stop), F-31 (board fix via jira-alignment-check), the BOT-4654 ≈ Task 2.1 join (DRI), and the qontak-action effort baseline (DRI/PM sizing).

Downstream propagation worklist (this pass)​

#FindingCanonical artifact to reconcileOwning tool / skillState
1A3 done + rollup 1-of-4 (25%)engineering-q3-2026/README.md + roadmap ## Portfolio progress & forecastdeterministic --fixwritten this pass
2QACF BE 3.0/5.0 md evidenceqontak-action/delivery/status/2026-07-23.md (no pct — effort TBD)step-6b + DRI sizing follow-upwritten this pass
3F-33 Eko staffingai-agent-testing/README.md + engineering-q3-2026/README.md + roadmap Implementors + capacity.mdhand-applied, lint:deliverywritten this pass
4F-2 accepted-risk restatedai-agent-impact-report/delivery/status/2026-07-23.mdrisk entry → ADR owed (Dimas)written this pass; decision open
5F-14 descope + effort shrinkai-agent-testing/delivery/status/2026-07-23.mdrisk entry → descope (Dimas/DRI)written this pass; decision open
6F-31 four orphan TasksJira board (parent each)jira-alignment-checkopen
7F-29 fast-track adds (now 4)adhoc intake gate / accepted-load noteadhoc-interrupt-doctrine + Dimasopen (escalated)
8F-30 unauthorized buildTPM decision → sprint-planner amend + capacityDimasopen (escalated)
9Engine: code-evidence off-map exclusion; Izzul queue-join; umbrella false positivesqontak-docs/scripts/sprint-reconcile.mjsupstream issueopen