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>
All four checks pass on the baked 1.6.0 artifact (skills register + precedence,
allowed-tools, operator-only sweep/triage, CoWork $ECHO fallback). Caveat noted:
allowed-tools globs match literal script names, not the "$ECHO" variable form —
re-confirm on the Claude Code CLI if that surface becomes routine.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Seeds archive/notes/README.md and asserts vault_lint flags retired-path —
fails against the pre-1.6.0 linter, passes with the retired-first check.
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>
Learned removing the retired archive/ and _agent/outputs/ trees: DELETE
cannot remove directories; the last-file deletion leaves empty folders
that the REST listing 404s (falsely reading as gone) while Obsidian
still shows them — manual cleanup required. Noted in api-reference.md
(Deleting Files) and linked to the TODO-1.6 retired-tree lint item.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Vault sanity check found archive/ and _agent/outputs/ (retired/unrouted
pre-0.6 trees) surviving in the live vault with only seed READMEs; the
permissive leaf-readme route matches before the retired-path check, so
/echo-health never flags them.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- docs/history/echo-improvements-prompt.md (ROADMAP-2.0 §5 box ticked)
- README repository layout brought to 1.5.1 reality: root docs
(CHANGELOG/TODO-1.6/ROADMAP-2.0/docs/history), build.py + dist/
(gitignored, secret-bearing), current eval harness contents, hooks/,
and the full scripts/ roster (recall/reflect/triage/queue/
concurrency/quality/output/doctor/hook modules) with the legacy
commands/ dir annotated as the TODO-1.6 migration target. Also
restores the eval-descriptor fix lost in the prior commit (edit was
applied in memory but never written back).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- TODO-1.6.md: skills-format migration of the eight slash commands
(allowed-tools, disable-model-invocation, de-duped $ECHO block),
plugin.json homepage, vault link repoints, and an open section for
findings from 1.5.x live testing.
- ROADMAP-2.0.md: packaging & structure major — repo artifact policy
(Gitea releases, prune versioned zips), delete legacy commands/ dir,
codex-as-build-target if ever needed, eval refresh to current
metrics. Includes a disposition table absorbing every open
MAINTENANCE.md item, so that checklist is removed.
- Delete "codex plugin/": drifted derived tree; operator decision to
regenerate from the canonical source after 2.0 if Codex use returns.
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>
Jason Stedwell
jason