docs: simplify default docker config; move project mount to advanced section

Remove -v workspaceFolder and -e AGENT_CONFIG_DIR from Options A and B.
Server runs in schema-free mode by default — project mount is only needed
for custom note schemas. Add Advanced section explaining the project mount
should only appear in per-project .mcp.json (Option B), not global
registrations (Option A), to avoid per-project schema bleed on shared configs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: jpicklyk

README.md

@@ -74,8 +74,6 @@ claude mcp add-json mcp-task-orchestrator '{
   "args": [
     "run", "--rm", "-i",
     "-v", "mcp-task-data:/app/data",
-    "-v", "${workspaceFolder}:/project:ro",
-    "-e", "AGENT_CONFIG_DIR=/project",
     "ghcr.io/jpicklyk/task-orchestrator:latest"
   ]
 }'
@@ -95,8 +93,6 @@ Add to `.mcp.json` in your project root (checked into source control so teammate
       "args": [
         "run", "--rm", "-i",
         "-v", "mcp-task-data:/app/data",
-        "-v", "${workspaceFolder}:/project:ro",
-        "-e", "AGENT_CONFIG_DIR=/project",
         "ghcr.io/jpicklyk/task-orchestrator:latest"
       ]
     }
@@ -110,6 +106,31 @@ The `mcp-task-data` Docker volume persists the SQLite database across container
 
 Configure your client with the same JSON as Option A above. STDIO transport works with any MCP-compatible client.
 
+### Advanced: Per-Project Note Schemas
+
+By default the server runs in schema-free mode — all 13 tools work with no additional configuration. If you want to define custom note schemas that gate role transitions (e.g., require an acceptance-criteria note before a work item can advance), you can point the server at your project's `.taskorchestrator/config.yaml`.
+
+Add the project mount to your **Option B** `.mcp.json` only (not the global Option A registration — a globally-registered server should not have its schema config vary per project):
+
+```json
+{
+  "mcpServers": {
+    "mcp-task-orchestrator": {
+      "command": "docker",
+      "args": [
+        "run", "--rm", "-i",
+        "-v", "mcp-task-data:/app/data",
+        "-v", "${workspaceFolder}:/project:ro",
+        "-e", "AGENT_CONFIG_DIR=/project",
+        "ghcr.io/jpicklyk/task-orchestrator:latest"
+      ]
+    }
+  }
+}
+```
+
+See [Workflow Guide](current/docs/workflow-guide.md) for the `.taskorchestrator/config.yaml` schema format and examples.
+
 ### Step 3: Claude Code Plugin (optional)
 
 Install the plugin for workflow skills, session-start hooks, and an orchestrator output style: