@rubytech/create-maxy-code 0.1.18 → 0.1.20

package/dist/__tests__/cdp-port-no-silent-fallback.test.js

@@ -2,7 +2,7 @@
 // silent-fallback-masks-root-cause violation. The four runtime sites that
 // previously substituted `9222 + offset` for a missing brand.json.cdpPort
 // (paths.ts, admin/mcp/index.ts, vnc.sh, test-laptop-vnc-boot.sh) plus the
-// installer-side brand stamp at packages/create-maxy/src/index.ts have all
+// installer-side brand stamp at packages/create-maxy-code/src/index.ts have all
 // been swept to loud-fail. This test asserts the three greps from criterion
 // 2 of the task brief return zero matches; reintroducing any silent fallback
 // fails CI immediately.
@@ -19,7 +19,7 @@ import { resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 const SELF_DIR = fileURLToPath(new URL(".", import.meta.url));
 // dist/__tests__/ → repo root is four levels up
-// (packages/create-maxy/dist/__tests__ → packages/create-maxy → packages → repo).
+// (packages/create-maxy-code/dist/__tests__ → packages/create-maxy-code → packages → repo).
 const REPO_ROOT = resolve(SELF_DIR, "..", "..", "..", "..");
 function grepReturns(pattern, includes) {
     const args = ["-RnE", pattern];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-code",
-  "version": "0.1.18",
+  "version": "0.1.20",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy-code": "./dist/index.js"
@@ -17,7 +17,7 @@
     "payload"
   ],
   "keywords": [
-    "maxy",
+    "maxy-code",
     "ai",
     "assistant",
     "raspberry-pi",

package/payload/platform/config/brand-registry.json

@@ -1,16 +1,16 @@
 {
   "brands": [
     {
-      "hostname": "maxy",
-      "configDir": ".maxy",
+      "hostname": "maxy-code",
+      "configDir": ".maxy-code",
       "vncDisplay": 99,
       "rfbPort": 5900,
       "websockifyPort": 6080,
       "cdpPort": 9222
     },
     {
-      "hostname": "realagent",
-      "configDir": ".realagent",
+      "hostname": "realagent-code",
+      "configDir": ".realagent-code",
       "vncDisplay": 100,
       "rfbPort": 5901,
       "websockifyPort": 6081,

package/payload/platform/config/brand.json

@@ -1,9 +1,9 @@
 {
   "productName": "Maxy",
-  "hostname": "maxy",
-  "serviceName": "maxy.service",
-  "installDir": "maxy",
-  "configDir": ".maxy",
+  "hostname": "maxy-code",
+  "serviceName": "maxy-code.service",
+  "installDir": "maxy-code",
+  "configDir": ".maxy-code",
   "tagline": "AI for Productive People",
   "strapline": "Convenience as standard.",
   "domain": "getmaxy.com",

package/payload/platform/plugins/cloudflare/scripts/reset-tunnel.sh

@@ -28,7 +28,7 @@ set -euo pipefail
 
 # shellcheck source=_stream-log.sh
 # Resolve symlinks before dirname — ~/reset-tunnel.sh is installed as a symlink
-# (see packages/create-maxy/src/index.ts:installTunnelScripts), so the raw
+# (see packages/create-maxy-code/src/index.ts:installTunnelScripts), so the raw
 # BASH_SOURCE[0] points at $HOME, not the scripts directory where _stream-log.sh lives.
 source "$(dirname "$(readlink -f "${BASH_SOURCE[0]}")")/_stream-log.sh"
 require_stream_log_path reset-tunnel

package/payload/platform/plugins/cloudflare/scripts/setup-tunnel.sh

@@ -33,7 +33,7 @@ set -euo pipefail
 
 # shellcheck source=_stream-log.sh
 # Resolve symlinks before dirname — ~/setup-tunnel.sh is installed as a symlink
-# (see packages/create-maxy/src/index.ts:installTunnelScripts), so the raw
+# (see packages/create-maxy-code/src/index.ts:installTunnelScripts), so the raw
 # BASH_SOURCE[0] points at $HOME, not the scripts directory where _stream-log.sh lives.
 source "$(dirname "$(readlink -f "${BASH_SOURCE[0]}")")/_stream-log.sh"
 require_stream_log_path setup-tunnel

package/payload/platform/plugins/docs/references/deployment.md

@@ -62,6 +62,10 @@ Failure signals to grep in `~/.maxy/logs/server.log` (or `~/.realagent/logs/serv
 - `[onboarding-gate] step=null complete=true` (the pre-Task-033 bug)
 - missing `[skill-load] name=onboarding` while `[onboarding-gate]` reports `complete=false`
 
+### QA regression replay
+
+`platform/scripts/qa/onboarding-fresh-install.sh <brand> [--watch]` replays the success chain end-to-end on a freshly-installed Pi. It exits zero only when every line above lands, and exits non-zero with the missing line named verbatim on any miss — so a future regression in this chain is caught by replay instead of by a customer. Pass `--watch` to keep polling Neo4j while the operator drives steps 1–9 in the UI; each `currentStep` advance asserts the matching `stepNCompletedAt` is persisted before the next step renders. Provide the admin PIN via `MAXY_ADMIN_PIN`.
+
 ## Service Management
 
 {{productName}} runs via systemd and starts automatically on boot. You don't need to start it manually. To check if it's running, ask {{productName}} "Check system status."
@@ -144,7 +148,7 @@ A separate operator-side harness at `platform/scripts/installer-device-verify.sh
 
 The installer registers Claude Code plugins on the device as the last step before the brand service starts. After registration, `claude plugin list` on the Pi shows every Maxy platform plugin shipped by the brand, every premium sub-plugin shipped by the brand, and any external plugins the brand declares (e.g. Telegram, Discord, iMessage from `claude-plugins-official`). Spawned `claude` sessions inherit those plugins from `~/.claude/` — the session manager passes no `--mcp-config` argv.
 
-**Where the manifests come from.** The Maxy plugin source tree uses `PLUGIN.md` (YAML frontmatter) for plugin metadata, not Claude Code's native `.claude-plugin/plugin.json`. At bundle time, `scripts/generate-plugin-manifests.mjs` walks the payload and synthesises a Claude-Code-native `plugin.json` per plugin plus a `marketplace.json` at each tree root. The generator runs in `packages/create-maxy/scripts/bundle.js` after platform + premium plugins are copied into the payload, so the deployed install directory carries:
+**Where the manifests come from.** The Maxy plugin source tree uses `PLUGIN.md` (YAML frontmatter) for plugin metadata, not Claude Code's native `.claude-plugin/plugin.json`. At bundle time, `scripts/generate-plugin-manifests.mjs` walks the payload and synthesises a Claude-Code-native `plugin.json` per plugin plus a `marketplace.json` at each tree root. The generator runs in `packages/create-maxy-code/scripts/bundle.js` after platform + premium plugins are copied into the payload, so the deployed install directory carries:
 
 - `<INSTALL_DIR>/platform/plugins/<name>/.claude-plugin/plugin.json` per platform plugin
 - `<INSTALL_DIR>/platform/plugins/.claude-plugin/marketplace.json` (marketplace `maxy-platform`)
@@ -165,7 +169,7 @@ Generator schema:
 
 Skills, agents, hooks, and commands directories at the plugin root are auto-discovered by Claude Code — no explicit field needed.
 
-**Install flow** (`registerLocalAndExternalPlugins()` in `packages/create-maxy/src/index.ts`):
+**Install flow** (`registerLocalAndExternalPlugins()` in `packages/create-maxy-code/src/index.ts`):
 
 1. Discover every `.claude-plugin/marketplace.json` under the install directory.
 2. For each one not already in `claude plugin marketplace list`, run `claude plugin marketplace add <dir>`. Pre-existing entries log `[plugin-marketplace] added <name> idempotent=true`.

package/payload/platform/scripts/installer-device-verify.sh

@@ -12,7 +12,7 @@
 # banner — is a non-zero exit with the failing device named on stderr.
 #
 # CONTRACT
-#   Archival of any task that touches packages/create-maxy/** is contingent
+#   Archival of any task that touches packages/create-maxy-code/** is contingent
 #   on this script exiting zero against the published version. The exit code
 #   and the per-device summary are quoted in the close commit body.
 #
@@ -191,7 +191,7 @@ for i in $(seq 0 $((DEVICE_COUNT - 1))); do
   # Step 2 — confirm a terminal-success banner in the latest install log.
   # Pick the newest install-*.log by mtime (`ls -t`) and grep for either of
   # the installer's two terminal-success markers emitted by
-  # packages/create-maxy/src/index.ts:
+  # packages/create-maxy-code/src/index.ts:
   #   • DISPLAY_MODE=virtual (Pi, headless VNC) →
   #     "Browser automation ready (CDP connected)"  (index.ts:3012)
   #   • DISPLAY_MODE=native  (laptop, on-demand Chromium) →

package/payload/platform/scripts/qa/onboarding-fresh-install.sh

@@ -0,0 +1,435 @@
+#!/usr/bin/env bash
+# Task 035 — Onboarding fresh-install Pi integration script.
+#
+# Replays the Task 033 success chain against a freshly-installed brand on
+# this Pi (Maxy Code or Real Agent Code). Exit zero ↔ the entire chain is
+# observable end-to-end. Any miss exits non-zero with the failing
+# observability line named verbatim.
+#
+# Success chain (fresh install, currentStep=0):
+#   [onboarding-seed] currentStep=0
+#     → installer log
+#   [install-invariant] onboarding-state-present
+#     → installer log
+#   [onboarding-gate] step=0 complete=false phase=create
+#     → server.log, fires on POST /api/admin/session
+#   [onboarding-inject] agent=admin step=0 injected=true
+#     → server.log, fires on first POST /api/admin/claude-sessions/:id/input
+#   [skill-load] skillName=onboarding result=unique
+#     → server.log, fires when admin MCP serves skill-load for the agent
+#
+# CONTRACT
+#   Exit 0 — every chain link landed; --watch (if set) walked 9 steps.
+#   Exit 1 — at least one chain assertion failed; missing line(s) named
+#            verbatim in the final report.
+#   Exit 2 — environment fault (cypher-shell unreachable, brand.json
+#            missing, refused-as-non-fresh-install, etc.) — never PASS.
+#
+# USAGE
+#   $ onboarding-fresh-install.sh <brand> [--watch]
+#
+#   <brand>   maxy-code | realagent-code (matches brands/<brand>/brand.json).
+#   --watch   After the fresh-install chain passes, poll Neo4j every 2s.
+#             For every observed currentStep advance N→N+1, assert that
+#             step(N+1)CompletedAt is non-null at the same moment. Exits 0
+#             when currentStep reaches 9 or the operator presses Ctrl-C
+#             after at least one advance.
+#
+# ENV
+#   MAXY_ADMIN_PIN   Admin PIN (required for the session-mint step).
+#                    May also be passed as the 2nd positional argument.
+#   MAXY_NEO4J_PASSWORD
+#                    Neo4j password (default: read from <installDir>/platform/config/.neo4j-password if present).
+#   MAXY_QA_TIMEOUT  Seconds to wait for the runtime log lines to appear
+#                    after the first /input call (default 30).
+#   MAXY_QA_HOST     Admin host (default 127.0.0.1).
+#
+# OUT-OF-SCOPE (per task 035)
+#   * Multi-Pi orchestration — one brand per invocation.
+#   * CI pipeline gating.
+#   * Driving steps 1–9 by curl. Steps 7 (Cloudflare OAuth), 8 (Anthropic
+#     API key paste), and 9 (free-form business profile data) cannot be
+#     deterministically scripted on a fresh install; the operator drives
+#     each step in the UI under --watch while this script polls Neo4j.
+
+set -euo pipefail
+
+# ---------------------------------------------------------------------------
+# Argv + env
+# ---------------------------------------------------------------------------
+
+if [ $# -lt 1 ]; then
+  echo "usage: $0 <brand> [--watch] [pin]" >&2
+  echo "       <brand> = maxy-code | realagent-code" >&2
+  exit 2
+fi
+
+BRAND=""
+WATCH=0
+PIN_POSITIONAL=""
+for arg in "$@"; do
+  case "$arg" in
+    --watch) WATCH=1 ;;
+    -*) echo "unknown flag: $arg" >&2; exit 2 ;;
+    *) if [ -z "$BRAND" ]; then BRAND="$arg"; else PIN_POSITIONAL="$arg"; fi ;;
+  esac
+done
+
+if [ -z "$BRAND" ]; then
+  echo "error: brand argument required" >&2
+  exit 2
+fi
+
+PIN="${MAXY_ADMIN_PIN:-$PIN_POSITIONAL}"
+if [ -z "$PIN" ]; then
+  echo "error: PIN required — set MAXY_ADMIN_PIN env or pass as second positional argument" >&2
+  exit 2
+fi
+
+HOST="${MAXY_QA_HOST:-127.0.0.1}"
+TIMEOUT="${MAXY_QA_TIMEOUT:-30}"
+
+# ---------------------------------------------------------------------------
+# Brand resolution — read live brand.json on the Pi for ports + paths.
+# ---------------------------------------------------------------------------
+
+INSTALL_DIR="$HOME/$BRAND"
+BRAND_JSON="$INSTALL_DIR/platform/config/brand.json"
+LOG_DIR="$HOME/.$BRAND/logs"
+SERVER_LOG="$LOG_DIR/server.log"
+
+if [ ! -f "$BRAND_JSON" ]; then
+  echo "error: brand.json not found at $BRAND_JSON" >&2
+  echo "hint: this script expects a brand installed via @rubytech/create-${BRAND}" >&2
+  exit 2
+fi
+
+# jq is on the deployment-doctrine list; if it's absent, the script must
+# loud-fail rather than fall back to a regex parse of brand.json.
+if ! command -v jq >/dev/null 2>&1; then
+  echo "error: jq required but not installed" >&2
+  exit 2
+fi
+
+NEO4J_PORT="$(jq -r '.neo4jPort' "$BRAND_JSON")"
+if [ -z "$NEO4J_PORT" ] || [ "$NEO4J_PORT" = "null" ]; then
+  echo "error: brand.json at $BRAND_JSON has no neo4jPort field" >&2
+  exit 2
+fi
+
+# Admin server PORT is set by the installer as a systemd Environment var, not
+# in brand.json (verified packages/create-maxy-code/src/port-resolution.ts).
+# Resolution order: MAXY_QA_PORT env → systemctl --user show <serviceName>
+# → fail loud (never a hard-coded default — silent-fallback masks root cause).
+ADMIN_PORT="${MAXY_QA_PORT:-}"
+if [ -z "$ADMIN_PORT" ]; then
+  SERVICE_NAME="$(jq -r '.serviceName' "$BRAND_JSON")"
+  if [ -n "$SERVICE_NAME" ] && [ "$SERVICE_NAME" != "null" ] && command -v systemctl >/dev/null 2>&1; then
+    ADMIN_PORT="$(systemctl --user show "$SERVICE_NAME" -p Environment 2>/dev/null \
+      | tr ' ' '\n' \
+      | grep -E '^PORT=' \
+      | head -n 1 \
+      | cut -d= -f2)"
+  fi
+fi
+if [ -z "$ADMIN_PORT" ]; then
+  echo "error: admin PORT not resolvable — set MAXY_QA_PORT env (e.g. MAXY_QA_PORT=19200)" >&2
+  exit 2
+fi
+
+NEO4J_URI="bolt://localhost:$NEO4J_PORT"
+ADMIN_BASE="http://$HOST:$ADMIN_PORT"
+
+NEO4J_PASSWORD="${MAXY_NEO4J_PASSWORD:-}"
+NEO4J_PASSWORD_FILE="$INSTALL_DIR/platform/config/.neo4j-password"
+if [ -z "$NEO4J_PASSWORD" ] && [ -r "$NEO4J_PASSWORD_FILE" ]; then
+  NEO4J_PASSWORD="$(cat "$NEO4J_PASSWORD_FILE")"
+fi
+if [ -z "$NEO4J_PASSWORD" ]; then
+  echo "error: Neo4j password required — set MAXY_NEO4J_PASSWORD env or place it at $NEO4J_PASSWORD_FILE" >&2
+  exit 2
+fi
+
+for tool in cypher-shell curl grep tail; do
+  if ! command -v "$tool" >/dev/null 2>&1; then
+    echo "error: $tool not on PATH" >&2
+    exit 2
+  fi
+done
+
+# ---------------------------------------------------------------------------
+# Cypher helper — exit 2 on unreachable, captures stderr tail for the report.
+# ---------------------------------------------------------------------------
+
+cypher() {
+  local query="$1"
+  cypher-shell -u neo4j -p "$NEO4J_PASSWORD" -a "$NEO4J_URI" --format plain "$query"
+}
+
+cypher_or_die() {
+  local query="$1"
+  local out
+  if ! out="$(cypher "$query" 2>&1)"; then
+    echo "error: cypher-shell unreachable at $NEO4J_URI" >&2
+    echo "$out" | tail -n 5 >&2
+    exit 2
+  fi
+  printf '%s' "$out"
+}
+
+# ---------------------------------------------------------------------------
+# Assertion bookkeeping — every assertion appends one row to the report so
+# the final block names every link verbatim, pass or fail.
+# ---------------------------------------------------------------------------
+
+REPORT=()
+FAIL_COUNT=0
+
+record() {
+  # record <status> <label> <detail>
+  REPORT+=("$1|$2|$3")
+  if [ "$1" = "FAIL" ]; then
+    FAIL_COUNT=$((FAIL_COUNT + 1))
+  fi
+}
+
+print_report() {
+  echo ""
+  echo "## onboarding fresh-install — final report"
+  echo ""
+  printf '| %-4s | %-50s | %s\n' "Step" "Assertion" "Detail"
+  printf '|------|----------------------------------------------------|-----\n'
+  local i=1
+  for row in "${REPORT[@]}"; do
+    local status="${row%%|*}"
+    local rest="${row#*|}"
+    local label="${rest%%|*}"
+    local detail="${rest#*|}"
+    local marker
+    case "$status" in
+      PASS) marker="PASS" ;;
+      FAIL) marker="FAIL" ;;
+      *)    marker="$status" ;;
+    esac
+    printf '| %-4s | %-50s | %s\n' "$marker" "$label" "$detail"
+    i=$((i + 1))
+  done
+  echo ""
+  echo "brand=$BRAND neo4j=$NEO4J_URI logs=$LOG_DIR"
+}
+
+# ---------------------------------------------------------------------------
+# Step 1 — Pre-flight: refuse if not a fresh install.
+# ---------------------------------------------------------------------------
+
+echo "[1/6] Pre-flight: assert OnboardingState{currentStep:0}"
+PREFLIGHT_OUT="$(cypher_or_die 'MATCH (o:OnboardingState) RETURN o.accountId AS accountId, o.currentStep AS currentStep, o.createdAt AS createdAt')"
+ROW_COUNT="$(printf '%s' "$PREFLIGHT_OUT" | tail -n +2 | grep -c . || true)"
+
+if [ "$ROW_COUNT" -eq 0 ]; then
+  echo "error: not a fresh install — no OnboardingState row exists" >&2
+  echo "hint: the installer's [install-invariant] onboarding-state-MISSING line would have fired; check ~/.${BRAND}/logs/install-*.log" >&2
+  exit 2
+fi
+if [ "$ROW_COUNT" -gt 1 ]; then
+  echo "error: not a fresh install — $ROW_COUNT OnboardingState rows exist (expected 1)" >&2
+  printf '%s\n' "$PREFLIGHT_OUT" >&2
+  exit 2
+fi
+
+CURRENT_STEP="$(printf '%s' "$PREFLIGHT_OUT" | tail -n 1 | awk -F', ' '{print $2}')"
+ACCOUNT_ID="$(printf '%s' "$PREFLIGHT_OUT" | tail -n 1 | awk -F', ' '{print $1}' | tr -d '"')"
+CREATED_AT="$(printf '%s' "$PREFLIGHT_OUT" | tail -n 1 | awk -F', ' '{print $3}' | tr -d '"')"
+
+if [ "$CURRENT_STEP" != "0" ]; then
+  echo "error: not a fresh install — currentStep=$CURRENT_STEP (refusing to drive on top of completed state)" >&2
+  echo "expected: currentStep=0" >&2
+  echo "actual:   $PREFLIGHT_OUT" >&2
+  exit 2
+fi
+record PASS "pre-flight: OnboardingState{currentStep:0}" "accountId=${ACCOUNT_ID:0:8} createdAt=$CREATED_AT"
+
+# ---------------------------------------------------------------------------
+# Step 2 — Installer log: [onboarding-seed] currentStep=0 + [install-invariant] onboarding-state-present.
+#
+# Installer logs live in $LOG_DIR/install-*.log (separate from server.log).
+# Both lines fire once per install run; pin to the newest install log so a
+# stale prior install on the same Pi cannot produce a false PASS.
+# ---------------------------------------------------------------------------
+
+echo "[2/6] Installer log: [onboarding-seed] + [install-invariant] onboarding-state-present"
+LATEST_INSTALL_LOG="$(ls -t "$LOG_DIR"/install-*.log 2>/dev/null | head -n 1 || true)"
+if [ -z "$LATEST_INSTALL_LOG" ]; then
+  record FAIL "[onboarding-seed] currentStep=0" "no install log under $LOG_DIR"
+  record FAIL "[install-invariant] onboarding-state-present" "no install log under $LOG_DIR"
+else
+  if grep -qF "[onboarding-seed] accountId=$ACCOUNT_ID currentStep=0" "$LATEST_INSTALL_LOG"; then
+    record PASS "[onboarding-seed] currentStep=0" "$(basename "$LATEST_INSTALL_LOG")"
+  else
+    record FAIL "[onboarding-seed] currentStep=0" "missing from $(basename "$LATEST_INSTALL_LOG")"
+  fi
+  if grep -qF "[install-invariant] onboarding-state-present accountId=$ACCOUNT_ID" "$LATEST_INSTALL_LOG"; then
+    record PASS "[install-invariant] onboarding-state-present" "$(basename "$LATEST_INSTALL_LOG")"
+  else
+    record FAIL "[install-invariant] onboarding-state-present" "missing from $(basename "$LATEST_INSTALL_LOG")"
+  fi
+fi
+
+# ---------------------------------------------------------------------------
+# Step 3 — POST /api/admin/session: assert onboardingComplete:false in response,
+# then assert [onboarding-gate] step=0 complete=false in server.log.
+# ---------------------------------------------------------------------------
+
+echo "[3/6] Mint admin session via PIN and assert [onboarding-gate] step=0 complete=false"
+TURN_MARKER_BEFORE="$(wc -l < "$SERVER_LOG" 2>/dev/null | tr -d ' ' || echo 0)"
+TURN_MARKER_BEFORE="${TURN_MARKER_BEFORE:-0}"
+SESSION_RESPONSE="$(curl -sS -X POST "$ADMIN_BASE/api/admin/session" \
+  -H 'content-type: application/json' \
+  -d "{\"pin\":\"$PIN\"}")" || {
+    record FAIL "POST /api/admin/session" "curl failed against $ADMIN_BASE"
+    print_report
+    exit 1
+  }
+
+if ! printf '%s' "$SESSION_RESPONSE" | jq -e '.onboardingComplete == false' >/dev/null 2>&1; then
+  record FAIL "POST /api/admin/session onboardingComplete:false" "response=$SESSION_RESPONSE"
+  print_report
+  exit 1
+fi
+SESSION_KEY="$(printf '%s' "$SESSION_RESPONSE" | jq -r '.session_key')"
+if [ -z "$SESSION_KEY" ] || [ "$SESSION_KEY" = "null" ]; then
+  record FAIL "session_key" "absent in /api/admin/session response"
+  print_report
+  exit 1
+fi
+record PASS "POST /api/admin/session onboardingComplete:false" "session minted"
+
+# Tail server.log from the byte offset captured before the call. grep -F
+# matches the substring literally — the gate phrasing in session.ts:193 is
+# `[onboarding-gate] session=... accountId=... step=0 complete=false phase=create`.
+if tail -n +"$TURN_MARKER_BEFORE" "$SERVER_LOG" 2>/dev/null | grep -qF "[onboarding-gate]"  \
+  && tail -n +"$TURN_MARKER_BEFORE" "$SERVER_LOG" 2>/dev/null | grep -F "[onboarding-gate]" | grep -qF "step=0 complete=false"; then
+  record PASS "[onboarding-gate] step=0 complete=false" "phase=create"
+else
+  record FAIL "[onboarding-gate] step=0 complete=false" "not found in $SERVER_LOG since session-mint"
+fi
+
+# ---------------------------------------------------------------------------
+# Step 4 — Spawn an admin claude-session so the next /input is injection-eligible.
+# ---------------------------------------------------------------------------
+
+echo "[4/6] Spawn admin claude-session and capture sessionId"
+SPAWN_RESPONSE="$(curl -sS -X POST "$ADMIN_BASE/api/admin/claude-sessions/?session_key=$SESSION_KEY" \
+  -H 'content-type: application/json' \
+  -d '{"channel":"browser"}')" || {
+    record FAIL "POST /api/admin/claude-sessions/" "curl failed"
+    print_report
+    exit 1
+  }
+SESSION_ID="$(printf '%s' "$SPAWN_RESPONSE" | jq -r '.sessionId // empty')"
+if [ -z "$SESSION_ID" ]; then
+  record FAIL "POST /api/admin/claude-sessions/" "no sessionId in response: $SPAWN_RESPONSE"
+  print_report
+  exit 1
+fi
+record PASS "spawn claude-session" "sessionId=${SESSION_ID:0:8}"
+
+# ---------------------------------------------------------------------------
+# Step 5 — First /input call. This triggers buildOnboardingPromptBlock,
+# which logs [onboarding-inject] step=0 injected=true. The agent then runs
+# the prepended skill-load directive, which logs [skill-load] skillName=onboarding.
+# ---------------------------------------------------------------------------
+
+echo "[5/6] Submit first admin input and wait up to ${TIMEOUT}s for [onboarding-inject] and [skill-load]"
+INPUT_MARKER_BEFORE="$(wc -l < "$SERVER_LOG" 2>/dev/null | tr -d ' ' || echo 0)"
+INPUT_MARKER_BEFORE="${INPUT_MARKER_BEFORE:-0}"
+INPUT_RESPONSE="$(curl -sS -X POST "$ADMIN_BASE/api/admin/claude-sessions/$SESSION_ID/input?session_key=$SESSION_KEY" \
+  -H 'content-type: application/json' \
+  -d '{"text":"hello"}')" || {
+    record FAIL "POST /api/admin/claude-sessions/:id/input" "curl failed"
+    print_report
+    exit 1
+  }
+# Status-only check — the manager owns the per-input contract.
+record PASS "POST first /input" "(skill-load arrives async)"
+
+# Poll-tail server.log for the two remaining lines.
+deadline=$(( $(date +%s) + TIMEOUT ))
+inject_seen=0
+skill_seen=0
+while [ "$(date +%s)" -lt "$deadline" ]; do
+  if [ "$inject_seen" -eq 0 ] \
+    && tail -n +"$INPUT_MARKER_BEFORE" "$SERVER_LOG" 2>/dev/null | grep -F "[onboarding-inject]" | grep -qF "step=0 injected=true"; then
+    inject_seen=1
+  fi
+  if [ "$skill_seen" -eq 0 ] \
+    && tail -n +"$INPUT_MARKER_BEFORE" "$SERVER_LOG" 2>/dev/null | grep -F "[skill-load]" | grep -qF "skillName=onboarding"; then
+    skill_seen=1
+  fi
+  if [ "$inject_seen" -eq 1 ] && [ "$skill_seen" -eq 1 ]; then break; fi
+  sleep 1
+done
+
+if [ "$inject_seen" -eq 1 ]; then
+  record PASS "[onboarding-inject] step=0 injected=true" "server.log"
+else
+  record FAIL "[onboarding-inject] step=0 injected=true" "not found within ${TIMEOUT}s"
+fi
+if [ "$skill_seen" -eq 1 ]; then
+  record PASS "[skill-load] skillName=onboarding" "server.log"
+else
+  record FAIL "[skill-load] skillName=onboarding" "not found within ${TIMEOUT}s"
+fi
+
+# ---------------------------------------------------------------------------
+# Step 6 — --watch mode: poll Neo4j and assert step-advance + timestamp.
+#
+# The operator drives steps 1–9 in the UI. For every observed currentStep
+# transition N→N+1, assert step(N+1)CompletedAt is non-null at the same
+# moment. The script never advances steps itself — steps 7 (Cloudflare
+# OAuth), 8 (Anthropic API key paste), and 9 (free-form business profile)
+# require operator-side inputs that cannot be forged from a script.
+# ---------------------------------------------------------------------------
+
+if [ "$FAIL_COUNT" -gt 0 ]; then
+  print_report
+  echo "Fresh-install chain failed before --watch could start." >&2
+  exit 1
+fi
+
+if [ "$WATCH" -eq 1 ]; then
+  echo "[6/6] --watch: polling Neo4j every 2s. Drive steps 1-9 in the UI now. Ctrl-C to abort."
+  last_step="$CURRENT_STEP"
+  while :; do
+    sleep 2
+    WATCH_OUT="$(cypher_or_die 'MATCH (o:OnboardingState) RETURN o.currentStep AS s, o.step1CompletedAt AS s1, o.step2CompletedAt AS s2, o.step3CompletedAt AS s3, o.step4CompletedAt AS s4, o.step5CompletedAt AS s5, o.step6CompletedAt AS s6, o.step7CompletedAt AS s7, o.step8CompletedAt AS s8, o.step9CompletedAt AS s9')"
+    NOW_STEP="$(printf '%s' "$WATCH_OUT" | tail -n 1 | awk -F', ' '{print $1}')"
+    if [ "$NOW_STEP" = "$last_step" ]; then continue; fi
+    # Advance observed. Check the timestamp for the new step.
+    new_step="$NOW_STEP"
+    if [ "$new_step" -le "$last_step" ]; then
+      record FAIL "step regression" "last=$last_step now=$new_step"
+      print_report
+      exit 1
+    fi
+    ts_field=$(( new_step + 1 ))  # awk fields are 1-indexed; currentStep is field 1, stepNCompletedAt is field N+1.
+    stamp="$(printf '%s' "$WATCH_OUT" | tail -n 1 | awk -F', ' "{print \$$ts_field}" | tr -d '"')"
+    if [ -z "$stamp" ] || [ "$stamp" = "NULL" ] || [ "$stamp" = "null" ]; then
+      record FAIL "step$new_step advanced without timestamp" "step${new_step}CompletedAt is NULL"
+      print_report
+      exit 1
+    fi
+    record PASS "step $new_step advance" "step${new_step}CompletedAt=$stamp"
+    last_step="$new_step"
+    if [ "$new_step" -ge 9 ]; then
+      echo "  currentStep=9 — onboarding complete"
+      break
+    fi
+  done
+fi
+
+print_report
+if [ "$FAIL_COUNT" -gt 0 ]; then
+  exit 1
+fi
+exit 0

package/payload/platform/scripts/redact-install-logs.sh

@@ -2,7 +2,7 @@
 # Existing-pi install-log redaction (Task 744).
 #
 # Idempotent one-shot remediation for Pis that completed installation BEFORE
-# the install-log redaction landed at packages/create-maxy/src/index.ts:152.
+# the install-log redaction landed at packages/create-maxy-code/src/index.ts:152.
 # Scans every `install-*.log` in the configured logs directory and replaces
 # every literal `set-initial-password ...<secret>` payload with
 # `set-initial-password [REDACTED]`. Re-running the script is safe —
@@ -10,7 +10,7 @@
 # edits occur.
 #
 # Source patterns covered:
-#   1. TS installer (packages/create-maxy/src/index.ts:152) — "[ISO] > sudo
+#   1. TS installer (packages/create-maxy-code/src/index.ts:152) — "[ISO] > sudo
 #      neo4j-admin dbms set-initial-password -- <secret>" or any args after
 #      "set-initial-password" (positional or "--" delimited).
 #   2. Legacy bash installer (removed) — "+ sudo neo4j-admin dbms

package/payload/platform/scripts/verify-skill-tool-surface.sh

@@ -8,7 +8,7 @@
 # and where a skill prescribes a forbidden direct-execution path
 # (`cypher-shell`, `neo4j-admin` invocations, raw-Cypher DML in prose).
 #
-# Wired into the root `packages/create-maxy/package.json` `prepublishOnly`
+# Wired into the root `packages/create-maxy-code/package.json` `prepublishOnly`
 # script so a regression cannot reach npm publish without firing.
 #
 # One stdout line per (skill, specialist) pair:

package/payload/platform/scripts/vnc.sh

@@ -45,7 +45,7 @@ BRAND_JSON="${PLATFORM_ROOT}/config/brand.json"
 # Task 959 — brand.json is the single source of truth at runtime; missing
 # fields loud-fail rather than silently substituting a vncDisplay-derived
 # offset (silent-fallback-masks-root-cause recurrence). The install-time
-# offset rule in packages/create-maxy/src/index.ts stamps every brand at
+# offset rule in packages/create-maxy-code/src/index.ts stamps every brand at
 # build time, so a correctly-installed device always has all five fields.
 if [ ! -f "$BRAND_JSON" ]; then
   echo "[vnc.sh] error reason=brand-config-missing path=$BRAND_JSON" >&2
@@ -89,7 +89,7 @@ mkdir -p "$LOG_DIR"
 log() { echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" >> "$LOG_FILE"; }
 
 # Task 929 — resolve the absolute Chromium binary path from the install-time
-# config file. The installer (packages/create-maxy/src/index.ts
+# config file. The installer (packages/create-maxy-code/src/index.ts
 # ensureNonSnapChromium + writeChromiumBinaryPathFile) writes this file with
 # the non-snap binary chosen for this device — `/usr/bin/chromium` on Pi
 # Bookworm (real .deb) or `/usr/bin/google-chrome-stable` on Ubuntu Noble

package/payload/premium-plugins/real-agency/plugins/brochures/skills/brand-design/SKILL.md

@@ -80,7 +80,7 @@ Two PNGs of the wordmark/lockup as the brand uses it. **The filename describes t
 | Filename | Art colour | Place it on |
 |---|---|---|
 | `<slug>-logo-light.png` | light/white/cream/pale pixels | dark surfaces (back-page hero, dark masthead) |
-| `<slug>-logo-dark.png` | dark/black/navy/charcoal pixels | light surfaces (TOC, page.html nav, paper backgrounds) |
+| `<slug>-logo-dark.png` | dark/black/navy/charcoal pixels | light surfaces (TOC, index.html nav, paper backgrounds) |
 
 So if you open `donnavincent-logo-light.png` and see white text, that is correct — it's the light-coloured variant. If you open `donnavincent-logo-dark.png` and see white text, the file was misnamed by an earlier run; rename it.
 

package/payload/premium-plugins/real-agency/plugins/brochures/skills/make-brochure/SKILL.md

@@ -23,7 +23,7 @@ The deliverable is identical to `property-brochure`'s outcome — written into `
 
 - `brochure.html` plus per-page 300 dpi PNG print snapshots (canonical, archival)
 - Two image-only PDFs: `<slug>-brochure-print.pdf` (300 dpi print master) and `<slug>-brochure-web.pdf` (192 dpi web/digital). Both built from per-page Playwright snapshots via img2pdf and linearized via qpdf — no Ghostscript anywhere in the chain. See `property-brochure → PDF deliverable` and `a4-print-documents → PDF deliverables`.
-- A self-contained **web bundle** at `output/web/` plus `output/<slug>-web.zip` — the smaller, ready-to-host version for property micro-sites; includes both the brochure and a companion **landing page** at `page.html` that presents the property as a continuous scrollable web page. See `property-brochure → Web bundle` and `property-brochure → Page`
+- A self-contained **web bundle** at `output/web/` plus `output/<slug>-web.zip` — the smaller, ready-to-host version for property micro-sites; includes both the brochure and a companion **landing page** at `index.html` that presents the property as a continuous scrollable web page. See `property-brochure → Web bundle` and `property-brochure → Page`
 
 The orchestrator's value is in what it does **not** redo:
 
@@ -271,19 +271,19 @@ After a complete run, the on-disk layout is **exactly** this — no deeper nesti
             qr-video.png, qr-listing.png
           web/                            # self-contained web bundle, generated alongside print archive
             brochure.html                 # same HTML; print-img refs point at .jpg snapshots; QR codes are clickable <a>
-            page.html                     # companion property landing page (Modern House-style scroll)
+            index.html                     # companion property landing page (Modern House-style scroll)
             <property_slug>-brochure.pdf  # digital PDF, copied for the in-page Download button
             cover-print.jpg
             page2-print.jpg … page15-print.jpg
             backpage-print.jpg
             images/                       # web-tier per-slot encodings: hero 1300/q82, story 1100/q80, thumb 800/q76
               <property_slug>-NN.webp
-              <property_slug>-hero-1-main.webp     # page.html hero rotator — source-res @ q88
-              <property_slug>-hero-2-<role>.webp   # page.html hero rotator — interior moment
-              <property_slug>-hero-3-<role>.webp   # page.html hero rotator — garden / outdoor
+              <property_slug>-hero-1-main.webp     # index.html hero rotator — source-res @ q88
+              <property_slug>-hero-2-<role>.webp   # index.html hero rotator — interior moment
+              <property_slug>-hero-3-<role>.webp   # index.html hero rotator — garden / outdoor
               <property_slug>-floorplan.png        # line-art PNG, copied unchanged from canonical
-              <brand_slug>-logo-light.png # light-coloured logo art — for dark surfaces (e.g. dark page.html sections)
-              <brand_slug>-logo-dark.png  # dark-coloured logo art — for light surfaces (e.g. page.html nav, brochure cover when paper)
+              <brand_slug>-logo-light.png # light-coloured logo art — for dark surfaces (e.g. dark index.html sections)
+              <brand_slug>-logo-dark.png  # dark-coloured logo art — for light surfaces (e.g. index.html nav, brochure cover when paper)
               qr-video.png, qr-listing.png
           <property_slug>-web.zip         # zipped form of web/, ready to upload to a static-site host
 ```
@@ -325,7 +325,7 @@ Determinism rules — a run that violates any of these is wrong, even if the bro
 | "House" instead of "home" at super-premium register | Wrong word for the buyer. "Home" is warmer, more aspirational, and matches the register. Replace globally. |
 | Text overlaid on photographs relying on a gradient + text-shadow for legibility | Insufficient against busy backgrounds (stone tile, golden-hour skies). Use a translucent dark panel directly behind the text. See `property-brochure → Text on images`. |
 | Including a detached gymnasium-summerhouse footprint in the principal home's first-floor sq ft | Misrepresents £/sq ft. List ancillary footprints separately. See `property-brochure → Floor area`. |
-| Shipping a web bundle without `page.html` | The web bundle is the property's hosted experience. The brochure is a downloadable folio; the landing page is the scrollable "for sale" page that links to it. Both are mandatory in the zip. See `property-brochure → Page`. |
+| Shipping a web bundle without `index.html` | The web bundle is the property's hosted experience. The brochure is a downloadable folio; the landing page is the scrollable "for sale" page that links to it. Both are mandatory in the zip. See `property-brochure → Page`. |
 | Putting QR codes on the back page without a visible URL or a clickable wrapper | A QR is unscannable from the digital screen showing the brochure. The clickable URL beneath each QR is mandatory; it makes the digital reader experience equivalent to the print reader experience. See `property-brochure → Back-page QR codes`. |
 | Using the same logo variant for the back-page masthead (dark surface) and the landing-page nav (light surface) | The two surfaces need opposite logo variants — white-on-transparent for the back page, dark/coloured for the landing nav. Both must be present in `output/web/images/`. |
 
@@ -339,7 +339,7 @@ Report `DONE` only after:
 - Both PDF deliverables exist alongside `brochure.html`: the print master (`<property_slug>-brochure-print.pdf`, ~50–80 MB at 300 dpi) and the web/digital (`<property_slug>-brochure-web.pdf`, ~20–35 MB at 192 dpi). Both are image-only, built from per-page Playwright snapshots via img2pdf and linearized via qpdf; both pass `qpdf --check`, both report `Optimized: yes`, and both have zero embedded fonts (`pdffonts | wc -l` returns 2). See `a4-print-documents → Verification`.
 - All per-page print snapshots referenced by the HTML's print CSS exist at expected names — `cover-print.png`, `page2-print.png` through `page15-print.png`, and `backpage-print.png` (16 files for the 16-page folio) — at the orientation-correct 300 dpi pixel dimensions (3509×2481 landscape / 2481×3509 portrait).
 - The brochure has an **even page count** (canonical 16; multiples of 2 required, ideally multiples of 4 for booklet binding) — see `a4-print-documents` → Even-page count for duplex printing.
-- The **web bundle** exists at `output/web/` and as a zipped `output/<slug>-web.zip` — see `property-brochure → Web bundle` for what it contains. The bundle includes both `brochure.html` and the companion `page.html` (see `property-brochure → Page`), plus a copy of the web PDF named simply `<property_slug>-brochure.pdf` to match the in-page Download links. Smoke-test was performed: an isolated HTTP server returned 200 for every referenced asset (HTML, web-tier images, jpg snapshots, the bundled PDF), and **both** `brochure.html` and `page.html` rendered correctly. Typical zip is 30–50 MB for a 16-page folio.
+- The **web bundle** exists at `output/web/` and as a zipped `output/<slug>-web.zip` — see `property-brochure → Web bundle` for what it contains. The bundle includes both `brochure.html` and the companion `index.html` (see `property-brochure → Page`), plus a copy of the web PDF named simply `<property_slug>-brochure.pdf` to match the in-page Download links. Smoke-test was performed: an isolated HTTP server returned 200 for every referenced asset (HTML, web-tier images, jpg snapshots, the bundled PDF), and **both** `brochure.html` and `index.html` rendered correctly. Typical zip is 30–50 MB for a 16-page folio.
 - **Back-page QR codes are clickable.** Each QR is wrapped in an `<a target="_blank">` tag and accompanied by a visible underlined URL beneath the label, so a digital reader can click instead of scan. See `property-brochure → Back-page QR codes`.
 - The user-facing report names which steps ran and which were reused, **and the chosen orientation**, **and the path to both the canonical print archive and the web zip**.
 - No image was read in violation of the 2000px rule (verifiable: every image read should have been preceded by a `sips`/`identify` measurement, and any over-threshold image was previewed via `/tmp/`).

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

@@ -9,7 +9,7 @@ Produce an A4 property brochure from raw assets. The default deliverable is a 16
 
 ## Output location
 
-By default the brochure is written to the **caller's current working directory**. The skill creates `./output/brochure.html`, `./output/web/page.html`, the print PNGs, and the two PDFs underneath `pwd` — no inference, no nesting under a brand workspace.
+By default the brochure is written to the **caller's current working directory**. The skill creates `./output/brochure.html`, `./output/web/index.html`, the print PNGs, and the two PDFs underneath `pwd` — no inference, no nesting under a brand workspace.
 
 If you want the output elsewhere, pass `output_dir` explicitly (an absolute path or a relative path resolved against CWD). Common overrides:
 
@@ -23,12 +23,12 @@ Do not silently nest the output under a brand workspace just because one is pres
 
 ## Step 1 — copy the canonical templates (do this first)
 
-`references/template.html` and `references/page.html` are the **only** acceptable starting points. They are placeholder-only — every property value is a `{{ token }}`. Copy them before doing anything else. **Do not write brochure HTML or page HTML from scratch. Do not start from a sibling property's output. Do not improvise structure from prose.**
+`references/template.html` and `references/index.html` are the **only** acceptable starting points. They are placeholder-only — every property value is a `{{ token }}`. Copy them before doing anything else. **Do not write brochure HTML or page HTML from scratch. Do not start from a sibling property's output. Do not improvise structure from prose.**
 
 ```bash
 mkdir -p <output_dir>/web
 cp ~/.claude/plugins/real-estate-brochure/skills/property-brochure/references/template.html <output_dir>/brochure.html
-cp ~/.claude/plugins/real-estate-brochure/skills/property-brochure/references/page.html      <output_dir>/web/page.html
+cp ~/.claude/plugins/real-estate-brochure/skills/property-brochure/references/index.html      <output_dir>/web/index.html
 ```
 
 `<output_dir>` is whatever the **Output location** section above resolves to — typically `./output/` in the caller's CWD.
@@ -43,7 +43,7 @@ Both files must contain canonical sentinels (proves they came from `references/`
 
 ```bash
 grep -q '{{ property_name }}'  <output_dir>/brochure.html  || echo "FAIL: brochure not from template"
-grep -q 'hero-stage'           <output_dir>/web/page.html  || echo "FAIL: page.html not from references"
+grep -q 'hero-stage'           <output_dir>/web/index.html  || echo "FAIL: index.html not from references"
 ```
 
 Both greps must succeed before populating content. If either fails, recopy.
@@ -74,14 +74,14 @@ Read the seller brief once before writing any copy. Then walk the `{{ placeholde
 | Editorial copy register, em-dash policy, "home" vs "house", text-on-images, typography, stats rows, AI hero prompt, **per-section composition guide** | [references/copy.md](references/copy.md) |
 | Orientation, 16-page layout, cover, floorplan, distinguishing features, Material Information, QR codes, location map | [references/structure.md](references/structure.md) |
 | Live editing, snapshot capture, PDF deliverable, web bundle | [references/build.md](references/build.md) |
-| `page.html` landing page — sections, hero rotator, mobile/drawer | [references/page-landing.md](references/page-landing.md) |
+| `index.html` landing page — sections, hero rotator, mobile/drawer | [references/index-landing.md](references/index-landing.md) |
 
 ### Substitution completion gate
 
 A brochure with any `{{ x }}` still in the rendered HTML is **shipped broken**. Before any snapshot capture or PDF build, run:
 
 ```bash
-unsubstituted=$(grep -c '{{' "$output_dir/brochure.html" "$output_dir/web/page.html" 2>/dev/null | awk -F: '{s+=$2} END {print s}')
+unsubstituted=$(grep -c '{{' "$output_dir/brochure.html" "$output_dir/web/index.html" 2>/dev/null | awk -F: '{s+=$2} END {print s}')
 [ "$unsubstituted" -eq 0 ] || { echo "DEFECT: $unsubstituted unsubstituted {{ tokens }} remain"; exit 1; }
 ```
 
@@ -106,7 +106,7 @@ unsubstituted=$(grep -c '{{' "$output_dir/brochure.html" "$output_dir/web/page.h
 - **Page count must be even** (16 default; 12 if the property is too small). 14 is forbidden.
 - **Image-only PDFs** — no fonts embedded, no Ghostscript anywhere in the chain.
 - **Self-contained `output/`** — never reference `../` paths. Every asset the HTML uses must live under `output/images/`.
-- **Web bundle must include `page.html`** — a bundle without it is incomplete.
+- **Web bundle must include `index.html`** — a bundle without it is incomplete.
 - **Suppress screen-only chrome before snapshotting** — the template's `.download-bar` is hidden under `@media print` but Playwright's `element.screenshot()` captures the screen render, where the bar IS visible. The render script in `build.md` injects a style tag (`.download-bar { display: none !important; }`) before capture. Any custom render script must do the same.
 - **No `{{ token }}` may remain in rendered output** — `grep '{{' output/brochure.html` must return zero matches before PDFs are built.
 

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

@@ -164,7 +164,7 @@ 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
-  page.html                          # companion landing page (mandatory in bundle)
+  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/
@@ -220,7 +220,7 @@ A 16-page folio's web-bundle snapshots total ~3 MB (vs ~85 MB for the canonical
 
 ### Copy the web PDF into the bundle
 
-The web PDF (`<slug>-brochure-web.pdf` at the property level) is also placed inside the bundle, named simply `<slug>-brochure.pdf` to match `page.html` and `brochure.html` link conventions (where there's only one PDF in scope, no `-web` suffix is needed):
+The web PDF (`<slug>-brochure-web.pdf` at the property level) is also placed inside the bundle, named simply `<slug>-brochure.pdf` to match `index.html` and `brochure.html` link conventions (where there's only one PDF in scope, no `-web` suffix is needed):
 
 ```bash
 cp output/<slug>-brochure-web.pdf output/web/<slug>-brochure.pdf
@@ -245,7 +245,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 page.html cover-print.jpg images/<slug>-01.webp images/<brand>-logo-light.png <slug>-brochure.pdf; do
+for f in brochure.html index.html cover-print.jpg 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
 ```
@@ -257,10 +257,10 @@ 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 |
-| `page.html` | — | ✓ companion landing page; see `page-landing.md` |
+| `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.pdf` | — | ✓ identical bytes to `-web.pdf`; matches page.html / brochure.html link |
+| `<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) |
 | `images/<slug>-NN.webp` | full-quality per Render-slot table | web-tier per the web table above |

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

@@ -109,7 +109,7 @@ If five cells at the chosen font size do not fit the available row width, **shri
 
 ## Per-section composition guide
 
-This section is the writing brief for each placeholder block in `template.html` and `page.html`. The token names map 1:1 to entries in `placeholders.md`; this file says **how the copy should read** for each one.
+This section is the writing brief for each placeholder block in `template.html` and `index.html`. The token names map 1:1 to entries in `placeholders.md`; this file says **how the copy should read** for each one.
 
 ### Cover & subtitle (page 1)
 
@@ -195,9 +195,9 @@ This section is the writing brief for each placeholder block in `template.html`
 - `{{ backpage_headline }}` — canonical phrasing "Arrange a viewing of <em>{{ property_name }}</em>". Do not paraphrase.
 - `{{ backpage_tagline }}` — single sentence, 25-45 words. Mirrors the cover/opener without duplicating phrases. Close with "Best understood in person." or an equivalent property-specific clincher.
 
-### Landing page (page.html)
+### Landing page (index.html)
 
-The landing-page tokens (`{{ landing_* }}`) source the same brief but render in continuous-scroll form rather than a 16-page folio. Each `{{ landing_*_para_N }}` follows the same length/voice rules as the equivalent brochure paragraph — see placeholders.md → "Category 9 — page.html editorial copy" for the per-section breakdown.
+The landing-page tokens (`{{ landing_* }}`) source the same brief but render in continuous-scroll form rather than a 16-page folio. Each `{{ landing_*_para_N }}` follows the same length/voice rules as the equivalent brochure paragraph — see placeholders.md → "Category 9 — index.html editorial copy" for the per-section breakdown.
 
 ## AI hero image prompt
 

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

@@ -120,7 +120,7 @@ The brochure is a **print-first deliverable**. Source images target the print-ma
 | **Map / screenshot** | screenshot with text labels | **2000 px** | source size, no resize | 88 |
 | **EPC chart** | small, already <100KB — copy through unchanged | n/a | as-is | as-is |
 
-**Floor plan exception — keep the source file as-is.** When the seller (or the agency's floor-plan provider) supplies a high-resolution PNG, **use it directly** — do not convert to WebP, do not downscale, do not re-encode. Floor plans are line art with thin strokes and crisp text where any quality loss is visibly worse than the same quality loss on photographic content. The same file (`<slug>-floorplan.png`) is referenced in the canonical brochure HTML, in the page.html landing page, and copied verbatim into `output/web/images/`. Because the new PDF pipeline rasterises whole pages from the rendered HTML (rather than passing the floor plan through a separate compression stage), the floor plan's quality at the PDF stage is determined by the snapshot DPI — 300 dpi for the print master, 192 dpi for the web PDF. A typical 2000 px floor plan slotted into a ~150 mm-wide brochure cell renders crisply at 300 dpi without any per-image processing. The **web bundle** also references the same `.png` (not a `.webp` substitute) — line art doesn't compress well as WebP and the file size is already modest.
+**Floor plan exception — keep the source file as-is.** When the seller (or the agency's floor-plan provider) supplies a high-resolution PNG, **use it directly** — do not convert to WebP, do not downscale, do not re-encode. Floor plans are line art with thin strokes and crisp text where any quality loss is visibly worse than the same quality loss on photographic content. The same file (`<slug>-floorplan.png`) is referenced in the canonical brochure HTML, in the index.html landing page, and copied verbatim into `output/web/images/`. Because the new PDF pipeline rasterises whole pages from the rendered HTML (rather than passing the floor plan through a separate compression stage), the floor plan's quality at the PDF stage is determined by the snapshot DPI — 300 dpi for the print master, 192 dpi for the web PDF. A typical 2000 px floor plan slotted into a ~150 mm-wide brochure cell renders crisply at 300 dpi without any per-image processing. The **web bundle** also references the same `.png` (not a `.webp` substitute) — line art doesn't compress well as WebP and the file size is already modest.
 
 The **source-px floor** is the floor on the input photo's longest edge **before optimisation** — see the `Image resolution floor` section in the **a4-print-documents** SKILL for the rationale and full thresholds.
 

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/brand-constants.json

@@ -2,7 +2,7 @@
   "productName": "Maxy",
   "tagline": "AI for Productive People",
   "domain": "getmaxy.com",
-  "hostname": "maxy",
+  "hostname": "maxy-code",
   "logo": "/brand/maxy-square.png",
   "favicon": "/brand/favicon.ico"
 }

package/payload/server/public/brand-defaults.css

@@ -1,5 +1,5 @@
 :root {
-  /* Brand defaults — generated by bundle.js from brands/maxy/brand.json */
+  /* Brand defaults — generated by bundle.js from brands/maxy-code/brand.json */
   --sage: #7C8C72;
   --sage-hover: #6A7A62;
   --sage-subtle: rgba(124, 140, 114, 0.08);