@rubytech/create-maxy 1.0.442 → 1.0.444

package/payload/platform/plugins/whatsapp/references/channels-whatsapp.md

@@ -1,6 +1,6 @@
 # WhatsApp Channels
 
-Taskmaster supports two WhatsApp connection methods via Baileys multi-account:
+The platform supports two WhatsApp connection methods via Baileys multi-account:
 
 | Provider | Use Case | Connection |
 |----------|----------|------------|
@@ -16,7 +16,7 @@ Most users will have two Baileys accounts (two phone numbers, both linked via QR
 | **Personal** | Admin self-chat, groups, personal contacts |
 | **Business** | Customer-facing DMs (can be WhatsApp Business app or regular WhatsApp) |
 
-WhatsApp Business **app** vs personal WhatsApp is irrelevant from Taskmaster's perspective — Baileys connects to both identically via QR. The Business app just adds business profile, catalog, and labels in the phone UI.
+WhatsApp Business **app** vs personal WhatsApp is irrelevant from the platform's perspective — Baileys connects to both identically via QR. The Business app just adds business profile, catalog, and labels in the phone UI.
 
 **Linked device note:** The primary phone must come online periodically (~every 14 days) to keep the Baileys linked-device session alive. It does NOT need to be on 24/7.
 
@@ -79,19 +79,19 @@ Cloud API requirements: Meta Business Account, System User Access Token, Cloudfl
 
 Baileys uses the same WebSocket protocol as WhatsApp Web/Desktop linked devices. Meta cannot blanket-block it without breaking their own official clients for hundreds of millions of users.
 
-**Responsibility model:** Taskmaster and its other users are not at risk — bans are per-number, targeting individual accounts for abusive behaviour. Users should be told: *"Don't use this for bulk messaging or spam. Meta may ban your number for abusive patterns. Normal business conversations are fine."*
+**Responsibility model:** The platform and its other users are not at risk — bans are per-number, targeting individual accounts for abusive behaviour. Users should be told: *"Don't use this for bulk messaging or spam. Meta may ban your number for abusive patterns. Normal business conversations are fine."*
 
 - Normal conversational use (replies, scheduling, quotes) = effectively zero risk
 - Ack reactions, typing indicators, and reply delays mimic real linked-device behaviour
 - Risk increases only with spam patterns: mass messaging, rapid-fire sends to unknown contacts, broadcasting
-- If a user's number is banned, it's between them and Meta — other Taskmaster users are unaffected
+- If a user's number is banned, it's between them and Meta — other users are unaffected
 - Cloud API code is available as a fallback for enterprise users who want official Meta support
 
 ## WhatsApp Outbound Policy — No Automated Broadcasts
 
 **WhatsApp's Terms of Service explicitly prohibit automated bulk/broadcast messaging.** This applies to both Baileys and Cloud API connections. Violations result in permanent number bans with no appeal.
 
-Taskmaster enforces this at multiple levels:
+The platform enforces this at multiple levels:
 
 1. **Broadcast action blocked** — The `message broadcast` action (which sends to multiple targets) always excludes WhatsApp as a target channel, regardless of config. This is a hard block that cannot be overridden.
 2. **Agent tool suppression** — When an agent session is on WhatsApp, the `broadcast` action is removed from the message tool schema entirely. Agents cannot invoke it.
@@ -154,7 +154,7 @@ The Public Agent Settings modal includes a **Model** dropdown that sets the defa
 **How it works:**
 1. UI resolves the selected workspace's public agent ID (e.g. `joes-coffee-public`)
 2. On change, writes the model to config via `writeAgentModelToConfig` (two params: agentId + model)
-3. Config stored in `agents.list[{agentId}].model` in `~/.taskmaster/taskmaster.json`
+3. Config stored in `agents.list[{agentId}].model` in `account.json`
 4. No gateway restart needed — `agents` prefix has `kind: "none"` reload rule (read dynamically)
 
 **Runtime model resolution — config is the single source of truth.** Every model read (LLM API call, `/status` display, chat UI initial load) calls `loadConfig()` fresh and resolves via `resolveDefaultModelForAgent({ cfg, agentId })`. There are no session-level model overrides — the model is always read from config at the point of use.
@@ -182,7 +182,7 @@ The Public Agent Settings modal includes a **Thinking** dropdown that sets the d
 **How it works:**
 1. UI resolves the selected workspace's public agent ID (e.g. `joes-coffee-public`)
 2. On change, writes the thinking level to config via `writeAgentThinkingToConfig` (two params: agentId + thinkingLevel)
-3. Config stored in `agents.list[{agentId}].thinkingLevel` in `~/.taskmaster/taskmaster.json`
+3. Config stored in `agents.list[{agentId}].thinkingLevel` in `account.json`
 4. No gateway restart needed — `agents` prefix has `kind: "none"` reload rule (read dynamically)
 
 **Runtime thinking resolution — config is the single source of truth.** Every thinking level read calls `loadConfig()` fresh and resolves via `resolveThinkingDefault({ cfg, provider, model, catalog, agentId })`. There are no session-level thinking overrides — thinking is always read from config at the point of use.
@@ -254,22 +254,19 @@ Baileys stores WhatsApp session credentials (linked-device state) on disk. The a
 | Priority | Path | When |
 |----------|------|------|
 | 1. Explicit config | `channels.whatsapp.accounts.{id}.authDir` | User overrides in config |
-| 2. Default | `~/.taskmaster/credentials/whatsapp/{accountId}/` | Normal operation |
-| 3. Legacy fallback | `~/.taskmaster/credentials/` | Old single-account installs (only if creds exist here and not at default path) |
-
-The state dir (`~/.taskmaster/`) can be overridden via `TASKMASTER_STATE_DIR` env var; the credentials subdirectory via `TASKMASTER_OAUTH_DIR`.
+| 2. Default | `~/.maxy/credentials/whatsapp/{accountId}/` | Normal operation |
 
 **Diagnostics on the Pi:**
 
 ```bash
 # List all WhatsApp auth directories
-ls -la ~/.taskmaster/credentials/whatsapp/
+ls -la ~/.maxy/credentials/whatsapp/
 
 # Check if credentials exist for an account
-ls ~/.taskmaster/credentials/whatsapp/default/creds.json
+ls ~/.maxy/credentials/whatsapp/default/creds.json
 
 # Check credential freshness (should be recent if just linked)
-stat ~/.taskmaster/credentials/whatsapp/default/creds.json
+stat ~/.maxy/credentials/whatsapp/default/creds.json
 ```
 
 If `creds.json` is missing, the session was never linked or was deleted. If it exists but WhatsApp rejects it (401), the session was invalidated (cleared from phone, expired after 14 days offline, or account banned).

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

@@ -10,7 +10,7 @@ tools:
   - workflow-validate
   - workflow-execute
   - workflow-runs
-metadata: {"taskmaster":{"always":false,"embed":false,"pluginKey":"workflows","optional":true,"recommended":true}}
+metadata: {"platform":{"always":false,"embed":[],"pluginKey":"workflows","optional":true,"recommended":true}}
 ---
 
 # Workflows