Skip to main content

Bifrost Sprint 1 (2026-Q3) — Jira reconciliation, pass 8 (2026-07-19)

Jira reconciliation — recheck (2026-07-19, pass 8)​

Context correction first. sprint_end is corrected 2026-07-17 → 2026-07-20 (the window was extended in real-world scheduling; the doc was never updated to match). Sprint 1's status: is reverted archived → active — pass 7 was run as a close pass against the stale end date, but the sprint had not actually ended. Passes 1–7 and the undated 2026-07-19 addendum remain valid evidence; this pass re-verifies all of it against a fresh live pull and treats pass 7's ## Sprint review as a provisional draft, not a completed close. The real close now runs at/after 2026-07-20 22:00.

Flow vitals (jira:digest equivalent, pulled via MCP + jq — no JIRA_* env creds available locally, so the digest was built manually per §2b rather than npm run jira:digest; sprint:reconcile was then run against it with --digest): 142 issues (−3 vs pass 7's 145), WIP 17 (unchanged), 10 done since 2026-07-17, oldest in-progress still BIF-8570 (Syafrizal Noor Abdillah, created 2026-06-17 → 32 days old, unchanged as the team's oldest WIP item).

Status of prior findings (by id):

  • F-1 (blocked-done-conflict, BIF-6428) — RESOLVED, but not through a resync pass: a direct code+Jira audit on 2026-07-19 produced decisions/0001-jira-done-plan-open-conflict.md and one-cid-multiple-waba/delivery/status/2026-07-19.md: BIF-6428 genuinely shipped most child Tasks, but all 7 Stories sat Waiting Confirmation and the core multi-WABA-shares-one-pool mechanism is still structurally blocked. New Epic BIF-8910 ("26Q3 Rollout") now owns the remainder; roadmap.md P11 row already reflects this. Confirmed via this pass's digest: BIF-6428 and BIF-8910 both carry zero sprint-21367 presence (consistent with the decision — the rollout hasn't been pulled into a sprint yet).
  • F-4 (off-plan-load, Syafrizal capacity) — STILL OPEN, 8th pass — but no longer a bare observation: decisions/0001-second-fe-engineer-decision.md was filed 2026-07-19 (status: proposal, dri: TBD). BIF-8570 (the prod-support bug cited in F-4) is still In Progress, now 32 days old — still the team's oldest WIP item. Escalation: owner Bifrost EM/TPM — decide the ADR (second FE engineer vs. descope) before Sprint 2 planning locks in.
  • F-7 (forecast-at-risk, A2/BIF-8751) — STILL OPEN, 8th pass, action still not effective: BIF-8751 is confirmed absent from sprint 21367 entirely in this pull (same as pass 7). Sprint 2's own draft already re-routes A2 to Satya as a firm close — correct per the Pull rule — but Sprint 1's own forecast needs a formal descope/carry note, not just a superseding mention in a different file. Escalation: owner Satya (Vinsensius) + TPM — write the carryover explicitly into this sprint's ## Sprint review (Carried over list already does this) and close the loop.
  • F-8 (off-plan-load, BIF-8757/BIF-7795) — STILL PRESENT: BIF-8757 now has 27 total children (18 Fast Track + 9 Task; was "25 children" at pass 7 — flat, within noise). BIF-7795 unchanged at 4. Owner: TPM — the tracked-bucket-container recommendation stands.
  • F-9 (bucket-tracker-drift, 26Q3 Adhoc core set) — SUPERSEDED: the bucket has grown from A1–A11 to A1–A17 (A12–A17 added 2026-07-16), all correctly reflected in the README tracker with real Jira keys; BIF-8695 now has 15 in-sprint children. No drift found beyond A9/A11, which continue to be tracked separately as F-16/F-17.
  • F-10 (coverage-gap, P13/P14/P16) — STILL OPEN, ⛔ ESCALATED, 5th recheck, scope widened: BIF-8658 (P13), BIF-8640 (P14), BIF-8641 (P16) all confirmed still zero board presence in this pull. New this pass: P15 (BIF-8659, Qontak Launchpad Audit Logs) has regressed from the 4 To-Do items noted at pass 7 (superseded into F-22) back to zero board presence — items were pulled out of the sprint, not resolved. Per doctrine this is a finding, not an assumption: confirm deliberate descope vs. an accidental sprint-scope edit. Escalation: owner TPM — confirm accepted sequencing vs. descope for all four initiatives before Sprint 1 closes; this has now run 5 passes with no decision.
  • F-13 (code-evidence-gap, self-subs BIF-8803/8804) — split, unchanged from the 2026-07-19 addendum: BIF-8803 stays RESOLVED (the BIF-8792 redirect, merged to hub-service origin/production since 2026-07-10, per the addendum's citation). This pass's independent key-based engine search separately finds an unmerged branch literally named for BIF-8803 in hub-core (origin/BIF-8803-be-hub-core-task-2-3-selfsubscriptions-initiate-in…) — this does not contradict the redirect; it is evidence of an earlier abandoned attempt under the same key in a different repo, and the addendum's citation (a different key, BIF-8792, in a different repo, hub-service) is the one that actually shipped. BIF-8804 remains STILL OPEN: Won't Fix, no trace in any of hub-chat/hub-core/moderator-be/hub-service. Owner: Grehasta/TPM.
  • F-14 (code-evidence-gap, self-topup BIF-8708/8709) — STILL OPEN, reconfirmed a 3rd time: this pass's engine run independently reconfirms zero trace across all three in-scope repos (hub-chat, hub-core, qontak-billing) for both issues — the same result the manual addendum found on 2026-07-19. Three independent checks now agree. Escalation: owner Madani/TPM — confirm a genuine no-diff fix or reverse the board status; this can no longer default to "PARTIAL, awaiting the missing repo."
  • F-15 (scope question, sales-invoice-jurnal BIF-7825) — STILL OPEN: BIF-7825 still Done on board with no code trace in hub-chat; Task 4 (BIF-8760, Download SI button) still In Progress (now the 3rd-oldest WIP item, created 2026-07-06). Owner: TPM.
  • F-16 (bucket-tracker-drift, A9) — STILL OPEN: BIF-8682 (A9's Story) still To Do; both children (FE BIF-8880, QA BIF-8876) confirmed still Done. The recommended Jira-side close has not happened across at least two passes now. Escalation: owner Satya/PM — close BIF-8682 on the board or state why not, rather than re-recording the same gap a third time.
  • F-17 (bucket-tracker-drift, A11) — STILL OPEN: BIF-8612 still Waiting Confirmation, per-repo owners still TBD per the README's own outstanding ask. Escalation: owner TPM — confirm the Expedite classification and name an authorizer, per the same open ask recorded in the bucket README since 2026-07-14.
  • F-18 (blocked-done-conflict, Qontak One Team) — STILL OPEN: all 7 sprint issues confirmed still Done (6/7 code-corroborated, unchanged). The initiative README carries no explicit health: field at all (not just a stale on-track value) — worth fixing structurally, separately from this finding. Owner: Addo/TPM — confirm initiative complete or identify remaining scope.
  • F-19 (epic-wiring-drift, 9 off-map parent Epics) — STILL OPEN, unchanged: counts identical to pass 7 (BIF-7803 ×12, BIF-8101 ×8, BIF-8757 ×9 Task-type, BIF-7795 ×4, BIF-8869 ×2, BIF-8293 ×2, BIF-7792 ×1, BIF-7550 ×1, BIF-7949 ×2). Zero movement across a full pass — escalation overdue. Owner: TPM, routes to jira-alignment-check.
  • F-20 (blocked-done-conflict, Meta WhatsApp Pricing) — SUPERSEDED / substantially RESOLVED: this pass's engine run, working independently of the 2026-07-19 addendum, itself finds no code-evidence-gap for BIF-8808 or BIF-8809 (Tasks 1.2/1.3) — corroborating the addendum's manual PR-#293/#294/#165 citations with a second, automated method. Phase-1 is genuinely 3/5 corroborated (~6.0/9.0 md). Remaining gaps: BIF-8810 (Task 1.4, Won't Fix/descoped — expected) and BIF-8762 (an RFC/docs task — expected, code-free). Ready for Addo/TPM to confirm and for the status file to move from the held 33%.
  • F-21 (blocked-done-conflict, Downgrade Webhook) — REOPENED, not resolved — a genuine attribution conflict. The 2026-07-19 addendum stated Phase 1 schema was "confirmed merged (PR #296, BIF-8813)." This pass's live pull shows BIF-8813 is still To Do on the board (as is its sibling BIF-8815, Phase 2 logic) — neither is Done. Meanwhile the tickets that are Done (BIF-8698, BIF-8811, BIF-8812) still fail this pass's independent code-evidence check: BIF-8811 has no trace in qontak-billing/moderator-be, and BIF-8812 shows only an unmerged-branch trace. So the addendum's PR-#296 citation does not attach to any ticket that is actually Done — either the addendum mis-keyed the citation (the PR likely belongs to BIF-8811/8812 instead, whose commit messages just don't key-match on grep) or the merge is real but mis-linked in Jira. Either way, F-21 cannot be read as resolved. The addendum's own flagged unexplained scope (wa_balance_holds/wa_reconciliation_batches migrations under BIF-8813) compounds this: since BIF-8813 is not Done, that scope currently has no owning ticket at all on the board. Escalation: owner Madani/TPM — reconcile which Jira key(s) PR #296 actually closes before this is written up as progress anywhere.
  • F-22 (coverage-gap, P9/P15) — split: P9 (BIF-8713, Quota Management) unchanged at 9 To-Do. P15 folds back into F-10 above (regressed to zero board presence — no longer a separate, narrower finding).

Recurring benign pattern, no reopen: the same "addo" assignment-drift pattern from F-11 (closed benign, pass 4) recurs across adhoc-q3-2026, deduction-v2, and sales-invoice-jurnal — Addo Hernando (PM, per roster.json's own _note) shows as a Jira assignee without an implementors/qa README entry. roster.json already documents this as a non-engineering discipline that routes to a TPM read, not a staffing-mirror edit — no new action.

What this pass does NOT fix: none of the above are written up the channel yet (status/ entries, ADR decisions, board fixes) — those are proposed next, confirmation-gated, once this ledger rewrite lands. F-21 in particular should NOT be treated as closed in any downstream artifact until Madani/TPM resolves the key attribution.

Downstream propagation worklist (this pass)​

#FindingCanonical artifact to reconcileOwning tool / skill
1F-1Already resolved — decisions/0001-jira-done-plan-open-conflict.md + one-cid-multiple-waba/delivery/status/2026-07-19.mdinitiative-timeline-mapper (done)
2F-4decisions/0001-second-fe-engineer-decision.md — needs a DRI + decision, not just a filed proposalEM/TPM
3F-7Sprint 1 ## Sprint review Carried-over list (already correct) + Sprint 2 queue (already correct)sprint-planner (no change needed)
4F-8capacity.md / roadmap Adhoc lane — consider a tracked container for BIF-8757TPM, hand-applied
5F-10 (+ former F-22/P15)roadmap ## Priority P13/P14/P15/P16 rows — confirm sequencing vs. descopeTPM
6F-14self-topup/delivery/status/ — do not raise progress on BIF-8708/8709 until confirmedMadani/TPM
7F-16 / F-17adhoc-q3-2026/README.md ## Stories (Jira-side Story close for A9; authorizer confirmation for A11)Satya/PM, TPM — board fix, not a repo edit
8F-18qontak-one-team/README.md — add health: field, confirm completeAddo/TPM
9F-19jira-alignment-check (D1–D6)jira-alignment-check
10F-20meta-whatsapp-pricing-oct-2026/delivery/status/ — update from 33% once Addo/TPM confirmsskill step 6b, hand-applied
11F-21Board fix / key reconciliation for PR #296 ↔ BIF-8811/8812/8813 — do NOT write up a resolved statusMadani/TPM