feat: release v0.2 self-evolving layer — skills, memory graph, reflections

[mayankbohradev]

Summary

Context Hub 0.2 — the self-evolving layer. Hermes-style procedural memory + LLM Wiki-style typed link graph on top of the existing flat memory store.

Zero breaking changes. Every existing tool keeps its signature, every existing memory keeps its data.

What's in this release

Schema (additive migration 0002_self_evolving.sql):

• memories gains 6 columns: confidence, verified_at, superseded_by, tier, access_count, last_accessed_at (all with safe defaults)
• 4 new tables: skills + skills_fts, memory_links, reflections, injection_log

Worker (src/index.ts) — 10 new MCP tools:

• save_skill, get_skill, list_skills, record_skill_outcome — procedural memory
• link_memories, get_memory_graph — typed graph (supersedes, contradicts, supports, related, example_of, refines)
• list_reflections, resolve_reflection — self-improvement queue
• get_hub_health, verify_memory — hygiene + decay

Plus injection scanner (8 rules), contradiction auto-detection at write time, skill-candidate auto-flagging, and a nudge layer that appends top-3 pending reflections to every save/search response.

CLI (create-context-hub@0.4.2):

• update command always probes remote D1 for 0.2 schema (fixes source-repo edge case)
• Auto-applies 0002 migration if D1 still on 0.1 schema, with confirmation
• Plain-English intro explaining what update does + what is preserved
• Smarter redeploy gate — offers redeploy when DB migrates even if files match
• Post-migration re-probe confirms the schema actually landed

Upgrade path for existing users

cd your-scaffolded-hub
npx create-context-hub@latest update

Existing memories are preserved with sensible defaults (confidence=0.8, tier='warm'). No data migration.

Test plan

• npm run typecheck passes on both root and CLI package
• Migration applied to live D1 against 2,256 existing memories — all preserved
• All 10 new MCP tools verified end-to-end via Claude Code (skill candidate, contradiction, supersedes-to-cold, FTS retrieval, hub health, foreign key cascade)
• CLI update flow tested on the source repo — probes correctly, migrates DB, re-probes to confirm
• Lint clean (0 errors), inspect clean on the live deployment

[vercel]

@mayankbohradev is attempting to deploy a commit to the Jaipuria AI Labs Team on Vercel.

A member of the Team first needs to authorize it.