fix: assemble complete release drafts before immutable publication

[CruxExperts]

The release workflow published 4.22.6 before its supplementary wheel, native sandbox and provenance assets could be attached. GitHub release immutability then correctly refused those uploads. This correction prepares a draft after the existing validation, archive and attestation gates, allowing the complete verified asset set and release notes to be assembled before publication. Existing releases, mismatched tags and uncertain API responses stop preparation without overwriting assets.

The release policy advances to the verified published 4.22.6 anchor and retires covered overrides. One new logical correction produces 4.22.7; the earlier slices are not counted again. Documentation explains draft completion and exact-release acceptance and identifies the actual Python 3.12 CI matrix.

Validation: 34 focused workflow/version-policy tests passed. The full Python suite passed 3,064 tests and five subtests (two skips, nine warnings); the subsequent documentation-only fixup and generated receipt passed drift/preflight checks. All nine smoke checks passed. Strict branding, architecture, catalog, package-surface and framework/documentation checks passed. Archive, source-wheel and sdist-wheel contents match; SDK payload, official SBOM schemas and reviewed visual hashes verify. Installed deterministic coding/heartbeat/compaction/recovery and both completion APIs passed, including cancellation, deadlines and exact LocalSetup/4.22.7 wire identity. Independent correction reviews found no unresolved actionable finding.

Follows #90. The existing immutable 4.22.6 release and its tag remain intact. Runtime behavior and the existing localsetup/lscli command identifiers are preserved.