ver-0.7

echo-memory.plugin.src/skills/echo-memory/references/bootstrap.md

@@ -4,6 +4,20 @@ The **plugin is the single source of truth** for ECHO's structure. Everything ne
 
 The vault holds **data only**. It carries no `CLAUDE.md` / `BOOTSTRAP.md` / `STRUCTURE.md` / `index.md`. The "is this vault set up?" signal is a small marker file, `_agent/echo-vault.md`.
 
+## Quick path — run the scripts
+
+Bootstrap, repair, and migration are deterministic scripts; prefer them over running the curl steps by hand. They resolve the scaffold relative to their own location, so they work regardless of the caller's CWD:
+
+```bash
+SCRIPTS="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts"
+"$SCRIPTS/bootstrap.sh" --dry-run     # preview what would be seeded
+"$SCRIPTS/bootstrap.sh"               # idempotent, additive — fills only what is missing (also the repair path)
+"$SCRIPTS/migrate.sh"                 # plan a schema migration (dry-run)
+"$SCRIPTS/migrate.sh" --apply         # perform the migration (moves/deletes, after review)
+```
+
+`bootstrap.sh` writes through `echo.sh`, so every step is status-checked and the marker is written last. The manual steps below document what the script does (and serve as a fallback if the script can't run).
+
 ```
 AUTH="Authorization: Bearer 241265fbe6830934a9a4ad3e69335f64a42153b663aa5b0017cb1ea1217b2bab"
 BASE="https://echoapi.alwisp.com"
@@ -75,9 +89,12 @@ PUT every file under this skill's `scaffold/templates/` to its mirrored vault pa
 
 Templates keep their Obsidian Templater tokens (`{{date:YYYY-MM-DD}}` etc.) verbatim — those are resolved by Templater / by the skill's daily-note routine, not at seed time.
 
+Resolve scaffold paths against the skill directory — **never a bare relative `@scaffold/...`**, which assumes the caller's CWD is the skill dir and silently sends an empty body otherwise:
+
 ```bash
+SCAFFOLD="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scaffold"
 curl -s -X PUT -H "$AUTH" -H "Content-Type: text/markdown" \
-  --data-binary @scaffold/templates/journal/templates/daily-note-template.md \
+  --data-binary @"$SCAFFOLD/templates/journal/templates/daily-note-template.md" \
   "$BASE/vault/journal/templates/daily-note-template.md"
 ```
 
@@ -115,6 +132,8 @@ Run the same steps 1–5, but GET-probe each path first and **only create what i
 
 ## Migrations (`schema_version` mismatch)
 
+`scripts/migrate.sh` automates this: it reads the marker's `schema_version`, applies each intervening migration (idempotent, additive; destructive steps gated behind `--apply` and printed first), and stamps the marker at the end. Run it dry-run, review the plan, then `--apply`. The steps below are what it encodes — and the manual fallback.
+
 When the marker's `schema_version` is older than the plugin's, apply the migration steps for each intervening version, then PATCH the marker's `schema_version` frontmatter to the new value.
 
 - **0 → 1** (control-docs-in-plugin): the vault previously carried root control docs (`CLAUDE.md`, `BOOTSTRAP.md`, `STRUCTURE.md`, `index.md`). Back them up outside the vault, DELETE them, PUT the thin `scaffold/README.vault.md` over the old verbose `README.md`, write the `_agent/echo-vault.md` marker, and scrub now-dangling `[[CLAUDE]]`/`[[BOOTSTRAP]]`/`[[STRUCTURE]]`/`[[index]]` links from the `## Related` sections of `operator-preferences.md` and `current-context.md` (leave historical session logs alone). Confirm with the operator before deleting.