chore(release): prepare 0.6.4

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -34,7 +34,7 @@ body:
     attributes:
       label: Version
       description: Output of `dikw version`.
-      placeholder: "0.6.3"
+      placeholder: "0.6.4"
     validations:
       required: true
   - type: dropdown

CHANGELOG.md

@@ -7,6 +7,8 @@ on each entry call out exactly what shape changes break.
 
 ## Unreleased
 
+## 0.6.4 — K-layer system prompts extracted to packaged `.md`; product self-reference unified to `dikw`
+
 ### Changed
 
 - **K-layer system prompts extracted to `prompts/*.md`; product self-reference

docs/deployment-docker.md

@@ -42,8 +42,8 @@ keeps the quick-start under a screenful.
   against it too:
 
   ```bash
-  docker run --rm -v ./base:/base ghcr.io/opendikw/dikw-core:0.6.3 init /base
-  docker run --rm ghcr.io/opendikw/dikw-core:0.6.3 version
+  docker run --rm -v ./base:/base ghcr.io/opendikw/dikw-core:0.6.4 init /base
+  docker run --rm ghcr.io/opendikw/dikw-core:0.6.4 version
   ```
 
   There is intentionally **no floating `:latest`** — downstream pins an

docs/getting-started.md

@@ -23,7 +23,7 @@ dikw init my-base --description "my research base"
 cd my-base
 ```
 
-Pin an exact version (`uv pip install 'dikw-core[postgres]==0.6.3'`) so your
+Pin an exact version (`uv pip install 'dikw-core[postgres]==0.6.4'`) so your
 client stays on the same release as the server it talks to — `dikw client`
 runs a [version handshake](server.md) and hard-fails on a mismatch.
 

examples/docker/.env.example

@@ -2,7 +2,7 @@
 # released version (https://github.com/OpenDIKW/dikw-core/releases); compose
 # fails closed until it's set, so the debug environment never rides a stale
 # default. Bump deliberately when you want to debug against a newer release.
-DIKW_VERSION=0.6.3
+DIKW_VERSION=0.6.4
 
 # Required — leave blank to force compose to fail-closed until set.
 # Generate strong values, e.g. `openssl rand -base64 24` for both.

examples/docker/docker-compose.yml

@@ -26,7 +26,7 @@ services:
     # (``docker compose up --build``); it does NOT auto-pull. Its ``args``
     # forward the same DIKW_VERSION so a local build matches the pinned tag
     # instead of the Dockerfile's ARG default.
-    image: ghcr.io/opendikw/dikw-core:${DIKW_VERSION:?set DIKW_VERSION in .env to a released version, e.g. 0.6.3}
+    image: ghcr.io/opendikw/dikw-core:${DIKW_VERSION:?set DIKW_VERSION in .env to a released version, e.g. 0.6.4}
     build:
       context: .
       dockerfile: Dockerfile

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "dikw-core"
-version = "0.6.3"
+version = "0.6.4"
 description = "AI-native knowledge engine across the DIKW pyramid (Data → Information → Knowledge → Wisdom)"
 readme = "README.md"
 requires-python = ">=3.12"