2 Commits

Author	SHA1	Message	Date
jason	d920f8821f	Remove ECHO back-compat shims — CHORUS is a clean break ... Decision: CHORUS deploys as fresh vaults on new machines for different users, so no ECHO adoption path is needed. Removed the Phase-1 shims: - chorus_config: legacy ECHO_* env aliasing and the read-only ~/.claude/echo-memory/config.json fallback - chorus_queue / chorus_hook_stop: ~/.echo-memory state-dir fallback - load/doctor/bootstrap/vault_lint/sweep/migrate: the _agent/echo-vault.md marker dual-probe; routing drops agent-marker-legacy (36 routes) - .gitignore, README, CHANGELOG, CHORUS-PLAN.md updated (decision #6; Phase 3 no longer migrates the live ECHO vault — fresh bootstrap only) All suites green: 25/25 unit, scaffold, routing-sync, 4 mock e2e, run_eval metrics unchanged. Rebuilt chorus-memory.plugin. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-21 13:42:14 -05:00
jason	7f76e3521d	Add CHORUS-PLAN.md — ECHO to group-based memory conversion plan ... Full review of the ECHO v1.5.1 architecture plus the phased plan to convert the plugin to multi-member (group) memory: identity model, schema-5 member namespacing, concurrency posture, rename map, and the five settled design decisions (shared rollups, group-visible prefs, shared-key first, /chorus-* commands, per-member + group inboxes). Deployment endpoint: chorusapi.mpm.to. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-21 13:19:45 -05:00