Align release lifecycle guidance with the canonical communication contract #227

Context and request

Reconcile the release-lifecycle guidance in existing MSXOrg/docs#208 with the user-confirmed settings and communication contract. Preserve its lifecycle intent while ensuring a later merge cannot restore the retired prerelease spelling, obsolete announcement marker, or incompatible migration-documentation ownership.

Acceptance criteria

• The complete release-lifecycle and publishing-target guidance is internally consistent with documented effective defaults and caller overrides and the release:prerelease/skip contract.
• Source-bound full release records contain consumer migration evidence and actual publication provenance; product docs and the generic operating procedure do not duplicate version-specific migration history.
• The announcement boundary agrees with PR Format and preserves the full GitHub release record; no Discord sender is introduced.
• Required lifecycle and recovery guarantees are not described as implemented producer behavior solely because documentation changes.
• Cross-references, generated navigation, repository documentation checks, and the complete review loop pass.

Technical decisions

Deliver through the existing #208 PR with one reconciliation owner for the overlapping #196/#209 canonical pages. Preserve the distinct durable-lifecycle proposal; do not bundle producer runtime, date strategies, automatic downstream propagation, historical metadata edits, or a Discord implementation. The settings/format handoff is bounded and does not require building the entire lifecycle engine. Required CI enforcement remains separate operational work in #166 through the native dependency.

Implementation plan

• Inspect the complete Release guidance defines durable lifecycle and complete consumer records #208 diff, current main contract, and coordinated candidate guidance before editing.
• Establish consistency checks for the label spelling, settings precedence, announcement boundary, source binding, and migration ownership.
• Reconcile the lifecycle and target pages without reverting neighboring accepted contracts or discarding unrelated changes.
• Validate indexes/links/site and existing documentation tests; complete the Copilot review loop.
• Record the scoped handoff and full acceptance evidence in Release guidance defines durable lifecycle and complete consumer records #208 and link this Task with a closing reference.