fix(mcp): drop static docker --name so MCP servers survive host reconnect (#452)

All four Docker-based MCP templates hardcoded `docker run --name <mcp>-<slug>`.
On a dropped stdio pipe the host (e.g. Claude Code) re-spawns the server, but
the original `--rm` container is still Up, so the reconnect's `docker run
--name …` collides with "container name already in use" and the host surfaces
an opaque MCP -32000 (JSON-RPC server error).

Remove the static --name from crystalium/tonberry/atomos/atlas-aci templates.
Per-project identity/filtering already rides `--label eidolons.project=<slug>`,
and parallel-project isolation is preserved by the distinct per-project bind
mounts — every `docker run` is its own container regardless of name; the name
only added a singleton guard that broke reconnect. `cli/src/memory.sh` already
strips --name from its out-of-band recall path for this exact reason.

atlas-aci's summary log line + render tests now assert the --label slug in
place of the retired --name. Consumers parse .mcp.json args by value, so
existing generated files with --name stay readable; regenerate via
`eidolons mcp sync`. mcp_atlas_aci.bats 17/17.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Rynaro

CHANGELOG.md

@@ -12,6 +12,10 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Version
 
 - **README revamped for the v2 line — research-grounded recomposition, not a polish pass.** Grounded in a 16-repo study of celebrated OSS READMEs plus peer-reviewed attention/reading research (F-pattern scanning, curiosity-gap theory, serial-position effects, processing fluency, the blemishing effect), produced with deliberate model tiering (haiku fact audit / sonnet research / opus cold-read checker / Fable composition). New: a **"See it route"** demo showing real, reproducible `eidolons run --json` kernel output; a **"When Eidolons is the wrong tool"** honest-scoping section; the ESL + **ECM** "lifecycle and the context economy" section (four sibling-contract table, 5-MCP catalogue incl. atomos); a linked MANIFESTO (previously orphaned) closing in the recency slot; and one deadpan acknowledgment of the Final Fantasy naming. Restructured: benefit-first intro (the ~90-word 11-concept sentence is gone), team-before-proof ordering, the free zero-token routing benchmark now *leads* "Does it actually work?" with the four billed measurements compressed to one summary table + `<details>`. Verified maker≠checker under ESL change `.spectra/changes/readme-v2-revamp/` (30/30 links, every number traced to committed scorecards, dynamic badges intact, dual-audience cold-read PASS).
 
+### Fixed
+
+- **Docker MCP servers no longer fail to reconnect after a dropped stdio pipe** (`cli/templates/mcp/{crystalium,tonberry,atomos,atlas-aci}.mcp.json.tmpl`). All four Docker-based MCP templates hardcoded a static `docker run --name <mcp>-<slug>`. When a host (e.g. Claude Code) lost the stdio connection and re-spawned the server, the original `--rm` container was still `Up`, so the reconnect's `docker run --name …` collided — `docker: Error response from daemon: Conflict. The container name "…" is already in use` — the subprocess exited immediately and the host surfaced it as an opaque MCP `-32000` (JSON-RPC server error). The static `--name` is removed from every template; per-project identity/filtering now rides the already-present `--label eidolons.project=<slug>`, and parallel-project isolation is preserved by the distinct per-project bind mounts (every `docker run` is its own container regardless of name — the name only added a singleton guard that broke reconnect). `cli/src/memory.sh` already stripped `--name` from its out-of-band recall path for this exact reason (*"avoid colliding with running serve container"*). atlas-aci's summary log line (`cli/src/mcp_atlas_aci.sh`) and its render tests (`cli/tests/mcp_atlas_aci.bats`) now assert the `--label` slug in place of the retired `--name`. Consumers already parse `.mcp.json` args by value, so existing generated files with `--name` remain readable; regenerate cleanly via `eidolons mcp sync`.
+
 ## [2.3.0] — 2026-07-07 — ECM P2/P3: host adapters + the atomos MCP
 
 ### Added

cli/src/mcp_atlas_aci.sh

@@ -80,7 +80,9 @@ What it does:
   4. Renders the Atlas-ACI MCP template into <project-root>/.mcp.json.
 
 The generated .mcp.json wires Atlas-ACI as a Docker-based MCP server with:
-  - A per-project container name (atlas-aci-<slug>) for parallel-project isolation.
+  - A per-project label (eidolons.project=<slug>) for identification/filtering.
+    No static --name — it would collide with the running serve container when the
+    host re-spawns on reconnect (docker: "container name already in use").
   - Distinct bind mounts so each project's codegraph.db is independent.
   - The pinned image digest (no tag drift).
 
@@ -296,7 +298,7 @@ fi
 
 # ─── Summary ──────────────────────────────────────────────────────────────
 info "Atlas-ACI MCP scaffold complete."
-info "  Container name : atlas-aci-${PROJECT_SLUG}"
+info "  Project label  : eidolons.project=${PROJECT_SLUG}"
 info "  Bind mount     : ${MEMEX_DIR} → /memex (inside container)"
 info "  Image digest   : ${IMAGE_DIGEST}"
 info ""

cli/templates/mcp/atlas-aci.mcp.json.tmpl

@@ -7,8 +7,6 @@
         "--rm",
         "-i",
         "--read-only",
-        "--name",
-        "atlas-aci-__PROJECT_SLUG__",
         "--label",
         "eidolons.project=__PROJECT_SLUG__",
         "-v",

cli/templates/mcp/atomos.mcp.json.tmpl

@@ -6,8 +6,6 @@
         "run",
         "--rm",
         "-i",
-        "--name",
-        "atomos-__PROJECT_SLUG__",
         "--label",
         "eidolons.project=__PROJECT_SLUG__",
         "-v",

cli/templates/mcp/crystalium.mcp.json.tmpl

@@ -6,8 +6,6 @@
         "run",
         "--rm",
         "-i",
-        "--name",
-        "crystalium-__PROJECT_SLUG__",
         "--label",
         "eidolons.project=__PROJECT_SLUG__",
         "-v",

cli/templates/mcp/tonberry.mcp.json.tmpl

@@ -6,8 +6,6 @@
         "run",
         "--rm",
         "-i",
-        "--name",
-        "tonberry-__PROJECT_SLUG__",
         "--label",
         "eidolons.project=__PROJECT_SLUG__",
         "-v",

cli/tests/mcp_atlas_aci.bats

@@ -214,16 +214,21 @@ file_md5() {
   # .atlas/memex/.gitkeep must exist.
   [ -f "$project/.atlas/memex/.gitkeep" ]
 
-  # The --name entry in the args array must equal "atlas-aci-<slug>".
+  # No static --name (it would collide with the running serve container on host
+  # reconnect). Per-project identity lives in the --label instead.
+  run bash -c "jq -e 'any(.mcpServers.\"atlas-aci\".args[]; . == \"--name\") | not' '$project/.mcp.json'"
+  [ "$status" -eq 0 ]
+
+  # The --label entry must equal "eidolons.project=<slug>".
   # Slug of "fresh-project" is "fresh-project".
-  local name_val
-  name_val="$(jq -r '
+  local label_val
+  label_val="$(jq -r '
     .mcpServers."atlas-aci".args as $a |
-    ($a | indices("--name"))[0] as $i |
+    ($a | indices("--label"))[0] as $i |
     $a[$i + 1]
   ' "$project/.mcp.json")"
 
-  [ "$name_val" = "atlas-aci-fresh-project" ]
+  [ "$label_val" = "eidolons.project=fresh-project" ]
 
   # Security hardening flags (H1): --cap-drop ALL and --security-opt no-new-privileges
   # must be present in the args array (defense-in-depth on top of the UID 10001 Dockerfile).
@@ -324,8 +329,8 @@ file_md5() {
   [ "$db_hash_before" = "$db_hash_after" ]
 }
 
-# ─── Test 4: two distinct project roots → distinct --name and bind paths ───
-@test "mcp atlas-aci: two distinct roots produce distinct --name values and bind-mount paths" {
+# ─── Test 4: two distinct project roots → distinct --label and bind paths ───
+@test "mcp atlas-aci: two distinct roots produce distinct --label values and bind-mount paths" {
   local project_a="$BATS_TEST_TMPDIR/project-alpha"
   local project_b="$BATS_TEST_TMPDIR/project-beta"
   mkdir -p "$project_a" "$project_b"
@@ -335,25 +340,25 @@ file_md5() {
   run_generator --project-root "$project_b"
   [ "$status" -eq 0 ]
 
-  # Extract --name values from each generated .mcp.json.
-  local name_a name_b
-  name_a="$(jq -r '
+  # Extract --label values from each generated .mcp.json.
+  local label_a label_b
+  label_a="$(jq -r '
     .mcpServers."atlas-aci".args as $a |
-    ($a | indices("--name"))[0] as $i |
+    ($a | indices("--label"))[0] as $i |
     $a[$i + 1]
   ' "$project_a/.mcp.json")"
-  name_b="$(jq -r '
+  label_b="$(jq -r '
     .mcpServers."atlas-aci".args as $a |
-    ($a | indices("--name"))[0] as $i |
+    ($a | indices("--label"))[0] as $i |
     $a[$i + 1]
   ' "$project_b/.mcp.json")"
 
-  # Names must differ.
-  [ "$name_a" != "$name_b" ]
+  # Labels must differ.
+  [ "$label_a" != "$label_b" ]
 
-  # Each --name must reference its own slug.
-  [ "$name_a" = "atlas-aci-project-alpha" ]
-  [ "$name_b" = "atlas-aci-project-beta" ]
+  # Each --label must reference its own slug.
+  [ "$label_a" = "eidolons.project=project-alpha" ]
+  [ "$label_b" = "eidolons.project=project-beta" ]
 
   # The bind-mount source for /memex must be distinct in each file.
   # Extract the string that precedes ":/memex" from the args array.
@@ -389,20 +394,20 @@ file_md5() {
   run bash -c "jq empty '$project/.mcp.json'"
   [ "$status" -eq 0 ]
 
-  # Extract the slug from the --name arg.
-  local name_val
-  name_val="$(jq -r '
+  # Extract the slug from the --label arg.
+  local label_val
+  label_val="$(jq -r '
     .mcpServers."atlas-aci".args as $a |
-    ($a | indices("--name"))[0] as $i |
+    ($a | indices("--label"))[0] as $i |
     $a[$i + 1]
   ' "$project/.mcp.json")"
 
-  # Expected: "atlas-aci-my-project-dir"
-  [ "$name_val" = "atlas-aci-my-project-dir" ]
+  # Expected: "eidolons.project=my-project-dir"
+  [ "$label_val" = "eidolons.project=my-project-dir" ]
 
-  # The slug portion (strip leading "atlas-aci-") must match
+  # The slug portion (strip leading "eidolons.project=") must match
   # the pattern: only lowercase letters, digits, and dashes.
-  local slug="${name_val#atlas-aci-}"
+  local slug="${label_val#eidolons.project=}"
   run bash -c "printf '%s' '$slug' | grep -Eq '^[a-z0-9-]+$'"
   [ "$status" -eq 0 ]