Repository · Merge safety
Post-merge verification
After every merge the platform re-checks that claude/esim-website-audit-16xl2r (or the PR's base) actually holds what a correct merge would leave there: the previous tip is still an ancestor, the PR head is in, the tree matches what git computes, and the objects exist. Merged PRs from before this verifier existed show as not verified — recompute one to check it now.
0verified
0failed
4not verified
| PR | Base | Merged | Verification | Detail |
|---|---|---|---|---|
| #3694 B2B revenue layer: bulk quotes, partner pipeline, corridor SEO pages, go-to-market playbook | main | 2026-06-11 | not verified | merged before verification existed |
| #3695 Fully functional store: eSIM lifecycle, top-ups, customer/admin dashboards, monitoring | main | 2026-06-11 | not verified | merged before verification existed |
| #3696 Merge pull request #1 from ccantynz-alt/claude/esim-website-audit-16xl2r | claude/esim-website-audit-16xl2r | 2026-06-11 | not verified | merged before verification existed |
| #3697 eSIM store: market audit, marketing site, dashboards, Stripe plumbing, SEO/AI-search engine | main | 2026-06-11 | not verified | merged before verification existed |
Showing the last 4 merged pull requests. Verdicts are audit-log rows (merge.verified / merge.verification_failed) — immutable, written by the merge path itself. A recompute on an older merge runs in historical mode: it checks the merge commit is still reachable from the current base tip rather than that the tip is the merge commit.