@rubytech/create-realagent-code 0.1.30 → 0.1.31

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-realagent-code",
-  "version": "0.1.30",
+  "version": "0.1.31",
   "description": "Install Real Agent — Built for agents. By agents.",
   "bin": {
     "create-realagent-code": "./dist/index.js"

package/payload/platform/lib/persistent-components/dist/index.d.ts

@@ -1,17 +1,16 @@
 /**
- * The component names that the platform UI treats as long-lived editor
- * surfaces (not single-shot prompts). They survive multiple `onSubmit`
- * fires because the operator may auto-save mid-edit, and they are also
- * the **server-side commitment surface** for Task 942: when the admin
- * agent emits one of these names via `render-component`, the live
- * stream-parser materialises the inline content as a sibling
- * `:KnowledgeDocument` artefact so the row appears in the artefacts
- * panel and survives session compaction.
+ * The historical persistent-component names. Pre-Task-066 the admin
+ * agent could emit a component tool_use carrying one of these names,
+ * and the live stream-parser materialised the inline content as a
+ * sibling `:KnowledgeDocument` artefact so the row appeared in the
+ * artefacts panel and survived session compaction.
  *
- * Single source of truth — the platform UI (`app/admin-types.ts`) and
- * the admin MCP server (`plugins/admin/mcp/src/index.ts`) both import
- * from this module. Any drift here is an account-isolation /
- * persistence-doctrine bug; keep the constant in one place.
+ * The emitting tool is gone on native Claude Code (Task 066); the
+ * constant is preserved so the rehydration path can still recognise
+ * `:Component` rows written by older conversations. New conversations
+ * never produce these rows. The single-source-of-truth contract still
+ * holds: `app/admin-types.ts` and any consumer that needs to classify
+ * a stored component name imports from here.
  */
 export declare const PERSISTENT_COMPONENTS: Set<string>;
 /**

package/payload/platform/lib/persistent-components/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,qBAAqB,aAKhC,CAAC;AAEH;;GAEG;AACH,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,GAAG,IAAI,GAAG,OAAO,CAE9E"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,qBAAqB,aAKhC,CAAC;AAEH;;GAEG;AACH,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,GAAG,IAAI,GAAG,OAAO,CAE9E"}

package/payload/platform/lib/persistent-components/dist/index.js

@@ -3,19 +3,18 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.PERSISTENT_COMPONENTS = void 0;
 exports.isPersistentComponent = isPersistentComponent;
 /**
- * The component names that the platform UI treats as long-lived editor
- * surfaces (not single-shot prompts). They survive multiple `onSubmit`
- * fires because the operator may auto-save mid-edit, and they are also
- * the **server-side commitment surface** for Task 942: when the admin
- * agent emits one of these names via `render-component`, the live
- * stream-parser materialises the inline content as a sibling
- * `:KnowledgeDocument` artefact so the row appears in the artefacts
- * panel and survives session compaction.
+ * The historical persistent-component names. Pre-Task-066 the admin
+ * agent could emit a component tool_use carrying one of these names,
+ * and the live stream-parser materialised the inline content as a
+ * sibling `:KnowledgeDocument` artefact so the row appeared in the
+ * artefacts panel and survived session compaction.
  *
- * Single source of truth — the platform UI (`app/admin-types.ts`) and
- * the admin MCP server (`plugins/admin/mcp/src/index.ts`) both import
- * from this module. Any drift here is an account-isolation /
- * persistence-doctrine bug; keep the constant in one place.
+ * The emitting tool is gone on native Claude Code (Task 066); the
+ * constant is preserved so the rehydration path can still recognise
+ * `:Component` rows written by older conversations. New conversations
+ * never produce these rows. The single-source-of-truth contract still
+ * holds: `app/admin-types.ts` and any consumer that needs to classify
+ * a stored component name imports from here.
  */
 exports.PERSISTENT_COMPONENTS = new Set([
     'action-list',

package/payload/platform/lib/persistent-components/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";;;AAyBA,sDAEC;AA3BD;;;;;;;;;;;;;;GAcG;AACU,QAAA,qBAAqB,GAAG,IAAI,GAAG,CAAS;IACnD,aAAa;IACb,iBAAiB;IACjB,qBAAqB;IACrB,aAAa;CACd,CAAC,CAAC;AAEH;;GAEG;AACH,SAAgB,qBAAqB,CAAC,IAA+B;IACnE,OAAO,OAAO,IAAI,KAAK,QAAQ,IAAI,6BAAqB,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;AACrE,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";;;AAwBA,sDAEC;AA1BD;;;;;;;;;;;;;GAaG;AACU,QAAA,qBAAqB,GAAG,IAAI,GAAG,CAAS;IACnD,aAAa;IACb,iBAAiB;IACjB,qBAAqB;IACrB,aAAa;CACd,CAAC,CAAC;AAEH;;GAEG;AACH,SAAgB,qBAAqB,CAAC,IAA+B;IACnE,OAAO,OAAO,IAAI,KAAK,QAAQ,IAAI,6BAAqB,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;AACrE,CAAC"}

package/payload/platform/lib/persistent-components/src/index.ts

@@ -1,17 +1,16 @@
 /**
- * The component names that the platform UI treats as long-lived editor
- * surfaces (not single-shot prompts). They survive multiple `onSubmit`
- * fires because the operator may auto-save mid-edit, and they are also
- * the **server-side commitment surface** for Task 942: when the admin
- * agent emits one of these names via `render-component`, the live
- * stream-parser materialises the inline content as a sibling
- * `:KnowledgeDocument` artefact so the row appears in the artefacts
- * panel and survives session compaction.
+ * The historical persistent-component names. Pre-Task-066 the admin
+ * agent could emit a component tool_use carrying one of these names,
+ * and the live stream-parser materialised the inline content as a
+ * sibling `:KnowledgeDocument` artefact so the row appeared in the
+ * artefacts panel and survived session compaction.
  *
- * Single source of truth — the platform UI (`app/admin-types.ts`) and
- * the admin MCP server (`plugins/admin/mcp/src/index.ts`) both import
- * from this module. Any drift here is an account-isolation /
- * persistence-doctrine bug; keep the constant in one place.
+ * The emitting tool is gone on native Claude Code (Task 066); the
+ * constant is preserved so the rehydration path can still recognise
+ * `:Component` rows written by older conversations. New conversations
+ * never produce these rows. The single-source-of-truth contract still
+ * holds: `app/admin-types.ts` and any consumer that needs to classify
+ * a stored component name imports from here.
  */
 export const PERSISTENT_COMPONENTS = new Set<string>([
   'action-list',

package/payload/platform/neo4j/schema.cypher

@@ -911,9 +911,12 @@ 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
+// Each legacy component event emitted on an assistant turn (pre-066
+// admin agent surface only) produced one Component node linked to its
+// parent Message via (Message)-[:HAS_COMPONENT]->(Component). New
+// conversations never write to this table; the rehydration path keeps
+// the rows in place so historical conversations replay intact. 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

package/payload/platform/plugins/admin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "admin",
-  "description": "Platform administration plugin. Provides system-status, public-hostname (deterministic Cloudflare public-URL resolver, single call returning the operator's canonical hostname so agents never guess property names on :CloudflareHostname nodes), brand-settings, account-manage, account-update, admin-add, admin-remove, admin-list, admin-update-pin, agent-list, agent-config-read, logs-read, plugin-read, skill-load (one-call resolve+read for SKILL.md by skill name, the canonical primitive for loading a named skill; plugin-read remains the reader for references/* and PLUGIN.md), store-skill (deterministic write counterpart to plugin-read; persists operator-authored skills as plugin files under the active account), session-reset, session-resume, file-attach, wifi, and action-approval tools (action-pending, action-approve, action-reject, action-edit) for managing the Maxy platform. The `render-component` MCP tool is also registered but is exposed to the public agent surface only (Anthropic API runtime); the admin agent on native Claude Code does not call it.",
+  "description": "Platform administration plugin. Provides system-status, public-hostname (deterministic Cloudflare public-URL resolver, single call returning the operator's canonical hostname so agents never guess property names on :CloudflareHostname nodes), brand-settings, account-manage, account-update, admin-add, admin-remove, admin-list, admin-update-pin, agent-list, agent-config-read, logs-read, plugin-read, skill-load (one-call resolve+read for SKILL.md by skill name, the canonical primitive for loading a named skill; plugin-read remains the reader for references/* and PLUGIN.md), store-skill (deterministic write counterpart to plugin-read; persists operator-authored skills as plugin files under the active account), session-reset, session-resume, file-attach, wifi, and action-approval tools (action-pending, action-approve, action-reject, action-edit) for managing the Maxy platform.",
   "version": "0.1.0",
   "author": {
     "name": "Rubytech LLC"

package/payload/platform/plugins/admin/PLUGIN.md

@@ -1,6 +1,6 @@
 ---
 name: admin
-description: "Platform administration plugin. Provides system-status, public-hostname (deterministic Cloudflare public-URL resolver, single call returning the operator's canonical hostname so agents never guess property names on :CloudflareHostname nodes), brand-settings, account-manage, account-update, admin-add, admin-remove, admin-list, admin-update-pin, agent-list, agent-config-read, logs-read, plugin-read, skill-load (one-call resolve+read for SKILL.md by skill name, the canonical primitive for loading a named skill; plugin-read remains the reader for references/* and PLUGIN.md), store-skill (deterministic write counterpart to plugin-read; persists operator-authored skills as plugin files under the active account), session-reset, session-resume, file-attach, wifi, and action-approval tools (action-pending, action-approve, action-reject, action-edit) for managing the Maxy platform. The `render-component` MCP tool is also registered but is exposed to the public agent surface only (Anthropic API runtime); the admin agent on native Claude Code does not call it."
+description: "Platform administration plugin. Provides system-status, public-hostname (deterministic Cloudflare public-URL resolver, single call returning the operator's canonical hostname so agents never guess property names on :CloudflareHostname nodes), brand-settings, account-manage, account-update, admin-add, admin-remove, admin-list, admin-update-pin, agent-list, agent-config-read, logs-read, plugin-read, skill-load (one-call resolve+read for SKILL.md by skill name, the canonical primitive for loading a named skill; plugin-read remains the reader for references/* and PLUGIN.md), store-skill (deterministic write counterpart to plugin-read; persists operator-authored skills as plugin files under the active account), session-reset, session-resume, file-attach, wifi, and action-approval tools (action-pending, action-approve, action-reject, action-edit) for managing the Maxy platform."
 tools:
   - name: system-status
     publicAllowlist: false
@@ -32,8 +32,6 @@ tools:
     publicAllowlist: false
   - name: store-skill
     publicAllowlist: false
-  - name: render-component
-    publicAllowlist: false
   - name: session-reset
     publicAllowlist: false
   - name: session-resume

package/payload/platform/plugins/admin/hooks/onboarding-skill-drift.sh

@@ -1,8 +1,9 @@
 #!/usr/bin/env bash
-# Task 063 / Task 049. Stop-event hook that flags admin agent onboarding
-# drift on the native Claude Code (PTY) surface. Post-Task-049 there is no
-# `render-component` tool, so the contract is no longer "called render-component";
-# it is "the assistant ends its turn on a prompt the operator can answer".
+# Task 063 / 066. Stop-event hook that flags admin agent onboarding
+# drift on the native Claude Code (PTY) surface. The contract is "the
+# assistant ends its turn on a prompt the operator can answer" — no
+# named tool, no per-turn imperative, just a chat-surface end-state
+# check.
 #
 # Behaviour:
 #   1. Read transcript_path from the Stop event JSON on stdin.

package/payload/platform/plugins/admin/mcp/dist/index.js

@@ -10,7 +10,6 @@ import { execFileSync } from "node:child_process";
 import { appendFileSync, cpSync, existsSync, mkdirSync, readdirSync, readFileSync, renameSync, rmSync, statSync, writeFileSync } from "node:fs";
 import { writeKey, validateKey, hasKey, keyFilePath, deleteKey } from "../../../../lib/anthropic-key/dist/index.js";
 import { writeAdminEntry, removeAdminFromAccount } from "../../../../lib/admins-write/dist/index.js";
-import { isPersistentComponent } from "../../../../lib/persistent-components/dist/index.js";
 import { deviceUrlBlock } from "../../../../lib/device-url/dist/index.js";
 import { substituteBrandPlaceholders } from "../../../../lib/brand-templating/dist/index.js";
 import { resolveEntitlement } from "../../../../lib/entitlement/dist/index.js";
@@ -507,7 +506,7 @@ const PLUGIN_DISPLAY = {
     waitlist: { value: "waitlist", label: "waitlist", description: "Waitlist lifecycle — extract sign-ups, review, schedule automation." },
     replicate: { value: "replicate", label: "replicate", description: "Image generation — photorealistic, design, and fast draft images via Replicate. Enhances: content-producer, research-assistant" },
 };
-server.tool("onboarding-plugin-options", "Return the fully-assembled multi-select options array for onboarding Step 1. Classification (core/recommended/available) is derived from brand.json — the agent renders the result directly via render-component without further transformation.", {}, async () => {
+server.tool("onboarding-plugin-options", "Return the fully-assembled plugin options array for onboarding Step 1. Classification (core/recommended/available) is derived from brand.json — the agent presents the entries to the operator as a numbered list in plain chat without further transformation.", {}, async () => {
     try {
         const brandPath = resolve(PLATFORM_ROOT, "config", "brand.json");
         if (!existsSync(brandPath)) {
@@ -1769,50 +1768,15 @@ eagerTool(server, "skill-load", "Load a plugin skill's SKILL.md body by skill na
         };
     }
 });
-// Task 940 — `"rendered"` is a sentinel, not a persistence ack. The platform
-// UI's stream-parser intercepts this tool_use upstream of the SDK reply
-// (platform/ui/app/lib/claude-agent/stream-parser.ts:362) and emits a typed
-// `component` event that admin-agent.ts's persistMessage flushes to Neo4j as
-// a sibling :Component node.
-//
-// Task 942 — render-component is also the *server commitment surface* for
-// PERSISTENT_COMPONENTS (action-list, document-editor, rich-content-editor,
-// grid-editor). The actual file write + :KnowledgeDocument projection lives
-// in the admin server process (stream-parser path) because the SDK delivers
-// `tool_use.input` to the UI in the assistant message but the MCP handler's
-// return reaches only the agent — there is no path back to persistMessage
-// from here. This handler emits a one-line observability marker per
-// persistence-eligible call so operators can grep for the commitment, and
-// returns richer JSON so the doctrine grep
-// `render-component.*"rendered"` resolves to a persistence-aware handler
-// rather than a bare stub.
-eagerTool(server, "render-component", "Render a pre-built UI component inline in the conversation. " +
-    "Call this instead of describing a UI — the component handles input collection. " +
-    "Wait for the user's response before continuing.", {
-    name: z.string().describe("Component name from the UI suite (e.g. single-select, confirm, info-card, form, progress)"),
-    data: z.record(z.string(), z.unknown()),
-}, async ({ name, data }) => {
-    if (isPersistentComponent(name)) {
-        // Persistence-eligible: log the commitment so the live + audit grep
-        // (`[render-component-persist]`) can correlate the MCP call against
-        // the downstream :KnowledgeDocument MERGE. Byte counts come from
-        // data.html (preferred) or data.content; both being absent is a
-        // legitimate render of an empty editor and the projection is skipped
-        // server-side.
-        const html = typeof data?.html === "string" ? data.html : "";
-        const content = typeof data?.content === "string" ? data.content : "";
-        const bytes = html.length > 0 ? html.length : content.length;
-        const mimeType = html.length > 0 ? "text/html" : (content.length > 0 ? "text/markdown" : "");
-        console.error(`[render-component-persist] componentName=${name} bytes=${bytes} mimeType=${mimeType || "none"}`);
-        return {
-            content: [{
-                    type: "text",
-                    text: JSON.stringify({ rendered: true, name, persistent: true, bytes, mimeType }),
-                }],
-        };
-    }
-    return { content: [{ type: "text", text: "rendered" }] };
-});
+// Task 066 — the inline UI-component tool is gone from the admin surface
+// on native Claude Code. The PTY runtime has no host bridge for the UI
+// primitives the legacy tool wrapped; calling it logged a "rendered"
+// sentinel that read like a successful render to the agent while the
+// chat surface saw nothing. Admin flows now use plain markdown for
+// reviewable artefacts (`skills/file-presentation/SKILL.md`) and
+// `file-attach` for downloadable artefacts. The :Component / :KnowledgeDocument
+// persistence pipeline is preserved for historical conversations that
+// already carry the rows; no new conversations write to it.
 eagerTool(server, "session-reset", "Reset the current session. Compacts conversation history to memory, clears the visible conversation, " +
     "and starts a fresh session with a new greeting. Call when the user asks to start a new session, " +
     "clear the conversation, or start fresh.", {}, async () => ({ content: [{ type: "text", text: "reset" }] }));
@@ -2984,10 +2948,11 @@ server.tool("premium-deliver", "Deliver a purchased premium plugin. Copies plugi
 // file-attach — copy a generated file into the attachment store for download
 // ---------------------------------------------------------------------------
 eagerTool(server, "file-attach", "Attach a file from the account directory for delivery to the user. " +
-    "Copies the file into the attachment store and returns metadata for rendering " +
-    "a download component. The file must be within the account directory tree. " +
-    "After calling this tool, call render-component with name 'file-attachment' " +
-    "and pass the returned metadata as data.", {
+    "Copies the file into the attachment store and returns metadata the chat " +
+    "surface uses to present the download. The file must be within the account " +
+    "directory tree. The returned metadata is the operator-visible record of the " +
+    "attachment; quote it back to the user in plain text so they have the filename " +
+    "and size on screen.", {
     filePath: z.string().describe("Absolute path to the file to attach"),
 }, async ({ filePath }) => {
     const TAG = "[file-attach]";