v7.210.0

T-538: saipen/CONVERGE.md is now the only place the cc lifecycle is defined -- stages A through M from recovery to fresh producer packages, the rule that no main-source mutation may follow the producer preparation, and the closure bar that decides when a converge run may clear the intent and stop. The order was previously implied by five documents that each knew one hop, so no single reader could answer "what comes after CLEAN" without assembling it, and assembling it is where two conformant agents diverge. hunt.md, clean.md, prepare.md and done.md each name their own stage and defer; none restates the sequence.

validate.py gains [converge-contract], which checks the 13 stages BY POSITION: a reordering FAILs while every stage is still present, because the way this contract actually breaks is two stages swapping and putting the factories before the cleanup that invalidates them -- not a deleted file. Two red controls cover exactly that (one renames a stage heading to another's, one deletes the ordering rule); audit_checks 168 of 168. The doc is registered in INDEX.md, saipen/MANIFEST.json and BOTH bootstrap injectors, whose copy lists are still hand-written beside the manifest.