2.0.0 — packaging & structure major: skills-only plugin, release-based artifacts

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>

.gitignore

@@ -20,8 +20,10 @@ eval/results/*.json
 /echo-memory.config.json
 /dist/
 
-# Per-user BAKED artifacts (build.py --bake-key, named echo-memory-<ver>-<label>.plugin)
-# carry a live vault bearer token — NEVER commit them. They belong in dist/ (above);
-# this also guards any that get built at the repo root. The version-only pointer
-# (echo-memory.plugin) and version-only artifacts (echo-memory-<ver>.plugin) stay tracked.
-echo-memory-*-*.plugin
+# Build artifacts (2.0 policy): the repo tracks ONLY the echo-memory.plugin pointer.
+# Versioned builds (echo-memory-<ver>.plugin) are published as Gitea release assets
+# on git.alwisp.com/jason/echo, one release per tag — not committed. Per-user BAKED
+# artifacts (echo-memory-<ver>-<label>.plugin) carry a live vault bearer token and
+# must NEVER be committed anywhere (they belong in dist/, also ignored above).
+*.plugin
+!echo-memory.plugin