README: update Claude Desktop examples and directory tree for entry points\n\nConfig examples now show venv/bin/heddle-mesh (no args) instead of\npython heddle_stdio_mesh.py. Directory tree reflects that entry-point\nscripts moved from project root into src/heddle/ with console_scripts\nregistration in pyproject.toml.\n\nv0.2 Pillar 3.

Author: goweft

README.md

@@ -254,8 +254,7 @@ To expose a unified Heddle mesh to Claude Desktop (and optionally to [CAS](https
 {
   "mcpServers": {
     "heddle-mesh": {
-      "command": "/path/to/heddle/venv/bin/python",
-      "args": ["/path/to/heddle/heddle_stdio_mesh.py"]
+      "command": "/path/to/heddle/venv/bin/heddle-mesh"
     }
   }
 }
@@ -300,8 +299,7 @@ heddle/
 │   ├── agents/          # Custom higher-level handlers
 │   └── web/             # Dashboard backend and frontend
 ├── tests/
-├── heddle_stdio_mesh.py # Unified Claude Desktop launcher
-└── heddle_dashboard.py  # Web dashboard launcher
+└── pyproject.toml       # Entry points: heddle, heddle-dashboard, heddle-mesh
 ```
 
 ## Tech Stack
@@ -332,8 +330,7 @@ CAS runs standalone. Heddle integration is optional and adds:
 {
   "mcpServers": {
     "heddle-mesh": {
-      "command": "/path/to/heddle/venv/bin/python",
-      "args": ["/path/to/heddle/heddle_stdio_mesh.py"]
+      "command": "/path/to/heddle/venv/bin/heddle-mesh"
     }
   }
 }