Problem

• After document-reviewer findings were corrected, the design and update-doc recipes re-ran code-verifier even when its result had already converged, adding review rounds without new evidence.
• Design Docs could absorb release steps, production checks, and rollout order. Because task execution treats the Design Doc as its baseline, that content turned into planned and implemented work.

Changes

• Apply the existing post-implementation re-run rule to the design phase: after a correction, only the reviewer that owns the corrected findings re-reviews, and code-verifier reruns only after corrections to its own findings (recipe-design, recipe-front-design, recipe-update-doc, HC-04, Review Resolution). Implementation recipes already follow this rule and are unchanged.
• State in the Design Doc definition why release and production work stays out, and that a requirement describing such work is met by designing the capability it uses.
• Make designer and document-reviewer criteria exclude that work explicitly, and remove template wording that invited it (rollout in Risks, production/staging examples in Verification Strategy).
• Bump version to 0.29.3.

🤖 Generated with Claude Code