@rubytech/create-maxy-code 0.1.29 → 0.1.30

package/dist/__tests__/init-logging.test.js

@@ -0,0 +1,85 @@
+// Coverage for runInitLogging's success and failure branches via injected
+// fs / stderr / exit impls. Task 062 (maxy-code).
+//
+// Brief asked for vitest. Codebase convention is node:test (matches
+// apt-resolve.test.ts, peer-brand-detect.test.ts, etc); the package has no
+// vitest dep and the test runner stanza in package.json invokes
+// `node --test 'dist/__tests__/*.test.js'`.
+import test from "node:test";
+import assert from "node:assert/strict";
+import { runInitLogging } from "../init-logging.js";
+const LOG_DIR = "/tmp/test-task-062-logs";
+const LOG_FILE = "/tmp/test-task-062-logs/install-2026-01-01T00-00-00-000Z.log";
+const PERSIST_DIR = "/tmp/test-task-062-persist";
+test("success path: header written via injected impls, no stderr, no exit", () => {
+    const appendCalls = [];
+    let stderrOut = "";
+    let exitCode = null;
+    runInitLogging({
+        logDir: LOG_DIR,
+        logFile: LOG_FILE,
+        persistDir: PERSIST_DIR,
+        headerLines: ["", "===", "  Maxy Code Install Log", "==="],
+        mkdirSyncImpl: () => { },
+        appendFileSyncImpl: (p, d) => { appendCalls.push([p, d]); },
+        stderrWriteImpl: (c) => { stderrOut += c; },
+        exitImpl: (c) => { exitCode = c; },
+    });
+    assert.equal(appendCalls.length, 1);
+    assert.equal(appendCalls[0][0], LOG_FILE);
+    assert.equal(appendCalls[0][1], "\n===\n  Maxy Code Install Log\n===\n");
+    assert.equal(stderrOut, "");
+    assert.equal(exitCode, null);
+});
+test("failure path: appendFileSync throws → stderr emits FAILED line, exit(1) called", () => {
+    let stderrOut = "";
+    let exitCode = null;
+    runInitLogging({
+        logDir: LOG_DIR,
+        logFile: LOG_FILE,
+        persistDir: PERSIST_DIR,
+        headerLines: ["a"],
+        mkdirSyncImpl: () => { },
+        appendFileSyncImpl: () => { throw new Error("EACCES: permission denied"); },
+        stderrWriteImpl: (c) => { stderrOut += c; },
+        exitImpl: (c) => { exitCode = c; },
+    });
+    assert.ok(stderrOut.includes("[create-maxy] init-logging FAILED reason=EACCES"), `stderr should contain init-logging FAILED line; got: ${JSON.stringify(stderrOut)}`);
+    assert.ok(stderrOut.includes(`log=${LOG_FILE}`));
+    assert.ok(stderrOut.includes(`persist=${PERSIST_DIR}`));
+    assert.equal(exitCode, 1);
+});
+test("failure path: mkdirSync throws → stderr emits FAILED line, exit(1) called", () => {
+    let stderrOut = "";
+    let exitCode = null;
+    let appendCalled = false;
+    runInitLogging({
+        logDir: LOG_DIR,
+        logFile: LOG_FILE,
+        persistDir: PERSIST_DIR,
+        headerLines: ["a"],
+        mkdirSyncImpl: () => { throw new Error("EROFS: read-only file system"); },
+        appendFileSyncImpl: () => { appendCalled = true; },
+        stderrWriteImpl: (c) => { stderrOut += c; },
+        exitImpl: (c) => { exitCode = c; },
+    });
+    assert.equal(appendCalled, false, "appendFileSync must not be invoked when mkdirSync throws");
+    assert.ok(stderrOut.includes("[create-maxy] init-logging FAILED reason=EROFS"));
+    assert.equal(exitCode, 1);
+});
+test("failure path: non-Error thrown value still surfaces as reason", () => {
+    let stderrOut = "";
+    let exitCode = null;
+    runInitLogging({
+        logDir: LOG_DIR,
+        logFile: LOG_FILE,
+        persistDir: PERSIST_DIR,
+        headerLines: ["a"],
+        mkdirSyncImpl: () => { },
+        appendFileSyncImpl: () => { throw "raw-string"; },
+        stderrWriteImpl: (c) => { stderrOut += c; },
+        exitImpl: (c) => { exitCode = c; },
+    });
+    assert.ok(stderrOut.includes("reason=raw-string"));
+    assert.equal(exitCode, 1);
+});

package/dist/index.js

@@ -7,6 +7,7 @@ import { resolveInstallPortFromFs, buildMaxyUnitFile, buildClaudeSessionManagerU
 import { classifyOnboardingReadBack } from "./onboarding-readback.js";
 import { parseOsRelease, isUbuntuLike as isUbuntuLikePure, parseAptCacheCandidate, decideAptResolution, } from "./apt-resolve.js";
 import { findPeerBrandOnDefaultNeo4jPort } from "./peer-brand-detect.js";
+import { runInitLogging } from "./init-logging.js";
 import { requireSupportedPlatform } from "./platform-detect.js";
 import { renderPlist } from "./launchd-plist.js";
 import { installAllBrewPackages } from "./brew-install.js";
@@ -82,15 +83,19 @@ const NPM_NET_FLAGS = [
 // Logging — timestamped to console AND persistent log file
 // ---------------------------------------------------------------------------
 function initLogging() {
-    mkdirSync(LOG_DIR, { recursive: true });
-    appendFileSync(LOG_FILE, [
-        "",
-        "=".repeat(64),
-        `  ${BRAND.productName} Install Log — ${new Date().toISOString()}`,
-        `  Node ${process.version} | ${process.platform} ${process.arch}`,
-        "=".repeat(64),
-        "",
-    ].join("\n") + "\n");
+    runInitLogging({
+        logDir: LOG_DIR,
+        logFile: LOG_FILE,
+        persistDir: PERSIST_DIR,
+        headerLines: [
+            "",
+            "=".repeat(64),
+            `  ${BRAND.productName} Install Log — ${new Date().toISOString()}`,
+            `  Node ${process.version} | ${process.platform} ${process.arch}`,
+            "=".repeat(64),
+            "",
+        ],
+    });
 }
 function logFile(msg) {
     try {
@@ -3596,8 +3601,14 @@ if (PLATFORM === "darwin") {
 const PLATFORM_HEADER = `[create-maxy] platform=${PLATFORM} arch=${process.arch}` +
     (MACOS_VERSION ? ` macos=${MACOS_VERSION}` : ``) +
     ` version=${PKG_VERSION}`;
-initLogging();
+// Task 062 — emit platform header and the resolved log/persist paths to
+// stdout BEFORE the log file is opened. If initLogging's mkdir or first
+// appendFileSync throws, the operator still sees brand/version/arch and the
+// exact path the log file SHOULD live at, instead of a silent exit between
+// the LOG_DIR mkdir and the first log write.
 console.log(PLATFORM_HEADER);
+console.log(`[create-maxy] log=${LOG_FILE} persist=${PERSIST_DIR}`);
+initLogging();
 console.log("================================================================");
 console.log(`  ${BRAND.productName} — ${BRAND.tagline}.  (${BRAND.hostname} v${PKG_VERSION})`);
 console.log("================================================================");

package/dist/init-logging.js

@@ -0,0 +1,28 @@
+// Installer log-file initialization with diagnostic stderr emission on
+// failure. Extracted from index.ts so the failure path can be covered by
+// node:test without bringing in the rest of the installer's import-time side
+// effects.
+//
+// Task 062 (maxy-code) — operator-observed silent exit between
+// `mkdirSync(LOG_DIR)` and the first `appendFileSync(LOG_FILE, header)`.
+// Both writes are guarded inside the same try/catch; a failure emits a
+// literal `[create-maxy] init-logging FAILED reason=<msg> log=<path>
+// persist=<path>` line to stderr and exits 1 so the operator always has a
+// forensic surface regardless of whether the log file ever opened.
+import { mkdirSync as realMkdirSync, appendFileSync as realAppendFileSync, } from "node:fs";
+export function runInitLogging(opts) {
+    const mkdir = opts.mkdirSyncImpl ?? ((p, o) => { realMkdirSync(p, o); });
+    const append = opts.appendFileSyncImpl ?? ((p, d) => { realAppendFileSync(p, d); });
+    const stderr = opts.stderrWriteImpl ?? ((c) => { process.stderr.write(c); });
+    const exit = opts.exitImpl ?? ((c) => { process.exit(c); });
+    try {
+        mkdir(opts.logDir, { recursive: true });
+        append(opts.logFile, opts.headerLines.join("\n") + "\n");
+    }
+    catch (err) {
+        const msg = err instanceof Error ? err.message : String(err);
+        stderr(`[create-maxy] init-logging FAILED reason=${msg} log=${opts.logFile} persist=${opts.persistDir}\n`);
+        exit(1);
+        return;
+    }
+}

package/package.json

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

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), render-component, session-reset, session-resume, file-attach, wifi, and action-approval tools (action-pending, action-approve, action-reject, action-edit) for managing the Maxy platform.",
+  "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.",
   "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), render-component, session-reset, session-resume, file-attach, wifi, and action-approval tools (action-pending, action-approve, action-reject, action-edit) for managing the Maxy platform."
+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."
 tools:
   - name: system-status
     publicAllowlist: false

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

@@ -1,100 +1,102 @@
 #!/usr/bin/env bash
-# Task 038 Outcome E1 — Stop-event hook that flags the admin agent's
-# onboarding-skill drift pattern: the prior /input carried an
-# `<onboarding-state>` block, but the latest assistant turn did not call
-# `render-component` AND did not end with a `?`-terminated sentence.
+# 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".
 #
 # Behaviour:
-#   1. Read the transcript_path from the Stop event JSON on stdin.
+#   1. Read transcript_path from the Stop event JSON on stdin.
 #   2. Walk the JSONL backwards. Find the most recent user event whose
-#      `message.content` (string or text-block array) contains the literal
-#      `<onboarding-state ` marker — that is the injection signature.
+#      `message.content` contains the literal `<onboarding-state ` marker.
 #   3. If no such user event exists in this transcript, fail-open (exit 0).
-#   4. Otherwise, find the most recent assistant event after that injection
-#      event. Extract its tool-use names and the trailing text characters.
-#   5. If the tool-use list does NOT contain `render-component` AND the
-#      trailing prose does NOT end with `?`, the agent has drifted — log
-#      one `[precision-check] rule=onboarding-skill-drift` line to the
-#      admin-side log directory and exit 0.
+#   4. Otherwise, find the most recent assistant event after that injection.
+#      Count assistant turns since the injection so the log line carries a turn number.
+#   5. Evaluate the ends-with-prompt contract on the assistant text:
+#        - PASS when the last non-whitespace character is `?`, OR
+#        - PASS when the trailing block (last ~8 lines) contains a numbered
+#          or bulleted list item (`1. `, `2) `, `- `, `* `).
+#        - FAIL otherwise.
+#   6. Emit `[onboarding-skill-drift] turn=<N> contract=ends-with-prompt
+#      result=<pass|fail> reason=<reason>` on stderr.
 #
-# Exit 0 always — this hook is observation, not enforcement. The
-# precision-check ledger increments via the log line; no retry is forced.
-# Infrastructure failures (jq missing, transcript unreadable) also exit 0
-# so a hook bug never blocks the agent's response.
+# Exit 0 always: this hook is observation, not enforcement. Infrastructure
+# failures (jq missing, transcript unreadable) also exit 0 so a hook bug
+# never blocks the agent's response.
 
 set -uo pipefail
-LOG_TAG="[precision-check]"
+LOG_TAG="[onboarding-skill-drift]"
 
-# fail-open if jq is unavailable — the transcript shape demands JSON parse
 if ! command -v jq >/dev/null 2>&1; then
-  echo "$LOG_TAG rule=onboarding-skill-drift result=skip reason=jq-missing" >&2
+  echo "$LOG_TAG turn=0 contract=ends-with-prompt result=skip reason=jq-missing" >&2
   exit 0
 fi
 
 INPUT=$(cat 2>/dev/null || echo '{}')
 TRANSCRIPT=$(echo "$INPUT" | jq -r '.transcript_path // empty' 2>/dev/null)
 if [ -z "$TRANSCRIPT" ] || [ ! -f "$TRANSCRIPT" ]; then
-  echo "$LOG_TAG rule=onboarding-skill-drift result=skip reason=no-transcript" >&2
+  echo "$LOG_TAG turn=0 contract=ends-with-prompt result=skip reason=no-transcript" >&2
   exit 0
 fi
 
-# Locate the most recent injection signature in user events. The injection
-# block is prepended verbatim to the operator's input on the first /input
-# of an eligible session, so it appears as the leading bytes of a user
-# event's message text. Search backwards to find the last one in this
-# transcript window.
+# Locate the most recent <onboarding-state ...> injection in a user event.
+# The injection block is prepended verbatim to the operator's input on the
+# first /input of an eligible session, so it appears as the leading bytes of
+# the user event's message text. Search backwards for the last one.
 INJECTION_LINE=$(grep -n '<onboarding-state ' "$TRANSCRIPT" 2>/dev/null \
   | grep '"type":"user"' \
   | tail -n 1 \
   | cut -d: -f1)
 
 if [ -z "$INJECTION_LINE" ]; then
-  # No injection in this transcript window — nothing to enforce.
+  # No injection in this transcript window. Nothing to evaluate.
   exit 0
 fi
 
-# Slice the file from just after the injection line to the end; the
-# assistant's response sits in that suffix.
+# Slice the file from just after the injection line.
 TAIL=$(tail -n "+$((INJECTION_LINE + 1))" "$TRANSCRIPT" 2>/dev/null)
 
-# Last assistant message in the suffix.
-ASSISTANT=$(echo "$TAIL" \
-  | grep '"type":"assistant"' \
-  | tail -n 1)
+# Count assistant turns since the injection and pick the most recent.
+ASSISTANT_TURNS=$(echo "$TAIL" | grep -c '"type":"assistant"')
+ASSISTANT=$(echo "$TAIL" | grep '"type":"assistant"' | tail -n 1)
 
 if [ -z "$ASSISTANT" ]; then
-  echo "$LOG_TAG rule=onboarding-skill-drift result=skip reason=no-assistant-turn" >&2
+  echo "$LOG_TAG turn=0 contract=ends-with-prompt result=skip reason=no-assistant-turn" >&2
   exit 0
 fi
 
-# Tool-use names from the assistant event.
-TOOL_USES=$(echo "$ASSISTANT" | jq -r '
-  .message.content // []
-  | map(select(.type == "tool_use") | .name)
-  | join(",")
-' 2>/dev/null)
-
-# Concatenated text content (final character matters for the `?` check).
+# Concatenated text content (final character matters for the `?` check; final
+# block matters for the enumerated-list check).
 ASSISTANT_TEXT=$(echo "$ASSISTANT" | jq -r '
   .message.content // []
   | map(select(.type == "text") | .text)
-  | join(" ")
+  | join("\n")
 ' 2>/dev/null)
 
-HAS_RENDER_COMPONENT=0
-case "$TOOL_USES" in
-  *render-component*) HAS_RENDER_COMPONENT=1 ;;
-esac
-
-# Trim trailing whitespace and check the last non-whitespace character.
+# Trim trailing whitespace and find the last non-whitespace character.
 TRIMMED=$(echo "$ASSISTANT_TEXT" | sed -E 's/[[:space:]]+$//')
 LAST_CHAR=$(echo -n "$TRIMMED" | tail -c 1)
 
-if [ "$HAS_RENDER_COMPONENT" = "0" ] && [ "$LAST_CHAR" != "?" ]; then
-  # Drift detected. Sample is the first 80 chars of the assistant text so
-  # the log line tells the operator what shape of drift fired.
-  SAMPLE=$(echo "$TRIMMED" | head -c 80 | tr '\n' ' ')
-  echo "$LOG_TAG rule=onboarding-skill-drift result=block class=PRECISION sample='${SAMPLE}'" >&2
+# Evaluate the ends-with-prompt contract.
+ENDS_WITH_PROMPT=0
+ENDS_WITH_PROMPT_REASON="neither-question-nor-list"
+
+if [ "$LAST_CHAR" = "?" ]; then
+  ENDS_WITH_PROMPT=1
+  ENDS_WITH_PROMPT_REASON="trailing-question-mark"
+else
+  # Take the last 8 lines and look for a numbered/bulleted list item.
+  TRAIL_LINES=$(echo "$TRIMMED" | tail -n 8)
+  if echo "$TRAIL_LINES" | grep -qE '^[[:space:]]*([0-9]+[.)]|[-*])[[:space:]]+'; then
+    ENDS_WITH_PROMPT=1
+    ENDS_WITH_PROMPT_REASON="trailing-enumerated-list"
+  fi
+fi
+
+if [ "$ENDS_WITH_PROMPT" = "1" ]; then
+  echo "$LOG_TAG turn=$ASSISTANT_TURNS contract=ends-with-prompt result=pass reason=$ENDS_WITH_PROMPT_REASON" >&2
+else
+  SAMPLE=$(echo "$TRIMMED" | tail -c 120 | tr '\n' ' ' | sed 's/[[:space:]]\+/ /g')
+  echo "$LOG_TAG turn=$ASSISTANT_TURNS contract=ends-with-prompt result=fail reason=$ENDS_WITH_PROMPT_REASON sample='${SAMPLE}'" >&2
 fi
 
 exit 0

package/payload/platform/plugins/admin/references/contextual-ui.md

@@ -1,6 +1,8 @@
-# Contextual UI Toolkit
+# Contextual UI Toolkit (public agent surface only)
 
-A suite of UI primitives rendered inline in the conversation via `render-component`. Use these when structured interaction improves clarity, reduces ambiguity, or prevents errors — not for every exchange.
+**Scope.** This file documents the `render-component` UI primitives available exclusively on the public agent surface (Anthropic API runtime). The admin agent on the native Claude Code (PTY) surface does not have `render-component` and must not call it; admin flows use plain markdown for review and `file-attach` for downloadable artefacts (see `skills/file-presentation/SKILL.md`). The MCP tool definition remains registered because the public agent depends on it.
+
+A suite of UI primitives rendered inline in the conversation via `render-component`. The public agent uses these when structured interaction improves clarity, reduces ambiguity, or prevents errors, not for every exchange.
 
 ## Component Catalogue
 

package/payload/platform/plugins/admin/skills/file-presentation/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: file-presentation
-description: "Render a file or document inline for the owner to view, edit, and download. Triggers when the owner asks to see, attach, or download a file, when content is generated that the owner needs to review (summary, report, draft), or when a downloadable artefact is the right output."
+description: "Deliver a file or document to the owner inside chat for review and download. Triggers when the owner asks to see, attach, or download a file, when content is generated that the owner needs to review (summary, report, draft), or when a downloadable artefact is the right output."
 ---
 
 # File presentation
 
-This skill makes a file visible and downloadable inside the chat. It is the only sanctioned path for delivering file content to the owner. Synthesised content (a summary, a report, a draft) follows the same path: render via `document-editor` so the owner can review and download.
+This skill makes a file visible and downloadable inside chat on the native Claude Code surface. Two delivery paths cover every case: a fenced markdown block for editable text content, and the `file-attach` tool for any file the operator should be able to download.
 
 ## The trigger
 
-The owner asks to view, review, attach, or download a file or a document, or the current turn produces a document that the owner needs to see. Example phrasings:
+The owner asks to view, review, attach, or download a file or a document, or the current turn produces a document the owner needs to see. Example phrasings:
 
 - "show me the file"
 - "attach the report"
@@ -18,39 +18,23 @@ The owner asks to view, review, attach, or download a file or a document, or the
 - "send me the brochure"
 - "save that as a markdown file"
 
-## How to render
+## How to deliver markdown text content
 
-Call `render-component` with:
+For a synthesised document (a summary, a report, a draft, a knowledge-base article), present the content as a single fenced markdown block in chat:
 
+````
+```markdown
+<the file content as markdown>
 ```
-name: "document-editor"
-data: {
-  title: "<owner-facing title>",
-  content: "<the file content as markdown>"
-}
-```
-
-The component gives the owner a render-review-edit-download flow: they see the content inline, can edit it in place, and can download it as a `.md` file directly from the component. Do not use `memory-write`, `memory-ingest`, or other tools to deliver file content to the owner; those tools have different purposes and skipping the render-review-download flow takes control away from the owner.
-
-## Character sanitisation: the silent-failure rule
-
-The document-editor's markdown parser fails silently on these typographical characters:
+````
 
-| Character | Unicode | Replace with |
-|---|---|---|
-| em-dash | U+2014 | hyphen with spaces |
-| en-dash | U+2013 | hyphen with spaces |
-| left curly double quote | U+201C | straight double quote |
-| right curly double quote | U+201D | straight double quote |
-| left curly single quote | U+2018 | straight single quote |
-| right curly single quote | U+2019 | straight single quote |
-| horizontal ellipsis | U+2026 | three periods |
+The operator reads the block inline, copy-edits in their next message if changes are needed, and approves before any persistence step. Do not call `memory-write`, `memory-ingest`, or other writers before the operator has approved the content; those tools have different purposes and skipping the review step takes control away from the owner.
 
-Strip and replace these characters in the `content` field before the `render-component` call. The owner does not see a partial render or a warning; the content just silently breaks at the offending character. Currency symbols (£, €), accented characters, and other Unicode are unaffected: use them normally.
+When the operator approves and the document should land on disk or in the graph, use the appropriate writer (`store-skill` for skill files under the active account, the relevant graph writer for `:KnowledgeDocument` nodes). Always state the destination before writing.
 
-## When the file is a binary
+## How to deliver a downloadable file
 
-For PDF, image, audio, or any binary deliverable, use `file-attach` plus `render-component` with `name: file-attachment` and pass the returned path. The document-editor component is for editable markdown text only.
+For any file the operator should be able to download (PDF, image, audio, a `.zip`, a `.md` artefact saved to disk, an `.ics` calendar export), call `file-attach` with the path. The tool returns the attachment reference and the chat client renders the download chip inline. No component wrapper is needed; `file-attach` is the delivery mechanism on the native Claude Code surface.
 
 ## For static-site delivery
 
@@ -58,10 +42,9 @@ When the owner has uploaded a `.zip` containing HTML and assets and wants it hos
 
 ## Failure modes
 
-- **Content is too large for the component** (typically over 50,000 characters of markdown). Surface the size and offer to split into sections, save as an attachment, or render only the first section with a follow-up for the rest.
-- **`render-component` returns an error.** Surface the error literally. Do not paste the content into chat as a fallback; the owner asked for the render-review-download flow, not a wall of text.
-- **The content contains characters the parser rejects after the sanitisation pass** (rare; usually a non-printable control character). Strip the offending characters and surface a one-line warning naming the position.
+- **Content is too large for one chat block** (typically over 50,000 characters of markdown). Surface the size and offer to split into sections, save as a `.md` file and `file-attach` it, or present only the first section with a follow-up for the rest.
+- **`file-attach` returns an error.** Surface the error literally. Do not paste binary contents or a base64 dump into chat as a fallback; the owner asked for a download, not a wall of bytes.
 
 ## What this skill does not do
 
-It does not write the content to the graph. It does not save the content to disk. The component handles the download path; the owner downloads what they edited in the component.
+It does not write content to the graph or to disk on its own. The fenced-block path is a review surface; persistence is a separate, named tool call that follows operator approval.

package/payload/platform/plugins/admin/skills/plugin-management/SKILL.md

@@ -42,7 +42,7 @@ Premium plugins are purchased separately and delivered from a staging area to th
 
 ### Browsing available premium plugins
 
-Call `premium-list`. It returns structured data for every plugin in the staging area: name, type (standalone/bundle), description, purchase status, and delivery status (per sub-plugin for bundles). Present the results using `render-component` with the `card` type.
+Call `premium-list`. It returns structured data for every plugin in the staging area: name, type (standalone/bundle), description, purchase status, and delivery status (per sub-plugin for bundles). Present the results as a plain numbered list, one entry per plugin, naming the plugin, its type, its description, its purchase status, and (for bundles) the delivery status of each sub-plugin.
 
 ### Plugin info before purchase
 

package/payload/platform/plugins/admin/skills/public-agent-manager/SKILL.md

@@ -92,7 +92,7 @@ Only present plugins from the curated list below. Before presenting, verify each
 | `sales` | Buying signal detection, closing techniques, objection handling |
 | `docs` | User guide and platform documentation |
 
-**Premium — Real Agency (only when delivered):**
+**Premium — Real Agent (only when delivered):**
 
 | Plugin | Description |
 |--------|-------------|

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

@@ -5,7 +5,7 @@ tools: []
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Brochures
+# Real Agent — Brochures
 
 End-to-end estate-agent brochure pipeline. From an agent website URL and a property listing URL, the skills produce a print-ready A4 PDF brochure plus the live HTML used to author it. The pipeline is idempotent: each upstream step is skipped when its output already exists on disk for the requested source.
 

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

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Buyer Management
+# Real Agent — Buyer Management
 
 Five skills covering the complete buyer lifecycle from initial enquiry through viewing management and educational content.
 
@@ -28,7 +28,6 @@ The user is handling buyer enquiries, qualifying applicants, managing viewings,
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/platform/plugins/deep-research/skills/book-mirror/SKILL.md

@@ -50,7 +50,7 @@ If the anchor is missing, ask for it in one sentence: "Mirror against the busine
 ## Chapter 2: ...
 ```
 
-Render the pack via `render-component name: document-editor` for owner review before saving. The owner can edit any chapter inline before the save. Once approved, write to the graph.
+Present the assembled pack as a single fenced markdown block in chat for owner review before saving. The owner reads the pack inline and can ask for chapter-level edits in their next message. Once the owner approves, write to the graph.
 
 ## Length discipline
 

package/payload/platform/plugins/deep-research/skills/strategic-reading/SKILL.md

@@ -52,7 +52,7 @@ If `lens` is missing, ask once: "Through which lens: a project, a goal, or a pro
 ... (three to seven items)
 ```
 
-Render the pack via `render-component name: document-editor` for review before save.
+Present the assembled pack as a single fenced markdown block in chat for owner review before save. The owner reads it inline and can ask for section-level edits in their next message. On approval, write to the graph.
 
 ## Difference from book-mirror
 

package/payload/platform/plugins/docs/references/plugins-guide.md

@@ -81,11 +81,11 @@ Brand decides which premium plugins ship. Maxy installs ship only `platform/plug
 
 **How it works:** Every boot {{productName}} delivers the brand's premium plugins from staging into `platform/plugins/` and stamps `enabledPlugins` against what is actually on disk. No conversation needed — the brand's full set is active from the first turn after install. Updates and reinstalls re-deliver from staging.
 
-Some premium plugins are **bundles** — multiple sub-plugins shipped under one directory in `premium-plugins/`, each independently activatable. For example, Real Agency ships 11 sub-plugins covering different aspects of estate agency work. They are all enabled by default. Sub-plugins you don't want active can be turned off individually with "disable <name>"; enabling or disabling individual sub-plugins does not affect the others.
+Some premium plugins are **bundles** — multiple sub-plugins shipped under one directory in `premium-plugins/`, each independently activatable. For example, Real Agent ships 11 sub-plugins covering different aspects of estate agency work. They are all enabled by default. Sub-plugins you don't want active can be turned off individually with "disable <name>"; enabling or disabling individual sub-plugins does not affect the others.
 
 If you ask {{productName}} about a tool from a plugin your brand does not ship (for example, a Maxy install asking about a Real Agent Loop CRM tool), {{productName}} responds with a structured `<tool-surface-error>` envelope naming the missing plugin and the remedy, rather than improvising with a generic alternative.
 
-**Public agent embedding:** Premium plugins marked as public-eligible have their full content (skills and reference knowledge) embedded in public agent prompts. This means a public agent for a Real Agency member can handle buyer enquiries, book viewings, deliver coaching content, and onboard new applicants — all powered by the premium plugin's domain knowledge. Plugins marked admin-only (listings, vendors, leads, business) are only available to the account owner's admin agent.
+**Public agent embedding:** Premium plugins marked as public-eligible have their full content (skills and reference knowledge) embedded in public agent prompts. This means a public agent for a Real Agent member can handle buyer enquiries, book viewings, deliver coaching content, and onboard new applicants — all powered by the premium plugin's domain knowledge. Plugins marked admin-only (listings, vendors, leads, business) are only available to the account owner's admin agent.
 
 Some premium plugins include specialist helpers that {{productName}} can dispatch for specific tasks (e.g. the writer-craft plugin includes a manuscript reviewer). These are activated automatically when the plugin is enabled.
 

package/payload/platform/plugins/estate-business/PLUGIN.md

@@ -30,7 +30,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency, Month-End and Business Operations
+# Real Agent, Month-End and Business Operations
 
 Eight skills covering month-end close and commission (the master workflow plus three building blocks) and the existing business operations skills.
 
@@ -56,7 +56,6 @@ The user is asking for the monthly close, the commission run, reconciliation aga
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` for domain knowledge
-- `render-component` for structured choices
 - `profile-read` and `profile-update` for the customisation profile
 - `action-pending`, `action-approve`, `action-reject`, `action-edit` for the writeoff, journal, payment-batch, and accountant-pack approval gates
 

package/payload/platform/plugins/estate-coaching/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Coaching & Development
+# Real Agent — Coaching & Development
 
 Four skills covering people development — from individual coaching through team performance management and structured sales training.
 
@@ -48,7 +48,6 @@ Each skill inherits this boundary. When a conversation crosses from coaching int
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/platform/plugins/estate-onboarding/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Onboarding
+# Real Agent — Onboarding
 
 First-run member setup — turning a new conversation into a profiled member with a clear starting point in the curriculum.
 
@@ -24,7 +24,6 @@ The user is going through initial onboarding (career stage assessment, profile s
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/platform/plugins/estate-sales/PLUGIN.md

@@ -19,7 +19,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency, Chase Progression and Sales
+# Real Agent, Chase Progression and Sales
 
 Seven skills covering chain progression (the headline workflow) and the existing sales cycle.
 
@@ -44,7 +44,6 @@ The user is working on stalled deals, chain progression, fall-through risk, sale
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` for domain knowledge
-- `render-component` for structured choices
 - `profile-read` and `profile-update` for the customisation profile
 - `action-pending`, `action-approve`, `action-reject`, `action-edit` for the per-message approval gates in chase-progression
 

package/payload/platform/plugins/estate-teaching/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Teaching & Content
+# Real Agent — Teaching & Content
 
 Structured content delivery from the Real Agency curriculum. Handles module browsing, topic search, interactive teaching, and progress tracking.
 
@@ -24,7 +24,6 @@ The user is browsing available content, asking about a topic, requesting a speci
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

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

@@ -29,7 +29,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency, Lead Generation and Morning Round
+# Real Agent, Lead Generation and Morning Round
 
 Six skills: four covering the daily morning round (master plus building blocks) and two covering longer-horizon lead nurturing and prospecting.
 
@@ -53,7 +53,6 @@ The user is asking for the morning round, the daily brief, the day's diary, over
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` to retrieve domain knowledge from the knowledge base
-- `render-component` to present structured choices during interactions
 - `profile-read` and `profile-update` for the customisation profile
 - `task-create` to file an open task when a chase needs deferring
 

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

@@ -61,7 +61,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency, Valuations and New Instructions
+# Real Agent, Valuations and New Instructions
 
 Fifteen skills covering the two listings-side master workflows (valuation-prep, new-instruction) plus the listing-presentation and marketing skills.
 
@@ -94,7 +94,6 @@ The user is preparing for a valuation or market appraisal, has just won an instr
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` for domain knowledge
-- `render-component` for structured choices
 - `profile-read` and `profile-update` for the customisation profile
 - `action-pending`, `action-approve`, `action-reject`, `action-edit` for the eight approval gates in new-instruction
 

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

@@ -73,7 +73,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Loop CRM
+# Real Agent — Loop CRM
 
 Full integration with Loop CRM V2 API (api.loop.software). Covers all 73 endpoints across 8 resource groups — properties, people, viewings, feedback, team, marketing, customer preferences, and supplier operations. Supports both read and write operations.
 

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

@@ -104,7 +104,7 @@ The `sessionKey` parameter on `schedule-event` automatically creates the `PART_O
 
 ## ICS calendar files
 
-Export events as `.ics` files so users can add them to Apple Calendar, Google Calendar, or Outlook. Use `schedule-export-ics` with the event IDs, then `file-attach` with the returned path and `render-component file-attachment` to deliver the download.
+Export events as `.ics` files so users can add them to Apple Calendar, Google Calendar, or Outlook. Use `schedule-export-ics` with the event IDs, then `file-attach` with the returned path; the chat client renders the download chip inline.
 
 Import `.ics` files uploaded by the user. Use `schedule-import-ics` with the attachment path. Present the extracted events for confirmation before creating them via `schedule-event`.
 

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

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Vendor Management
+# Real Agent — Vendor Management
 
 Four skills covering the active vendor lifecycle from valuation enquiry through offer negotiation.
 
@@ -27,7 +27,6 @@ The user is managing vendor relationships — handling valuation requests, provi
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/premium-plugins/real-agent/BUNDLE.md

@@ -1,6 +1,6 @@
 ---
 name: real-agent
-description: "UK estate agency skills + Loop CRM integration — 11 sub-plugins covering sales, listings, vendor management, buyer management, lead generation, coaching, business operations, onboarding, teaching, Loop CRM, and property brochures. 3 specialist roles (negotiator, valuer, compliance). 32 skills + 22 MCP tools."
+description: "UK estate agency skills + Loop CRM integration — 11 sub-plugins covering sales, listings, vendor management, buyer management, lead generation, coaching, business operations, onboarding, teaching, Loop CRM, and property brochures. 3 specialist roles (negotiator, valuer, compliance). 32 skills + 23 MCP tools."
 plugins:
   - estate-sales
   - listings
@@ -23,9 +23,9 @@ Premium plugin bundle for UK estate agency professionals. Shipped on every non-M
 
 | Role | Agent file | Tools | Focus |
 |---|---|---|---|
-| Negotiator | `agents/negotiator.md` | All Loop CRM tools + memory-search + render-component | Buyer pipeline, viewings, feedback, offers, deal progression |
-| Valuer | `agents/valuer.md` | Loop property/people tools + memory-search + render-component | Market appraisal preparation, comparable evidence analysis |
-| Compliance | `agents/compliance.md` | All Loop CRM tools + memory-search + perplexity-search + render-component | UK estate agency law, listing audit, AML/KYC, regulatory compliance |
+| Negotiator | `agents/negotiator.md` | All Loop CRM tools + memory-search | Buyer pipeline, viewings, feedback, offers, deal progression |
+| Valuer | `agents/valuer.md` | Loop property/people tools + memory-search | Market appraisal preparation, comparable evidence analysis |
+| Compliance | `agents/compliance.md` | All Loop CRM tools + memory-search + perplexity-search | UK estate agency law, listing audit, AML/KYC, regulatory compliance |
 
 ## Sub-Plugins
 
@@ -40,5 +40,5 @@ Premium plugin bundle for UK estate agency professionals. Shipped on every non-M
 | `estate-business` | 4 | — | Business owner skills — growth, operations, brand, partnerships |
 | `estate-onboarding` | 1 | — | First-run member onboarding |
 | `estate-teaching` | 1 | — | Structured education module browsing and delivery |
-| `loop` | — | 22 | Loop CRM integration — properties, people, viewings, feedback, team, marketing, customer preferences, supplier |
+| `loop` | — | 23 | Loop CRM integration — properties, people, viewings, feedback, team, marketing, customer preferences, supplier |
 | `brochures` | 5 | — | Property brochure pipeline — brand extract, property extract, A4 layout, print constraints |

package/payload/premium-plugins/real-agent/agents/compliance.md

@@ -3,7 +3,7 @@ name: compliance
 description: "UK estate agency legal and compliance guidance — legislation, regulation, codes of practice, AML obligations, consumer protection, data protection, material information, advertising standards, and lettings law. Delegate when the task involves regulatory compliance, legal obligations, listing audit against legislative requirements, AML/KYC procedures, data handling questions, advertising rules, or any question about what the law requires of an estate agent or letting agent."
 summary: "Your compliance officer — advises on UK estate agency law, audits listings against regulatory requirements, and cites current legislation."
 model: claude-opus-4-7
-tools: mcp__loop__loop-key-register, mcp__loop__loop-key-deregister, mcp__loop__loop-key-list, mcp__loop__loop-people-search, mcp__loop__loop-people-detail, mcp__loop__loop-property-search, mcp__loop__loop-property-detail, mcp__loop__loop-property-listed, mcp__loop__loop-property-request, mcp__loop__loop-viewing-search, mcp__loop__loop-viewing-detail, mcp__loop__loop-viewing-create, mcp__loop__loop-viewing-update, mcp__loop__loop-feedback-get, mcp__loop__loop-feedback-submit, mcp__loop__loop-team-info, mcp__loop__loop-team-availability, mcp__loop__loop-marketing-match, mcp__loop__loop-marketing-match-batch, mcp__loop__loop-marketing-match-request, mcp__loop__loop-marketing-enquiry, mcp__loop__loop-customer-preferences, mcp__loop__loop-supplier, mcp__memory__memory-search, mcp__deep-research__perplexity-search, mcp__admin__render-component
+tools: mcp__loop__loop-key-register, mcp__loop__loop-key-deregister, mcp__loop__loop-key-list, mcp__loop__loop-people-search, mcp__loop__loop-people-detail, mcp__loop__loop-property-search, mcp__loop__loop-property-detail, mcp__loop__loop-property-listed, mcp__loop__loop-property-request, mcp__loop__loop-viewing-search, mcp__loop__loop-viewing-detail, mcp__loop__loop-viewing-create, mcp__loop__loop-viewing-update, mcp__loop__loop-feedback-get, mcp__loop__loop-feedback-submit, mcp__loop__loop-team-info, mcp__loop__loop-team-availability, mcp__loop__loop-marketing-match, mcp__loop__loop-marketing-match-batch, mcp__loop__loop-marketing-match-request, mcp__loop__loop-marketing-enquiry, mcp__loop__loop-customer-preferences, mcp__loop__loop-supplier, mcp__memory__memory-search, mcp__deep-research__perplexity-search
 ---
 
 # Compliance

package/payload/premium-plugins/real-agent/agents/negotiator.md

@@ -3,7 +3,7 @@ name: negotiator
 description: "CRM operations, buyer pipeline management, viewing coordination, feedback analysis, offer preparation, and deal progression. Delegate when the task involves querying or correlating CRM data, managing buyer interactions, preparing offer packages, or tracking deal status."
 summary: "Your negotiator — manages buyer pipeline, viewings, feedback, offers, and deal progression using Loop CRM."
 model: claude-sonnet-4-6
-tools: mcp__loop__loop-key-register, mcp__loop__loop-key-deregister, mcp__loop__loop-key-list, mcp__loop__loop-people-search, mcp__loop__loop-people-detail, mcp__loop__loop-property-search, mcp__loop__loop-property-detail, mcp__loop__loop-property-listed, mcp__loop__loop-property-request, mcp__loop__loop-viewing-search, mcp__loop__loop-viewing-detail, mcp__loop__loop-viewing-create, mcp__loop__loop-viewing-update, mcp__loop__loop-feedback-get, mcp__loop__loop-feedback-submit, mcp__loop__loop-team-info, mcp__loop__loop-team-availability, mcp__loop__loop-marketing-match, mcp__loop__loop-marketing-match-batch, mcp__loop__loop-marketing-match-request, mcp__loop__loop-marketing-enquiry, mcp__loop__loop-customer-preferences, mcp__loop__loop-supplier, mcp__memory__memory-search, mcp__admin__render-component
+tools: mcp__loop__loop-key-register, mcp__loop__loop-key-deregister, mcp__loop__loop-key-list, mcp__loop__loop-people-search, mcp__loop__loop-people-detail, mcp__loop__loop-property-search, mcp__loop__loop-property-detail, mcp__loop__loop-property-listed, mcp__loop__loop-property-request, mcp__loop__loop-viewing-search, mcp__loop__loop-viewing-detail, mcp__loop__loop-viewing-create, mcp__loop__loop-viewing-update, mcp__loop__loop-feedback-get, mcp__loop__loop-feedback-submit, mcp__loop__loop-team-info, mcp__loop__loop-team-availability, mcp__loop__loop-marketing-match, mcp__loop__loop-marketing-match-batch, mcp__loop__loop-marketing-match-request, mcp__loop__loop-marketing-enquiry, mcp__loop__loop-customer-preferences, mcp__loop__loop-supplier, mcp__memory__memory-search
 ---
 
 # Negotiator

package/payload/premium-plugins/real-agent/agents/valuer.md

@@ -3,7 +3,7 @@ name: valuer
 description: "Market appraisal preparation, comparable evidence analysis, and valuation booking support. Delegate when the task involves preparing for a valuation appointment, assembling comparable sales data, analysing competing listings, or handling valuation enquiries."
 summary: "Your valuer — prepares market appraisals, assembles comparable evidence, and analyses local market conditions using Loop CRM."
 model: claude-sonnet-4-6
-tools: mcp__loop__loop-property-search, mcp__loop__loop-property-detail, mcp__loop__loop-property-listed, mcp__loop__loop-people-search, mcp__memory__memory-search, mcp__admin__render-component
+tools: mcp__loop__loop-property-search, mcp__loop__loop-property-detail, mcp__loop__loop-property-listed, mcp__loop__loop-people-search, mcp__memory__memory-search
 ---
 
 # Valuer

package/payload/premium-plugins/real-agent/plugins/brochures/PLUGIN.md

@@ -5,7 +5,7 @@ tools: []
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Brochures
+# Real Agent — Brochures
 
 End-to-end estate-agent brochure pipeline. From an agent website URL and a property listing URL, the skills produce a print-ready A4 PDF brochure plus the live HTML used to author it. The pipeline is idempotent: each upstream step is skipped when its output already exists on disk for the requested source.
 

package/payload/premium-plugins/real-agent/plugins/buyers/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Buyer Management
+# Real Agent — Buyer Management
 
 Five skills covering the complete buyer lifecycle from initial enquiry through viewing management and educational content.
 
@@ -28,7 +28,6 @@ The user is handling buyer enquiries, qualifying applicants, managing viewings,
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/premium-plugins/real-agent/plugins/estate-business/PLUGIN.md

@@ -30,7 +30,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency, Month-End and Business Operations
+# Real Agent, Month-End and Business Operations
 
 Eight skills covering month-end close and commission (the master workflow plus three building blocks) and the existing business operations skills.
 
@@ -56,7 +56,6 @@ The user is asking for the monthly close, the commission run, reconciliation aga
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` for domain knowledge
-- `render-component` for structured choices
 - `profile-read` and `profile-update` for the customisation profile
 - `action-pending`, `action-approve`, `action-reject`, `action-edit` for the writeoff, journal, payment-batch, and accountant-pack approval gates
 

package/payload/premium-plugins/real-agent/plugins/estate-coaching/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Coaching & Development
+# Real Agent — Coaching & Development
 
 Four skills covering people development — from individual coaching through team performance management and structured sales training.
 
@@ -48,7 +48,6 @@ Each skill inherits this boundary. When a conversation crosses from coaching int
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/premium-plugins/real-agent/plugins/estate-onboarding/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Onboarding
+# Real Agent — Onboarding
 
 First-run member setup — turning a new conversation into a profiled member with a clear starting point in the curriculum.
 
@@ -24,7 +24,6 @@ The user is going through initial onboarding (career stage assessment, profile s
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/premium-plugins/real-agent/plugins/estate-sales/PLUGIN.md

@@ -19,7 +19,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency, Chase Progression and Sales
+# Real Agent, Chase Progression and Sales
 
 Seven skills covering chain progression (the headline workflow) and the existing sales cycle.
 
@@ -44,7 +44,6 @@ The user is working on stalled deals, chain progression, fall-through risk, sale
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` for domain knowledge
-- `render-component` for structured choices
 - `profile-read` and `profile-update` for the customisation profile
 - `action-pending`, `action-approve`, `action-reject`, `action-edit` for the per-message approval gates in chase-progression
 

package/payload/premium-plugins/real-agent/plugins/estate-teaching/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Teaching & Content
+# Real Agent — Teaching & Content
 
 Structured content delivery from the Real Agency curriculum. Handles module browsing, topic search, interactive teaching, and progress tracking.
 
@@ -24,7 +24,6 @@ The user is browsing available content, asking about a topic, requesting a speci
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References
 

package/payload/premium-plugins/real-agent/plugins/leads/PLUGIN.md

@@ -29,7 +29,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency, Lead Generation and Morning Round
+# Real Agent, Lead Generation and Morning Round
 
 Six skills: four covering the daily morning round (master plus building blocks) and two covering longer-horizon lead nurturing and prospecting.
 
@@ -53,7 +53,6 @@ The user is asking for the morning round, the daily brief, the day's diary, over
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` to retrieve domain knowledge from the knowledge base
-- `render-component` to present structured choices during interactions
 - `profile-read` and `profile-update` for the customisation profile
 - `task-create` to file an open task when a chase needs deferring
 

package/payload/premium-plugins/real-agent/plugins/listings/PLUGIN.md

@@ -61,7 +61,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency, Valuations and New Instructions
+# Real Agent, Valuations and New Instructions
 
 Fifteen skills covering the two listings-side master workflows (valuation-prep, new-instruction) plus the listing-presentation and marketing skills.
 
@@ -94,7 +94,6 @@ The user is preparing for a valuation or market appraisal, has just won an instr
 No MCP server. Skills operate via existing platform tools:
 
 - `memory-search` for domain knowledge
-- `render-component` for structured choices
 - `profile-read` and `profile-update` for the customisation profile
 - `action-pending`, `action-approve`, `action-reject`, `action-edit` for the eight approval gates in new-instruction
 

package/payload/premium-plugins/real-agent/plugins/loop/PLUGIN.md

@@ -73,7 +73,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Loop CRM
+# Real Agent — Loop CRM
 
 Full integration with Loop CRM V2 API (api.loop.software). Covers all 73 endpoints across 8 resource groups — properties, people, viewings, feedback, team, marketing, customer preferences, and supplier operations. Supports both read and write operations.
 

package/payload/premium-plugins/real-agent/plugins/vendors/PLUGIN.md

@@ -6,7 +6,7 @@ always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Vendor Management
+# Real Agent — Vendor Management
 
 Four skills covering the active vendor lifecycle from valuation enquiry through offer negotiation.
 
@@ -27,7 +27,6 @@ The user is managing vendor relationships — handling valuation requests, provi
 
 No MCP server. Skills operate via existing platform tools:
 - `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
 
 ## References