@rubytech/create-maxy-code 0.1.17 → 0.1.19

package/payload/premium-plugins/real-agency/plugins/brochures/skills/property-brochure/references/{page-landing.md → index-landing.md}

@@ -1,12 +1,12 @@
-# Page — companion property landing page (`page.html`)
+# Page — companion property landing page (`index.html`)
 
-The web bundle includes a **single-page property landing site** at `output/web/page.html`. The brochure is a folio for download; the landing page is the "for sale" web page a property micro-site or a portal page links to. They share the same web-tier images in `images/` but present the property differently — the brochure as an editorial document; the landing page as a continuous, scrollable web page.
+The web bundle includes a **single-page property landing site** at `output/web/index.html`. The brochure is a folio for download; the landing page is the "for sale" web page a property micro-site or a portal page links to. They share the same web-tier images in `images/` but present the property differently — the brochure as an editorial document; the landing page as a continuous, scrollable web page.
 
-The landing page is **mandatory in the web bundle**. A property-brochure run that ships the brochure web bundle without `page.html` is incomplete.
+The landing page is **mandatory in the web bundle**. A property-brochure run that ships the brochure web bundle without `index.html` is incomplete.
 
-## Canonical reference — `references/page.html` is the only starting point
+## Canonical reference — `references/index.html` is the only starting point
 
-`references/page.html` ships with this skill alongside `references/template.html`. It is the **only** acceptable starting point for the landing page, exactly as `template.html` is the only acceptable starting point for the brochure. Every property-brochure run that produces a web bundle MUST start by copying `references/page.html` to `<property_dir>/output/web/page.html` and substituting the markers — never re-build the file from scratch from the prose in this reference.
+`references/index.html` ships with this skill alongside `references/template.html`. It is the **only** acceptable starting point for the landing page, exactly as `template.html` is the only acceptable starting point for the brochure. Every property-brochure run that produces a web bundle MUST start by copying `references/index.html` to `<property_dir>/output/web/index.html` and substituting the markers — never re-build the file from scratch from the prose in this reference.
 
 The subsections below describe **why** the canonical is the way it is. They are **not** instructions to rebuild it. If the canonical file already encodes a rule (e.g. drop cap on the first paragraph of every body-block, the 3-slide Ken-Burns rotator with reduced-motion fallback, the hamburger drawer with full nav set on mobile), copying the canonical IS following the rule. The reference file's leading comment block lists the editorial decisions baked in — read it once before any substitution.
 
@@ -14,12 +14,12 @@ The subsections below describe **why** the canonical is the way it is. They are
 
 Per the same logic as the brochure's *Forbidden template sources*, do **not** start the landing page from any of:
 
-- A sibling property's rendered `output/web/page.html` (will inherit that property's hand-tuned text + image refs)
-- A previous version of `references/page.html` cached anywhere outside the live skill folder
+- A sibling property's rendered `output/web/index.html` (will inherit that property's hand-tuned text + image refs)
+- A previous version of `references/index.html` cached anywhere outside the live skill folder
 - The prose alone, hand-copying CSS/markup blocks from the section descriptions below
 - A "modern landing page generator" or any tool that produces a layout from scratch
 
-A run that reconstructs page.html from prose, even if the result *looks* close to the canonical, drifts every brochure cycle. The dropcap, the rotator timing, the `BRAND-SLUG-logo-dark.png` filename pattern, the sub-nav scroll behaviour, the drawer markup — all of it lives literally in `references/page.html`. Copy it.
+A run that reconstructs index.html from prose, even if the result *looks* close to the canonical, drifts every brochure cycle. The dropcap, the rotator timing, the `BRAND-SLUG-logo-dark.png` filename pattern, the sub-nav scroll behaviour, the drawer markup — all of it lives literally in `references/index.html`. Copy it.
 
 ## How to populate
 
@@ -27,7 +27,7 @@ Two steps:
 
 1. **Bulk-substitute literal placeholders** (one find/replace pass each):
    - `PROPERTY-SLUG` → property slug (e.g. `warblers-lodge`). Rewrites every image src (`PROPERTY-SLUG-NN.webp`, `PROPERTY-SLUG-floorplan.png`, `PROPERTY-SLUG-hero-N-<role>.webp`) and the in-bundle PDF link (`PROPERTY-SLUG-brochure.pdf`).
-   - `BRAND-SLUG` → brand slug (e.g. `rossmargetts`). Rewrites the brand logo path (`BRAND-SLUG-logo-dark.png` — the dark-art variant on the warm-paper top nav). The page.html canonical only uses the dark variant; the light variant is brochure-only.
+   - `BRAND-SLUG` → brand slug (e.g. `rossmargetts`). Rewrites the brand logo path (`BRAND-SLUG-logo-dark.png` — the dark-art variant on the warm-paper top nav). The index.html canonical only uses the dark variant; the light variant is brochure-only.
 
 2. **Substitute each `<!-- REPLACE: ... -->` block** with property-specific copy drawn from the seller brief and `property.json`. Walk the file top-to-bottom: `<title>`, meta description, top-nav utility links, drawer nav + foot, sticky sub-nav left/right, hero info-card (tag, title, address, price, meta, four spec cells, three link slots, CTA mailto subject), three hero slides + alt text, six body-block sections (Story, The Home, Bedrooms, The Garden, The Area — eyebrow + h2 + paragraphs), six photo grids (four cells each, 4:3 cover), floor-plan section meta, key-facts grid (~15 rows), CTA strip, footer.
 
@@ -77,7 +77,7 @@ If the property has no kitchen/garden distinction (e.g. an apartment), substitut
 
 The hero shows each image **fullscreen at viewport scale**, with a 1.05–1.20× Ken-Burns transform on top. That means a body-tier 1300 px @ q82 webp will visibly soften at typical desktop and Retina viewports. The hero needs its own encode tier:
 
-| Setting | Body tier (rest of `page.html`) | **Hero tier** |
+| Setting | Body tier (rest of `index.html`) | **Hero tier** |
 |---|---|---|
 | Long edge | 1300 px (hero) / 1100 px (story) / 800 px (thumb) | **source resolution** (no `-resize`) — typically 1536–1600 px |
 | Quality | q82 / q80 / q76 | **q88** |
@@ -198,7 +198,7 @@ Some viewers find subtle continuous motion uncomfortable. The `@media (prefers-r
 The page has two image tiers:
 
 1. **Hero rotator** — three dedicated `<slug>-hero-1-main.webp`, `<slug>-hero-2-<role>.webp`, `<slug>-hero-3-<role>.webp` files at source resolution and q88. See **Hero — rotating Ken-Burns stage** above. These are *additional* files; they don't replace the body-tier images even when sourced from the same originals — the body-tier `<slug>-03.webp` is still used in the photo grids.
-2. **Body photo grids** — `<slug>-NN.webp` at the body-tier (1300/1100/800 px @ q82/80/76) — the same images the brochure HTML references. Both `brochure.html` and `page.html` resolve them to the same file under `output/web/images/`.
+2. **Body photo grids** — `<slug>-NN.webp` at the body-tier (1300/1100/800 px @ q82/80/76) — the same images the brochure HTML references. Both `brochure.html` and `index.html` resolve them to the same file under `output/web/images/`.
 
 Distribute every brochure image across the photo grids — typically 24–28 unique images across 6 grids of 4. If the count doesn't divide cleanly (e.g. 23 images for 6 grids of 4 = 24 cells), reuse the cover hero in the final cell as a closing visual.
 
@@ -361,10 +361,10 @@ When testing at mobile widths, screenshot at three viewports: **390 × 844** (iP
 
 ## Bundling and smoke-test
 
-`page.html` is included in `<slug>-web.zip` automatically (the zip command zips everything in `output/web/`). After zipping, the smoke-test must include both `brochure.html` AND `page.html`:
+`index.html` is included in `<slug>-web.zip` automatically (the zip command zips everything in `output/web/`). After zipping, the smoke-test must include both `brochure.html` AND `index.html`:
 
 ```bash
-for f in brochure.html page.html cover-print.jpg images/<slug>-01.webp images/<brand>-logo-dark.png <slug>-brochure.pdf; do
+for f in brochure.html index.html cover-print.jpg images/<slug>-01.webp images/<brand>-logo-dark.png <slug>-brochure.pdf; do
   echo "$(curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8765/$f) $f"
 done
 ```
@@ -373,4 +373,4 @@ Both pages must return 200 and render correctly. The landing page should not exh
 
 ## When to regenerate
 
-`page.html` is regenerated whenever the brochure's image set changes (new photos, swapped slot assignments) or whenever the brochure's chapter copy materially changes (the landing page mirrors the brochure's narrative). Cosmetic CSS-only changes to the brochure don't require a landing-page regenerate. The landing page is *not* part of the canonical print archive — it lives only in `output/web/` and the zip.
+`index.html` is regenerated whenever the brochure's image set changes (new photos, swapped slot assignments) or whenever the brochure's chapter copy materially changes (the landing page mirrors the brochure's narrative). Cosmetic CSS-only changes to the brochure don't require a landing-page regenerate. The landing page is *not* part of the canonical print archive — it lives only in `output/web/` and the zip.

package/payload/premium-plugins/real-agency/plugins/brochures/skills/property-brochure/references/{page.html → index.html}

@@ -1,6 +1,6 @@
 <!--
   ════════════════════════════════════════════════════════════════════════════
-  COMPANION LANDING PAGE — page.html · canonical reference template
+  COMPANION LANDING PAGE — index.html · canonical reference template
   ════════════════════════════════════════════════════════════════════════════
 
   This file is the canonical starting point for the property micro-site that
@@ -13,7 +13,7 @@
   ─────────────────────
   Every property-specific value in this file is a {{ token }} placeholder.
   There is no exemplar copy left to accidentally inherit. After substitution,
-  `grep "{{" output/web/page.html` must return ZERO matches — any remaining
+  `grep "{{" output/web/index.html` must return ZERO matches — any remaining
   {{ x }} is a bug.
 
   The full token list (with source field, format, length, voice) lives in
@@ -23,7 +23,7 @@
 
   Contract:
 
-  1. Copy this file to <property>/output/web/page.html.
+  1. Copy this file to <property>/output/web/index.html.
   2. Substitute every {{ placeholder }} token from the master placeholders.md.
   3. Update <title>, meta description, OG/Twitter image refs.
   4. If a section does not apply (e.g. property has no garden complex), follow
@@ -40,7 +40,7 @@
     - Mobile collapse: top-nav → hamburger drawer at ≤960px; hero stacks at
       ≤760px; hero aspect 5/4 at ≤440px.
     - Type system: Cormorant Garamond (display) + Lora (body serif) + Inter
-      (UI labels). DO NOT swap these per-brand — the page.html register is
+      (UI labels). DO NOT swap these per-brand — the index.html register is
       tuned to the canonical premium tier; brand identity lives in the logo,
       copy and brand-specific colour accents that may be added via :root
       overrides if needed (rare).

package/payload/premium-plugins/real-agency/plugins/brochures/skills/property-brochure/references/placeholders.md

@@ -1,6 +1,6 @@
 # Placeholders — the substitution contract
 
-`template.html` and `page.html` are pure placeholder templates: every property-specific value is a `{{ token }}` token. There is no exemplar copy left to accidentally inherit. After rendering, `grep "{{" output/brochure.html` (and `output/web/page.html`) MUST return **zero matches**. Any remaining `{{ x }}` is a substitution bug.
+`template.html` and `index.html` are pure placeholder templates: every property-specific value is a `{{ token }}` token. There is no exemplar copy left to accidentally inherit. After rendering, `grep "{{" output/brochure.html` (and `output/web/index.html`) MUST return **zero matches**. Any remaining `{{ x }}` is a substitution bug.
 
 This file is the substitution contract — the exhaustive list of every token used across both templates, what fills it, what format it takes, and what voice the copy tokens need. Style and composition guidance lives in `copy.md` (and is referenced inline from each `<!-- REPLACE: ... -->` comment in the templates). The two files are complementary: this one says **what** each token is; `copy.md` says **how** the copy should read.
 
@@ -11,7 +11,7 @@ Worked examples below quote the validated Sparrows Farm reference brochure at `/
 1. Open the seller brief at `<property_dir>/seller-brief.md` and `<property_dir>/property.json` side-by-side.
 2. Walk the categories below top-to-bottom — common tokens first (identity, brand, agent, listing, specs), then chapter-by-chapter editorial copy.
 3. For each token, write the substitution into a single dict / map keyed by token name. The substitution step at the end of `property-brochure` reads the map and rewrites both files in one pass.
-4. Run the **completion check**: `grep -c "{{" output/brochure.html output/web/page.html`. Both files must return `0`. If any token is unsubstituted, it is a defect — the brochure is not shippable until every `{{ x }}` is gone.
+4. Run the **completion check**: `grep -c "{{" output/brochure.html output/web/index.html`. Both files must return `0`. If any token is unsubstituted, it is a defect — the brochure is not shippable until every `{{ x }}` is gone.
 
 ## Category 1 — Property identity
 
@@ -46,7 +46,7 @@ From the brand pack at `<brand_dir>/{description.md, DESIGN.md}` and `property.j
 | `{{ brand_name }}` | `description.md` first line | Title Case | "Muvin", "Beacons Real Estate". |
 | `{{ brand_town }}` | `description.md` officials block | Title Case | Branch town. |
 | `{{ brand_county }}` | `description.md` officials block | Title Case | |
-| `{{ brand_year }}` | Current year | YYYY | Used in the page.html footer copyright. |
+| `{{ brand_year }}` | Current year | YYYY | Used in the index.html footer copyright. |
 | `{{ office_address_line_1 }}` | `description.md` registered office line | "25 Bell Street" | Street, first line of the postal address. |
 | `{{ office_address_line_2 }}` | `description.md` registered office line | "Sawbridgeworth, Hertfordshire CM21 9AR" | Locality + county + postcode. |
 | `{{ office_phone }}` | `property.json -> agent.phone` | Display format | "01873 377 575". |
@@ -208,7 +208,7 @@ Every `{{ mi_* }}` token corresponds to a Material Information row. Mark unknown
 | `{{ backpage_headline }}` | "Arrange a viewing of <em>{{ property_name }}</em>" — canonical phrasing. |
 | `{{ backpage_tagline }}` | 25-45 words. Mirrors but does not duplicate the cover/opener. Close with "Best understood in person." or equivalent clincher. |
 
-## Category 9 — page.html (landing) editorial copy
+## Category 9 — index.html (landing) editorial copy
 
 The landing page mirrors the brochure's content but in a continuous-scroll form. Tokens are prefixed `landing_*` to avoid name collisions with the brochure tokens. Sections:
 
@@ -235,7 +235,7 @@ The substitution step that runs `property-brochure` should end with this verific
 
 ```bash
 PROP=<property_dir>
-remaining=$(grep -c '{{' "$PROP/output/brochure.html" "$PROP/output/web/page.html" 2>/dev/null | awk -F: '{s+=$2} END {print s}')
+remaining=$(grep -c '{{' "$PROP/output/brochure.html" "$PROP/output/web/index.html" 2>/dev/null | awk -F: '{s+=$2} END {print s}')
 if [ "$remaining" -gt 0 ]; then
   echo "DEFECT: $remaining unsubstituted {{ tokens }} remain — see grep '{{' output/"
   exit 1
@@ -247,4 +247,4 @@ A brochure with any `{{ x }}` remaining in the rendered output is shipped broken
 
 ## Adding a new token
 
-If a property has a feature the canonical placeholder set doesn't cover (e.g. an annexe with separate utility, a wine cellar, a moat — they exist), do not invent a new token in the templates without also adding the entry here. The substitution contract is what catches the bug; an unlisted token gets silently ignored by the substitution step and the brochure ships with `{{ wine_cellar }}` literal in the body. Either reuse an existing token, or add the new one to this file AND to template.html/page.html before rendering.
+If a property has a feature the canonical placeholder set doesn't cover (e.g. an annexe with separate utility, a wine cellar, a moat — they exist), do not invent a new token in the templates without also adding the entry here. The substitution contract is what catches the bug; an unlisted token gets silently ignored by the substitution step and the brochure ships with `{{ wine_cellar }}` literal in the body. Either reuse an existing token, or add the new one to this file AND to template.html/index.html before rendering.

package/payload/server/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "maxy-server-deps",
+  "name": "maxy-code-server-deps",
   "private": true,
   "type": "module",
   "dependencies": {

package/payload/server/public/assets/{Checkbox-nrf4ISU0.js → Checkbox-BmlrSRF8.js}

@@ -1 +1 @@
-import{t as e}from"./jsx-runtime-Bz7aoCi7.js";var t=e();function n({checked:e,onChange:n,label:r,disabled:i}){return(0,t.jsxs)(`label`,{className:`maxy-checkbox${i?` maxy-checkbox--disabled`:``}`,children:[(0,t.jsx)(`input`,{type:`checkbox`,checked:e,onChange:e=>n(e.target.checked),disabled:i}),(0,t.jsx)(`span`,{className:`maxy-checkbox__box`,children:`✱`}),r&&(0,t.jsx)(`span`,{className:`maxy-checkbox__label`,children:r})]})}export{n as t};
+import{t as e}from"./jsx-runtime-BSJRynxp.js";var t=e();function n({checked:e,onChange:n,label:r,disabled:i}){return(0,t.jsxs)(`label`,{className:`maxy-checkbox${i?` maxy-checkbox--disabled`:``}`,children:[(0,t.jsx)(`input`,{type:`checkbox`,checked:e,onChange:e=>n(e.target.checked),disabled:i}),(0,t.jsx)(`span`,{className:`maxy-checkbox__box`,children:`✱`}),r&&(0,t.jsx)(`span`,{className:`maxy-checkbox__label`,children:r})]})}export{n as t};