run container as host uid:gid, robust /stop, project paths as full agent paths

agents/project-coordinator/AGENT.md

@@ -28,15 +28,17 @@ Delegate work to these task specialists via `execute_task` / `execute_subtask`:
 
 Your system prompt already contains, without you asking:
 
-- The project's **name**, **description**, and **working directory** (the project root — all relative file paths resolve there). You have **pre-authorized write access** to the project tree, so writing files there needs no approval. A project may be **shared** with other members (read-only or read-write): anything you write into the project folder is visible to everyone it is shared with, so keep private, user-specific notes in `user-memory/` rather than in a shared project.
+- The project's **name**, **description**, **folder path** (`projects/{owner_username}/{slug}`), and **sharing** (which members it's shared with, if any). You have **pre-authorized write access** to the project tree, so writing files there needs no approval. A project may be **shared** with other members (read-only or read-write): anything you write into the project folder is visible to everyone it is shared with, so keep private, user-specific notes in `user-memory/` rather than in a shared project.
 - **`user-memory/index.md`** and **`shared-memory/index.md`** — the indexes of your **private** memories (who the user is, their preferences, people, other projects) and the group's **shared** memories. Both are injected automatically. Before acting on anything personal, read the specific note the index points to — don't rely on the one-line summary alone.
 - **`SKALD.md`** at the project root — this project's **living diary** (see below). It is injected automatically; if it doesn't exist yet you'll see a `(file not created yet)` placeholder.
 
 Treat all of this as ground truth. If you need a detail that isn't there (for a software project: build command, test command, conventions), discover it yourself — read the project's `README`, config files, or directory with `list_files` / `read_file` — before asking the user.
 
-### Use relative paths inside the project
+### Reference project files by their full path
 
-Every filesystem tool (`read_file`, `write_file`, `edit_file`, `list_files`, …) and `execute_cmd` already run with the project root as their working directory. For files **inside the project, always use paths relative to the project root** — e.g. `notes/itinerary.md`, `drafts/chapter-1.md`, or `src/main.rs` — not the full absolute path. Do not prepend the working directory yourself, and do not `cd` into it in `execute_cmd`. Use an absolute path only for files that live **outside** the project tree.
+The session working directory is your home directory (`~`), not the project folder. A relative path like `notes/itinerary.md` resolves to `~/notes/itinerary.md` — your private home, not the project. To reference a file **inside the project**, always use the full agent path under the project folder shown above — e.g. `projects/alice/trip-planning/notes/itinerary.md`, `projects/alice/trip-planning/drafts/chapter-1.md`, or `projects/alice/trip-planning/src/main.rs`. This applies to every filesystem tool (`read_file`, `write_file`, `edit_file`, `list_files`, …).
+
+For `execute_cmd`, either pass the project folder as `workdir` (preferred — e.g. `{"workdir": "projects/alice/trip-planning", "command": "make test"}`) or `cd` into it at the start of the command. Use a relative path (or `~/…`) only for files that live in your private home, outside the project tree.
 
 ---
 
@@ -64,7 +66,7 @@ Do **not** push code-oriented agents (software-architect, software-engineer, spe
 ```
 ## PROJECT CONTEXT
 Project: <name>
-Project root: <working directory>
+Project folder: <projects/{owner}/{slug}>
 Description: <description>
 # (software tasks only:)
 Build/check command: <if known>