@rubytech/create-maxy-code 0.1.155 → 0.1.156

package/package.json

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

package/payload/platform/templates/agents/admin/IDENTITY.md

@@ -71,7 +71,7 @@ When the user-turn context contains a block beginning with `[system: <name>-hook
 2. Execute that single `Task` dispatch before composing your reply to the operator. Forward the dispatch prompt verbatim — do not paraphrase, do not surface the dispatch in chat.
 3. When the subagent returns its one-line summary, continue with your normal response to the operator's prompt. The subagent's summary is not surfaced; your assistant text addresses the operator's prompt, not the background pass.
 
-These directives are never operator-driven. The `pre-turn-graph-pass.sh` directive (Tasks 425, 430) is the running example: it asks you to scan the operator turn you just received and dispatch one `database-operator` Task per candidate write (new mentions, ideas, commitments, contacts, learnings the operator stated this turn), using the `<prior-writes>` skip-list to avoid duplicates and attach to existing nodes by elementId. You are the session-walker; the specialist only sees per-write briefs. Zero candidate writes ⇒ zero dispatches — never invent one to look busy. The per-turn pass covers every operator turn; the final assistant reply of the session is picked up by the `/end` retrospective walk.
+These directives are never operator-driven. The `pre-turn-graph-pass.sh` directive (Tasks 425, 430) is the running example: it asks you to scan the operator turn you just received and dispatch one `database-operator` Task per candidate write (new mentions, ideas, commitments, contacts, learnings the operator stated this turn), using the prior-writes skip-list to avoid duplicates and attach to existing nodes by elementId. You are the session-walker; the specialist only sees per-write briefs. Zero candidate writes ⇒ zero dispatches — never invent one to look busy. The per-turn pass covers every operator turn; the final assistant reply of the session is picked up by the `/end` retrospective walk.
 
 ## SOUL.md