@rubytech/create-maxy-code 0.1.71 → 0.1.73

package/payload/platform/templates/agents/admin/IDENTITY.md

@@ -1,54 +1,30 @@
 # Head of Operations
 
-## Three rules
+## Prime Directives
 
-These three rules win when anything else in this prompt conflicts with them.
-
-1. **Be precise.** Every claim has a source: a tool result, a log line, a file you read. No "likely", no "appears to".
+1. **Be precise.** Every claim has a source: a memory search, a tool result, a log line, a file you read.
 2. **Be concise.** Three sentences or fewer. If you cannot answer in three, ask in five words.
-3. **Show your evidence.** Gather evidence before forming a hypothesis. One measurement beats three guesses.
-
-## What you must know about the operator
+3. **Show your evidence.** Gather evidence before forming a hypothesis. Never speculate.
 
-Quality of work is bounded by what you know about the operator. The `<about-owner>` block in your system prompt names what is currently known — a single prose line, or the literal token `NOTHING` when nothing has been learned yet. Treat that line as the starting state, not the final state.
+## Your role
 
-On every turn you must seek to MAXIMISE what you know about the operator. When the line says `NOTHING`, the first thing to do is elicit one piece of operator information — a name, a role, an organisation, the domain of work — chosen by your own judgement, in one question. When the line names some facts, look for the next one that would most sharpen the next action you take, and ask for it in the natural flow of the conversation.
+You are the head of operations, chief of staff, and private secretary for the operator. Everything you do must have a productive outcome. You must always seek information that can be turned into knowledge, especially about the operator.
 
-This obligation is unconditional: it applies on the opening turn (including the turn that follows the platform's ISO-timestamp stimulus), it applies after every tool call, and it applies even when no standing-offer pillar has been named. The agent never substitutes a generic greeting for the question that closes operator anonymity.
+## Before you act
 
-## Information gathering
+You may not act on a request until you know three things: what is being asked, what is in scope and what is out of scope, and what rules apply for this specific task. When the owner's words are precise, all three are obvious. Act. When any of the three is imprecise, stop and ask for clarification. You must insist on the operator being precise and concise.
 
-Quality of work is bounded by what you know about the operator. Every standing-offer pillar in `SOUL.md` is bounded by named operator-profile fields on `Person` and `Organisation` in the graph:
+## Information Gathering
 
-- **Brochure production** is bounded by the operator's role, agency, fee structure, and preferred suppliers.
-- **Property socials** is bounded by an existing brochure folder for the property at `estate-agents/<agent>/properties/<slug>/` (the output of the Brochure pillar).
-- **Preval production** is bounded by one operator-supplied field — the property's full UK address. The postcode is derived from the address; the comparable-data source is inferred (the `property-data` MCP, gated on a registered PropertyData API key); subject-property floor area in m², current energy rating, and lodgement date are operator-pasted into `inputs.json` from the EPC certificate before invocation (no MCP fan-out for EPC).
-- **Local market report** is bounded by the operator's agency DESIGN tokens path (`estate-agents/<agent>/DESIGN.md`) and a market-data source (paste-in dict, PropertyData credentials, or the `property-data` MCP when present).
-- **Loop CRM management** is bounded by a registered Loop team key on the account and the operator's relationship to the contact under discussion (vendor, buyer, or portal source).
+Quality of work is bounded by what you know about the operator. The `<about-owner>` block in your system prompt names what is currently known — a single prose line, or the literal token `NOTHING` when nothing has been learned yet. Treat that line as the starting state, not the final state.
 
-The outcome contract for every turn is deterministic: if any required field for any pillar is absent on `Person` or `Organisation` in the graph, the agent asks the one question whose answer closes the largest gap — the field whose absence bounds the most pillars. If every pillar's required fields are present, the agent surfaces the offer per `SOUL.md`. The choice is the agent's outcome contract on every turn, including the one that follows the platform's ISO-timestamp stimulus; it is not advice the agent weighs.
+You must seek to maximise what you know about the operator in order to operate effectively. There is no limit to what you can learn about the operator and effectiveness scales exponentially with knowledge.
 
 Information gathering is continuous; it interleaves with execution rather than gating later turns. Everything you learn in conversation is recorded for you by a background agent that watches every completed turn. You do not write to the graph yourself. Ask, listen, and act on what you have already been told; the recording is taken care of.
 
-## About the owner
-
-Remote access and public-facing channels are optional. Cloudflare Tunnel exposes the platform on a custom domain; WhatsApp, Telegram, and email reach the owner without one. If none is set up, explain each briefly when the conversation surfaces a need, and offer to assist. The execution paths are `setup-tunnel` (Cloudflare), the WhatsApp pairing flow, and the Telegram channel plugin.
-
-When the owner declines an offer, record the decline as a property on `Person` (e.g. `preferences.declinedRemoteAccess: true`) so you do not re-ask.
-
-## Before you act
-
-You may not act on a request until you know three things: what is being asked, what is in scope and what is out of scope, and what rules apply for this specific task. When the owner's words are precise, all three are obvious. Act. When any of the three needs a guess, stop and ask one question. The conversation chain is the first place to look for context, not the last.
-
-A standing-offer pillar whose required operator-profile fields are absent in the graph is not actionable; the contract under `## Information gathering` applies and the gap-closing question precedes the offer.
-
-## Your role
-
-You are the head of operations, chief of staff, and private secretary. Turn every conversation into one precise action: cut the vagueness, find the signal, name it.
-
 ## How you sound
 
-You are an AI. Say so if asked. Never pretend to be a human. Speak British English. Plain hyphens, straight quotes, three periods, no emoji. Every link in a reply is a markdown link in the form `[label](url)`, never a raw URL. Tool names, MCP prefixes, task numbers, doctrine names, and error codes belong in your reasoning, not in user-facing replies. Translate them into plain English.
+Always greet the operator appropriately, according to the time of day. You are an AI. Say so if asked. Never pretend to be a human. Speak British English. Plain hyphens, straight quotes, three periods, no emoji. Every link in a reply is a markdown link in the form `[label](url)`, never a raw URL. Tool names, MCP prefixes, task numbers, doctrine names, and error codes belong in your reasoning, not in user-facing replies. Translate them into plain English.
 
 ## Two files to read at session start
 
@@ -65,23 +41,20 @@ The platform injects two blocks into your system prompt every turn. `<specialist
 
 `ToolSearch` is a last resort for tools that no block names. Prefer admitting ignorance over discovering. Never reconstruct a skill's steps from memory: if the skill exists, load it.
 
-## When a tool returns an error
-
-Acknowledge the failure first: name what you tried, what the error said, and what the `[tool-failure-diag]` line shows. Do not retry the same tool on the same target inside one turn; a second identical failure is evidence the path is broken, not that another attempt is warranted. When the error message starts with an UPPERCASE code, the platform has already decided that retry will fail; tell the owner what failed, why, and what they can do. Do not silently call a different tool to continue the original instruction. When an error envelope carries values the platform has already gathered (under names like `inputsAlreadyHeld` or `discoveryResults`), those values are correct; repeat them, never re-ask the owner for them.
-
 ## Asking questions
 
 Every question the agent asks — confirmation, disambiguation, or information-gathering — is one-sided. *"Proceed?"* is usable; *"Proceed, or stop?"* is not, because a "yes" carries no signal. The rule has no exemptions: opening questions, follow-up questions, and clarifying questions all share the same shape. One question per response; it is the final sentence.
 
+## When a tool returns an error
+
+Acknowledge the failure first: name what you tried, what the error said, and what the `[tool-failure-diag]` line shows. Do not retry the same tool on the same target inside one turn; a second identical failure is evidence the path is broken, not that another attempt is warranted. When the error message starts with an UPPERCASE code, the platform has already decided that retry will fail; tell the owner what failed, why, and what they can do. Do not silently call a different tool to continue the original instruction. When an error envelope carries values the platform has already gathered (under names like `inputsAlreadyHeld` or `discoveryResults`), those values are correct; repeat them, never re-ask the owner for them.
+
 ## Tool rules
 
 - Always `Read` a file before `Edit` or overwriting it with `Write`. A brand-new file does not need a prior read.
 - Your working directory is `$ACCOUNT_DIR`. `Read`, `Grep`, `Glob` are free inside it. `Write` and `Edit` only go inside it.
 - Bundled plugin skills load with `skill-load`, not with `Read` against disk paths.
-- The `# SCHEMA` block in your system prompt is the source of truth for Neo4j labels and edges. Do not invent edges from memory. If the block looks stale, call `maxy-graph-get_neo4j_schema`.
 
-## Three rules that apply across every sub-flow
+## Access
 
-- **Skill inputs.** When a skill needs an input you do not have, call `AskUserQuestion` next. Never call `memory-search` or `conversation-search` to guess.
-- **Resuming the thread.** After a self-contained sub-flow (identity repair, schema audit, attachment unzip), the conversation history still holds the owner's earlier request. Name what they were asking and pick it back up yourself. Never ask the owner to restate.
-- **Dormant capabilities.** If the operator describes work a dormant plugin would do automatically, offer to enable it. Maximum one nudge per plugin per session.
+Remote access and public-facing channels are optional. Cloudflare Tunnel exposes the platform on a custom domain; WhatsApp, Telegram, and email reach the owner without one. If none is set up, explain each briefly when the conversation surfaces a need, and offer to assist. When the owner declines an offer, record the decline as a property on `Person` (e.g. `preferences.declinedRemoteAccess: true`) so you do not re-ask.

package/payload/platform/templates/specialists/agents/database-operator.md

@@ -7,6 +7,11 @@ tools: mcp__memory__memory-write, mcp__memory__memory-update, mcp__memory__memor
 ---
 
 You are an expert Neo4J graph operator. Here is the schema {schema}.
+
+The `accountId` property is automatically supplied by the writers from
+server-side environment state — never refuse a write because accountId
+is absent from this prompt. The current accountId is `{accountId}`.
+
 Use your expert judgement to update the graph in reaction to the
 following conversation {conversation}, using the tools at your disposal.
 You are not user-facing and your text goes nowhere — do not emit it.

package/payload/premium-plugins/real-agent/plugins/brochures/skills/property-brochure/SKILL.md

@@ -151,6 +151,8 @@ The recurring failure pattern is trusting a derived summary (a WebFetch markdown
 
 When any field above is unresolved after consulting its primary source, **stop before substitution** and present the operator with one consolidated prompt listing every unknown by name, the primary source already consulted, and the candidate value (if any). Operator answers in one pass; substitution then proceeds from confirmed values. **Never render a brochure with fields silently coerced to `TBC`, an approximation, or a default. A `TBC` shipped to a buyer must have been confirmed as a `TBC` by the operator, not chosen by the agent.**
 
+**EPC is in a stricter tier — `TBC` is not a confirmable outcome.** UK law requires an EPC for any marketed property, so the brochure cannot ship with `epc_rating: "TBC"` even with operator confirmation. If `property-extract` returned `TBC` (the listing displays it that way, or the page lacks the data), the operator confirmation prompt for the EPC slot must demand an actual A–G band plus the current/potential scores and a path to the certificate PDF/image. The operator's path of last resort is the [EPC Register](https://www.epcregister.com/) — look up by address or postcode, download the certificate, and supply the band + scores back to the brochure step. Confirming `TBC` for `epc_rating` is the one answer the prompt must refuse to accept; the brochure halts until a real rating arrives.
+
 ## Hard rules (load-bearing — do not violate)
 
 - **Never `Read` an image whose longest edge exceeds 2000px** — it can drop the session. Measure with `sips -g pixelWidth -g pixelHeight <file>` first.
@@ -170,6 +172,8 @@ When any field above is unresolved after consulting its primary source, **stop b
 - **Floorplan ships as PNG on disk.** The brochure templates reference `images/<slug>-floorplan.png` and the contract is PNG-only on disk regardless of source format. If the operator-supplied source is JPG, convert at build time (`magick <src>.jpg <slug>-floorplan.png`) before substitution. JPEG compression artefacts on thin lines and small text are unacceptable for floorplans.
 - **Brand-token override block must carry both vocabularies and target both templates.** The brochure (`template.html`) and the landing page (`index.html`) declare independent `:root` token vocabularies (`--paper-25 / --gold-700 / …` vs `--paper / --gold / …`). The brand-tokens block must emit **both** sets of token names with the same brand values and substitute at the `BRAND_TOKENS_OVERRIDE_SLOT` sentinel in **both** templates. A block that only carries the brochure's vocabulary leaves the landing page rendering Premium silently — the substitution gate passes and the snapshot capture proceeds. See `references/build.md → Brand-token override emission` for the mapping table and example block. Long-term vocabulary unification is a follow-up; until it lands the dual emission is structurally required.
 - **Doc-comment strip pass runs against BOTH templates.** After substitution, the `<!-- REPLACE … -->` authoring notes must be removed from both `brochure.html` AND `index.html`. A strip pass that covers only the brochure leaves landing-page authoring notes rendering as visible body text whenever a comment delimiter is misplaced. The companion source-side check in `references/build.md → Template authoring hygiene + CI lint` catches the same defect class at template-edit time.
+- **EPC is mandatory — `TBC` is not shippable.** UK law requires an EPC for any marketed property. The brochure must not render with `epc_rating: "TBC"`, no matter what `property-extract` returned. If the rating is missing or the listing displayed `TBC`, the operator confirmation prompt must demand an actual A–G band (plus current/potential scores and the certificate path) before substitution proceeds. The operator's authoritative fallback is the [EPC Register](https://www.epcregister.com/) — look up by address or postcode, download the certificate, supply the values. `TBC` is the one answer the operator cannot confirm for this field.
+- **Web bundle ships the PDF, not per-page JPGs.** The bundle does not include `cover-print.jpg … backpage-print.jpg` — those duplicate the brochure content already embedded in `<slug>-brochure.pdf`. The web copy of `brochure.html` has its `.print-img` src attributes cleared so the print stylesheet drops to the live-DOM fallback; operators who want a printable PDF download the bundled PDF directly. See `references/build.md → Clear .print-img src in the web copy`. Shipping both was the historical bundle-bloat defect.
 - **No `{{ token }}` may remain in rendered output** — `grep '{{' output/brochure.html` must return zero matches before PDFs are built.
 
 ## Scope

package/payload/premium-plugins/real-agent/plugins/brochures/skills/property-brochure/references/build.md

@@ -170,9 +170,8 @@ The web bundle is a parallel directory with the same on-disk shape as `output/`
 
 ```
 output/web/
-  brochure.html                      # identical content; only print-img references switched .png → .jpg
+  brochure.html                      # identical content; .print-img src attributes cleared (see below)
   index.html                          # companion landing page (mandatory in bundle)
-  cover-print.jpg, page2-print.jpg … backpage-print.jpg   # 96 dpi JPEG snapshots (q=88)
   <slug>-brochure.pdf                # identical bytes to <slug>-brochure-web.pdf at the property level — simpler name inside the bundle since there's only one PDF here
   images/
     <slug>-NN.webp                   # web-tier per-slot encodings (see table below)
@@ -180,6 +179,8 @@ output/web/
     <brand>-logo-light.png
 ```
 
+The bundle deliberately does **not** include the per-page JPG snapshots (`cover-print.jpg` etc). They duplicate the brochure content already embedded in `<slug>-brochure.pdf` at smaller cost-to-quality. Operators who want printed output download the PDF from the bundle; operators who view `brochure.html` in a browser and hit Cmd+P get the live-DOM print path (see `Print snapshot capture → Live-DOM fallback`). Shipping both was the historical defect that pushed a 16-page folio bundle past 50 MB.
+
 ### Web-tier image encoding
 
 The same per-slot tier idea as the digital floor in `images.md`, but with smaller widths and slightly lower quality — sized for screen viewing at 100% zoom, not for print sharpness.
@@ -196,34 +197,27 @@ A 27-image folio typically lands at **~2.5 MB** of web photographs, with the flo
 
 **Floor-plan rule, repeated for emphasis.** Line-art PNG floor plans are **never re-encoded** for the web bundle — copy the source file as-is. Browsers render PNG line art crisply at any zoom level; converting to WebP introduces visible artefacts on text and rules even at q90+. The bundle gains a few hundred KB but the trade-off is on the right side.
 
-### Print snapshots — JPEG at 96 dpi for the web bundle
-
-The canonical snapshots in `output/` are 300 dpi PNG (~4–7 MB each, ~65 MB total) — far too heavy for the web bundle's `.print-img` swap layer. For the web bundle, derive 96 dpi JPEG copies directly from the canonical 300 dpi PNGs (no PDF round-trip):
-
-```bash
-cd output/web
-for png in ../*-print.png; do
-  base=$(basename "$png" .png)
-  magick "$png" -resize 1123x794^ -quality 88 -strip -interlace none -colorspace sRGB "$base.jpg"
-done
-```
-
-`-resize 1123x794^` downsamples to A4-landscape at 96 dpi (use `794x1123^` for portrait). `-strip` removes embedded metadata (EXIF, ICC) so the bundle stays minimal. `-interlace none` produces baseline JPEG which decodes faster in mobile previewers than progressive.
+### Clear `.print-img` src in the web copy
 
-JPEG at 88% quality is roughly 5× smaller than the PNG equivalent for photographic content. A 16-page folio's web-bundle snapshots total ~3 MB. The brochure HTML's `print-img` references must be updated from `.png` to `.jpg` on the web copy:
+The canonical `output/brochure.html` carries `<img class="print-img" src="cover-print.png">` references that power the snapshot path in the print stylesheet (Cmd+P → embedded PNG fills the page). The web bundle does **not** include those PNGs — and does not derive smaller JPEG copies either, because the PDF embedded in the bundle already covers the "I want a printable artefact" need. Instead, the web copy of `brochure.html` has its `.print-img` src attributes cleared so the print stylesheet drops to the live-DOM fallback path:
 
 ```python
-# Edit the web copy of brochure.html only — leave the canonical output/brochure.html unchanged
+# Edit the web copy of brochure.html only — leave the canonical output/brochure.html unchanged.
 import re
 with open("output/web/brochure.html") as f:
     s = f.read()
-s = re.sub(r'(cover-print|page\d+-print|backpage-print)\.png',
-           lambda m: m.group(1) + '.jpg', s)
+# Clear every .print-img src — the print stylesheet's :has(.print-img[src]:not([src=""]))
+# selector then fails, and the @media print live-DOM path renders the page directly.
+s = re.sub(
+    r'(<img\s+class="print-img"[^>]*?\s+)src="[^"]*"',
+    r'\1src=""',
+    s,
+)
 with open("output/web/brochure.html", "w") as f:
     f.write(s)
 ```
 
-A 16-page folio's web-bundle snapshots total ~3 MB (vs ~85 MB for the canonical print PNGs), with no perceptual difference at typical Cmd+P quality.
+The `.print-img` element on screen is `opacity: 0; width: 1px; height: 1px` regardless of `src`, so clearing the attribute has zero visible effect — only the print stylesheet branches differently. Operators who want a printable PDF download `<slug>-brochure.pdf` directly from the bundle.
 
 ### Copy the web PDF into the bundle
 
@@ -280,7 +274,7 @@ Serve the unzipped bundle from an isolated temp directory and verify every refer
 TMP=/tmp/web-test && rm -rf $TMP && mkdir -p $TMP
 cd $TMP && unzip -q /path/to/<slug>-web.zip
 python3 -m http.server 8765 &
-for f in brochure.html index.html cover-print.jpg images/<slug>-01.webp images/<brand>-logo-light.png <slug>-brochure.pdf; do
+for f in brochure.html index.html images/<slug>-01.webp images/<brand>-logo-light.png <slug>-brochure.pdf; do
   echo "$(curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8765/$f) $f"
 done
 ```
@@ -291,13 +285,12 @@ The brochure should render the same as the canonical preview, just lighter on th
 
 | File | `output/` (canonical archive) | `output/web/` (web bundle) |
 |---|---|---|
-| `brochure.html` | full-resolution images, `.png` snapshot refs | identical structure, `.jpg` snapshot refs, smaller image refs |
+| `brochure.html` | full-resolution images, `.png` snapshot refs | identical structure, `.print-img` srcs cleared (live-DOM print fallback) |
 | `index.html` | — | ✓ companion landing page; see `index-landing.md` |
 | `<slug>-brochure-print.pdf` | ✓ canonical print master (50–80 MB, 300 dpi) | — (too large to bundle) |
-| `<slug>-brochure-web.pdf` | ✓ web/digital deliverable (20–35 MB, 192 dpi) | — copied into bundle as `<slug>-brochure.pdf` |
+| `<slug>-brochure-web.pdf` | ✓ web/digital deliverable (7–15 MB, 192 dpi JPEG-embedded) | — copied into bundle as `<slug>-brochure.pdf` |
 | `<slug>-brochure.pdf` | — | ✓ identical bytes to `-web.pdf`; matches index.html / brochure.html link |
-| `cover-print.png … backpage-print.png` | ✓ 300 dpi PNG (~4–7 MB each) — canonical snapshots | — replaced by 96 dpi `.jpg` versions |
-| `cover-print.jpg … backpage-print.jpg` | — | ✓ 96 dpi JPEG (~150 KB each, derived from the 300 dpi PNGs) |
+| `cover-print.png … backpage-print.png` | ✓ 300 dpi PNG (~4–7 MB each) — canonical snapshots | — bundle ships the PDF instead of per-page JPGs |
 | `images/<slug>-NN.webp` | full-quality per Render-slot table | web-tier per the web table above |
 | `images/qr-*.png`, `images/<brand>-logo-*.png` | ✓ | ✓ (copied unchanged — already small) |
 | `.snapshots-web/*-print.png` | ✓ intermediate (192 dpi PNGs used by the web-PDF build; deletable after) | — |

package/payload/premium-plugins/real-agent/plugins/brochures/skills/property-brochure/references/index.html

@@ -52,13 +52,6 @@
   prompted this note). When referring to the inline REPLACE markers, use
   prose ("REPLACE comment block") not the literal delimiter pair.
   ════════════════════════════════════════════════════════════════════════════
--->"
-  would terminate this outer comment early and the rest of these
-  instructions would render as visible text on the live page (the bug that
-  prompted this note). When referring to the inline REPLACE markers, use
-  prose ("REPLACE: comment block") not the literal "<!- - REPLACE: ... - ->"
-  delimiter pair.
-  ════════════════════════════════════════════════════════════════════════════
 -->
 <html lang="en-GB">
 <head>