v0.4.0

What's Changed

• Make knot ask beat Trail on retrieval, keep the index current, add Go and Java by @dreygur in #11

New Contributors

• @dreygur made their first contribution in #11

Full Changelog: v0.3.0...v0.4.0

What's Changed

• Make knot ask beat Trail on retrieval, keep the index current, add Go and Java by @dreygur in #11

New Contributors

• @dreygur made their first contribution in #11

Full Changelog: v0.3.0...v0.4.0

What's Changed

• Make knot ask beat Trail on retrieval, keep the index current, add Go and Java by @dreygur in #11

New Contributors

• @dreygur made their first contribution in #11

Full Changelog: v0.3.0...v0.4.0

What's Changed

• Make knot ask beat Trail on retrieval, keep the index current, add Go and Java by @dreygur in #11

New Contributors

• @dreygur made their first contribution in #11

Full Changelog: v0.3.0...v0.4.0

v0.3.0 — Content-Addressable Wisdom (CAW)

Content-Addressable Wisdom — Refactor-Immune Memory

Knot now tracks wisdom by content identity (BLAKE3 hash) rather than file path. Move or rename a file and your memories follow automatically.

What's new

Auto-Relink (Auto-Healing)
When a file is missing at recall time, Knot scans the project tree (bounded by git root, depth 8) for a file with the matching BLAKE3 hash. If found, verification_path is silently updated and the node is returned as Verified instead of stale.

path_map table
New table mapping content_hash → last_known_path. Every file-backed save_wisdom call registers here, giving relink a starting point.

Archive instead of delete
prune_ghosts now moves stale nodes to an archived_nodes table in a single SQL transaction (zero impact on active queries). Archived nodes are auto-purged after 30 days if they were never recalled (success_count = 0). Nodes with recall history are kept indefinitely until manually cleared.

Token efficiency

• recall_memory results now include a path: line per hit by default (no full_content required to see where wisdom lives)
• knot_status shows Archived count alongside L1/L2/L3

Fix: blake3 hash label in save confirmation was incorrectly shown as sha256

Migration

No action required — all new tables are created automatically on first run via additive migrations.

Full Changelog: v0.2.2...v0.3.0

Full Changelog: v0.2.2...v0.3.0

Full Changelog: v0.2.2...v0.3.0

v0.2.2

Full Changelog: v0.2.1...v0.2.2

Full Changelog: v0.2.1...v0.2.2

Full Changelog: v0.2.1...v0.2.2

Full Changelog: v0.2.1...v0.2.2

Full Changelog: v0.2.1...v0.2.2

v0.2.1

Full Changelog: v0.2.0...v0.2.1

Full Changelog: v0.2.0...v0.2.1

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Full Changelog: v0.1.0...v0.2.0

Full Changelog: v0.1.0...v0.2.0

v0.1.0

Full Changelog: https://github.com/dreygur/knot/commits/v0.1.0

Full Changelog: https://github.com/dreygur/knot/commits/v0.1.0

Full Changelog: https://github.com/dreygur/knot/commits/v0.1.0