Bilko MC #105109 — stranded commit e7986b47 verdict

Bilko stranded commit e7986b47 — verdict (MC #105109)

Question

Commit e7986b47 on branch fix/stripe-webhook-jsonb-104218 (MC #104218, "Stripe metadata/jsonb fixevi + testovi") was never merged to main. Does it need a PR, or is it stale?

Verdict: STALE / SUPERSEDED — no PR needed

Tool-verified findings (repo: ~/business/ALAI-Holding-AS/products/Bilko)

1. Canonical branch is Azure DevOps azdo/main (GitHub origin/gh-ssh main is legacy/dead for CI, per MC #104218-era decision).
2. git merge-base --is-ancestor e7986b47 azdo/main -> NO. e7986b47 is reachable only from GitHub origin/main (stuck at 4fb01780, 2026-06-22) and its own feature branch — never merged into azdo/main.
3. azdo/main already has an independently authored duplicate fix for the same bug: commit 1761df9e "fix(billing): MC #104301 — StripeWebhookEvents.payload text()->jsonb() (REAL root cause)" (2026-06-24). Tables.kt:849 -> val payload = jsonb("payload") — same functional outcome as e7986b47, plus a companion fix for organizations.billing_status (PG ENUM bind, commit c29a57fc) that e7986b47 did not cover.
4. MC #104301 also shipped a broader regression suite covering this path (3f8edc2d "comprehensive 'Moja pretplata' UAT suite, 31 checks" + f27b615c), superseding the narrower 5-test StripeWebhookJsonbInsertTest.kt that shipped with e7986b47 (that file does not exist on azdo/main).
5. MC #104301's fix is what's live in production (Stripe-verified 2026-06-24 per prior project memory / evidence).

Action taken

• MC #104218 closed as superseded by MC #104301 (duplicate root-cause fix already shipped and live).
• e7986b47 / branch fix/stripe-webhook-jsonb-104218 left as-is (not merged, not deleted) — recommend deleting as a follow-up cleanup since it will never be merged.

Evidence

• ~/system/evidence/105109/stranded-commit-e7986b47-verdict.md
• ~/system/evidence/105109/codecraft-verdict.md (independent prior pass, same conclusion)
• ~/system/evidence/105109/e7986b47-main-verification.txt