rollout-standards-releaselisted

# Roll out a Standards release Drive fleet adoption through `make rollout VERSION=<published-version>`. Treat the repository's typed rollout module and checked-in consumer registry as the source of truth; do not recreate its clone, update, diff, branch, PR, or auto-merge logic in ad hoc commands. ## Select the operation - For an audit or status request, run `plan --version VERSION`, then `status --version VERSION`. Do not create branches or PRs. - For an explicitly requested propagation or published release, run `plan --version VERSION`, inspect the result, then run `apply --version VERSION` and `status --version VERSION`. - To repair incomplete historical releases, run `reconcile`. Use the reported version with `status` before making any nondeterministic change. - Never run `apply` for an unpublished version. Publishing, merging the source release, approving PRs, and bypassing branch protection require separate authority. Run commands from the Standards repository root. Require an exact version; do not guess from a working tree with uncommitted or unreleased version changes. ## Handle an incomplete rollout 1. Preserve the controller's branch and PR. Rerun `apply` safely before doing manual recovery; the operation is idempotent. 2. If a human modified the rollout branch, the base moved incompatibly, or the controller rejects the diff, stop and report that condition. Never force push, overwrite the branch, broaden the allowed diff, or bypass protecti