Pass 7 — 2026-07-16 (same-day follow-up to pass 6)

Trigger: explicit user instruction — "add BOT-4662 to the plan" — applying pass 6's F-20 escalation now that its registration decision has been confirmed. No new Jira pull was needed (board state unchanged since pass 6, same day); this pass documents the repo-side registration and re-runs sprint:reconcile --team chatbot --json once to confirm the fix lands as expected.

Status of F-20 (epic-wiring-drift, BOT-4662):

• RESOLVED, pass 7. Registered BOT-4662 ("26Q3 Chatbot - CRM Actions: Custom Fields") as the canonical child Epic for the CRM Deals Custom Fields action group under qontak-action:
  • qontak-action/README.md: added a ## Jira Epics family-table row (BOT-4662) and an ## Action catalog row; added implementors: [eko.aprianto, agus.suparman, baghiz.firdausa] (README previously had no implementors: field at all).
  • qontak-action/prds/crm-actions-custom-fields.md: corrected jira_epic from the stale BOT-3350 (the already-shipped, different action group) to BOT-4662.
  • qontak-action/rfcs/crm-actions-custom-fields.md (BE RFC): corrected its two BOT-3350 citations (metadata line + header table) to BOT-4662 to match.
  • chatbot/delivery/sprints/2026-07-13-sprint-01.md: replaced both "Placeholder — CRM Deals Custom Field Support (Epic TBD)" rows (Baghiz #1, Agus #2) with the real Epic/PRD/RFC/ task-breakdown links and current board status; added a new queue row for Eko Aprianto (previously entirely absent from the plan despite holding 5 of 6 BE tasks, 3 already Done); updated the Initiative-index P10 row from "Visible backlog only... not projected into Sprint 01" to reflect the actual off-plan pull-in; corrected the ## Deviations from roadmap priority "placeholder only" bullet and the ## Sprint review "Added mid-sprint" bullet.
  • chatbot/delivery/roadmap.md: P10 Qontak Action Implementors column — → eko.aprianto, agus.suparman, baghiz.firdausa.
  • chatbot/delivery/capacity.md: added qontak-action (BE/FE) TBD allocation notes to the eko.aprianto, agus.suparman, and baghiz.firdausa rows (task-breakdown days cited as context, not yet DRI-signed-off man-days per the "captures, never estimates" rule).
  • lint:delivery clean throughout (0 errors; 85 advisory warnings, +1 from RFC_EFFORT_UNRECONCILED / EFFORT_TASKBREAKDOWN_UNRECONCILED on qontak-action/README.md now that its RFCs are Epic-linked and visible to that check — expected, matches the same advisory pattern already seen on several other initiatives; not a registration error).

Re-verified via sprint:reconcile --team chatbot --json: epic-wiring-drift (BOT-4662, off-map) still fires — expected, not a residual bug. The engine's initiative-index map resolves an initiative only via its top-level jira_epic (BOT-4597 for qontak-action, an umbrella anchor); it does not read the ## Jira Epics family table, so it cannot see that BOT-4662 is now a registered child. This is the same known limitation already carried for BOT-4602/BOT-4609/ BOT-4482/BOT-4500 — BOT-4662 joins that list as a 5th confirmed-legitimate off-map Epic, not a new gap. (Also incidentally surfaced: an editorial bucket-tracker-drift row on engineering-q3-2026 Story A3 — the engine's mechanical status-category mapping defaults all indeterminate Jira statuses to in-progress, while pass 6 set A3 to the more precise in-review by reading the actual Jira status text ("In Review"). The engine's own code comments this exact case as "editorial — a human call"; pass 6's row stands.)

What this pass does NOT do: it does not add effort_* frontmatter to qontak-action/README.md for this action group — the initiative's other two action groups (BOT-3350 shipped, BOT-4341 in review) also carry no effort figures, and picking one child Epic to size while leaving siblings TBD would be an inconsistent, unrequested judgment call. Left for initiative-timeline-mapper for the whole initiative, or a follow-up now that the DRI is asked. It also does not add a Tito/Izzul QA task for BOT-4662 (no QA presence exists on the board for this Epic yet) — noted in the sprint doc's ## Deviations bullet as a live gap, not fixed here.

Downstream propagation worklist (this pass)

#	Finding	Canonical artifact to reconcile	Owning tool / skill	Applied?
F-20	epic-wiring-drift → registration gap	qontak-action/README.md (family table + implementors:), PRD + BE RFC jira_epic, sprint doc (placeholder rows + Eko queue row + Initiative index + Deviations + Sprint review), roadmap P10, capacity.md	hand-edit + lint:delivery	✅ applied this pass
(follow-up, not a numbered finding)	No QA coverage on BOT-4662	sprint doc / sprint-jira-sync	PM/TPM + QA lead	not applied — noted only