@rubytech/create-maxy 1.0.739 → 1.0.741

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

@@ -2,15 +2,15 @@
 
 ## What a Plugin Is
 
-A plugin extends what Maxy can do. Each plugin adds a focused capability — contacts management, Telegram messaging, scheduling, email, research. Plugins are modular: you enable only what you need.
+A plugin extends what {{productName}} can do. Each plugin adds a focused capability — contacts management, Telegram messaging, scheduling, email, research. Plugins are modular: you enable only what you need.
 
-Maxy's own capabilities are plugins too. Marketplace plugins (like Stripe) work the same way — Maxy manages all of them through conversation.
+{{productName}}'s own capabilities are plugins too. Marketplace plugins (like Stripe) work the same way — {{productName}} manages all of them through conversation.
 
 ## Plugin Groups
 
 ### Core (always active)
 
-These are part of Maxy's foundation and cannot be disabled:
+These are part of {{productName}}'s foundation and cannot be disabled:
 
 | Plugin | What it does |
 |--------|-------------|
@@ -25,7 +25,7 @@ These are part of Maxy's foundation and cannot be disabled:
 | `workflows` | Persistent named workflows — reusable instruction sets |
 | `contacts` | CRM contact management — create, lookup, update, list |
 
-### Maxy Plugins (user-selectable)
+### {{productName}} Plugins (user-selectable)
 
 These are enabled during onboarding and can be added or removed at any time. Some plugins enhance a specific specialist role — when enabled, that specialist gains additional capabilities.
 
@@ -51,7 +51,7 @@ Third-party plugins from the Claude marketplace:
 
 ### Premium Plugins
 
-Premium plugins are one-off purchases that grant permanent ownership. They are not part of the standard install — once purchased, Maxy delivers them automatically.
+Premium plugins are one-off purchases that grant permanent ownership. They are not part of the standard install — once purchased, {{productName}} delivers them automatically.
 
 | Plugin | Type | What it does | Public agent |
 |--------|------|-------------|-------------|
@@ -59,35 +59,43 @@ Premium plugins are one-off purchases that grant permanent ownership. They are n
 | `real-agency` | Bundle (11 sub-plugins) | UK estate agency skills — sales, listings, brochures, vendor management, buyer management, lead generation, coaching, business operations, onboarding, teaching, and Loop CRM. 2 specialist roles (negotiator, valuer) | 4 sub-plugins (estate-sales, buyers, estate-coaching, estate-onboarding) |
 | `writer-craft` | Skills + Agent | Manuscript review and writing craft — story architecture, reader engagement, prose craft, editorial practice, and multi-level review | No — writing craft serves the author |
 
-**How it works:** When you purchase a premium plugin, it's delivered to your Maxy via conversation. Tell Maxy "Enable the teaching plugin" and it handles the rest. Premium plugins are yours permanently — they survive updates and reinstalls.
+**How it works:** When you purchase a premium plugin, it's delivered to your {{productName}} via conversation. Tell {{productName}} "Enable the teaching plugin" and it handles the rest. Premium plugins are yours permanently — they survive updates and reinstalls.
 
 Some premium plugins are **bundles** — a single purchase that delivers multiple sub-plugins, each independently activatable. For example, Real Agency delivers 11 sub-plugins covering different aspects of estate agency work. You can enable all of them or just the ones you need (e.g., "Enable estate-sales" for just the sales skills). Enabling or disabling individual sub-plugins does not affect the others.
 
 **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.
 
-Some premium plugins include specialist helpers that Maxy can dispatch for specific tasks (e.g. the writer-craft plugin includes a manuscript reviewer). These are activated automatically when the plugin is enabled.
+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.
 
-Some premium plugins include pre-built public agent templates — ready-made configurations for customer-facing agents. When you enable the plugin, Maxy shows you what templates are available and offers to create agents from them. You review and approve every file before the agent is created. The template is a starting point — you can edit the identity, personality, plugins, and settings to make it yours. The result is a standard public agent, indistinguishable from one you created from scratch.
+Some premium plugins include pre-built public agent templates — ready-made configurations for customer-facing agents. When you enable the plugin, {{productName}} shows you what templates are available and offers to create agents from them. You review and approve every file before the agent is created. The template is a starting point — you can edit the identity, personality, plugins, and settings to make it yours. The result is a standard public agent, indistinguishable from one you created from scratch.
 
 Some premium plugins ship pre-built workflows that are created when the plugin is enabled. These workflows are fully yours — you can inspect, edit, run, and manage them through conversation, exactly like workflows you create yourself. The plugin provides the starting point; you own the result.
 
 ## Choosing Plugins
 
-During first-time setup, Maxy presents a plugin selection screen where you choose which plugins to activate. Core plugins are pre-selected and locked. Recommended plugins are pre-selected but optional. You can change your mind later.
+During first-time setup, {{productName}} presents a plugin selection screen where you choose which plugins to activate. Core plugins are pre-selected and locked. Recommended plugins are pre-selected but optional. You can change your mind later.
 
 ## Adding or Removing Plugins
 
-Tell Maxy:
+Tell {{productName}}:
 
 - "Enable the Telegram plugin"
 - "Add the Stripe plugin"
 - "Disable the waitlist plugin"
 
-Maxy handles the installation or removal. If the plugin requires any setup (API keys, bot tokens, configuration), Maxy will walk you through it.
+{{productName}} handles the installation or removal. If the plugin requires any setup (API keys, bot tokens, configuration), {{productName}} will walk you through it.
 
 ## Viewing Your Plugins
 
-Ask Maxy: "What plugins do I have?" or "List my plugins."
+Ask {{productName}}: "What plugins do I have?" or "List my plugins."
+
+## Brand Templating (for plugin and skill authors)
+
+Skill content, plugin manifests, agent templates, and reference files reference the operator-visible brand name only via the literal `{{productName}}` placeholder. The platform substitutes from `brand.json.productName` at read time — Maxy installs render `Maxy`, Real Agent installs render `Real Agent`, all from the same source content.
+
+**Author rule:** never write the literal string `Maxy` (or any brand name) in shipped skill, plugin, or template content. Use `{{productName}}` whenever the operator should see the brand name. The audit grep `grep -rn "\bMaxy\b" platform/plugins/admin/skills/ platform/plugins/*/skills/ platform/templates/agents/` must return zero matches; a literal brand name is a defect, not a stylistic choice.
+
+The runtime substitution happens at the read sites that flow content into a system prompt or operator-visible UI (admin agent's `plugin-read` tool, public agent's recursive plugin assembly, IDENTITY/SOUL/AGENTS/KNOWLEDGE markdown reads). Missing or empty `productName` hard-fails — there is no fallback to a default brand string. See [.docs/agents.md](../../.docs/agents.md) § "Brand templating" for the full contract.
 
 ## MCP Plugin Observability (for plugin authors)
 

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

@@ -8,13 +8,13 @@ Projects are ideal when the user has work involving multiple people, sequential
 
 ## Creating a Project
 
-Tell Maxy naturally:
+Tell {{productName}} naturally:
 
 - "Create a project for Mrs. Chen's kitchen refit — strip the old kitchen, plumbing first fix, electrical first fix, install units, then tiling and finishing"
 - "Set up a project for the bathroom renovation, standard tier, due by end of June"
 - "Start a project: boiler install for Sarah Thompson, quick job, just order parts, install, and test"
 
-Maxy creates the project and all work items in one step. Dependencies between steps (e.g., "install units after plumbing and electrical") are set up automatically based on the order and relationships you describe.
+{{productName}} creates the project and all work items in one step. Dependencies between steps (e.g., "install units after plumbing and electrical") are set up automatically based on the order and relationships you describe.
 
 Each project has a tier that reflects its complexity:
 - **Quick** — straightforward, few steps (e.g., boiler install)
@@ -30,32 +30,32 @@ Ask naturally:
 - "Show me the Davies bathroom project"
 - "What should I focus on?"
 
-Maxy shows project health at a glance:
+{{productName}} shows project health at a glance:
 - **Green** — on track, no issues
 - **Amber** — warning signs (overdue task or blocker)
 - **Red** — at risk (multiple overdue, critical blocker, or stale)
 
-When you start a new conversation, Maxy automatically shows active project summaries so you know where things stand without asking.
+When you start a new conversation, {{productName}} automatically shows active project summaries so you know where things stand without asking.
 
 ## Updating a Project
 
-Tell Maxy when things change:
+Tell {{productName}} when things change:
 
 - "Move the kitchen refit to the active phase"
 - "The materials for the kitchen refit are delayed by a week"
 - "Update the Davies bathroom target date to July 15th"
 - "Change the boiler install to a standard tier — it's more complex than we thought"
 
-Maxy records phase changes and issues as part of the project's history, creating an audit trail.
+{{productName}} records phase changes and issues as part of the project's history, creating an audit trail.
 
 ## Completing a Project
 
-Tell Maxy:
+Tell {{productName}}:
 
 - "Mark the boiler install as done"
 - "Complete the kitchen refit project"
 
-If any work items are still pending, Maxy will let you know and ask how to handle them — cancel, defer, or keep working on them.
+If any work items are still pending, {{productName}} will let you know and ask how to handle them — cancel, defer, or keep working on them.
 
 ## Abandoning a Project
 
@@ -64,10 +64,10 @@ If a project is no longer needed:
 - "Abandon the Davies bathroom — client cancelled"
 - "Stop the kitchen refit project"
 
-Maxy records the reason and marks the project as abandoned.
+{{productName}} records the reason and marks the project as abandoned.
 
 ## Projects vs. Tasks
 
 Use a **task** for standalone work — a single action, a reminder, a follow-up. Use a **project** when the work has multiple steps that depend on each other, a client or stakeholder, and a lifecycle that progresses through phases.
 
-When you describe multi-step work, Maxy will ask if you'd like to structure it as a project. Over time, it learns your preference and stops asking.
+When you describe multi-step work, {{productName}} will ask if you'd like to structure it as a project. Over time, it learns your preference and stops asking.

package/payload/platform/plugins/docs/references/settings.md

@@ -2,36 +2,36 @@
 
 ## Output Style
 
-Controls how Maxy communicates with you.
+Controls how {{productName}} communicates with you.
 
 | Style | Behaviour |
 |-------|-----------|
 | `default` | Concise, direct responses — gets to the point |
 | `explanatory` | More detailed responses with educational context — explains reasoning and trade-offs |
 
-**Changing output style:** Tell Maxy "Switch to explanatory mode" or "Use default output style."
+**Changing output style:** Tell {{productName}} "Switch to explanatory mode" or "Use default output style."
 
 Changes take effect on the next session. The current session continues with the existing style.
 
 ## Effort Level
 
-Controls how much work Maxy puts into each task — specifically, how many steps it takes before stopping and checking with you.
+Controls how much work {{productName}} puts into each task — specifically, how many steps it takes before stopping and checking with you.
 
 | Level | Max turns | Use when |
 |-------|-----------|----------|
 | `low` | 5 | Quick questions, simple lookups |
 | `medium` | 10 | Standard tasks — most daily use |
 | `high` | 20 | Complex multi-step tasks |
-| `auto` | 20 | Let Maxy decide (same ceiling as high) |
+| `auto` | 20 | Let {{productName}} decide (same ceiling as high) |
 | `max` | 40 | Long autonomous workflows |
 
-**Changing effort level:** Tell Maxy "Set effort to high" or "Use low effort mode."
+**Changing effort level:** Tell {{productName}} "Set effort to high" or "Use low effort mode."
 
 Changes take effect on the next session.
 
 ## Thinking View
 
-Controls how Maxy's thinking process is displayed in the chat.
+Controls how {{productName}}'s thinking process is displayed in the chat.
 
 | Mode | Behaviour |
 |------|-----------|
@@ -39,25 +39,25 @@ Controls how Maxy's thinking process is displayed in the chat.
 | `expanded` | Everything shown expanded — thinking, tool use, and results |
 | `collapsed` | Everything collapsed — compact view, expand on tap |
 
-**Changing thinking view:** Tell Maxy "Show thinking by default", "Show everything expanded", or "Hide thinking."
+**Changing thinking view:** Tell {{productName}} "Show thinking by default", "Show everything expanded", or "Hide thinking."
 
 Changes take effect on the next session.
 
 ## Viewing Current Settings
 
-Ask Maxy: "What are my current settings?" or "What output style am I using?"
+Ask {{productName}}: "What are my current settings?" or "What output style am I using?"
 
 ## Default Agent
 
 Controls which public agent serves the root URL (`/`). Visitors who go to your public site without specifying an agent slug see this agent.
 
-**Changing the default agent:** Tell Maxy "Make sales the default agent" or "Set the default to support."
+**Changing the default agent:** Tell {{productName}} "Make sales the default agent" or "Set the default to support."
 
 The change takes effect on the next page load. The previous default agent remains accessible at its `/{slug}` URL.
 
 ## Account Preferences
 
-You can ask Maxy to show or change any of the following:
+You can ask {{productName}} to show or change any of the following:
 
 - Default agent (which public agent serves the root URL)
 - Admin model (which Claude model powers the admin agent)
@@ -67,10 +67,10 @@ You can ask Maxy to show or change any of the following:
 - Context mode
 - Enabled plugins
 
-Tell Maxy what you want to change and it handles the rest.
+Tell {{productName}} what you want to change and it handles the rest.
 
 ## PIN
 
-Your admin PIN is set during initial setup. To change it, ask Maxy: "Change my admin PIN."
+Your admin PIN is set during initial setup. To change it, ask {{productName}}: "Change my admin PIN."
 
-Maxy will ask for your current PIN to verify, then set the new one.
+{{productName}} will ask for your current PIN to verify, then set the new one.

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

@@ -2,11 +2,11 @@
 
 ## What the Telegram Plugin Does
 
-The Telegram plugin connects Maxy to a Telegram bot. Once set up, you can:
+The Telegram plugin connects {{productName}} to a Telegram bot. Once set up, you can:
 
-- Send messages to individuals or groups via Maxy ("Send a message to the team: standup in 10 minutes")
-- Receive messages from your Telegram bot and have Maxy respond
-- Use Telegram as a channel for Maxy notifications and alerts
+- Send messages to individuals or groups via {{productName}} ("Send a message to the team: standup in 10 minutes")
+- Receive messages from your Telegram bot and have {{productName}} respond
+- Use Telegram as a channel for {{productName}} notifications and alerts
 
 ## Setup
 
@@ -19,39 +19,39 @@ The Telegram plugin connects Maxy to a Telegram bot. Once set up, you can:
 
 ### Step 2: Connect the plugin
 
-Tell Maxy: "Set up Telegram" or "Configure the Telegram bot."
+Tell {{productName}}: "Set up Telegram" or "Configure the Telegram bot."
 
-Maxy will ask for your bot token, then save it and activate the plugin. The bot is now connected.
+{{productName}} will ask for your bot token, then save it and activate the plugin. The bot is now connected.
 
 ### Step 3: Start the bot
 
 In Telegram, open your bot and send `/start`. The bot is now active and listening.
 
-## Sending Messages via Maxy
+## Sending Messages via {{productName}}
 
-Once connected, tell Maxy to send messages on your behalf:
+Once connected, tell {{productName}} to send messages on your behalf:
 
 - "Send a Telegram message to John: I'll be 10 minutes late"
 - "Message the team channel: server maintenance at 11pm"
 - "Tell Sarah via Telegram that the proposal is ready"
 
-Maxy needs a chat ID or username to target a specific person or group. For groups, you'll need to add the bot to the group first.
+{{productName}} needs a chat ID or username to target a specific person or group. For groups, you'll need to add the bot to the group first.
 
 ## Getting a Chat ID
 
-To message a specific person or group, Maxy needs their chat ID. The easiest way:
+To message a specific person or group, {{productName}} needs their chat ID. The easiest way:
 
 1. Have the person (or yourself) send any message to your bot
-2. Ask Maxy: "What chat IDs have messaged the bot recently?"
-3. Maxy will look up the message history and show you the IDs
+2. Ask {{productName}}: "What chat IDs have messaged the bot recently?"
+3. {{productName}} will look up the message history and show you the IDs
 
 ## Message History
 
-Ask Maxy: "What messages has the bot received?" or "Show recent Telegram activity."
+Ask {{productName}}: "What messages has the bot received?" or "Show recent Telegram activity."
 
 ## Troubleshooting
 
-**Bot not responding:** Check that the bot token is correct — ask Maxy "What's my Telegram bot token configured as?" and verify it matches BotFather.
+**Bot not responding:** Check that the bot token is correct — ask {{productName}} "What's my Telegram bot token configured as?" and verify it matches BotFather.
 
 **Can't send to a group:** The bot must be a member of the group. Add it via the group settings in Telegram, then try again.
 

package/payload/platform/plugins/docs/references/troubleshooting.md

@@ -33,8 +33,8 @@ tail -200 ~/.maxy/logs/maxy-ui.log | rg '\[remote-auth\].*resolvedKind='
 **Symptom:** You send a message and nothing comes back, or the response never arrives.
 
 **Check:**
-1. Ask Maxy: "Check system status" — the `system-status` tool will report whether all services are running
-2. Check the platform logs: ask Maxy "Show me the recent logs"
+1. Ask {{productName}}: "Check system status" — the `system-status` tool will report whether all services are running
+2. Check the platform logs: ask {{productName}} "Show me the recent logs"
 3. If the admin agent itself won't start: restart the platform (see below)
 
 **Common causes:**
@@ -46,15 +46,15 @@ tail -200 ~/.maxy/logs/maxy-ui.log | rg '\[remote-auth\].*resolvedKind='
 
 ## Memory Not Working
 
-**Symptom:** Maxy doesn't remember things you've told it, or search returns nothing.
+**Symptom:** {{productName}} doesn't remember things you've told it, or search returns nothing.
 
 **Check:**
-1. Ask Maxy: "Check the Neo4j connection"
-2. Ask Maxy: "Search memory for [something you know was stored]"
+1. Ask {{productName}}: "Check the Neo4j connection"
+2. Ask {{productName}}: "Search memory for [something you know was stored]"
 
 **Common causes:**
 - Neo4j service stopped — restart the platform, which restarts Neo4j
-- Memory index is stale — ask Maxy: "Reindex memory"
+- Memory index is stale — ask {{productName}}: "Reindex memory"
 
 ---
 
@@ -63,12 +63,12 @@ tail -200 ~/.maxy/logs/maxy-ui.log | rg '\[remote-auth\].*resolvedKind='
 **Symptom:** You send a message to the bot and nothing happens.
 
 **Check:**
-1. Confirm the bot token is correct: ask Maxy "What Telegram bot token is configured?"
+1. Confirm the bot token is correct: ask {{productName}} "What Telegram bot token is configured?"
 2. Verify the bot is running: send `/start` to the bot in Telegram
-3. Check the MCP server logs: ask Maxy "Show Telegram plugin logs"
+3. Check the MCP server logs: ask {{productName}} "Show Telegram plugin logs"
 
 **Common causes:**
-- Bot token changed (if you regenerated it in BotFather) — update it by telling Maxy "Update my Telegram bot token"
+- Bot token changed (if you regenerated it in BotFather) — update it by telling {{productName}} "Update my Telegram bot token"
 - Webhook not connected — restart the platform
 
 ---
@@ -78,46 +78,46 @@ tail -200 ~/.maxy/logs/maxy-ui.log | rg '\[remote-auth\].*resolvedKind='
 **Symptom:** A tool fails with an error, or a plugin says it can't connect.
 
 **Check:**
-1. Ask Maxy: "Show me recent errors"
-2. Ask Maxy: "Restart the [plugin name] plugin"
+1. Ask {{productName}}: "Show me recent errors"
+2. Ask {{productName}}: "Restart the [plugin name] plugin"
 
 **Common causes:**
-- Missing environment variable (API key, token) — the error message will name it; ask Maxy to help configure it
+- Missing environment variable (API key, token) — the error message will name it; ask {{productName}} to help configure it
 - MCP server crashed — restarting the platform restarts all MCP servers
 
 ---
 
 ## Restarting the Platform
 
-From the admin interface, ask Maxy: "Restart the platform."
+From the admin interface, ask {{productName}}: "Restart the platform."
 
-If Maxy itself isn't responding (the page loads but the agent won't connect), try refreshing the browser. If the page itself won't load, the platform process may have stopped — power-cycle the Raspberry Pi by unplugging and reconnecting power, then wait a minute for services to restart automatically.
+If {{productName}} itself isn't responding (the page loads but the agent won't connect), try refreshing the browser. If the page itself won't load, the platform process may have stopped — power-cycle the Raspberry Pi by unplugging and reconnecting power, then wait a minute for services to restart automatically.
 
 ---
 
 ## Checking Logs
 
-Ask Maxy: "Show me the logs" or "Show errors from the last hour."
+Ask {{productName}}: "Show me the logs" or "Show errors from the last hour."
 
 For specific plugin logs: "Show Telegram logs" or "Show contacts plugin logs."
 
-Maxy has access to all platform logs and can filter them for you.
+{{productName}} has access to all platform logs and can filter them for you.
 
 ---
 
 ## Cloudflare Tunnel Down (Remote Access Broken)
 
-**Symptom:** You can reach Maxy on your local network but not via your public domain.
+**Symptom:** You can reach {{productName}} on your local network but not via your public domain.
 
-**Check:** Ask Maxy "Check the Cloudflare tunnel status."
+**Check:** Ask {{productName}} "Check the Cloudflare tunnel status."
 
-**Fix:** Ask Maxy "Restart the Cloudflare tunnel."
+**Fix:** Ask {{productName}} "Restart the Cloudflare tunnel."
 
-If the tunnel won't reconnect, re-run the Cloudflare setup: ask Maxy "Reconnect Cloudflare."
+If the tunnel won't reconnect, re-run the Cloudflare setup: ask {{productName}} "Reconnect Cloudflare."
 
-If the initial Cloudflare login fails during setup, Maxy will fall back to asking you for a connection key. You can create one in the Cloudflare dashboard (Maxy will guide you through this in the browser).
+If the initial Cloudflare login fails during setup, {{productName}} will fall back to asking you for a connection key. You can create one in the Cloudflare dashboard ({{productName}} will guide you through this in the browser).
 
-**If you switched Cloudflare accounts or are stuck on the wrong one:** ask Maxy "Reset my Cloudflare login and start over." This is a clean reset — Maxy clears every stored credential, then opens a fresh browser sign-in. The next sign-in binds to whichever Cloudflare account you choose, with no risk of the previous account's stored credentials silently coming back.
+**If you switched Cloudflare accounts or are stuck on the wrong one:** ask {{productName}} "Reset my Cloudflare login and start over." This is a clean reset — {{productName}} clears every stored credential, then opens a fresh browser sign-in. The next sign-in binds to whichever Cloudflare account you choose, with no risk of the previous account's stored credentials silently coming back.
 
 ---
 
@@ -269,7 +269,7 @@ Most common failures and fixes:
 
 ## Terminal fails after upgrade — `Invalid response` or `window absent from target display`
 
-**Symptom:** You upgraded a Maxy device and the header-menu **Terminal** click now fails — overlay shows `Invalid response`, or `terminal-launch.log` shows `[terminal-launch] failed err="window absent from target display after spawn" pid=<N> display=:99 observed_windows=0 transport=vnc cmd="/usr/bin/xterm "`. The terminal worked on the previous version and the upgrade reported success.
+**Symptom:** You upgraded a {{productName}} device and the header-menu **Terminal** click now fails — overlay shows `Invalid response`, or `terminal-launch.log` shows `[terminal-launch] failed err="window absent from target display after spawn" pid=<N> display=:99 observed_windows=0 transport=vnc cmd="/usr/bin/xterm "`. The terminal worked on the previous version and the upgrade reported success.
 
 **What it means:** The installer declared a new apt dep between versions (e.g. `xdotool` in 1.0.667), but on your device the installer's apt step was silently skipped because `sudo` requires a password and the installer could not escalate non-interactively. The declared dep was never installed, and `vnc.sh check_window_on_display` then either failed to find the binary (exit 127 — Task 634 now surfaces this as a distinct `failed err="xdotool not installed — re-run installer to repair"` line) or reached the `window absent` path because its preflight tool was missing. See `.docs/deployment.md` ("sudo interactivity contract") for the full mechanism.
 

package/payload/platform/plugins/linkedin-import/skills/linkedin-import/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: linkedin-import
-description: Import a LinkedIn Basic Data Export into a Maxy Neo4j graph. Triggers when the user asks to import a LinkedIn archive, ingest LinkedIn connections/messages/positions into the graph, or mentions a `Basic_LinkedInDataExport_*.zip` folder. One reference per CSV under `references/`; edges come from what each CSV naturally encodes, never from synthetic "anchor" patterns.
+description: Import a LinkedIn Basic Data Export into a {{productName}} Neo4j graph. Triggers when the user asks to import a LinkedIn archive, ingest LinkedIn connections/messages/positions into the graph, or mentions a `Basic_LinkedInDataExport_*.zip` folder. One reference per CSV under `references/`; edges come from what each CSV naturally encodes, never from synthetic "anchor" patterns.
 ---
 
 # LinkedIn Import
 
-Ingests a LinkedIn Basic Data Export (unzipped directory of CSVs + subdirs) into a Maxy Neo4j graph. Every edge written corresponds to a real relationship expressed by the data — not a convenience anchor.
+Ingests a LinkedIn Basic Data Export (unzipped directory of CSVs + subdirs) into a {{productName}} Neo4j graph. Every edge written corresponds to a real relationship expressed by the data — not a convenience anchor.
 
 ## Archive-owner confirmation (mandatory first step)
 
@@ -17,7 +17,7 @@ The confirmation flow:
 
 1. List every `:AdminUser` in the graph and display each as `{userId, name, createdAt, accountId(s) via ADMIN_OF}`.
 2. Ask the operator to name the archive owner. Accept one of:
-   - An existing AdminUser userId from the list (typical — Joel's own archive, or a partner who is already a Maxy operator).
+   - An existing AdminUser userId from the list (typical — Joel's own archive, or a partner who is already a {{productName}} operator).
    - A new external Person identity (not-yet-an-AdminUser) — create a fresh `:Person` with `givenName`, `familyName`, `email`/`telephone` (at least one) and use its `elementId` as the owner anchor. This path covers ingesting a non-operator's archive for reference.
 3. Echo the chosen owner back verbatim (`userId=<id> name=<name>`) and require explicit yes/no confirmation before any CSV is touched.
 4. Persist the confirmed owner as `$ownerUserId` (for AdminUser-type owners) or `$ownerPersonId` (for external Person owners) — this parameter flows into every reference.
@@ -32,7 +32,7 @@ When the owner is an AdminUser (the common case):
 (:AdminUser {userId: $ownerUserId}) -[:HAS_PROFILE]-> (:UserProfile {accountId, userId})
 ```
 
-Both nodes already exist for any Maxy operator — the HAS_PROFILE edge is MERGEd by [`platform/ui/app/lib/neo4j-store.ts`](../../../../ui/app/lib/neo4j-store.ts) at session start. The LinkedIn import updates these existing nodes; it does not create parallel operator identities.
+Both nodes already exist for any {{productName}} operator — the HAS_PROFILE edge is MERGEd by [`platform/ui/app/lib/neo4j-store.ts`](../../../../ui/app/lib/neo4j-store.ts) at session start. The LinkedIn import updates these existing nodes; it does not create parallel operator identities.
 
 - **Identity + account-scoped behaviour** → `:AdminUser` and `:UserProfile` (existing, unchanged).
 - **LinkedIn profile enrichment** (headline, summary, websites, industry, geoLocation) → property updates on `:UserProfile`.
@@ -45,14 +45,14 @@ When the owner is an external Person (non-operator archive), the anchor is the c
 1. **Schema first.** The LinkedIn additions (`person_linkedin_url` index, `:Credential` constraint) live in [`platform/neo4j/schema.cypher`](../../../../neo4j/schema.cypher) and are applied by `platform/scripts/seed-neo4j.sh` on every install / upgrade. The skill assumes the schema has been seeded; it does not bootstrap schema itself. If a constraint or index is missing, the operator re-runs `seed-neo4j.sh` from the installer — schema-bootstrap is installer-side, never agent-side.
 2. **Owner confirmed first.** No reference runs until `$ownerUserId` (or `$ownerPersonId`) is persisted and echo-confirmed. The reference set is parameterised — no hard-coded owner.
 3. **Natural edges only.** Every edge written is one the CSV actually expresses. `Connections.csv` encodes "I am connected on LinkedIn to this person" — that becomes `CONNECTED_ON_LINKEDIN`. No synthetic attach-to-owner pattern bolted onto rows that don't describe a relationship to the owner.
-4. **Reuse Maxy labels.** Schema-extension is last resort. The LinkedIn set maps onto existing labels wherever semantics align:
+4. **Reuse {{productName}} labels.** Schema-extension is last resort. The LinkedIn set maps onto existing labels wherever semantics align:
    - LinkedIn companies → `:Organization` (existing, memory-write registered).
    - LinkedIn schools → `:Organization` with `organizationCategory: 'educational'`.
    - LinkedIn skills → `:DefinedTerm` with `category: 'linkedin-skill'`.
    - LinkedIn articles → `:CreativeWork` with `category: 'linkedin-article'`.
    - LinkedIn recommendations → `:Review`.
    - LinkedIn DMs → `:Message:LinkedInMessage` + `:Conversation:LinkedInConversation` (sublabels on the existing labels, per Task 633 pattern).
-   - Certifications → `:Credential` (genuinely new — no existing Maxy label fits `schema:EducationalOccupationalCredential`).
+   - Certifications → `:Credential` (genuinely new — no existing {{productName}} label fits `schema:EducationalOccupationalCredential`).
 5. **Schema-base property names.** `givenName` / `familyName` / `telephone` / `dateSent` — not `firstName` / `phone` / `sentAt`. See [`platform/plugins/memory/references/schema-base.md`](../../../../plugins/memory/references/schema-base.md).
 6. **Schema-base edge names.** `(:Person)-[:WORKS_FOR]->(:Organization)` for positions. Custom LinkedIn edges (`CONNECTED_ON_LINKEDIN`, `ENDORSED`) only where schema-base has no canonical name.
 7. **Provenance stamp.** Every new node: `createdByAgent='linkedin-import'`, `createdBySource='linkedin-import'`, `createdBySession=$sessionId` (UUID per skill run), `createdAt=datetime()`, plus `source='linkedin'` as the data-origin marker.

package/payload/platform/plugins/linkedin-import/skills/linkedin-import/references/profile.md

@@ -1,6 +1,6 @@
 # Reference: Profile.csv
 
-Enriches the confirmed archive owner's `:UserProfile` with the LinkedIn profile fields. No new nodes, no new edges — `:AdminUser` and `:UserProfile` already exist for any Maxy operator and are linked by `[:HAS_PROFILE]` at session start (neo4j-store handles that on session boot, not this skill).
+Enriches the confirmed archive owner's `:UserProfile` with the LinkedIn profile fields. No new nodes, no new edges — `:AdminUser` and `:UserProfile` already exist for any {{productName}} operator and are linked by `[:HAS_PROFILE]` at session start (neo4j-store handles that on session boot, not this skill).
 
 Runs before every other reference because later files display LinkedIn profile fields (headline, summary) on the owner node they search.
 
@@ -46,7 +46,7 @@ This reference invokes `mcp__memory__memory-update` once with the parsed row's p
     "address": null,
     "birthDate": null,
     "headline": "Founder, Rubytech",
-    "description": "Building Maxy …",
+    "description": "Building {{productName}} …",
     "industry": "Software",
     "postalCode": null,
     "addressLocality": "London, UK",

package/payload/platform/plugins/whatsapp/skills/connect-whatsapp/SKILL.md

@@ -5,7 +5,7 @@ description: Guide the user through connecting WhatsApp via QR code pairing, reg
 
 # Connect WhatsApp
 
-Conversational flow for linking a WhatsApp account to Maxy via Baileys QR pairing, followed by admin phone registration and public agent selection. All three phases are required for a correctly configured WhatsApp channel.
+Conversational flow for linking a WhatsApp account to {{productName}} via Baileys QR pairing, followed by admin phone registration and public agent selection. All three phases are required for a correctly configured WhatsApp channel.
 
 ## When to activate
 
@@ -25,7 +25,7 @@ Call `whatsapp-status` first to check the current state. If already connected, t
 
 3. **Wait for scan** — call `whatsapp-login-wait`. This polls for up to 60 seconds. While waiting, tell the user you're watching for the scan.
 
-4. **Confirm connection** — when pairing completes, the tool returns the linked phone number (the *self phone* — the WhatsApp account Maxy now controls). The platform automatically registers this phone as an admin phone and creates the WhatsApp config in `account.json`. Confirm: "WhatsApp connected as {phone}. Your phone is registered as admin."
+4. **Confirm connection** — when pairing completes, the tool returns the linked phone number (the *self phone* — the WhatsApp account {{productName}} now controls). The platform automatically registers this phone as an admin phone and creates the WhatsApp config in `account.json`. Confirm: "WhatsApp connected as {phone}. Your phone is registered as admin."
 
 5. **Verify** — call `whatsapp-status` to confirm the connection is live.
 

package/payload/platform/plugins/workflows/mcp/test-workflows.sh

@@ -28,7 +28,11 @@ echo ""
 
 # Neo4j connectivity check
 echo -n "Checking Neo4j... "
-NEO4J_URI="${NEO4J_URI:-bolt://localhost:7687}"
+# NEO4J_URI is hard-required (Task 788). No default — set explicitly before running tests.
+if [ -z "${NEO4J_URI:-}" ]; then
+  echo "Error: NEO4J_URI required (no default — see Task 788)" >&2
+  exit 1
+fi
 if ! nc -z "$(echo "$NEO4J_URI" | sed 's|.*://||;s|:.*||')" "$(echo "$NEO4J_URI" | sed 's|.*:||')" 2>/dev/null; then
   echo "SKIP — Neo4j not reachable at $NEO4J_URI"
   echo "Tests require Neo4j. Run on the Pi or start Neo4j locally."