Publication preparation checklist

Question

Implement the pre-publication checklist from the conventions:

• LICENSE present, and its terms match the intent.
• README.md answers what, why, install, minimal usage, and where the documentation is.
• CHANGELOG.md has an entry for the version being released.
• No secrets in the working tree or in the history — scan and treat any hit as compromised and rotate it.
• No absolute paths, machine names, or personal directories in tracked files.
• Build reproduces from a clean checkout with the documented command.
• dist/ is ignored and the release artifact is attached to the tag, not committed.
• Links in the documentation resolve after restructuring, including relative ones.
• The repository name matches the project. A name inherited from an earlier project is a permanent source of confusion; rename it, or state the discrepancy in the README.

Decision needed: Create a release checklist document and CI checks for these items.

Label: wayfinder:task
Part of #2517

Start by reviewing LICENSE, README.md, CHANGELOG.md, the tracked files, and the repository's documented build and release process against each checklist item. Done means a release checklist document exists and CI checks cover the listed publication requirements, including secrets, paths, links, repository naming, and release artifacts.