Release workflow, verification, and publication gates

Use the standard Release workflow and leave workflow_dispatch.version unset unless an override is explicitly requested; Craft owns stable version and changelog computation. Before dispatch, confirm the intended merge is on main, no blocker or duplicate release exists, and no release is pending. Verify the computed version, release branch, exact SHA, expected changelog/version changes, merge ancestry, publish issue, and enabled targets. Never apply accepted while required CI for that exact commit is pending or failing. Inspect complete failure logs before changing or retrying anything. After approval, verify the publication workflow, release assets, targets, and compatibility rather than inferring success from preparation or merge.