chore(compose): one compose file, and a pinned project name

AGENTS.md

@@ -560,7 +560,8 @@ poetry run python scripts/dev/timebox_log_query.py llm --log-path logs/llm_io_20
 - `NOTION_TIMEBOXING_PARENT_PAGE_ID`: parent page where DBs are installed/reused.
 
 ## Local run (dev)
-- Canonical stack is `docker-compose.yml` at repo root (the `infra/docker-compose-2.yml` file is legacy).
+- The stack is `docker-compose.yml` at repo root, and it is the only compose file for it.
+  It pins `name: admonish-1`, so volumes keep one set of names no matter where you run it from.
 - VS Code tasks in `.vscode/tasks.json` start the stack (`FateForger: Compose Up (Core)` / `FateForger: Compose Up (Everything)`).
 
 ## Testing and test suite upkeep

docker-compose.yml

@@ -1,5 +1,12 @@
 version: "3.9"
 
+# Pin the project name. Compose otherwise derives it from the directory the
+# file happens to sit in, so the same service run from two places gets two
+# sets of volumes. That is exactly how the calendar server ended up with an
+# empty `tokens.json` while the real credentials sat in a volume nothing
+# mounted (2026-09-09).
+name: admonish-1
+
 volumes:
   ticktick_data:
     driver: local

scripts/README.md

@@ -216,11 +216,6 @@ For the active durable-memory runtime path, start Neo4j + Graphiti MCP from the
 docker compose up -d neo4j graphiti-mcp
 ```
 
-Or use the infra-only stack:
-
-```bash
-docker compose -f infra/docker-compose.yml up -d neo4j graphiti-mcp
-```
 
 Expected local endpoints: