@rubytech/create-maxy 1.0.461 → 1.0.463

package/dist/index.js

@@ -567,6 +567,10 @@ function deployPayload() {
         cpSync(liveAccountsDir, persistentAccountsDir, { recursive: true, force: true });
         console.log("  Backed up account data.");
     }
+    // Stop the running service before wiping directories (upgrade path).
+    // The server holds open files in platform/ — rmSync fails with ENOTEMPTY if it's running.
+    const svcName = BRAND.serviceName.replace(".service", "");
+    spawnSync("systemctl", ["--user", "stop", svcName], { stdio: "pipe" });
     // Wipe old platform/maxy/premium-plugins to prevent stale files
     // The UI server directory in the payload is always named "maxy" regardless of brand
     for (const dir of ["platform", "maxy", "premium-plugins", "docs", ".claude"]) {
@@ -598,9 +602,6 @@ function deployPayload() {
 }
 function buildPlatform() {
     log("8", TOTAL, "Installing dependencies and building...");
-    // Stop the running service before rebuilding (upgrade path)
-    const svcName = BRAND.serviceName.replace(".service", "");
-    spawnSync("systemctl", ["--user", "stop", svcName], { stdio: "pipe" });
     console.log(`  Installing platform dependencies (${join(INSTALL_DIR, "platform")})...`);
     shellRetry("npm", ["install", ...NPM_NET_FLAGS], { cwd: join(INSTALL_DIR, "platform") }, 3, 15);
     // MCP server dist/ files are pre-compiled in the payload — no build step needed.

package/package.json

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

package/payload/maxy/server.js

@@ -5102,7 +5102,7 @@ function getMcpServers(accountId, enabledPlugins) {
     // the always-on Chromium instance started by vnc.sh on display :99.
     "plugin_playwright_playwright": {
       command: "npx",
-      args: ["-y", "@playwright/mcp@latest", "--cdp-endpoint", "http://127.0.0.1:9222"]
+      args: ["-y", "@playwright/mcp@latest", "--cdp-endpoint", "http://127.0.0.1:9222", "--caps", "pdf"]
     }
   };
   if (process.env.TELEGRAM_PUBLIC_BOT_TOKEN) {

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

@@ -41,6 +41,7 @@ Tools are available via the `admin` MCP server.
 | Manage access grants | Admin asks to invite visitors, revoke or extend access, list who has access, or set an agent's access mode | `skills/access-manager/SKILL.md` |
 | Manage plugins and settings | User asks to install, enable, disable, or configure plugins, or change account settings | `skills/plugin-management/skill.md` |
 | Manage specialists | User asks to install or remove a specialist subagent, or activate/deactivate premium plugin agents | `skills/specialist-management/skill.md` |
+| Generate print-quality PDF | User asks to create a PDF document, one-pager, brochure, or any HTML intended for print/download | `skills/a4-print-documents/SKILL.md` |
 
 ## Hooks
 

package/payload/platform/plugins/admin/skills/a4-print-documents/SKILL.md

@@ -0,0 +1,241 @@
+---
+name: a4-print-documents
+description: >
+  Constraints for producing print-quality A4 HTML documents intended for PDF output
+  via browser_pdf_save. Use when creating or modifying any HTML document that will be
+  saved as PDF, uses A4 page dimensions, or contains glassmorphism/backdrop-filter effects
+  that must survive print. Trigger phrases: "PDF", "print to PDF", "download PDF",
+  "one-pager", "A4", "brochure", "executive document", "market analysis", or any request
+  to generate a document for print or download.
+---
+
+# A4 Print-Ready HTML Documents
+
+Constraints for producing HTML documents that render correctly when saved as PDF via the browser-specialist's `browser_pdf_save` tool. Every rule exists because violating it caused a visible problem in production documents.
+
+## Rendering path
+
+Generate the HTML document, then delegate to the browser-specialist to save it as PDF using `browser_pdf_save`. The browser-specialist controls Playwright — you compose the delegation brief describing what to render and any pre-render steps (like glassmorphism screenshot capture).
+
+## Glassmorphism does not survive print
+
+`backdrop-filter: blur()`, CSS glassmorphism, and layered transparency effects render as flat, transparent boxes in browser print/PDF output. This is a browser limitation, not a CSS error.
+
+**Required pattern:** Every section using glassmorphism needs a pre-rendered PNG fallback that is hidden on screen and shown only in print.
+
+```css
+.cover-print-img { display: none; }
+
+@media print {
+  .cover > *:not(.cover-print-img) { display: none !important; }
+  .cover-print-img {
+    display: block !important;
+    position: absolute;
+    inset: 0;
+    width: 100%;
+    height: 100%;
+    object-fit: cover;
+  }
+}
+```
+
+```html
+<div class="cover">
+  <img class="cover-print-img" src="cover-print.png" alt="">
+  <!-- live glassmorphism content follows -->
+</div>
+```
+
+This pattern applies to every full-bleed glassmorphism section (cover pages, back pages).
+
+### Capturing the print image
+
+Each glassmorphism section needs its own screenshot — you cannot reuse a print image from a different document or a differently-sized section.
+
+Delegate to the browser-specialist with a brief that includes:
+
+1. **Serve the HTML over HTTP** — `file://` protocol is blocked by Playwright. The specialist should start a local server.
+2. **Set the viewport** to match the element's rendered size. Measure the element's bounding box first, then resize the viewport to `Math.ceil(width) + 1` by `Math.ceil(height) + 1` to eliminate scrollbars.
+3. **Hide UI chrome** (download buttons, navigation overlays) and set `document.body.style.overflow = 'hidden'` to suppress body-level scrollbars.
+4. **Screenshot the specific element** (e.g. `.cover`, `.backpage`) using element-level screenshot — not a full-page or viewport screenshot.
+5. **Save the PNG** alongside the HTML, named for the section it replaces (e.g. `cover-print.png`, `backpage-print.png`).
+6. **Restore** hidden elements and overflow after capture.
+7. **Verify** the saved PNG visually — confirm no scrollbars, no UI chrome, correct dimensions.
+
+After capturing all print images, delegate a second task to save the final PDF via `browser_pdf_save`.
+
+## Page margins, page numbers, and running footers
+
+Use `@page` margin boxes for page numbers and running footers — not `position: fixed` elements.
+
+```css
+@page {
+  margin: 0.6in 0.7in 0.8in;
+  @bottom-center {
+    content: counter(page);
+    font-family: 'Playfair Display', Georgia, serif;
+    font-size: 9pt;
+    color: #8A8A84;
+  }
+}
+
+/* Cover page: zero margins, no page number */
+@page :first {
+  margin: 0;
+  @bottom-center { content: none; }
+}
+
+/* Named page for full-bleed back page */
+@page backpage-full {
+  margin: 0;
+  @bottom-center { content: none; }
+}
+```
+
+Then in `@media print`, the cover needs NO `page:` property — `@page :first` handles it. Only the backpage needs the named page assignment:
+
+```css
+@media print {
+  .cover {
+    width: auto; margin: 0; box-shadow: none; /* reset screen-only properties */
+    min-height: 0;
+    height: 100vh;
+    page-break-after: always;
+    position: relative;
+    overflow: hidden;
+  }
+  .backpage {
+    width: auto; margin: 0; box-shadow: none; /* reset screen-only properties */
+    min-height: 0;
+    height: 100vh;
+    page-break-before: always;
+    position: relative;
+    overflow: hidden;
+    page: backpage-full;
+  }
+}
+```
+
+**Key details:**
+- `@page :first` zeros the margins for the cover — no named page needed on the cover element.
+- Named pages are only needed for non-first full-bleed pages (backpage).
+- `counter(page)` gives automatic page numbering with no JavaScript.
+- No `position: fixed` hacks are needed for repeating headers/footers.
+- If the screen CSS uses `width: 210mm; margin: 20px auto; box-shadow: ...` on the cover/backpage (for the card-on-grey-background look), the print CSS MUST explicitly reset these: `width: auto; margin: 0; box-shadow: none;`. Screen-only layout properties leak into print if not reset. Do NOT use `width: 100vw` or `margin: 0 !important` — just `width: auto; margin: 0`.
+- The print image uses `position: absolute; inset: 0; width: 100%; height: 100%; object-fit: cover;`.
+
+## A4 layout — continuous flow, not fixed-height boxes
+
+Forcing each section into a fixed `height: 297mm` div creates large whitespace gaps when content doesn't fill a full page.
+
+**Correct approach:**
+
+- **Cover page:** `min-height: 100vh` on screen; `height: 100vh; page-break-after: always;` in print.
+- **Content:** Flows naturally. The `@page` margins handle spacing. No fixed-height containers.
+- Use `page-break-inside: avoid` on logical units (cards, tables, callouts, stat groups, timeline items, competitor cards, pullquotes).
+- Use `page-break-before: always` on major section dividers (part breaks).
+- Use `page-break-after: avoid` on headings and section numbers so they don't strand at the bottom of a page.
+- Set `orphans: 3; widows: 3;` on paragraphs to prevent single-line stragglers.
+
+## Dark backgrounds are stripped in print
+
+Browsers strip background colours by default when printing.
+
+**Required:** Add both properties to every dark element in `@media print`:
+
+```css
+@media print {
+  .dark-element {
+    -webkit-print-color-adjust: exact;
+    print-color-adjust: exact;
+  }
+}
+```
+
+## Stripping glassmorphism from content areas
+
+In multi-page documents, strip `backdrop-filter` from content sections (where it won't render correctly anyway) while preserving it on cover/backpage elements that are replaced with print images:
+
+```css
+@media print {
+  /* Strip glass from content */
+  .content *, .content *::before, .content *::after {
+    backdrop-filter: none !important;
+    -webkit-backdrop-filter: none !important;
+    border-radius: 0 !important;
+    box-shadow: none !important;
+  }
+}
+```
+
+## Document structure pattern
+
+Multi-page documents follow this structure:
+
+1. **Cover** — full-bleed, glassmorphism, with print image fallback. Uses `@page :first { margin: 0; }` — NO named page on the element. `page-break-after: always`.
+2. **Table of contents** (optional) — `page-break-after: always` to start content on a fresh page.
+3. **Content sections** — flowing, with part dividers using `page-break-before: always`.
+4. **Back page** — full-bleed CTA/contact page. **Not** an inline footer div — a separate top-level element outside `.body-wrap` with its own named page, print image fallback, and `page-break-before: always`.
+
+**The back page is mandatory for multi-page documents.** An inline CTA footer (a `div` inside flowing content) ends up floating mid-page with whitespace below it. The back page pattern guarantees a clean final page.
+
+```css
+@page backpage-full {
+  margin: 0;
+  @bottom-center { content: none; }
+}
+
+@media print {
+  .backpage {
+    page: backpage-full;
+    min-height: 0; height: 100vh;
+    page-break-before: always;
+    position: relative; overflow: hidden;
+  }
+  .backpage > *:not(.backpage-print-img) { display: none !important; }
+  .backpage-print-img {
+    display: block !important;
+    position: absolute;
+    inset: 0;
+    width: 100%; height: 100%;
+    object-fit: cover;
+  }
+}
+```
+
+```html
+<!-- Outside .body-wrap, after it closes -->
+<div class="backpage">
+  <img class="backpage-print-img" src="backpage-print.png" alt="" style="display:none;">
+  <!-- live backpage content (bg, text, contact info) -->
+</div>
+```
+
+The backpage print image is captured via the same browser-specialist delegation process as the cover — element-level screenshot with UI chrome hidden.
+
+## Single-page documents
+
+For single A4 documents (one-pagers), use fixed dimensions:
+
+```css
+.page {
+  width: 210mm;
+  min-height: 297mm;
+  margin: 0 auto;
+  overflow: hidden;
+}
+
+@page { size: A4; margin: 0; }
+
+@media print {
+  .page {
+    width: 210mm;
+    height: 297mm;
+    page-break-after: always;
+  }
+}
+```
+
+## Document background for multi-page screen viewing
+
+Multi-page documents use a neutral body background (e.g. `body { background: var(--background); }`) on screen. In `@media print`, reset to `body { background: white; }`.

package/payload/platform/plugins/admin/skills/skill-builder/SKILL.md

@@ -46,6 +46,8 @@ Ask what rules the agent should follow when using this skill:
 
 Not every skill needs all of these. Only include what's relevant.
 
+If the skill involves generating PDFs or print-ready documents, load `references/pdf-generation.md` for the constraints on HTML layout and the `browser_pdf_save` rendering path.
+
 ## Step 4: Decide on References
 
 If the skill has detailed procedures, templates, or data formats, those belong in `references/` files — not inline in SKILL.md.

package/payload/platform/plugins/admin/skills/skill-builder/references/pdf-generation.md

@@ -0,0 +1,30 @@
+# PDF Generation in Skills
+
+When a skill needs to produce a PDF, the output is always a two-stage process: the skill authors the HTML, and the browser-specialist renders it to PDF via the `browser_pdf_save` MCP tool.
+
+## The rule
+
+Never instruct the agent to write or execute raw Node.js scripts (e.g. `require('playwright')`, `page.pdf()`, `npx playwright`). Playwright is not in the Node.js module path — these scripts fail with MODULE_NOT_FOUND, waste tool calls searching the filesystem, and produce hardcoded paths that break on reinstall.
+
+Instead, skills that produce PDFs should:
+
+1. **Build the HTML** — the skill's behaviour section describes what the document contains and how it's structured. The agent writes the HTML file using standard file tools.
+2. **Delegate rendering to browser-specialist** — the agent asks the browser-specialist to navigate to the HTML file and call `browser_pdf_save` to produce the PDF. The specialist has Playwright access through governed MCP tools; the admin agent does not.
+
+## Print-ready HTML constraints
+
+HTML intended for PDF output must follow print-ready layout patterns. The most common failures when agents design their own pagination are rigid fixed-height page divs (causing whitespace gaps) and `position: fixed` hacks for headers/footers (causing overlap and duplication).
+
+**Continuous flow layout** — content flows naturally. Use `@page` margin rules for page margins, not wrapper divs with fixed heights. Use `page-break-inside: avoid` on logical units (cards, tables, stat groups) and `page-break-before: always` on major section dividers.
+
+**Page numbers and running footers** — use `@page` margin boxes (`@bottom-center { content: counter(page); }`), not JavaScript or position-fixed elements.
+
+**Dark backgrounds in print** — browsers strip background colours by default. Add `print-color-adjust: exact; -webkit-print-color-adjust: exact;` to dark elements in `@media print`.
+
+**Cover and back pages** — full-bleed pages use `height: 100vh; page-break-after: always;` in `@media print` with zero `@page` margins (via `@page :first` for covers, named pages for back pages).
+
+**Glassmorphism and backdrop-filter** — these do not survive browser print rendering. Any section using glassmorphism needs a pre-rendered PNG fallback image that is hidden on screen and shown only in `@media print`.
+
+## What the skill file should contain
+
+The skill's SKILL.md describes the document's purpose and structure. A `references/` file holds the HTML template or content specification. The skill should state that PDF rendering is delegated to browser-specialist — it should not contain Playwright code, npm commands, or file path assumptions about the Playwright installation.

package/payload/platform/plugins/docs/references/getting-started.md

@@ -31,6 +31,7 @@ Conversation is the only interface. Type what you need:
 - "Schedule a call with Sarah for Thursday at 2pm"
 - "What did I last discuss with Tom?"
 - "Send a Telegram message to the team: standup in 10 minutes"
+- "Create a one-pager PDF about our new product launch"
 
 Maxy understands plain language. You don't need to learn commands or navigate menus.
 

package/payload/platform/plugins/whatsapp/skills/manage-whatsapp-config/SKILL.md

@@ -17,22 +17,42 @@ Call `whatsapp-status` first — if no WhatsApp account is connected, direct the
 
 ## Presenting settings
 
-Call `whatsapp-config action: schema` to get field definitions with descriptions, types, defaults, and constraints. Use the Description column from the schema output as the `description` field on each form field — do not improvise descriptions.
+Call `whatsapp-config action: schema` to get field definitions with descriptions, and `whatsapp-config action: get-config` to get current values. Use the Description column from the schema output as the `description` field on each form field — do not improvise descriptions.
 
-Group related settings logically when presenting:
+### Admin phones
 
-1. **Messaging policies** — dmPolicy, groupPolicy, allowFrom, groupAllowFrom
-2. **Operational limits** — mediaMaxMb, textChunkLimit, debounceMs
-3. **Behaviour** — sendReadReceipts, ackReaction
-4. **Account settings** — name, enabled, selfChatMode
-5. **Group configuration** — groups (per-group activation)
+Before the form, call `whatsapp-config action: list-admin-phones` and display the result. Admin phones are managed via `add-admin-phone` / `remove-admin-phone` — they are not editable in this form.
 
-Present settings as a `render-component` form with:
-- `description` on every field (from schema output)
-- `defaultValue` showing the current value or the schema default
-- Rich option labels with descriptions for enum fields (e.g. dmPolicy options should explain what "open", "allowlist", and "disabled" each mean)
+### Form fields
 
-Before the user submits, summarise what each default does — the user should understand the implications of keeping defaults, not just see them pre-filled.
+Present settings as a `render-component` form. Each field must have a unique `name` matching the schema field name (used as the state key and the `update-config` field key), a `type`, a `label` (plain English), and a `description` (from schema output). For selects, specify `options`. For all fields, set `defaultValue` from `get-config` (current value) or the schema default.
+
+**Messaging policies:**
+
+- `dmPolicy` (`select`): label "Who can message your agent (DMs)", options:
+  - `open` — "Open — anyone can message"
+  - `allowlist` — "Allowlist — only approved numbers"
+  - `disabled` — "Disabled — no public DMs"
+- `groupPolicy` (`select`): label "Group message handling", options:
+  - `open` — "Always — respond to all group messages"
+  - `allowlist` — "Allowlist — only in approved groups"
+  - `disabled` — "Disabled — ignore all group messages"
+
+**Behaviour:**
+
+- `sendReadReceipts` (`select`): label "Blue ticks (read receipts)", options:
+  - `true` — "On — contacts see read receipts"
+  - `false` — "Off — no read receipts"
+
+**Operational limits:**
+
+- `mediaMaxMb` (`number`): label "Media size limit (MB)"
+- `textChunkLimit` (`number`): label "Message chunk limit (characters)"
+- `debounceMs` (`number`): label "Message batching delay (ms)"
+
+### Submit
+
+The form's `submitMessage` must map the field values back to `update-config` field names: `Save these WhatsApp settings: {{json}}` — where `{{json}}` produces the JSON object with field names as keys (e.g. `{ "dmPolicy": "open", "mediaMaxMb": 50, ... }`).
 
 ## Group configuration
 
@@ -51,9 +71,11 @@ After the user submits, write changes via `whatsapp-config action: "update-confi
 
 ## Language
 
-Use plain English:
-- "Who can message your agent" not "dmPolicy"
-- "Message batching delay" not "debounceMs"
-- "Media size limit" not "mediaMaxMb"
-- "Blue ticks" not "sendReadReceipts"
-- Group names, not JIDs
+Plain English goes in `label` — schema field names go in `name`. The `name` property is the machine key (must match the schema exactly); the `label` is what the user reads. Examples:
+
+- `name: "dmPolicy"`, `label: "Who can message your agent (DMs)"`
+- `name: "debounceMs"`, `label: "Message batching delay (ms)"`
+- `name: "mediaMaxMb"`, `label: "Media size limit (MB)"`
+- `name: "sendReadReceipts"`, `label: "Blue ticks (read receipts)"`
+
+Group names (not JIDs) in all user-facing text.

package/payload/platform/templates/specialists/agents/browser-specialist.md

@@ -3,7 +3,7 @@ name: browser-specialist
 description: "Web browser tasks — visiting websites, filling forms, clicking buttons, and reading page content. Delegate when a task requires controlling the browser."
 summary: "Browses the web on your behalf — visiting websites, filling in forms, and extracting information. For example, when you need to sign up for a service, check a competitor's pricing page, or set up an online account."
 model: claude-sonnet-4-6
-tools: mcp__plugin_playwright_playwright__browser_navigate, mcp__plugin_playwright_playwright__browser_navigate_back, mcp__plugin_playwright_playwright__browser_snapshot, mcp__plugin_playwright_playwright__browser_take_screenshot, mcp__plugin_playwright_playwright__browser_click, mcp__plugin_playwright_playwright__browser_fill, mcp__plugin_playwright_playwright__browser_fill_form, mcp__plugin_playwright_playwright__browser_type, mcp__plugin_playwright_playwright__browser_press_key, mcp__plugin_playwright_playwright__browser_hover, mcp__plugin_playwright_playwright__browser_select_option, mcp__plugin_playwright_playwright__browser_wait_for, mcp__plugin_playwright_playwright__browser_handle_dialog, mcp__plugin_playwright_playwright__browser_evaluate, mcp__plugin_playwright_playwright__browser_console_messages, mcp__plugin_playwright_playwright__browser_resize, mcp__plugin_playwright_playwright__browser_tabs, mcp__plugin_playwright_playwright__browser_close, mcp__admin__api-key-store
+tools: mcp__plugin_playwright_playwright__browser_navigate, mcp__plugin_playwright_playwright__browser_navigate_back, mcp__plugin_playwright_playwright__browser_snapshot, mcp__plugin_playwright_playwright__browser_take_screenshot, mcp__plugin_playwright_playwright__browser_click, mcp__plugin_playwright_playwright__browser_fill, mcp__plugin_playwright_playwright__browser_fill_form, mcp__plugin_playwright_playwright__browser_type, mcp__plugin_playwright_playwright__browser_press_key, mcp__plugin_playwright_playwright__browser_hover, mcp__plugin_playwright_playwright__browser_select_option, mcp__plugin_playwright_playwright__browser_wait_for, mcp__plugin_playwright_playwright__browser_handle_dialog, mcp__plugin_playwright_playwright__browser_evaluate, mcp__plugin_playwright_playwright__browser_console_messages, mcp__plugin_playwright_playwright__browser_resize, mcp__plugin_playwright_playwright__browser_tabs, mcp__plugin_playwright_playwright__browser_close, mcp__plugin_playwright_playwright__browser_pdf_save, mcp__admin__api-key-store
 ---
 
 # Browser Specialist