AC-LAST-SMOKE p7-followup-path-a-reviewer-pattern probe (do not promote)

This article is a disposable end-to-end probe generated by GitHub Issue #45 to verify that the Phase 7 magi-issue-handler → auto-merge.yml → squash-merge chain still produces a magi-brain main history whose first-parent commits are all authored by magi-bot[bot] (the DP4 invariant). It intentionally carries no authoritative content and should be archived or deleted as soon as the chain finishes.

What this probe verifies

The probe walks the full Path A reviewer-pattern flow introduced in enhancements/p7-followup-path-a-reviewer-pattern.md. The chain under test is: GitHub Issue labeled with a magi pipeline label, headless claude -p worker, branch push to magi-brain, draft pull request opened with the auto-merge label, GitHub App token (magi-bot, App ID 3489271) used by auto-merge.yml to enable squash-merge, and the resulting main commit authored as magi-bot[bot]. Each link in this chain has its own failure modes — token expiry, branch-protection drift, missing label, stale handler quota — so a known-good probe issued from a clean main is the cheapest signal that the pipeline is healthy.

Why DP4 must stay intact

DP4 is the data-protection invariant that every commit on magi-brain/main past _D13_ADOPTION_SHA = e967f7a was authored by magi-bot[bot] via squash-merge from a feature branch — never a direct push, never a human-authored merge. The invariant is what lets the system trust the audit log: any divergence between knowledge content and the last magi-bot[bot] commit is an alert. The smoke probe therefore must land via the same path real content uses; if it accidentally landed via a direct push or a non-bot squash author, the tests/test_dp4_preserved.py allowlist would have to grow, weakening the invariant.

How the probe self-cleans

Because the smoke note carries confidence: low and the explicit do not promote marker in the title, the next pass of magi normalize plus a manual archive move will retire it without leaving a stale stub in knowledge/technology/. The originating issue (magi#45) is closed automatically by the handler’s _maybe_close_issue hook once the PR opens, so no human bookkeeping is required after the probe lands. If the chain breaks partway, the rollback runbook in CLAUDE.md (Issue Handler PR Rollback Runbook) applies unchanged.

Sources

• enhancements/p7-followup-path-a-reviewer-pattern.md — Path A reviewer-pattern spec
• docs/claude/decisions/ADR-p7-repo-split.md — DP4 invariant and _D13_ADOPTION_SHA anchor
• docs/claude/decisions/ADR-p5-github-issue-driven-writes.md — magi-issue-handler contract
• tests/test_dp4_preserved.py — DP4 enforcement test on magi-brain main