ver 0.9

echo-memory.plugin.src/commands/echo-health.md

@@ -1,14 +1,15 @@
 ---
 description: Run the ECHO vault-health linter and summarize any invariant violations
-allowed-tools: Bash(*/echo-memory/scripts/vault-lint.sh*)
+allowed-tools: Bash(python3 */echo-memory/scripts/vault_lint.py*), Bash(python */echo-memory/scripts/vault_lint.py*)
 ---
 
-Run the bundled, read-only vault linter and report findings. Pass the conversation's current date so stale/aging math uses the same clock the agent writes with:
+Run the bundled, read-only vault linter and report findings. Pass the conversation's current date (`ECHO_TODAY`) so stale/aging math uses the same clock the agent writes with:
 
 ```bash
-ECHO_TODAY=$(date +%F) "${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/vault-lint.sh"
+ECHO_TODAY=<currentDate> python3 "${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/vault_lint.py"
+# Windows: use `python` or `py -3` if `python3` is not on PATH.
 ```
 
-Exit codes: `0` clean · `1` violations (printed, grouped by check) · `2` vault unreachable · `3` vault not bootstrapped (run `bootstrap.sh`).
+Exit codes: `0` clean · `1` violations (printed, grouped by check) · `2` vault unreachable · `3` vault not bootstrapped (run `bootstrap.py`).
 
 Summarize the violations grouped by category and propose fixes, but **do not auto-fix** without Jason's go-ahead. If this is the first substantive session of a calendar month, offer to write the findings to `_agent/health/YYYY-MM-vault-health.md` (per the skill's **Vault Health** section).

echo-memory.plugin.src/commands/echo-load.md

@@ -2,12 +2,13 @@
 description: Load ECHO memory — cold-start context read (profile, scope, latest session, today, inbox)
 ---
 
-Use the **echo-memory** skill to load memory now. Run the cold-start **Loading procedure** from `SKILL.md`: issue the 5–6 reads in parallel (marker, operator-preferences, current-context, heartbeat→latest session, today's daily note, inbox), then do the load-time **reconcile** (inbox-depth + scope-drift) and surface it in a single line.
-
-Prefer the bundled client for each read:
+Use the **echo-memory** skill to load memory now. Run the cold-start **Loading procedure** from `SKILL.md`: the six orientation reads (marker, operator-preferences, current-context, heartbeat, today's daily note, inbox) in **one call**, then do the load-time **reconcile** (inbox-depth + scope-drift) and surface it in a single line.
 
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.sh" get _agent/memory/semantic/operator-preferences.md
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py" load
+# Windows: use `python` or `py -3` if `python3` is not on PATH.
 ```
 
+`load` prints all six sections (404s on today's note / inbox are shown as absent, not errors) and flags an un-bootstrapped vault. Follow up with `echo.py scope show` if you need the sessions-since-switch count, and a project search if a specific project is in play.
+
 Do not narrate the reads. End with a one-line orientation: who/what/where the active scope is, and any reconcile prompt.

echo-memory.plugin.src/commands/echo-recall.md

@@ -0,0 +1,17 @@
+---
+description: Recall a topic from ECHO memory — matching notes plus their linked neighbourhood
+argument-hint: "[topic, person, or project]"
+---
+
+Use the **echo-memory** skill to recall context for:
+
+> $ARGUMENTS
+
+Run the one-call recall — it resolves the term against the entity index, searches, and expands one hop along `## Related` links and `source_notes`, so you get the connected web (linked decisions, people, prior sessions), not an isolated note:
+
+```bash
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py" recall "$ARGUMENTS"
+# Windows: use `python` or `py -3` if `python3` is not on PATH.
+```
+
+Then answer from the assembled context. If you only need the canonical path for one entity, use `echo.py resolve "<title>"` instead. Don't narrate the retrieval.

echo-memory.plugin.src/commands/echo-save.md

@@ -7,16 +7,19 @@ Use the **echo-memory** skill to persist this to the ECHO vault:
 
 > $ARGUMENTS
 
-Follow the skill's write discipline exactly:
-1. **Route** via `references/routing-map.md` (the canonical map). If no path fits, capture to `inbox/captures/inbox.md`.
-2. **Search-first** for any new slug-addressed note (slug AND human title) before creating — merge/promote instead of duplicating.
-3. Write through the bundled client so the call is status-checked and idempotent:
+Prefer the one-call **`capture`** — it routes (via the entity index), derives the canonical path, stamps frontmatter, indexes, auto-links mentioned entities, and writes the Agent-Log line. Pick the `--kind` from the content (`person, company, concept, reference, meeting, project, area, semantic, episodic, working, skill, decision`); use `--inbox` only when the home is genuinely unknown. Write multi-line bodies to a file with the Write tool (cross-platform, no heredoc).
 
 ```bash
-ECHO="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.sh"
-"$ECHO" append inbox/captures/inbox.md "- $(date +%F): <entry>"      # idempotent capture
-"$ECHO" put <routed/path>.md  <bodyfile>                              # create/overwrite (verifies)
-"$ECHO" patch <path>.md append heading "<H1::Sub>" <bodyfile>        # targeted append
+ECHO="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py"   # run with: python3 "$ECHO" ... (Windows: python / py -3)
+python3 "$ECHO" capture "<title>" <bodyfile> --kind <kind> [--aliases a,b] [--source p1,p2]
+python3 "$ECHO" capture "<title>" --inbox     # unknown home -> idempotent inbox line
 ```
 
-4. Write in third person about Jason; set `agent_written: true` + `source_notes`; never put `[[wikilinks]]` in frontmatter; `bump` `updated:` only on substantive changes.
+Drop to the low-level verbs only for shapes `capture` doesn't model (a project `## Status` replace, an ADR mirror, a daily-note edit):
+
+```bash
+python3 "$ECHO" put   <routed/path>.md <bodyfile>                       # create/overwrite (verifies)
+python3 "$ECHO" patch <path>.md append heading "<H1::Sub>" <bodyfile>   # targeted append
+```
+
+Write in third person about Jason; never put `[[wikilinks]]` in frontmatter. `capture` handles `agent_written`, `source_notes`, indexing, and linking for you; if you write by hand, `resolve "<title>"` first to avoid duplicates and `bump` `updated:` only on substantive changes.

echo-memory.plugin.src/commands/echo-sweep.md

@@ -0,0 +1,14 @@
+---
+description: Bring the ECHO vault up to the current feature spec (entity index + cross-links)
+allowed-tools: Bash(python3 */echo-memory/scripts/sweep.py*), Bash(python */echo-memory/scripts/sweep.py*)
+---
+
+Use the **echo-memory** skill to bring the vault up to the current spec. Run the sweep **dry-run first**, show Jason the plan, and only `--apply` on his go-ahead:
+
+```bash
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/sweep.py"            # plan (read-only)
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/sweep.py" --apply    # write
+# Windows: use `python` or `py -3` if `python3` is not on PATH.
+```
+
+The sweep (1) creates `_agent/index/`, (2) rebuilds the entity index from existing notes, (3) symmetrizes `## Related` cross-links (adds only the missing reciprocal direction — never invents new links), and (4) stamps the marker `schema_version`. It is idempotent and read-only without `--apply`. If `schema_version` is behind, run `migrate.py` first. After applying, run `/echo-health` to confirm invariants.

echo-memory.plugin.src/commands/echo-triage.md

@@ -5,7 +5,8 @@ description: Triage the ECHO inbox — route aging captures to their canonical h
 Use the **echo-memory** skill to run **Inbox Triage**. GET `inbox/captures/inbox.md`, list captures older than ~7 days that were never routed, and offer to route them.
 
 ```bash
-"${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.sh" get inbox/captures/inbox.md
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py" get inbox/captures/inbox.md
+# Windows: use `python` or `py -3` if `python3` is not on PATH.
 ```
 
 For each capture Jason accepts: send it to its proper home per the routing map (preference → `operator-preferences.md::Observations`; project idea → `projects/incubating/`; durable fact → `_agent/memory/semantic/`; person → `resources/people/`), then record the move in `inbox/processing-log/YYYY-MM-DD.md` (`- <original> → <destination>`). Do **not** delete the original capture unless Jason explicitly asks — the processing log is the audit trail.