@rubytech/create-maxy 1.0.762 → 1.0.763

package/package.json

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

package/payload/platform/neo4j/schema.cypher

@@ -802,6 +802,56 @@ FOR (tc:ToolCall) REQUIRE tc.callId IS UNIQUE;
 CREATE INDEX tool_call_account_started IF NOT EXISTS
 FOR (tc:ToolCall) ON (tc.accountId, tc.startedAt);
 
+// ----------------------------------------------------------
+// Component — Task 815 admin-resume rehydration.
+//
+// Every render-component event emitted on an assistant turn
+// produces one Component node linked to its parent Message via
+// (Message)-[:HAS_COMPONENT]->(Component). The agent's narrative
+// text stays on Message.content; component name + data JSON +
+// position-relative-to-text live here. Sibling-node design (not
+// JSON-on-Message) avoids Neo4j's 128KB property soft-limit when
+// document-editor bodies are large.
+//
+// Atomicity: persisted in the same Cypher transaction as the
+// parent Message — no orphan Component possible. Reader is a
+// single round-trip via OPTIONAL MATCH + collect (sort-before-
+// collect: WITH m, c ORDER BY c.ordinal ASC, then collect).
+//
+// Properties:
+//   componentId  — UUID, primary key
+//   conversationId / accountId / messageId — denormalised for
+//     account-scoped reads and cross-account isolation audits
+//   name         — component name (document-editor, action-buttons,
+//                   single-select, etc.)
+//   data         — JSON-encoded payload string. Validated structurally
+//                   on read (parseable, non-null object); per-component
+//                   schema validation lives in validateComponentData.
+//   ordinal      — 0-indexed sequence within the parent Message,
+//                   tiebreak for components with the same textOffset.
+//   textOffset   — length of Message.content at the moment this
+//                   component arrived in the SSE stream. Reader uses
+//                   it to interleave text-runs and components when
+//                   reconstructing events: AdminEvent[].
+//   submitted    — true once a PERSISTENT_COMPONENT (action-list,
+//                   document-editor, rich-content-editor, grid-editor)
+//                   was submitted by the user. Server-side detection
+//                   of `_componentDone:true` user turns flips this.
+//   submittedAt  — datetime when submitted=true was set (null otherwise)
+//   createdAt    — datetime when the component was persisted
+//
+// (:Message)-[:HAS_COMPONENT]->(:Component)
+// ----------------------------------------------------------
+
+CREATE CONSTRAINT component_id_unique IF NOT EXISTS
+FOR (c:Component) REQUIRE c.componentId IS UNIQUE;
+
+CREATE INDEX component_message IF NOT EXISTS
+FOR (c:Component) ON (c.messageId);
+
+CREATE INDEX component_account IF NOT EXISTS
+FOR (c:Component) ON (c.accountId);
+
 // ----------------------------------------------------------
 // :Trashed — Task 576 soft-delete primitive.
 //