@awesomate/hosting-mcp 0.14.0 → 0.16.0

package/dist/index.js

@@ -40031,7 +40031,7 @@ server.registerTool(
 server.registerTool(
   "awesomate_get_context",
   {
-    description: "Call this FIRST each session. Returns the connected Awesomate account: plan, capabilities (shell access), plan limits, scopes this token can exercise, token expiry (warn the user if within 7 days), cPanel routing when provisioned, and skill.updateAvailable \u2014 if true, the local awesomate-hosting skill files are older than this server; tell the user to re-run Connect Claude Code from hub.awesomate.ai/sites to refresh them (this also renews the token).",
+    description: "Call this FIRST each session. Returns the connected Awesomate account: plan, capabilities (shell access), plan limits, scopes this token can exercise, token expiry (warn the user if within 7 days), cPanel routing when provisioned, and skill.updateAvailable \u2014 if true, the local Awesomate skill files are older than this server; run awesomate_skill_update to refresh them in place (new content loads next session \u2014 mention once, finish the current task first). If the token is also near expiry, re-running Connect Claude Code from hub.awesomate.ai/sites refreshes skills AND renews the token in one go.",
     inputSchema: {}
   },
   async () => {
@@ -40285,10 +40285,10 @@ server.registerTool(
 server.registerTool(
   "awesomate_support",
   {
-    description: "Help the user with the service itself \u2014 questions, being stuck, or reaching a human. action 'faq' {q} searches the published help library (answer FROM the results; never invent policy or pricing). action 'create_ticket' {subject, message} opens a support ticket \u2014 draft it in the user's words, SHOW it, and get an explicit yes before sending; it emails the Awesomate team and returns a portal URL. action 'list_tickets' shows their tickets and status. Use the awesomate-support skill for the full flow. Not for building \u2014 route n8n work to awesomate-n8n and hosting to awesomate-hosting.",
+    description: "Help the user with the service itself \u2014 questions, being stuck, or reaching a human. action 'faq' {q} searches the published help library (answer FROM the results; never invent policy or pricing). action 'help_docs' {q} searches the full Help Centre articles live \u2014 use when the FAQ has no good answer, and cite the returned article URLs. action 'create_ticket' {subject, message} opens a support ticket \u2014 draft it in the user's words, SHOW it, and get an explicit yes before sending; it emails the Awesomate team and returns a portal URL. action 'list_tickets' shows their tickets and status. Use the awesomate-support skill for the full flow. Not for building \u2014 route n8n work to awesomate-n8n and hosting to awesomate-hosting.",
     inputSchema: {
-      action: external_exports.enum(["faq", "create_ticket", "list_tickets"]),
-      q: external_exports.string().optional().describe("faq only: the question"),
+      action: external_exports.enum(["faq", "help_docs", "create_ticket", "list_tickets"]),
+      q: external_exports.string().optional().describe("faq and help_docs: the question or topic"),
       subject: external_exports.string().optional().describe("create_ticket only"),
       message: external_exports.string().optional().describe("create_ticket only: the body, in the user's words")
     }
@@ -40299,6 +40299,10 @@ server.registerTool(
       if (action === "faq") {
         return textResult(await hubGet(cfg, `/api/help/faq${q ? `?q=${encodeURIComponent(q)}` : ""}`));
       }
+      if (action === "help_docs") {
+        if (!q) return errorResult(new Error("help_docs needs q"));
+        return textResult(await hubGet(cfg, `/api/help/docs?q=${encodeURIComponent(q)}`));
+      }
       if (action === "list_tickets") {
         return textResult(await hubGet(cfg, "/api/support/tickets"));
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.14.0",
+  "version": "0.16.0",
   "description": "Awesomate MCP server \u2014 lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
   "license": "UNLICENSED",
   "type": "module",

package/skill/awesomate-credentials/SKILL.md

@@ -1,13 +1,21 @@
 ---
 name: awesomate-credentials
-description: Safely capture and store API keys, tokens, database URLs and other secrets for the user's Awesomate apps — encrypted in the hub and injected into the app's .env, never committed to git, never echoed back. Use whenever the user pastes something that looks like a secret, says "here's my API key", "add this key", "store this secret / token / password", "save my credentials", or drops a key into a file. Companion to awesomate-app-builder. If the secret is for an n8n workflow or automation, route to the awesomate-n8n skill instead — n8n credentials are created on the n8n instance, never in .env.
+description: Safely capture and store API keys, tokens, database URLs and other secrets for the user's Awesomate apps — via a local secret-drop link so the value never enters the chat, encrypted in the hub and injected into the app's .env, never committed to git, never echoed back. Use whenever the user needs to provide a secret ("here's my API key", "I need to give you a key / token / password", "add this key", "store this secret", "save my credentials"), pastes something that looks like a secret, or drops a key into a file. Companion to awesomate-app-builder. If the secret is for an n8n workflow or automation, route to the awesomate-n8n skill instead — n8n credentials are created on the n8n instance, never in .env.
 ---
 
 # Awesomate Credentials — handle secrets safely
 
-Non-technical users will hand you secrets the easy way: pasted into chat or
-dropped in a file. Your job is to get them into the right place **safely** and
-never leak them.
+The best moment to protect a secret is BEFORE it is typed. When the user needs
+to provide one, don't ask them to paste it — serve a secret-drop link (below).
+If they've already pasted it, store it fast and say the rotation line.
+
+## Direct invocation (`/awesomate-credentials`)
+
+When the user invokes this skill by name without revealing a secret, go
+straight to the link flow — the link IS the answer, not a description of it.
+If the conversation already says which app the key is for, launch hub mode for
+that app now. Otherwise ask exactly one question — *"is this for one of your
+apps, or just a key to keep on this machine?"* — then launch.
 
 ## The rules (non-negotiable)
 
@@ -17,46 +25,91 @@ never leak them.
 2. **Never commit a secret.** App secrets live in `.env` (gitignored) or the
    hub's encrypted store — never in tracked files. If you see a secret in code
    about to be committed, stop and move it.
-3. **A secret pasted in chat is exposed.** Store it, then tell the user plainly:
-   *"Because that key was pasted into the chat, treat it as exposed — rotate it
-   when convenient, and next time drop it in the inbox file (below) instead."*
-4. **Prefer the file-drop path** for anything sensitive (below).
+3. **A secret that entered the conversation is exposed** — pasted into chat OR
+   read from a file into your context. Store it, then tell the user plainly:
+   *"treat it as exposed — rotate it when convenient; next time I'll give you a
+   secret-drop link so it never touches the chat."*
+4. **The secret-drop link is the only zero-exposure flow.** Prefer it whenever
+   the value hasn't been revealed yet.
+
+## The secret-drop link (preferred)
+
+A one-time form served on the user's own machine (binds 127.0.0.1 only). The
+value goes browser → destination directly; you only ever see the key NAMES.
+
+1. Pick a free port (45000–49000) and invent a 32-char hex token. Both may
+   appear in chat — they gate the link, not the secret.
+2. Start it in the background. Two destinations:
+
+   **App runtime secret** (an API key the backend calls, a token — goes to the
+   app's encrypted hub env, then its `.env`, then the app restarts):
+   ```bash
+   node ~/.claude/skills/awesomate-credentials/scripts/secret-drop.mjs \
+     --hub-app <appId> --env dev --keys STRIPE_SECRET_KEY --port <port> --token <hex>
+   ```
+   Get `<appId>` from `awesomate_app_list`. Keys are UPPER_SNAKE (lowercase is
+   auto-uppercased). Node apps only — static sites have no server env. The
+   script posts each value to the hub with the user's own PAT
+   (`~/.awesomate/credentials.json`) — the same route `awesomate_app_set_env`
+   uses, so encryption, `.env` injection and restart all behave identically.
+
+   **A personal key just to keep** (not an app runtime secret):
+   ```bash
+   node ~/.claude/skills/awesomate-credentials/scripts/secret-drop.mjs \
+     --keys OPENAI_API_KEY --port <port> --token <hex>
+   ```
+   Writes to `~/.config/api-keys.env` (mode 600); `--file .env` targets a local
+   dev env file instead (gitignored files only).
+
+3. Give the user the link as clickable markdown —
+   `http://127.0.0.1:<port>/?t=<token>` — and say: *"click this and paste your
+   key there; I never see the value."*
+4. The background task prints `SAVED: <names>` (names only, never values). In
+   hub mode a failed key prints `FAILED: <name> (status …)` and the form stays
+   up so the user can resubmit — report the reason and have them retry.
+5. `EADDRINUSE` on start → relaunch on another port with a fresh token.
+6. Confirm with key names only. No rotation warning needed — the value never
+   entered the conversation.
 
 ## Detect and offer
 
 If the user's message contains something shaped like a secret — `sk-…`,
 `ghp_`/`gho_…`, `AKIA…`, `xox[bp]-…`, a bearer token, a `postgres://…` /
-`mysql://…` URL, or they say "here's my key" — don't just carry on. Offer to
-store it safely: *"I'll store that as an encrypted secret for your app and keep
-it out of the code — what's it for?"* Then store it (below) and redact it from
-your own responses.
+`mysql://…` URL — it is already exposed: store it immediately (below), redact
+it from your responses, and say the rotation line. But if they ANNOUNCE a
+secret without pasting it ("I've got the Stripe key ready"), that is the moment
+the link flow exists for.
 
 ## Where a secret goes
 
 Read [references/where-secrets-go.md](references/where-secrets-go.md) for the
 full map. Short version:
 
-- **A running app needs it** (API key the backend calls, a DB URL) → store it on
-  the app with **`awesomate_app_set_env`** (tool). It's encrypted in the hub AND
-  written to the app's `.env` (0600), then the app restarts. Ask which env
-  (default `dev`). Node apps only — static sites have no server env.
-- **A personal key just to keep** (not an app runtime secret) → your local
-  `~/.config/api-keys.env` (chmod 600), with a note if it was pasted in chat.
+- **A running app needs it** (API key the backend calls, a DB URL) → the app's
+  encrypted hub env + `.env` (0600) + restart. Via the secret-drop `--hub-app`
+  link when the value hasn't been revealed, or **`awesomate_app_set_env`**
+  (tool) when it already has. Ask which env (default `dev`). Node apps only —
+  static sites have no server env.
+- **A personal key just to keep** → `~/.config/api-keys.env` (chmod 600), via
+  the file-mode link; add a rotation note if it came through the chat.
 - **Never** a tracked file, a commit, or the chat.
 
-## The safe file-drop flow (preferred)
+## Fallback: the file-drop flow
 
-For anything sensitive, steer the user away from pasting in chat:
+Only when the link flow can't work (e.g. Claude is running on a remote machine
+the user's browser can't reach as 127.0.0.1):
 
 1. Tell them: *"Create a file `.awesomate/secret-inbox.txt` in your project and
    paste the value there — I'll grab it and wipe the file."* (`.awesomate/` is
    gitignored by the github skill.)
-2. Read the file to capture the value, call `awesomate_app_set_env` to store it,
-   then **scrub the file**:
+2. Read the file, store via `awesomate_app_set_env`, then **scrub the file**:
    `node ~/.claude/skills/awesomate-credentials/scripts/capture-secret.mjs .awesomate/secret-inbox.txt`
-   — this securely overwrites and removes it so the plaintext doesn't linger.
-3. Confirm with the key name only.
+3. Be honest with the user: reading the file put the value in the conversation
+   record, so the rotation nudge still applies — softer than a chat paste, not
+   zero.
 
 ## After storing
-Tell the user what you set (key + env), that it's encrypted and injected, and —
-if it came through the chat — the one-line rotation nudge. Never restate the value.
+
+Tell the user what you set (key + env + where), that it's encrypted and
+injected, and — if the value ever entered the conversation — the one-line
+rotation nudge. Never restate the value.

package/skill/awesomate-credentials/references/where-secrets-go.md

@@ -2,25 +2,28 @@
 
 | The secret is… | Put it… | How |
 |---|---|---|
-| An app runtime secret (API key the backend calls, a third-party token, a DB URL) | The app's `.env` **and** the hub's encrypted store | `awesomate_app_set_env` (tool) — encrypts hub-side + injects into `.env` (0600) + restarts the app |
+| An app runtime secret (API key the backend calls, a third-party token, a DB URL) | The app's `.env` **and** the hub's encrypted store | Not yet revealed → secret-drop link with `--hub-app` (value never enters the chat). Already exposed → `awesomate_app_set_env` (tool). Both encrypt hub-side + inject into `.env` (0600) + restart the app |
 | An n8n webhook URL the app calls (`N8N_WEBHOOK_URL`) | Same as above | `awesomate_app_set_env` — it's not secret-secret, but it belongs in `.env` with the rest |
-| A personal key the user just wants kept (not used by a running app) | `~/.config/api-keys.env` (chmod 600) | Append `KEY=value`; add a `# pasted in chat <date> — rotate` note if it came through chat |
+| A personal key the user just wants kept (not used by a running app) | `~/.config/api-keys.env` (chmod 600) | Secret-drop link in file mode (the default); add a `# pasted in chat <date> — rotate` note if it came through chat instead |
 | Anything, ever | **NOT** in code, a tracked file, a commit, or the chat transcript | — |
 
 ## Why two places for app secrets
 The hub's encrypted `hosted_app_env_secrets` row is the **durable source of
 truth** (survives redeploys, is auditable, uses the same AES-256-GCM as the DB
 password). The host `.env` is what the **running process actually reads**
-(`dotenv/config`). `awesomate_app_set_env` writes both in one step.
+(`dotenv/config`). Both the secret-drop `--hub-app` flow and
+`awesomate_app_set_env` write both in one step — they share the same hub route.
 
 ## Redaction pattern
 When you confirm, show at most a short prefix:
 - `sk-proj-abc…` → `OPENAI_API_KEY = sk-proj-…redacted`
 - a DB URL → `DATABASE_URL = postgresql://…redacted`
-Never the full value.
+Never the full value. Keys captured through the secret-drop link need no
+redaction gymnastics — you never saw the value; confirm with the name alone.
 
-## Rotation note (chat-pasted keys)
-A value pasted into the conversation is in the transcript — treat it as exposed.
-After storing it, tell the user once: *"rotate this when convenient, and next
-time use the `.awesomate/secret-inbox.txt` drop so it stays out of the chat."*
+## Rotation note (keys that entered the conversation)
+A value pasted into the conversation — or read from a file into context — is in
+the transcript; treat it as exposed. After storing it, tell the user once:
+*"rotate this when convenient, and next time I'll give you a secret-drop link
+so it never touches the chat."*
 High-value keys (payment, production DB, cloud root) — recommend rotating now.

package/skill/awesomate-credentials/scripts/secret-drop.mjs

@@ -0,0 +1,279 @@
+#!/usr/bin/env node
+// secret-drop — one-time localhost form for handing secrets to Claude
+// without them entering the chat. Values are never printed; only key names.
+//
+// File mode (default): writes KEY=value into an env file (mode 600).
+//   node secret-drop.mjs [--file ~/.config/api-keys.env] [--keys A,B]
+// Hub mode: posts each key to the Awesomate hub's encrypted app env —
+// the same POST /api/my-apps/apps/:id/env route as awesomate_app_set_env,
+// authenticated with the user's own PAT from ~/.awesomate/credentials.json.
+//   node secret-drop.mjs --hub-app <appId> [--env dev|staging|prod] [--keys A,B]
+// Common: [--port 0] [--token <hex>] [--ttl 15] [--stay]
+
+import http from 'node:http';
+import crypto from 'node:crypto';
+import fs from 'node:fs';
+import path from 'node:path';
+import os from 'node:os';
+
+const args = process.argv.slice(2);
+const argVal = (name, def) => {
+  const i = args.indexOf(`--${name}`);
+  return i >= 0 && args[i + 1] !== undefined ? args[i + 1] : def;
+};
+const expandHome = (p) => (p === '~' || p.startsWith('~/')) ? path.join(os.homedir(), p.slice(1)) : p;
+
+const hubAppId = argVal('hub-app', '');
+const hubEnv = argVal('env', 'dev');
+const hubMode = hubAppId !== '';
+const filePath = path.resolve(expandHome(argVal('file', '~/.config/api-keys.env')));
+const ttlMs = Number(argVal('ttl', '15')) * 60_000;
+const port = Number(argVal('port', '0'));
+const token = argVal('token', crypto.randomBytes(16).toString('hex'));
+const stay = args.includes('--stay');
+
+const FILE_KEY_RE = /^[A-Za-z_][A-Za-z0-9_]*$/;
+const HUB_KEY_RE = /^[A-Z][A-Z0-9_]{0,63}$/;
+const SAFE_VAL_RE = /^[A-Za-z0-9_@%+=:,.\/-]*$/;
+
+const fail = (msg) => { console.error(`secret-drop: ${msg}`); process.exit(1); };
+
+if (hubMode && (!/^[1-9]\d*$/.test(hubAppId))) fail(`--hub-app must be a positive app id, got: ${hubAppId}`);
+if (hubMode && !['dev', 'staging', 'prod'].includes(hubEnv)) fail(`--env must be dev|staging|prod, got: ${hubEnv}`);
+
+const normalizeKey = (name) => (hubMode ? name.toUpperCase() : name);
+const keyValid = (name) => (hubMode ? HUB_KEY_RE.test(name) : FILE_KEY_RE.test(name));
+
+const expectedKeys = (argVal('keys', '') || '').split(',').map((s) => normalizeKey(s.trim())).filter(Boolean);
+for (const k of expectedKeys) {
+  if (!keyValid(k)) fail(`invalid key name: ${k}`);
+}
+
+let hubAuth = null;
+if (hubMode) {
+  let pat = process.env.AWESOMATE_PAT || '';
+  let base = process.env.AWESOMATE_API_BASE || '';
+  if (!pat || !base) {
+    try {
+      const raw = JSON.parse(fs.readFileSync(path.join(os.homedir(), '.awesomate', 'credentials.json'), 'utf8'));
+      const prof = raw.profiles
+        ? raw.profiles[process.env.AWESOMATE_ACCOUNT || raw.defaultProfile] || raw
+        : raw;
+      pat = pat || prof.pat || '';
+      base = base || prof.apiBase || '';
+    } catch { /* handled below */ }
+  }
+  if (!pat) fail('no Awesomate PAT found — connect your hosting first (~/.awesomate/credentials.json), or set AWESOMATE_PAT');
+  hubAuth = { pat, base: (base || 'https://hub.awesomate.ai').replace(/\/+$/, '') };
+}
+
+const destinationLabel = hubMode
+  ? `app #${hubAppId} (${hubEnv} environment) — encrypted in your Awesomate hub`
+  : filePath;
+
+const tokenOk = (t) => {
+  if (typeof t !== 'string') return false;
+  const a = Buffer.from(t);
+  const b = Buffer.from(token);
+  return a.length === b.length && crypto.timingSafeEqual(a, b);
+};
+
+const esc = (s) => s.replace(/[&<>"']/g, (c) => ({ '&': '&amp;', '<': '&lt;', '>': '&gt;', '"': '&quot;', "'": '&#39;' }[c]));
+
+const page = (title, body) => `<!doctype html><html><head><meta charset="utf-8">
+<meta name="viewport" content="width=device-width,initial-scale=1">
+<title>${title}</title><style>
+  body{background:#1c1917;color:#e7e5e4;font:15px/1.5 -apple-system,system-ui,sans-serif;
+       display:flex;justify-content:center;padding:48px 16px}
+  main{width:100%;max-width:560px}
+  h1{font-size:20px;font-weight:600}
+  .card{background:#292524;border:1px solid #44403c;border-radius:12px;padding:24px;margin-top:16px}
+  label{display:block;font-size:13px;color:#a8a29e;margin:14px 0 4px}
+  input.sec,textarea{width:100%;box-sizing:border-box;background:#1c1917;
+    color:#e7e5e4;border:1px solid #44403c;border-radius:8px;padding:10px;font:13px ui-monospace,monospace}
+  textarea{min-height:110px;resize:vertical}
+  button{margin-top:18px;background:#6366f1;color:#fff;border:0;border-radius:8px;
+    padding:10px 18px;font-size:14px;font-weight:600;cursor:pointer}
+  .muted{color:#a8a29e;font-size:13px}
+  code{background:#1c1917;padding:1px 5px;border-radius:4px;font-size:12.5px}
+  ul{padding-left:20px}
+  .ok{color:#4ade80}
+  .bad{color:#f87171}
+</style></head><body><main>${body}</main></body></html>`;
+
+const formPage = () => {
+  const fields = expectedKeys.map((k) =>
+    `<label for="k_${k}">${k}</label><input type="password" class="sec" id="k_${k}" name="k_${k}" autocomplete="off" spellcheck="false">`
+  ).join('');
+  return page('Secret drop', `
+    <h1>Secret drop</h1>
+    <p class="muted">Values submitted here go straight to <code>${esc(destinationLabel)}</code>.
+    They never enter the Claude chat — Claude only sees the key names.</p>
+    <div class="card"><form method="post" action="/save">
+      <input type="hidden" name="t" value="${token}">
+      ${fields}
+      <label for="bulk">${expectedKeys.length ? 'Or paste' : 'Paste'} one or more <code>KEY=value</code> lines</label>
+      <textarea id="bulk" name="bulk" autocomplete="off" spellcheck="false" placeholder="${hubMode ? 'STRIPE_SECRET_KEY=sk_live_...' : 'OPENROUTER_API_KEY=sk-or-...&#10;RESEND_API_KEY=re_...'}"></textarea>
+      ${expectedKeys.length ? `<label style="display:flex;align-items:center;gap:6px;margin-top:10px">
+        <input type="checkbox" onchange="document.querySelectorAll('.sec').forEach(i=>i.type=this.checked?'text':'password')" style="width:auto"> show values
+      </label>` : ''}
+      <button type="submit">Save securely</button>
+    </form></div>`);
+};
+
+function quoteVal(v) {
+  if ((v.startsWith('"') && v.endsWith('"') && v.length >= 2) ||
+      (v.startsWith("'") && v.endsWith("'") && v.length >= 2)) return v;
+  if (SAFE_VAL_RE.test(v)) return v;
+  return `'${v.replace(/'/g, `'\\''`)}'`;
+}
+
+function writeEnv(file, updates) {
+  fs.mkdirSync(path.dirname(file), { recursive: true });
+  let lines = fs.existsSync(file) ? fs.readFileSync(file, 'utf8').split('\n') : [];
+  while (lines.length && lines[lines.length - 1] === '') lines.pop();
+  const replaced = new Set();
+  lines = lines.map((line) => {
+    const m = line.match(/^(export\s+)?([A-Za-z_][A-Za-z0-9_]*)=/);
+    if (m && updates.has(m[2])) {
+      replaced.add(m[2]);
+      return `${m[1] || ''}${m[2]}=${quoteVal(updates.get(m[2]))}`;
+    }
+    return line;
+  });
+  for (const [k, v] of updates) {
+    if (!replaced.has(k)) lines.push(`${k}=${quoteVal(v)}`);
+  }
+  fs.writeFileSync(file, lines.join('\n') + '\n', { mode: 0o600 });
+  fs.chmodSync(file, 0o600);
+}
+
+async function hubSet(key, value) {
+  const res = await fetch(`${hubAuth.base}/api/my-apps/apps/${hubAppId}/env`, {
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json', Authorization: `Bearer ${hubAuth.pat}` },
+    body: JSON.stringify({ key, value, env: hubEnv }),
+    signal: AbortSignal.timeout(20_000),
+  });
+  let detail = '';
+  try {
+    const j = await res.json();
+    detail = String(j.error || j.detail || '').slice(0, 200);
+  } catch { /* non-JSON body */ }
+  return { ok: res.ok, status: res.status, detail };
+}
+
+function parseSubmission(params) {
+  const updates = new Map();
+  const invalid = [];
+  const add = (rawName, rawVal) => {
+    const name = normalizeKey(rawName.trim());
+    const val = rawVal.replace(/\r/g, '').trim();
+    if (!val) return;
+    if (keyValid(name)) updates.set(name, val);
+    else invalid.push(rawName.trim());
+  };
+  for (const [k, v] of params) {
+    if (k.startsWith('k_')) add(k.slice(2), v);
+  }
+  for (const line of (params.get('bulk') || '').split('\n')) {
+    const s = line.replace(/\r$/, '').trim();
+    if (!s || s.startsWith('#')) continue;
+    const eq = s.indexOf('=');
+    if (eq <= 0) continue;
+    add(s.slice(0, eq).replace(/^export\s+/, ''), s.slice(eq + 1));
+  }
+  return { updates, invalid };
+}
+
+const server = http.createServer((req, res) => {
+  res.setHeader('Cache-Control', 'no-store');
+  res.setHeader('Referrer-Policy', 'no-referrer');
+  const url = new URL(req.url, 'http://127.0.0.1');
+
+  if (req.method === 'GET' && url.pathname === '/') {
+    if (!tokenOk(url.searchParams.get('t'))) { res.writeHead(403); return res.end('forbidden'); }
+    res.writeHead(200, { 'Content-Type': 'text/html; charset=utf-8' });
+    return res.end(formPage());
+  }
+
+  if (req.method === 'POST' && url.pathname === '/save') {
+    let body = '';
+    req.on('data', (c) => {
+      body += c;
+      if (body.length > 1_048_576) req.destroy();
+    });
+    req.on('end', async () => {
+      const params = new URLSearchParams(body);
+      if (!tokenOk(params.get('t'))) { res.writeHead(403); return res.end('forbidden'); }
+      const { updates, invalid } = parseSubmission(params);
+      const invalidNote = invalid.length
+        ? `<p class="bad">Skipped invalid key name${invalid.length > 1 ? 's' : ''}: <code>${invalid.map(esc).join(', ')}</code>${hubMode ? ' (letters, digits and underscores only, starting with a letter)' : ''}</p>`
+        : '';
+      if (!updates.size) {
+        res.writeHead(200, { 'Content-Type': 'text/html; charset=utf-8' });
+        return res.end(page('Secret drop', `<h1>Nothing saved</h1>${invalidNote}
+          <p class="muted">No valid <code>KEY=value</code> entries found. Go back and try again.</p>`));
+      }
+
+      if (hubMode) {
+        const results = [];
+        for (const [key, value] of updates) {
+          try {
+            results.push({ key, ...(await hubSet(key, value)) });
+          } catch (e) {
+            results.push({ key, ok: false, status: 0, detail: String((e && e.message) || e).slice(0, 200) });
+          }
+        }
+        const saved = results.filter((r) => r.ok).map((r) => r.key);
+        const failed = results.filter((r) => !r.ok);
+        if (saved.length) console.log(`SAVED: ${saved.join(',')} -> hub app ${hubAppId} (${hubEnv})`);
+        for (const f of failed) console.log(`FAILED: ${f.key} (status ${f.status}${f.detail ? `: ${f.detail}` : ''})`);
+        const allOk = failed.length === 0;
+        const rows = results.map((r) => r.ok
+          ? `<li class="ok">✓ ${esc(r.key)}</li>`
+          : `<li class="bad">✗ ${esc(r.key)} — ${r.status ? `error ${r.status}` : 'request failed'}${r.detail ? `: ${esc(r.detail)}` : ''}</li>`
+        ).join('');
+        res.writeHead(200, { 'Content-Type': 'text/html; charset=utf-8' });
+        res.end(page('Secret drop', `<h1 class="${allOk ? 'ok' : 'bad'}">${allOk ? 'Saved' : 'Partly saved'}</h1>
+          ${invalidNote}<ul>${rows}</ul>
+          <p class="muted">Destination: <code>${esc(destinationLabel)}</code>.
+          ${allOk && !stay ? 'You can close this tab — the link is now dead.' : 'Go back to retry the failed keys.'}</p>`));
+        if (allOk && !stay) setTimeout(() => { server.close(); process.exit(0); }, 750);
+        return;
+      }
+
+      try {
+        writeEnv(filePath, updates);
+      } catch (e) {
+        res.writeHead(500, { 'Content-Type': 'text/html; charset=utf-8' });
+        return res.end(page('Secret drop', `<h1>Write failed</h1><p class="muted">${esc(String((e && e.message) || e))}</p>`));
+      }
+      const names = [...updates.keys()];
+      console.log(`SAVED: ${names.join(',')} -> ${filePath}`);
+      res.writeHead(200, { 'Content-Type': 'text/html; charset=utf-8' });
+      res.end(page('Secret drop', `<h1 class="ok">Saved</h1>${invalidNote}
+        <p>Wrote <strong>${names.map(esc).join(', ')}</strong> to <code>${esc(filePath)}</code>.</p>
+        <p class="muted">You can close this tab${stay ? '' : ' — the link is now dead'}.</p>`));
+      if (!stay) setTimeout(() => { server.close(); process.exit(0); }, 750);
+    });
+    return;
+  }
+
+  res.writeHead(404);
+  res.end('not found');
+});
+
+server.listen(port, '127.0.0.1', () => {
+  const p = server.address().port;
+  console.log('secret-drop listening (127.0.0.1 only)');
+  console.log(`  dest:  ${destinationLabel}`);
+  if (expectedKeys.length) console.log(`  keys:  ${expectedKeys.join(', ')}`);
+  console.log(`  open:  http://127.0.0.1:${p}/?t=${token}`);
+  console.log(`  expires in ${Math.round(ttlMs / 60000)} min${stay ? '' : '; exits after first successful save'}`);
+});
+
+setTimeout(() => {
+  console.log('secret-drop: expired');
+  process.exit(0);
+}, ttlMs);

package/skill/awesomate-hosting/SKILL.md

@@ -37,8 +37,9 @@ once (plus `awesomate_get_limits` before any create/change) and cache:
 - **`patExpiresAt`** — within ~7 days, or any 401: re-run the setup prompt at
   **hub.awesomate.ai/sites → Connect Claude Code** to refresh the token.
 - **`skill.updateAvailable`** — this skill's local files are older than the MCP
-  server. Mention once (don't nag); the same Connect re-run refreshes the skill
-  and renews the token in one go. Not urgent — finish the user's request first.
+  server. Mention once (don't nag); run `awesomate_skill_update` to refresh in
+  place (new content loads next session). If the token is also near expiry, the
+  Connect re-run above does both. Not urgent — finish the user's request first.
 - **`cpanel`** routing (host/user), present once hosting is provisioned.
 
 If `awesomate_get_context` fails with a connectivity error, it's the user's

package/skill/awesomate-support/SKILL.md

@@ -20,18 +20,22 @@ also carries the plan). Describe what a plan or upgrade INCLUDES from
 balance without spending anything. Never quote a plan, price, or balance
 from memory.
 
-## 1. FAQ first
+## 1. FAQ first, then help docs
 
 For any "how do I", "why does", "what is" question about the service:
 
 1. Call `awesomate_support {action:'faq', q:'<their question>'}`.
 2. Answer FROM the returned entries, in your own plain words. Cite nothing
    the FAQ and tools didn't say — no invented policy, no guessed pricing.
-3. If the FAQ answers it, you're done. If it partially answers, give what
-   you have and say which part is unconfirmed.
-4. If it doesn't answer it: "I don't have a confirmed answer for that. Want
+3. If the FAQ misses or only partially answers, call
+   `awesomate_support {action:'help_docs', q:'<topic>'}` — a live search of
+   the full Help Centre articles. Answer from the excerpts and give the
+   article's URL so the user can read the full steps.
+4. If neither answers it: "I don't have a confirmed answer for that. Want
    me to ask the Awesomate team? I'll draft a support ticket for you to
-   approve first." Then go to §2 if they say yes.
+   approve first." Then go to §2 if they say yes. (An empty help_docs
+   result can also mean the search is temporarily down — the response's
+   help_centre_url is always safe to offer for browsing.)
 
 ## 2. Ticket flow — talking to a human