@rubytech/create-maxy 1.0.709 → 1.0.711

package/payload/platform/plugins/memory/mcp/scripts/boot-smoke.sh

@@ -0,0 +1,69 @@
+#!/usr/bin/env bash
+# Memory MCP boot-smoke gate (Task 743).
+#
+# Spawns dist/index.js with a stub env, holds stdin open via `tail -f /dev/null`
+# (the MCP SDK's StdioServerTransport exits on EOF — closing stdin would mask a
+# clean boot as a failure), sleeps 2s, then asserts the process is still alive.
+# A schema-loader throw, an import failure, or any other module-load fault
+# would have killed the child by now and `kill -0` would return non-zero.
+#
+# Wired to the memory MCP `prepublish` script in package.json so a regression
+# can never reach npm publish without the gate firing first. Local matrix:
+#
+#   $ ./scripts/boot-smoke.sh
+#   [boot-smoke] memory ok
+#
+#   $ # break the schema content, rebuild, retry
+#   $ ./scripts/boot-smoke.sh
+#   [boot-smoke] memory FAILED tail=<schema-loader throw>
+#   exit 1
+set -euo pipefail
+
+SCRIPT_DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
+MCP_DIR=$(cd "$SCRIPT_DIR/.." && pwd)
+ENTRY="$MCP_DIR/dist/index.js"
+PLATFORM_ROOT=$(cd "$MCP_DIR/../../.." && pwd)
+
+if [ ! -f "$ENTRY" ]; then
+  echo "[boot-smoke] memory FAILED tail=\"dist/index.js missing — run npm run build first\"" >&2
+  exit 1
+fi
+
+LOG_DIR=$(mktemp -d -t mcp-boot-smoke.XXXXXX)
+trap 'rm -rf "$LOG_DIR"' EXIT
+
+# stdin from a `tail -f /dev/null` keeps the StdioServerTransport open. The
+# pipeline's left side is a tiny long-running process; the right side is the
+# MCP server we are smoke-testing. Both are killed below.
+# Disable pipefail for this block — when bash forks the pipeline, $! is the
+# PID of the LAST command (the node process), which is what we test below.
+set +o pipefail
+
+tail -f /dev/null | env \
+  ACCOUNT_ID=boot-smoke-test \
+  PLATFORM_ROOT="$PLATFORM_ROOT" \
+  LOG_DIR="$LOG_DIR" \
+  STREAM_LOG_PATH="$LOG_DIR/stream.log" \
+  NEO4J_URI=bolt://localhost:7687 \
+  SESSION_ID=boot-smoke \
+  node "$ENTRY" > /dev/null 2>"$LOG_DIR/stderr-direct.log" &
+
+NODE_PID=$!
+sleep 2
+
+if ! kill -0 "$NODE_PID" 2>/dev/null; then
+  TAIL=$(tail -n 5 "$LOG_DIR/stderr-direct.log" 2>/dev/null | tr '\n' ' ' | sed 's/"/\\"/g')
+  echo "[boot-smoke] memory FAILED tail=\"$TAIL\"" >&2
+  # Reap the tail process by killing its parent group (the pipeline subshell).
+  kill 0 2>/dev/null || true
+  exit 1
+fi
+
+echo "[boot-smoke] memory ok"
+kill "$NODE_PID" 2>/dev/null || true
+# Reap the still-running `tail -f /dev/null` so the script exits cleanly.
+# `disown` first so bash does not print a job-control "Terminated" line
+# when the pipeline subshell is killed by exit-trap.
+{ disown -a 2>/dev/null; pkill -P $$ -f "tail -f /dev/null"; } 2>/dev/null || true
+wait 2>/dev/null || true
+exit 0

package/payload/platform/plugins/memory/references/graph-primitives.md

@@ -38,6 +38,28 @@ deterministic path through the shim is the only supported way to read
 the graph, and any substitute path loses the read-only + namespace +
 token-limit discipline the upstream server enforces.
 
+## When the memory tools are absent
+
+If `mcp__memory__memory-write`, `mcp__memory__memory-search`,
+`mcp__memory__memory-rank`, `mcp__memory__memory-reindex`,
+`mcp__memory__session-compact`, `mcp__memory__session-compact-status`, or
+`mcp__memory__conversation-search` is missing from your tool list, the
+memory MCP server failed to start on this device. Reply once with
+exactly:
+
+> The memory MCP server failed to start on this device. Run the admin
+> system-status check to diagnose — do not retry by other routes.
+
+Then stop. Do not search for a similarly-named tool via `ToolSearch`, do
+not improvise via `maxy-graph-read_neo4j_cypher` (it is read-only — every
+write goes through the schema-aware memory tools), do not paraphrase.
+A missing memory tool is a deterministic failure of the per-account
+memory server: the platform's `[mcp-init-error] server=memory` line in
+the per-conversation stream log already names it; the user-facing reply
+exists so the operator knows the session cannot proceed without an
+operator-side fix (Task 743 propagates Task 560's loud-fail contract
+from graph to memory).
+
 ## Mutation intents
 
 The graph tools above are read-only. Every write intent has a schema-aware

package/payload/platform/plugins/memory/references/schema-base.md

@@ -165,7 +165,7 @@ The classifier returns `kind` strings from the closed enumeration above. `kind`
 | `CREATED` | `UserProfile` → `Project` | Standalone-node anchor. |
 | `UNDER` | `Project` → `Organization` | Optional Project context. |
 | `AT` | `Section:Position` → `Organization` | Position's employer. |
-| `PARTY` | `KnowledgeDocument` → `Person|Organization` | Contract Parties — written from `documentEdges`. |
+| `PARTY` | `KnowledgeDocument` → `Person` or `Organization` | Contract Parties — written from `documentEdges`. |
 | `DEFINES` | `Section:Definitions` → `DefinedTerm` | Contract definitions — written from per-section `related`. |
 
 **Ontology-growth review query.** When a document accumulates several `:Section:Other` nodes, the operator (or admin agent) can run the following Cypher to surface candidate ontology additions: