v0.0.5 — Substrate codec, kernel, OMC-PROTOCOL v1

WHAT CHANGED

• Substrate codec (omc_codec_encode / omc_codec_decode_lookup):
  canonicalize source, tokenize, sample every Nth ID, return
  compressed payload + content hash. Library-lookup decode.
• omc-kernel: content-addressed filesystem store at
  ~/.omc/kernel/store/<hex_hash>.omc. Alpha-rename invariant — two
  processes converging on the same canonical form produce the same
  address. CLI: ingest, fetch, stat, ls, sign, verify.
• omc-grep: code archaeology via canonical hash. Found 31.7%
  redundancy in OMC's own examples tree.
• OMC-PROTOCOL v1: formalized substrate-signed wire format for
  inter-agent messaging. No PKI; integrity via canonical-hash
  recompute.
• MCP server (omnimcode-mcp): exposes OMC as a runtime to LLM clients.
• Substrate-aware tokenizer: 285+ builtins, 113 phrase-level dict
  entries, CRT-packed (kind, vocab_id, position_class) IDs,
  token_distance metric, attractor folding.

WHY IT MATTERS
The substrate gains an identity layer (canonical hash) and a wire
format. Two agents talking over OMC-PROTOCOL can verify each other's
claims by recomputing hashes — no shared keys needed. The tokenizer
turns OMC source into a substrate-typed symbol stream — the
foundation for the substrate-indexed completion engine that comes next.

NOW POSSIBLE

• Compress code by 10-50× via library-lookup codec.
• Persist Values content-addressed and dedupe across processes.
• Inter-agent messaging with cryptographic-style integrity but no
  key infrastructure.
• LLM clients can drive OMC over MCP.

See CHANGELOG.md#v0.0.5-codec-kernel-protocol for the chapter index.