Release v0.33.0 — Referent binding, pre-merge snapshots, .kin schema v2 · wandercom/kindex

Added

Referent binding + two clocks (R0). Nodes can bind the external thing their claim describes — {path|url, content_digest, digest_scope} — plus asserted_at (claim time) and true_of (referent observation time). kin add --referent / MCP add(referent=...) bind at capture; kin stale / MCP stale_check re-hash file-scope referents, demote moved-or-missing referents from trusted_only recall (stale_referent), mark them [stale-referent] in search/context, and list re-verification candidates; --rebind re-verifies without re-dating the claim. Export/import and the .kin index carry the binding.
Pre-merge DB snapshots. Every automated destructive merge (graph_merge, dream-cycle auto-merges) first copies the SQLite store via the backup API to $XDG_STATE_HOME/kindex/snapshots/ (ten kept per database) and logs a db_snapshot changelog entry with a restore hint. Fail-closed: no snapshot, no merge.
.kin schema versioning. .kin/index.json advances to schema v2: unknown top-level fields pass through the kin merge-kin driver via 3-way field merge, and a side declaring a newer schema version makes the driver decline (normal git conflict) instead of silently rewriting it.

SQLite schema v8 → v9 (atomic, rollback-safe): nodes gain nullable referent, asserted_at, true_of.

_migrate_v8 stamped the code's current SCHEMA_VERSION instead of the literal 8, which would have marked v9+ migrations applied before they ran on any multi-step upgrade.

docs/spec-contradiction-check.md: reviewed v1 contract for the contradiction_check tool (spec only). docs/prd-lineage-grounding-2026-08.md: the reviewed PRD behind this work. Human/MCP guides and README cover referent binding, staleness, and snapshot restore.