Fold v0.4.1 changelog before tagging the GitHub Release

[byte271]

Package version is already 0.4.1. This is not a version bump.

CHANGELOG.md still listed scanner, lint, guard, clipboard, robustness, and audit notes under Unreleased while ## v0.4.1 only had the five-layer mix notes. Fold those notes into v0.4.1 so the immutable tag matches the tree that will be published.

Also record in docs/release.md (and lock it with a test) that tools/verify_release_install.py writes SHA256SUMS.txt into dist/ before the Linux job uploads that directory. gh release create ... release-dist/* therefore publishes the checksum file the Unix and Windows installers require. Same pattern as the existing v0.4.0 assets.

After this merges to green main:

1. Push immutable tag v0.4.1 on that merge commit (do not retag v0.4.0).
2. Dispatch Release Engineering with publish_github_release=true on that SHA.
3. Follow-up commit: record the published v0.4.1 wheel SHA-256 in README and docs/install.md.
4. Website deploy (mark.q1z.org, demo.html, d.q1z.org/mark) stays manual.

Frozen confirmation artifacts and the published v0.4.0 wheel are unchanged.

  

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}