@rubytech/create-maxy 1.0.699 → 1.0.700

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.699",
+  "version": "1.0.700",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/plugins/docs/references/deployment.md

@@ -65,6 +65,7 @@ The logs will show which service failed to start and why. Common causes:
 - **Neo4j not started** — run `sudo systemctl start neo4j` and retry
 - **Port 19200 already in use** — check for another process: `lsof -i :19200`
 - **Claude OAuth expired** — the next admin session will prompt you to re-authenticate
+- **NEO4J_URI port mismatch** — the admin agent throws `port :X disagrees with brand.json neo4jPort :Y`. Edit `NEO4J_URI` in `~/{configDir}/.env` to match the brand's declared `neo4jPort`, or correct `neo4jPort` in `brand.json` and reinstall. (Task 681)
 
 ## Systemd units on each device
 

package/payload/platform/plugins/docs/references/graph.md

@@ -36,3 +36,19 @@ the filter popover to surface them; they render with a faded fill and dashed
 border, with their zoom-tier labels intact. The `N msgs` count excludes
 trashed Messages, so the detailed-tier label reflects only live turns in the
 conversation.
+
+## Agent-execution telemetry
+
+`ToolCall`, `StepResult`, `WorkflowStep`, and `WorkflowRun` nodes are
+agent-execution telemetry — kept for audit but noisy for day-to-day graph
+navigation (they make up roughly 9% of a typical brand's live nodes).
+They are hidden from `/graph` by default. To see them — for audit, debug,
+or tracing a specific agent run — open the filter popover and tick
+**Include agent actions** (the checkbox directly below **Show trashed**).
+Flipping it on surfaces the four labels as chips in the popover roster AND
+keeps them on the canvas when you pivot into a neighbourhood. The toggle
+is session-scoped: every new session starts with agent actions hidden, so
+the 90% domain-navigation path stays clean without having to remember to
+switch them off. Flipping it off again also drops them from any already-
+expanded neighbourhood so a click near a `ToolCall` does not re-introduce
+it.