chore(release): prepare 0.6.4

[helebest]

What

Cut the 0.6.4 release: bump every user-facing version reference (0.6.3 → 0.6.4) ahead of tagging.

Unlike 0.6.3 (a cadence release, src/ untouched, wheel byte-identical to 0.6.2), 0.6.4 ships a real engine-side change — PR #246: the three inline K-layer system-prompt constants were extracted into packaged prompts/*.md, and every packaged prompt's product self-reference was unified dikw-core → dikw. Constant names, call sites, on-disk format, schema, CLI, and API are unchanged; the wheel now carries three new prompt resource files.

file	change
pyproject.toml + uv.lock	version 0.6.3 → 0.6.4
CHANGELOG.md	## Unreleased → ## 0.6.4 — … (awk-extractable by release.yml); fresh empty ## Unreleased
docs/deployment-docker.md	2 GHCR image tags
docs/getting-started.md	pip-install pin
examples/docker/.env.example	DIKW_VERSION default
examples/docker/docker-compose.yml	error-message version example
.github/ISSUE_TEMPLATE/bug_report.yml	version placeholder

examples/docker/Dockerfile is intentionally not bumped — release.yml's sync-dockerfile job auto-bumps it after the tag publishes to PyPI. Its current 0.6.3 is already published, so the Dockerfile guard stays green.

After merge

Tag v0.6.4 on the squash-merge commit → release.yml runs the full pre-release gate, builds + publishes the wheel/sdist to PyPI (trusted publishing), builds + pushes the GHCR image, cuts the GitHub Release (CHANGELOG notes + dist assets), and opens the auto chore(docker): bump DIKW_VERSION PR.

Verification

• uv build → dikw_core-0.6.4-{whl,tar.gz}; the three new prompts/*_system.md confirmed present in the wheel.
• grep sweep: every user-facing 0.6.3 → 0.6.4; only the CHANGELOG ## 0.6.3 history heading and the Dockerfile ARG (published) remain.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Released version 0.6.4.

• Documentation

  • Updated setup and deployment examples to reference the latest release.
  • Refreshed Docker and getting-started instructions, plus example environment values, to match the new version.

• Chores

  • Updated the issue template’s example version number to stay current.
  • Added a new changelog entry for this release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1b91fc2a-27a0-4533-ae71-a80cd8e19cdf

📥 Commits

Reviewing files that changed from the base of the PR and between 8d61455 and e279790.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (7)

• .github/ISSUE_TEMPLATE/bug_report.yml
• CHANGELOG.md
• docs/deployment-docker.md
• docs/getting-started.md
• examples/docker/.env.example
• examples/docker/docker-compose.yml
• pyproject.toml

---

📝 Walkthrough

Walkthrough

Version bump from 0.6.3 to 0.6.4 across all reference points: pyproject.toml, CHANGELOG.md, Docker deployment docs, getting-started guide, Docker Compose example files, and the GitHub bug report issue template.

Changes

Version bump 0.6.3 → 0.6.4

Layer / File(s)	Summary
Package version and changelog pyproject.toml, CHANGELOG.md	[project].version set to 0.6.4; new 0.6.4 subsection added under Unreleased.
Docs, Docker examples, and issue template docs/deployment-docker.md, docs/getting-started.md, examples/docker/.env.example, examples/docker/docker-compose.yml, .github/ISSUE_TEMPLATE/bug_report.yml	All version pins, image tags, and placeholder examples updated from 0.6.3 to 0.6.4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• OpenDIKW/dikw-core#244: Previous version bump (0.6.2 → 0.6.3) updating the same set of files with the same pattern.
• OpenDIKW/dikw-core#232: Same release-version bookkeeping pattern across pyproject.toml, Docker examples, and docs.
• OpenDIKW/dikw-core#240: Coordinated release version bump across the same files including issue template and Docker compose.

Poem

🐇 Hop, hop, version's new!
From three to four we flew,
The changelog bears the tale,
The Docker tags set sail,
And docs all fall in line —
0.6.4, so fine! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is detailed, but it doesn't follow the required template or include the Summary, Test plan, and Notes / breaking changes sections.	Rewrite it using the repo template: add a Summary, fill the checkbox-based Test plan, and include Notes / breaking changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly indicates a release prep for 0.6.4, which matches the version-bump changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch worktree-release-0.6.4

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!