Repository · Merge safety
Post-merge verification
After every merge the platform re-checks that claude/tradequote-ai-plugin-spec-ADZYG (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 |
|---|---|---|---|---|
| #3944 Fix CI: package-lock.json, WPCS step, @wordpress/scripts upgrade | main | 2026-05-30 | not verified | merged before verification existed |
| #3945 feat: complete TradeQuote AI — all spec features, security fixes, CI/CD | main | 2026-05-30 | not verified | merged before verification existed |
| #3946 Merge pull request #1 from ccantynz-alt/claude/tradequote-ai-plugin-s… | claude/tradequote-ai-plugin-spec-ADZYG | 2026-05-30 | not verified | merged before verification existed |
| #3947 feat: TradeQuote AI WordPress plugin v1.0.0 — full implementation | main | 2026-05-30 | 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.