chore(release): automate GitHub Release + document the flow

[KylinMountain]

Summary

`.github/workflows/publish.yml` has been in the repo for a while but no release has actually gone through it — all 6 PyPI versions (0.0.1 through 0.1.3) were uploaded directly via `twine` from a maintainer's laptop. There are zero git tags on the remote, the GitHub Releases page is empty, and the project has no changelog. This PR closes the gap so the next release can flow tag → CI → PyPI → GitHub Release in one step.

Changes

`.github/workflows/publish.yml`

• Added a pre-build step that asserts the pushed tag matches `pyproject.toml` `[project].version` exactly (e.g. `v0.1.4` ↔ `0.1.4`). This catches the most common release mistake before any artifact is built.
• Added a final step using `softprops/action-gh-release@v3.0.0` (pinned by SHA, same style as the other actions in the file) to create a GitHub Release on each `v*` tag with `generate_release_notes: true` and the built `dist/*` attached.
• Granted `contents: write` permission to the job — required for the release-creation step. `id-token: write` (used by PyPI OIDC) is unchanged.

`RELEASING.md` (new)
Maintainer-facing doc. The flow is now strictly:

1. Bump version in `pyproject.toml`.
2. Move `[Unreleased]` entries in `CHANGELOG.md` into a new dated section.
3. Commit and push to `main`.
4. `git tag -a vX.Y.Z -m "Release X.Y.Z" && git push origin vX.Y.Z`.
5. CI does the rest.

Explicitly calls out: do not run `twine upload` locally anymore.

`CHANGELOG.md` (new)
Keep-a-Changelog skeleton with an `[Unreleased]` section listing the substantive changes already merged or in flight (#34, #38, #45, #47 / #49, and #48 if it lands). The four pre-existing PyPI releases (0.1.0, 0.1.1, 0.1.3 — 0.1.2 leaves no commit trail and only exists on PyPI) are backfilled with short summaries from `git log`, honestly noting that no tag was created at the time.

What this PR deliberately does NOT do

• Retroactively tag 0.1.3. Doing so would push `v0.1.3` and trigger the workflow to attempt to re-publish 0.1.3, which PyPI would reject. So the first real exercise of the new flow will be the next version bump (0.1.4 or whatever).
• Switch to setuptools-scm / dynamic versioning. That's a bigger refactor and out of scope here. The version-match assertion in CI is the lightweight equivalent.

Test plan

• `yamllint` clean (no whitespace issues).
• Reviewer to verify on a dry-run: push a `v0.0.0-test` tag from a fork or a deletable branch and confirm:
  • The tag-version assertion fires correctly on mismatch.
  • The PyPI publish step runs (will fail on duplicate version, which is fine for dry-run).
  • The release-creation step would have run.
• The next real release will be the first end-to-end exercise.

🤖 Generated with Claude Code

[KylinMountain]

Code review

Found 2 issues:

1. CHANGELOG [Unreleased] references the openkb init --language feature from PR feat(cli): add --language flag and prompt to openkb init #48, but feat(cli): add --language flag and prompt to openkb init #48 is OPEN, not merged — the feature does not exist at main HEAD. By convention [Unreleased] documents merged-but-not-released work; listing an open PR's feature misleads readers about what's actually in the codebase. Remove this bullet (re-add it when feat(cli): add --language flag and prompt to openkb init #48 merges):

OpenKB/CHANGELOG.md

Lines 13 to 18 in b82f786

	matches (NFKC + case + `_`↔`-`) get rewritten to canonical form,
	unresolved targets become plain text. (#49)
	- `openkb init --language` / `-l` flag and interactive prompt for wiki
	output language at initialization. (#48)
	- Anthropic prompt caching via `cache_control` markers in the compile
	pipeline. Subsequent LLM calls reuse `(system + doc + summary +

2. The [Unreleased] compare URL targets a tag that doesn't exist. git ls-remote --tags origin shows zero tags and this PR's own RELEASING.md (§ "Past releases not on git tags") acknowledges that 0.1.3 was published without tagging. The link 404s today. Either use compare/main...HEAD, or pin to the SHA 96cb6ef (the version-bump commit for 0.1.3), or drop the link until the first real tag exists:

OpenKB/CHANGELOG.md

Lines 74 to 76 in b82f786

	[Unreleased]: https://github.com/VectifyAI/OpenKB/compare/v0.1.3...HEAD
	[0.1.3]: https://pypi.org/project/openkb/0.1.3/

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}