One schema-bump release (recall-index schema 3, entity-index schema 2; old
recall indexes rebuild automatically, no vault migration):
- Local-first recall index: the live BM25 index lives in the machine state dir
(keyed by endpoint hash); capture's upkeep is a zero-network atomic file
write, no advisory lock — replacing the O(vault) GET/PUT-whole-index round
trip per write. The vault copy is a snapshot (sweep + session-end) used to
seed fresh machines / catch up after another client swept
(ECHO_RECALL_SYNC_HOURS, default 24). The read path never PUTs the vault.
- Incremental sweep: entity + recall meta carry 16-char content hashes;
`sweep --fast` fetches only new/gone/hash-missing notes plus a rotating
weekday shard (--all-shards forces everything); deletions drop from both
indexes; index-only so no --apply gate. `load` auto-runs it past
ECHO_FAST_SWEEP_DAYS (7); doctor reports index freshness. Obsidian-side
edits now reach the indexes without manual maintenance.
- Stemming + alias expansion: echo_stem.py (conservative Porter-lite, unit-
tested families + over-stemming guards) applied at index AND query time;
a query fuzzy-matching an entity folds its title/alias vocabulary into the
BM25 query at half weight — expansion can only boost docs containing the
terms. capture hashes the note's FINAL content (auto-link reordered first).
Eval gold set 8 -> 14 queries (6 paraphrases): recall@5/MRR 1.00/1.00 vs
keyword baseline 0.75/0.79. +3 unit tests, +10 e2e; test harnesses now isolate
ECHO_STATE_DIR. All seven suites green.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ECHO as 14 typed MCP tools (streamable HTTP, stateless JSON, bearer auth, open
/health) wrapping the 2.1.1 *_op cores in-process:
- mcp-server/app.py: FastMCP app; duplicate gate + offline queueing surface as
DATA (merge_into/force are parameters, never blind retries); recall packs
excerpts into budget_chars by score; get_note is traversal-guarded with
section/max_chars; patch_note enriches invalid-target errors with the note's
actual headings; log_session wraps the session-end bundle (heartbeat-last);
ECHO_MCP_TOOLS=core exposes only the six daily drivers; all MCP writes
serialize in-process; startup fails fast on missing env.
- Dockerfile (legacy format — no BuildKit on the CI runner), python:3.12-slim,
healthcheck probes 127.0.0.1; .dockerignore keeps the context lean.
- .gitea/workflows/docker-build.yml: standard image build; PORT redeploy
trigger targets the echo-mcp container explicitly (repo name is echo).
- deploy.unraid.yml: br0/auto-IP, /data volume, vault adjacency
(ECHO_BASE=http://10.2.0.35:27123), secrets as SECRET: refs.
- SKILL.md: prefer the echo_* tools when the connector is present; CLI recipes
stay as the fallback. Spec header marked BUILT (tool count corrected to 14).
- eval/test_mcp_server.py: e2e over real streamable HTTP (health/auth/
initialize/tools-list + capture->gate->merge->recall->log_session); skips
cleanly when the SDK is absent. All seven suites green.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Internal refactor per docs/MCP-SERVER-SPEC.md §4; CLI output and exit codes
unchanged (wrappers reproduce them from the envelopes):
- echo_ops: capture_op/resolve_op/link_op — duplicate gate and offline queueing
are data (action: duplicate-gate + candidates; queued: true); the --json
stdout-swallow hack is deleted (helper chatter -> stderr inside the cores);
capture_op takes body_text= directly (the MCP path, no temp file).
- echo_recall.recall_op — one structured result backs prose and --json.
- echo_triage.list_op/route_op, echo_reflect.apply_op,
echo_session.session_end_op — call capture_op internally, count gate outcomes
from envelopes.
- echo.scope_show_op/scope_set_op/load_op (+ shared _load_gather), and
echo_doctor.run_op (checks as data).
New eval/test_ops_api.py asserts the contract for every core: envelope shape
AND stdout purity (a stray print would corrupt an MCP response stream). All six
suites green. The 2.2 server build now starts directly at the app layer.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Three independently useful changes (IMPROVEMENT-PLANS #1/#3/#7), no schema changes:
- load --brief: token-budgeted cold-start digest (facts full, last-10 observations,
scope+freshness, last session's key sections, agent-log lines, inbox count;
ECHO_LOAD_BUDGET ~8000 chars, lowest-priority-first trimming). SessionStart hook
injects the brief form; /echo-load keeps the full dump. All load reads (+ the
sessions listing, which also feeds the heartbeat fallback) fetched in parallel.
- Offline capture durability: a fully-offline capture queues the WHOLE op as one
semantic record; flush replays it through capture so routing/gate/aliasing re-run
against the current index; a gate stop on replay is kept + flagged
(needs_attention, surfaced by flush and load), never landed blind; update-path
and ensure_daily_log writes ride safe_request; same-args captures dedupe.
- session-end: one call, one lock — session log -> agent-log line -> reflect
proposals (gate-aware) -> optional scope set -> heartbeat LAST as the commit
marker; dry-run default; ECHO_NOW pins HHMM; validation runs before any write.
Stop hook nudge names the command and recognizes it as reflected.
- Fix: main() now catches the __main__ twin-module EchoError (via RuntimeError +
.code) so helper-module errors exit with their intended codes, not tracebacks.
+19 e2e checks; all suites green. Plans renumbered: MCP container is 2.2.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Memory behavior unchanged; the major signals a distribution/install break.
- Legacy commands/ directory DELETED (skills-only; the 1.6.0 skills were verified
on desktop + CoWork and already took precedence). Pre-skills clients install
1.6.0 from the release history.
- Artifact policy: the repo tracks only the echo-memory.plugin pointer; the 15
historical versioned zips leave the tree (git history retains them); versioned
builds ship as Gitea release assets, one release per v<version> tag, starting
v2.0.0. .gitignore: *.plugin except the pointer.
- README: post-2.0 repository layout; "packaging for other agent runtimes" note
(ports are build targets from the canonical tree, never a second source tree).
- ROADMAP-2.0 items ticked; manifest -> 2.0.0.
All suites green (25/25 unit + 4 e2e suites); artifact rebuilt skills-only
(79 entries, no commands/).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Skills migration: each of the eight slash commands gains a skills/<name>/SKILL.md
twin (same invocation name, byte-identical body). Per-skill allowed-tools
pre-authorize the resolved python3/python/py -3 invocations + the CoWork ls
fallback probe; disable-model-invocation: true makes /echo-sweep and /echo-triage
operator-only. Docs-confirmed: a same-name skill takes precedence over the legacy
command, so commands/ coexists until its scheduled 2.0 deletion. The $ECHO
path-resolution dedupe is resolved as not-supported (skill dirs are
self-contained; no cross-skill snippet sharing).
Lint fix: vault_lint.py checks retired patterns BEFORE routes, so a seed README
inside a retired tree (archive/...) flags retired-path instead of being absolved
by the permissive leaf-readme route. New end-to-end regression test seeds
archive/notes/README.md (fails pre-fix, passes now).
plugin.json: version 1.6.0, homepage + repository -> git.alwisp.com/jason/echo.
All suites green: 25/25 client unit tests (incl. routing-sync guard), feature,
reflect, offline-queue, PATCH-semantics. Artifact rebuilt (87 entries, both
formats); pointer refreshed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Live 1.5.0 use caught the gate blocking a decision note over the single
vault-common token "echo" (min-normalized overlap gives any one-token
entity a 1.0 score). New echo_index.gate_candidates() + token_df():
- gate blocks same-kind candidates only; cross-kind name collisions
(a decision titled after its project) warn instead of blocking
- a lone shared token blocks only when unique to that entity (df == 1);
multi-token overlaps still block
fuzzy_candidates (advisory warnings) and exit-76/--merge-into/--force
semantics unchanged. +3 offline unit tests, gate e2e cases restructured
+2 new; verified live both directions. All suites green.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Promotes the previously session-local search-first write rule into the
canonical plugin and applies items 2-7 from echo-skill-improvements memory:
1. Loading Step 4 and a new mandatory pre-write search section now require
POST /search/simple/?query=<slug> across all four project lifecycle
subfolders before creating any slug-addressed note.
2. Daily-note Agent Log uses a resilient PATCH procedure that auto-creates
the daily note from the template if missing and adds the heading if
absent before patching.
3. New Style Rule: `created:` is the earliest known date, not "today";
preserve it on merges.
4. New Project Lifecycle section: incubating / active / on-hold / archived,
with the rule that folder and frontmatter.status must agree.
5. Session filename pinned to YYYY-MM-DD-HHMM-<slug>.md (lex-sortable);
existing files left as-is.
6. Loading Step 3: read only the ~5 most recent sessions by reverse lex
sort instead of the full list.
7. `source_notes` defined as a backward link to inputs; forward links
belong in `## Related` in the body.
Repo layout: promotes the previously zipped-only plugin to a tracked
source tree at echo-memory.plugin.src/. The .plugin zip is rebuilt
from source on each version bump.
Bumps plugin.json to 0.3.0.
Jason Stedwell
jason