dev-ship — Finalize and draft PR

Core

Prepare a reviewable Draft PR for the agreed change, with evidence that it meets the requirements and the repository's delivery rules. Review depth follows the actual impact; a gate count or file-count threshold is not a substitute for judgment.

Reuse completed cleanup, review, and verification while their inputs remain unchanged. Establish missing evidence before publishing, and re-check evidence affected by a fix:

The fix changed	Re-check affected evidence
Source code	Cleanup, standards and requirements reviews, affected verification
Documents only (ADR, README)	Document review and applicable link or documentation-build checks
Config, CI, metadata	Consumers of the configuration and affected review or governance requirements

The table is a starting point. A changed requirement invalidates its requirements review even if code is untouched; changed security or governance evidence needs its own review. Name the input or command behind reused evidence instead of treating an old green result as current proof.

Repeated failure without new evidence: after two attempts at the same unresolved cause, report the attempts and blocker. Continue only with a materially different, evidence-backed approach within the authorized scope.

Review depth

Inspect behavior and consumers: migrations, schemas, public contracts, authentication, authorization, secrets, dependencies, deployment, CI, and runtime configuration may carry risk even in a one-line change. Unknown impact calls for investigation. The user's label "simple" is not evidence of low risk.