ver 1.3 and 1.3.1

echo-memory.plugin.src/skills/echo-memory/eval/perf/README.md

@@ -6,7 +6,7 @@ targeted. It reuses the live `echo` client module, so it measures the real poole
 concurrent code path — not a reimplementation.
 
 This is a **manual / pre-release** tool, not a CI gate: it depends on the live
-endpoint (`echoapi.alwisp.com`) and WAN latency. Gates are **relative ratios**
+configured endpoint (`echo.BASE` / `$ECHO_BASE`) and WAN latency. Gates are **relative ratios**
 (portable), with absolute milliseconds kept as informational context.
 
 See `PERF-TEST-PLAN.md` for the design rationale behind each metric.
@@ -25,8 +25,8 @@ python3 bench.py resolve                 # 1.2.0 fuzzy correctness table + timin
 python3 bench.py soak --soak-seconds 120 # stability / leak watch
 ```
 
-Set the key first if the baked-in fallback warning bothers you:
-`python3 ../../scripts/echo.py write-key <token>` (or `export ECHO_KEY=...`).
+Configure this machine first (owner/endpoint/key):
+`python3 ../../scripts/echo.py config init` then edit the file, or `export ECHO_BASE=... ECHO_KEY=...`.
 
 ## Metrics
 
@@ -90,7 +90,7 @@ metric + gate above regression-guard this so it can't quietly revert to serial.
   sandbox vault so the replay doesn't write to production; that's deferred (the
   plan's synthetic-vault item). The metric still proves enqueue works and reports
   queue depth.
-- **Absolute ms depend on where you run from.** WAN latency to `echoapi.alwisp.com`
-  dominates single-request times; that's why gates are ratios.
+- **Absolute ms depend on where you run from.** WAN latency to the configured
+  endpoint dominates single-request times; that's why gates are ratios.
 - **Synthetic-vault scaling (100/500/1000 notes) is deferred** per decision — the
   suite benchmarks the real ~190-note vault today.