Two-part handover following the repo's existing convention: Part A for a fresh
Claude session, Part B for the owner.
Part A leads with the trap rather than the deliverables, because it is the thing
most likely to cause damage: main advanced 13 commits mid-audit and had already
fixed two of the audit's findings, so this branch would have reverted them
without the merge. Includes the fetch-and-merge commands to re-check the baseline
if main has moved again overnight.
Also records, so a future session does not undo them:
- The tense split — past-tense records are annotated, never rewritten. "Finishing
the job" by rewriting the milestone docs or the 41 completed plans is the wrong
instinct and destroys the audit trail.
- One finding was WITHDRAWN during the audit (the asset table lists esbuild entry
points, so imported-only sources are correctly absent). Adding them back would
reintroduce a non-defect.
- The known false-positive link-check hit inside a ```diff fence.
- The submodule invariant: git diff main..HEAD -- user must stay empty. An earlier
git reset -- user here silently reverted main's pin bump; that was caught, and
the check is written down so it is not re-broken.
- P5's booby trap: removing shortcode-gallery-plusplus may take shortcode-core
with it and break stories.
Part B is the two things only the owner can do: one command to open the PR (tea
needs an interactive TTY), and the 7 recommendation decisions with why each needs
a human. Notes that the PR body file lives in a Claude job dir and is
reconstructable from the spec if it has been cleaned up.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
m038andClaude Opus 5
086c36d157