@rubytech/create-maxy-code 0.1.62 → 0.1.64

package/payload/platform/plugins/loop/mcp/src/tools/viewing-detail.ts

@@ -1,171 +0,0 @@
-import {
-  aggregateAcrossTeams,
-  formatAggregationResult,
-  loopGet,
-} from "../lib/loop-api.js";
-
-// ─── Loop API V2: /residential/{dept}/viewings/{id} ────────────
-// Fields: id, dateCreated, dateOfAppointment, dateOfAppointmentEnd,
-//   dateBuyerFeedbackGiven, dateSellerFeedbackGiven, dateDone,
-//   status, type, comment, buyerFeedback, sellerFeedback,
-//   buyerConfirmed, sellerConfirmed, agentConfirmed,
-//   property (nested PropertySummary), buyer (nested BuyerSummary),
-//   seller (nested SellerSummary),
-//   attendingAgent (nested TeamMember), creatingAgent (nested TeamMember),
-//   teamId
-// ────────────────────────────────────────────────────────────────
-interface LoopViewingDetail {
-  id: number;
-  dateCreated?: string;
-  dateOfAppointment?: string;
-  dateOfAppointmentEnd?: string;
-  dateBuyerFeedbackGiven?: string | null;
-  dateSellerFeedbackGiven?: string | null;
-  dateDone?: string | null;
-  status?: string;
-  type?: string;
-  comment?: string | null;
-  buyerFeedback?: string | null;
-  sellerFeedback?: string | null;
-  buyerConfirmed?: boolean;
-  sellerConfirmed?: boolean;
-  agentConfirmed?: boolean;
-  property?: {
-    id: number;
-    propertyAddress?: string;
-    status?: string;
-    propertyType?: string;
-    price?: number;
-    bedrooms?: number;
-    [key: string]: unknown;
-  };
-  buyer?: {
-    id: number;
-    buyerGroupName?: string;
-    maxPrice?: number | null;
-    position?: string;
-    viewingCount?: number;
-    offerCount?: number;
-    [key: string]: unknown;
-  };
-  seller?: {
-    id: number;
-    sellerGroupName?: string;
-    propertyAddress?: string;
-    price?: number;
-    [key: string]: unknown;
-  };
-  attendingAgent?: {
-    id: string;
-    firstName?: string;
-    lastName?: string;
-    email?: string;
-    mobilePhone?: string;
-    jobTitle?: string;
-    [key: string]: unknown;
-  };
-  creatingAgent?: {
-    id: string;
-    firstName?: string;
-    lastName?: string;
-    [key: string]: unknown;
-  };
-  teamId?: string;
-  [key: string]: unknown;
-}
-
-type Department = "sales" | "lettings";
-
-export async function viewingDetail(params: {
-  accountId: string;
-  viewingId: number;
-  department: Department;
-  teamName?: string;
-}): Promise<string> {
-  const { accountId, viewingId, department, teamName } = params;
-
-  const result = await aggregateAcrossTeams<LoopViewingDetail>(
-    accountId,
-    "viewings",
-    "loop-viewing-detail",
-    async (apiKey, team) => {
-      const path = `/residential/${department}/viewings/${viewingId}`;
-      const data = await loopGet<LoopViewingDetail>(apiKey, path, "loop-viewing-detail", team);
-      if (data && typeof data === "object" && !Array.isArray(data)) {
-        return [data];
-      }
-      return [];
-    },
-    { teamName }
-  );
-
-  return formatAggregationResult(
-    result,
-    (v) => {
-      const propAddr = v.property?.propertyAddress ?? "Unknown property";
-      const lines = [`**${propAddr}** [Viewing ID: ${v.id}]`];
-
-      // Appointment time
-      if (v.dateOfAppointment) {
-        const start = formatDateTime(v.dateOfAppointment);
-        const end = v.dateOfAppointmentEnd ? formatDateTime(v.dateOfAppointmentEnd) : "";
-        lines.push(`Date/Time: ${start}${end ? ` — ${end}` : ""}`);
-      }
-      if (v.status) lines.push(`Status: ${v.status}`);
-      if (v.type) lines.push(`Type: ${v.type}`);
-
-      // Confirmation status
-      const confirmParts: string[] = [];
-      if (v.buyerConfirmed != null) confirmParts.push(`Buyer: ${v.buyerConfirmed ? "yes" : "no"}`);
-      if (v.sellerConfirmed != null) confirmParts.push(`Seller: ${v.sellerConfirmed ? "yes" : "no"}`);
-      if (v.agentConfirmed != null) confirmParts.push(`Agent: ${v.agentConfirmed ? "yes" : "no"}`);
-      if (confirmParts.length) lines.push(`Confirmed — ${confirmParts.join(", ")}`);
-
-      // Property details
-      if (v.property) {
-        const prop = v.property;
-        if (prop.price != null) lines.push(`Property price: £${prop.price.toLocaleString("en-GB")}`);
-        if (prop.propertyType) lines.push(`Property type: ${prop.propertyType}`);
-        if (prop.bedrooms != null) lines.push(`Bedrooms: ${prop.bedrooms}`);
-        if (prop.id) lines.push(`Property ID: ${prop.id}`);
-      }
-
-      // Buyer
-      if (v.buyer) {
-        const b = v.buyer;
-        lines.push(`\n**Buyer:** ${b.buyerGroupName ?? "Unknown"} [ID: ${b.id}]`);
-        if (b.maxPrice != null) lines.push(`  Max price: £${b.maxPrice.toLocaleString("en-GB")}`);
-        if (b.position && b.position !== "none") lines.push(`  Position: ${b.position}`);
-      }
-
-      // Seller
-      if (v.seller) {
-        const s = v.seller;
-        lines.push(`\n**Seller:** ${s.sellerGroupName ?? "Unknown"} [ID: ${s.id}]`);
-      }
-
-      // Attending agent
-      if (v.attendingAgent) {
-        const a = v.attendingAgent;
-        const agentName = [a.firstName, a.lastName].filter(Boolean).join(" ");
-        const title = a.jobTitle ? ` (${a.jobTitle})` : "";
-        const contact = a.email ?? a.mobilePhone ?? "";
-        lines.push(`\n**Attending agent:** ${agentName}${title}${contact ? ` — ${contact}` : ""}`);
-      }
-
-      // Feedback
-      if (v.buyerFeedback) lines.push(`\nBuyer feedback: ${v.buyerFeedback}`);
-      if (v.sellerFeedback) lines.push(`Seller feedback: ${v.sellerFeedback}`);
-      if (v.comment) lines.push(`Notes: ${v.comment}`);
-
-      return lines.join("\n");
-    },
-    "viewing details"
-  );
-}
-
-function formatDateTime(iso: string): string {
-  const [datePart, timePart] = iso.split("T");
-  if (!timePart) return datePart;
-  return `${datePart} ${timePart.slice(0, 5)}`;
-}

package/payload/platform/plugins/loop/mcp/src/tools/viewing-search.ts

@@ -1,92 +0,0 @@
-import {
-  aggregateAcrossTeams,
-  formatAggregationResult,
-  loopGet,
-} from "../lib/loop-api.js";
-
-// ─── Loop API V2: /residential/{dept}/viewings ─────────────────
-// Fields: id, propertyId, propertyAddress, status,
-//   dateOfAppointment, dateOfAppointmentEnd,
-//   attendingAgentId, creatingAgentId, type, buyerName
-// ────────────────────────────────────────────────────────────────
-interface LoopViewingSummary {
-  id: number;
-  propertyId?: number;
-  propertyAddress?: string;
-  status?: string;
-  dateOfAppointment?: string;
-  dateOfAppointmentEnd?: string;
-  attendingAgentId?: string;
-  creatingAgentId?: string;
-  type?: string;
-  buyerName?: string;
-  [key: string]: unknown;
-}
-
-type Department = "sales" | "lettings" | "both";
-
-export async function viewingSearch(params: {
-  accountId: string;
-  department?: Department;
-  searchTerm?: string;
-  appointmentStartDate?: string;
-  appointmentEndDate?: string;
-  status?: string;
-  teamName?: string;
-  limit?: number;
-}): Promise<string> {
-  const {
-    accountId, department = "both", searchTerm,
-    appointmentStartDate, appointmentEndDate, status,
-    teamName, limit,
-  } = params;
-
-  const result = await aggregateAcrossTeams<LoopViewingSummary>(
-    accountId,
-    "viewings",
-    "loop-viewing-search",
-    async (apiKey, team) => {
-      const depts: string[] =
-        department === "both" ? ["sales", "lettings"] : [department];
-      const all: LoopViewingSummary[] = [];
-
-      for (const dept of depts) {
-        const qp: string[] = [];
-        if (searchTerm) qp.push(`SearchTerm=${encodeURIComponent(searchTerm)}`);
-        if (appointmentStartDate) qp.push(`AppointmentStartDate=${encodeURIComponent(appointmentStartDate)}`);
-        if (appointmentEndDate) qp.push(`AppointmentEndDate=${encodeURIComponent(appointmentEndDate)}`);
-        if (status) qp.push(`Status=${encodeURIComponent(status)}`);
-
-        const query = qp.length > 0 ? `?${qp.join("&")}` : "";
-        const path = `/residential/${dept}/viewings${query}`;
-        const data = await loopGet<LoopViewingSummary[]>(apiKey, path, "loop-viewing-search", team);
-        if (Array.isArray(data)) all.push(...data);
-      }
-      return all;
-    },
-    { teamName, limitPerTeam: limit ?? 50, limitTotal: limit ?? 200 }
-  );
-
-  return formatAggregationResult(
-    result,
-    (v) => {
-      const addr = v.propertyAddress ?? "Unknown property";
-      const id = v.id != null ? ` [ID: ${v.id}]` : "";
-      // dateOfAppointment is ISO datetime e.g. "2026-04-10T15:30:00"
-      const when = v.dateOfAppointment
-        ? formatDateTime(v.dateOfAppointment)
-        : "No date";
-      const viewStatus = v.status ? ` [${v.status}]` : "";
-      const buyer = v.buyerName ? ` — ${v.buyerName}` : "";
-      const viewType = v.type ? ` (${v.type})` : "";
-      return `- ${addr}${id} — ${when}${viewType}${buyer}${viewStatus}`;
-    },
-    "viewings"
-  );
-}
-
-function formatDateTime(iso: string): string {
-  const [datePart, timePart] = iso.split("T");
-  if (!timePart) return datePart;
-  return `${datePart} ${timePart.slice(0, 5)}`;
-}

package/payload/platform/plugins/loop/mcp/src/tools/viewing-update.ts

@@ -1,53 +0,0 @@
-import { loopPost, withTeamKey } from "../lib/loop-api.js";
-
-type Department = "sales" | "lettings";
-
-// Feedback parties map to swagger endpoints:
-// sales: buyer-feedback, seller-feedback
-// lettings: renter-feedback, landlord-feedback
-type FeedbackParty = "buyer" | "seller" | "renter" | "landlord";
-type Action = "note" | "feedback";
-
-// ─── Loop API V2: POST /residential/{dept}/viewings/{id}/{suffix}
-// Suffix: "note" for notes, "{party}-feedback" for feedback
-// Request body: { result: string } (StringResponse format)
-// Response: boolean success
-// ────────────────────────────────────────────────────────────────
-interface LoopBooleanResponse {
-  success?: boolean;
-  [key: string]: unknown;
-}
-
-export async function viewingUpdate(params: {
-  accountId: string;
-  teamName: string;
-  viewingId: number;
-  department: Department;
-  action: Action;
-  text: string;
-  feedbackParty?: FeedbackParty;
-}): Promise<string> {
-  const { accountId, teamName, viewingId, department, action, text, feedbackParty } = params;
-
-  if (action === "feedback" && !feedbackParty) {
-    throw new Error("feedbackParty is required when action is 'feedback'. Use: buyer, seller, renter, or landlord.");
-  }
-
-  await withTeamKey<LoopBooleanResponse>(
-    accountId,
-    teamName,
-    "viewings",
-    "loop-viewing-update",
-    async (apiKey) => {
-      const suffix = action === "note"
-        ? "note"
-        : `${feedbackParty}-feedback`;
-      const path = `/residential/${department}/viewings/${viewingId}/${suffix}`;
-      // Loop expects the text as a StringResponse body
-      return loopPost<LoopBooleanResponse>(apiKey, path, { result: text }, "loop-viewing-update", teamName);
-    }
-  );
-
-  const actionLabel = action === "note" ? "Note added" : `${feedbackParty} feedback recorded`;
-  return `${actionLabel} for viewing ${viewingId} (${department}) via team "${teamName}".`;
-}

package/payload/platform/plugins/loop/mcp/tsconfig.json

@@ -1,20 +0,0 @@
-{
-  "compilerOptions": {
-    "target": "ES2022",
-    "module": "Node16",
-    "moduleResolution": "Node16",
-    "lib": ["ES2022"],
-    "outDir": "dist",
-    "rootDir": "src",
-    "strict": true,
-    "esModuleInterop": true,
-    "skipLibCheck": true,
-    "forceConsistentCasingInFileNames": true,
-    "resolveJsonModule": true,
-    "declaration": true,
-    "declarationMap": true,
-    "sourceMap": true
-  },
-  "include": ["src"],
-  "exclude": ["src/**/__tests__/**", "src/**/*.test.ts"]
-}

package/payload/platform/plugins/loop/mcp/vitest.config.ts

@@ -1,9 +0,0 @@
-import { defineConfig } from "vitest/config";
-
-export default defineConfig({
-  test: {
-    environment: "node",
-    include: ["src/**/__tests__/**/*.test.ts"],
-    testTimeout: 10_000,
-  },
-});

package/payload/platform/plugins/loop/skills/compliance-flag-checker/SKILL.md

@@ -1,53 +0,0 @@
----
-name: compliance-flag-checker
-description: "Flag AML, GDPR, DMCCA 2024 material information, ASA/CAP advertising standards, and Equality Act risks in any output before the operator approves it. Cross-cutting skill called by every workflow that produces an outbound message, a listing, terms of business, or a payment batch. Owned by the compliance specialist."
----
-
-# Compliance flag checker
-
-A cross-cutting building-block skill. Runs against every output that touches a regulated surface (a portal listing, a terms-of-business document, an outgoing message to a buyer or vendor, a payment batch, the AML status on a deal). Returns a list of flags the operator should see before approval.
-
-## What it checks
-
-- **Material information.** DMCCA 2024 disclosure requirements for property listings: council tax band, tenure, ground rent and service charge if leasehold, property type, construction, utilities, heating, broadband, parking, and the wider Part C signals (flood risk, listed status, structural issues, planning permission, mining, and the rest). Missing items are flagged with the specific legislative requirement.
-- **Advertising standards.** ASA upheld-complaint patterns: fee transparency (VAT inclusion, mandatory surcharges disclosed), property descriptions accurate and substantiated, "local" claims supported, "leading" and "number one" claims substantiated.
-- **EPC display.** Asset rating present in any commercial media for the listing.
-- **AML state on the vendor.** Blocks a portal launch unless AML status is "passed" or the operator has explicitly overridden.
-- **GDPR.** Marketing messages to non-existing-client contacts checked for PECR opt-in basis. Data-retention prompts surfaced on close files.
-- **Equality Act.** Listing copy and outgoing messages checked for discriminatory phrasing (most commonly the "No DSS" pattern in lettings, court-declared as unlawful indirect discrimination).
-- **EAA s.21 personal interest disclosure.** Flags any output where the agent has a personal interest in the property and the disclosure has not been made.
-- **Renters' Rights Act 2025.** Where the workflow produces lettings output: bidding-ban compliance (must publish asking rent, must not request or accept above-advertised offers), discrimination ban (benefits, children), pet provisions, PRS database registration check, ombudsman membership display.
-- **Client money handling.** EAA 1979 ss.12 to 17 obligations on prescribed accounts, interest, trust requirements.
-
-## Output
-
-Each flag returns:
-
-- The cited legislation (Act, SI, regulation, code provision), with format like `[DMCCA 2024, Part 4, s.237]`
-- The specific issue
-- The remediation required
-- The penalty exposure for non-compliance
-
-The calling workflow surfaces the flags at the top of the staged output. The operator clears the flags or accepts the residual risk before approving.
-
-## What it does not do
-
-- It does not block approval. The operator decides; the skill informs.
-- It does not provide legal advice. Use "the legislation requires", "the regulatory position is", "this appears to fall short of". Never "you should" or "my advice is".
-- It does not certify a transaction or a listing as compliant. It flags gaps and cites requirements.
-- It does not amend the output it checks. Remediation is for the calling workflow or the operator.
-
-## Connectors
-
-Read: profile (compliance state, AML provider, scheme memberships), CRM (deal, vendor, listing), the deep-research tool when an unfamiliar provision needs verification.
-Write: none.
-
-## Profile keys
-
-- `realagent.compliance.cmp_scheme_membership`
-- `realagent.compliance.redress_scheme`
-- `realagent.compliance.ico_registration`
-- `realagent.compliance.mlro_designation`
-- `realagent.compliance.aml_provider`
-- `realagent.compliance.tpo_membership`
-- `realagent.compliance.propertymark_membership`

package/payload/platform/plugins/loop/skills/priority-ranker/SKILL.md

@@ -1,40 +0,0 @@
----
-name: priority-ranker
-description: "Order any list of items using the profile's urgency weights. Cross-cutting skill used by the morning round's top three and chase-progression's stalled list."
----
-
-# Priority ranker
-
-A cross-cutting building-block skill. Given a list of items with feature attributes, returns the same list ordered by relative urgency.
-
-## Inputs
-
-The calling workflow passes:
-
-- A list of items. Each item has a feature attribute map (for chase-progression, the features are risk score, fee value, days stalled, recipient type, and so on).
-- An optional cap on how many top items to return (the morning round uses 3).
-
-## What it does
-
-Reads the profile's weights for the relevant features. Returns the items in descending urgency order. If the cap is supplied, returns only the top N.
-
-For the top-three case the skill also returns, alongside each item, the feature that contributed most to its rank. The calling workflow uses that feature to write the reason sentence the operator reads ("Mrs Patel, her buyer's mortgage offer expires in 9 days and the survey was booked but not done").
-
-## Learning
-
-When the operator actions a different item than the top-ranked one within the same session, the weighting reweights toward whatever feature distinguished the actioned item. Slow signal, high quality. All writes go through `profile-writer`.
-
-## What it does not do
-
-- It does not generate the reason sentence. That is `variance-narrator`.
-- It does not decide what to do with the ranked items. The calling workflow owns that.
-- It does not write to the CRM.
-
-## Connectors
-
-Read: profile (weights). No writes.
-
-## Profile keys
-
-- `realagent.priority_weights.*` (per feature, learned)
-- `realagent.priority_weights.fee_multiplier`

package/payload/platform/plugins/loop/skills/tone-matched-drafter/SKILL.md

@@ -1,53 +0,0 @@
----
-name: tone-matched-drafter
-description: "Draft a message in the operator's voice for a specific recipient type and channel. Cross-cutting skill used by chase-progression, new-instruction (vendor welcome), and any other workflow that needs an outgoing message. Never sends; the calling workflow owns the send gate."
----
-
-# Tone-matched drafter
-
-The cross-cutting skill that produces every outgoing message in Real Agent. The deepest learning hook in the product: edit-before-send diffs feed back here.
-
-## Inputs
-
-The calling workflow passes:
-
-- Recipient type (vendor familiar, vendor formal, buyer familiar, buyer formal, vendor solicitor, buyer solicitor, mortgage broker, surveyor, photographer, EPC supplier, floorplan supplier, accountant, other)
-- Channel (WhatsApp, email, SMS, or "infer from recipient")
-- Intent (chase the solicitor on searches, welcome a new vendor, request a viewing, confirm a meeting, and so on)
-- Reference data (the deal record, the property record, the contact's prior messages)
-
-## What it does
-
-Reads the profile's tone preference for the recipient type and the agent's voice samples. Drafts a message that matches:
-
-- The agent's vocabulary (the words they actually use)
-- The agent's sentence length and rhythm
-- The agent's preferred greeting and sign-off for the recipient type
-- The phrases the agent has previously edited out (the pet-peeve list), which are never included
-- The channel's constraints (WhatsApp templating for first contact, email subject lines, SMS character limits)
-
-The draft is returned to the calling workflow with the channel decision attached. The workflow decides when to surface the draft to the operator and when to fire on approval.
-
-## What it does not do
-
-- It never sends. The calling workflow owns the send gate.
-- It does not negotiate. Drafts are messages the operator would send; negotiating substance is the operator's decision.
-- It does not invent facts. Every reference to a number, name, or date is read from the deal record or the connector. If a field is missing, the draft says so explicitly and the operator fills it.
-
-## Learning
-
-Every time the operator edits a draft before approval, the diff is captured and weighted into the profile's tone preference and pet-peeve list. Within a quarter, the workflow should produce drafts the agent sends without editing 80% of the time on the common recipient types.
-
-## Connectors
-
-Read: profile (tone, voice samples, pet peeves, channel preferences), CRM (deal and contact records).
-Write: none. The calling workflow handles sends.
-
-## Profile keys
-
-- `realagent.tone_profile.*` (per recipient type)
-- `realagent.voice_samples`
-- `realagent.phrasing_pet_peeves`
-- `realagent.channel_preference.<recipient_id>`
-- `realagent.tone_profile.greetings.*`
-- `realagent.tone_profile.signoffs.*`

package/payload/platform/plugins/loop/skills/variance-narrator/SKILL.md

@@ -1,50 +0,0 @@
----
-name: variance-narrator
-description: "Write short prose summaries of numerical changes. Used by the morning round to write the cause sentence under each stalled deal, and by month-end-close to write the two paragraphs comparing the period to the prior month and the same period last year."
----
-
-# Variance narrator
-
-A cross-cutting building-block skill. Turns a set of numbers and structured events into a sentence or short paragraph in plain English, in the agent's voice.
-
-## Two output shapes
-
-### Cause sentence (used by morning round and chase-progression)
-
-Given a deal's state, produces one short sentence that names the most likely cause of the stall. The skill picks the pattern that fits the observable signals, not the one that sounds most dramatic. Examples:
-
-- "Mortgage offer expires in 9 days and the survey was booked but not done."
-- "Searches outstanding at day 28; solicitor last contacted day 14."
-- "Vendor unresponsive since day 12; buyer's broker has chased twice."
-
-If no pattern fits, the sentence reads "no clear cause from connectors, manual check recommended". The skill never invents a cause it cannot trace to data.
-
-### Variance paragraphs (used by month-end-close)
-
-Given the period's reconciliation totals and the two comparison periods (prior month, same month last year), produces two paragraphs in plain language with no jargon. Example:
-
-> April was GBP 8,400 down on March because three completions slipped into May, all expected to land. The reconciliation matched cleanly otherwise; the only variance was a GBP 120 referral deduction on the Norton sale.
->
-> Year-on-year April is 15% up on the same month last year. The increase came from two completions over GBP 8,000 fee value, both new instructions taken in February.
-
-The paragraphs are suitable to paste into a board update, a tax-return cover note, or a conversation with a partner.
-
-## Voice source
-
-Reads the profile's voice samples and the operator's prior narrative paragraphs. Learns from edit-before-approve diffs.
-
-## What it does not do
-
-- It does not write outgoing messages. That is `tone-matched-drafter`.
-- It does not produce numerical totals. The calling workflow passes the numbers in; this skill writes the prose around them.
-- It does not write to the CRM or the accounting platform.
-
-## Connectors
-
-Read: profile (voice samples, narrative voice). No writes.
-
-## Profile keys
-
-- `realagent.voice_samples`
-- `realagent.close.narrative_voice_samples`
-- `realagent.cause_phrases`

package/payload/platform/plugins/loop/skills/vendor-research/SKILL.md

@@ -1,54 +0,0 @@
----
-name: vendor-research
-description: "Public-record and CRM-history lookup on a vendor, with the profile's privacy line enforced. Used in valuation-prep, in new-instruction AML staging, and in chase-progression when a vendor goes silent. Surfaces useful context; flags sensitive signals separately."
----
-
-# Vendor research
-
-A cross-cutting building-block skill. Looks the vendor up across the sources the platform has access to and returns a structured summary with the privacy line applied.
-
-## What it looks at
-
-- Land Registry: ownership history, joint owners, transactions
-- The agency's CRM history with this vendor and with the property
-- Council planning portal: planning applications and decisions for the property
-- The portal record if the property has been listed before
-- Public probate registry where relevant
-- Public news sources via the deep-research tool when the brief warrants it
-
-## The privacy line
-
-The profile holds a privacy preference. Default behaviour:
-
-- **Surface.** Ownership and planning history.
-- **Flag-but-suppress.** Deaths registered against the address, ownership changes that correlate with bereavement, planning disputes, anything that the agent could not quote in the appointment without harming their reputation.
-
-The flag-but-suppress signals are not deleted; they are summarised at the top of the output as "n suppressed signals exist on this address, available on request". The operator can say "show me everything you find" to see them, or "drop the sensitive stuff" to remove the heading entirely.
-
-## Output shape
-
-A structured summary with:
-
-- How long the vendor has owned
-- Last purchase price
-- Joint owners on the title
-- Planning history (one-line per material event)
-- Prior listings (agent, asking price, sold or withdrawn)
-- CRM history with this agent
-
-Plus the suppressed-signal heading if any apply.
-
-## What it does not do
-
-- It does not draft anything to send to the vendor. That is `tone-matched-drafter`.
-- It does not produce a valuation. That is `pricing-scenario-builder`.
-- It does not write to the CRM. The calling workflow stores anything it wants kept.
-
-## Connectors
-
-Read: Land Registry, planning portal, CRM, portal data, probate registry, deep-research tool. No writes.
-
-## Profile keys
-
-- `realagent.privacy_line.surface` (list of signal types)
-- `realagent.privacy_line.suppress` (list of signal types)

package/payload/platform/plugins/preval/.claude-plugin/plugin.json

@@ -1,8 +0,0 @@
-{
-  "name": "real-agent-preval",
-  "description": "Single-address pre-valuation pitch pack. One full UK address in, 5-page A4 PDF out (cover · subject valuation · market context · comparables · recently with <brand>). Consumes the real-agent-property-data and real-agent-epc MCPs — no MCP tools of its own.",
-  "version": "0.1.0",
-  "author": {
-    "name": "Rubytech LLC"
-  }
-}

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

@@ -1,47 +0,0 @@
----
-name: real-agent-preval
-description: "Single-address pre-valuation pitch pack. One full UK address in, 5-page A4 PDF out (cover · subject valuation · market context · comparables · recently with <brand>). Consumes the real-agent-property-data and real-agent-epc MCPs — no MCP tools of its own."
-skills:
-  - skills/property-preval/SKILL.md
-always: false
-metadata: {"platform":{"optional":true,"embed":["admin"]}}
----
-
-# Real Agent — Preval
-
-Consumer sub-plugin. No MCP server, no new tools — only a skill (`property-preval`) that takes one full UK address plus operator-supplied brand tokens, subject details, agent listings, and a market summary, and renders a **5-page A4 pre-valuation PDF** designed as a sales pitch for the listing.
-
-## What it produces
-
-A 5-page A4 PDF and the source HTML, written to `~/Documents/Maxy/preval/<postcode-compact>-<YYYY-MM-DD>/`:
-
-- **Page 1 — Cover.** Full-bleed subject hero photo with gradient scrim. Light brand wordmark top-left. Address in display-italic. Postcode chip. Four-up meta strip (Report · Address · Postcode · Generated). Lifted from the `property-market-report` cover contract.
-- **Page 2 — Subject valuation.** KPI strip (floor area, bedrooms, EPC rating, type). Valuation panel: headline range = `subject.sqft × sold £/sqft 70pc band` (Land Registry), asking £/sqft cross-check, operator adjustments (`subject.adjustments[]`) shown as a stacked list with colour-coded percentages, final indicative range pill. `subject.sqft` is required — a null value aborts the run.
-- **Page 3 — Market context.** Market summary headline + paragraphs with drop cap. KPI strip (avg asking £, avg sold £, £/sqft). Price-growth panel (YoY) + demand pill with gauge. 7-year sparkline of £ and £/sqft. Same patterns as `property-market-report`.
-- **Page 4 — Comparables.** Full-width Land Registry sold-transactions table (≤ 6 rows), stacked above a full-width live-asking-comparables tile grid (≤ 4 tiles). Never side-by-side — corrects the cramped two-column layout in v1 preval.
-- **Page 5 — Recently with `<brand>` + sources.** Operator-curated `agent_listings[]` rendered as a clickable tile grid with status badges (Sold / Under offer / For sale), then the sources & methodology block. The vendor reads this page and knows who to call.
-
-## Tool dependencies
-
-The skill fans out to **13** MCP calls in parallel:
-
-- **12 PropertyData** tools (postcode-keyed): `prices`, `prices-per-sqf`, `sold-prices`, `sold-prices-per-sqf`, `growth`, `growth-psf`, `demand`, `demand-rent`, `property-types`, `crime`, `flood-risk`, `council-tax`.
-- **1 EPC** tool (address-keyed): `epc-lookup-by-address` for subject floor area + energy rating + lodgement date.
-
-`property-data-address-match-uprn` and `property-data-planning-applications` are deliberately not called (CRM hygiene and dev-precedent reports, respectively).
-
-## Failure handling
-
-Every failure is fail-loud. The skill emits `[preval] aborted reason=<cause> …` and exits 2; no partial `index.html` or PDF is left on disk.
-
-- **PropertyData `key-not-registered`** → abort `reason=property-data-key-not-registered` with the `property-data-key-register` remediation hint.
-- **PropertyData `http-429`** → back off and retry the single throttled tool once. A second `http-429` aborts `reason=property-data-rate-limited`.
-- **PropertyData `http-5xx` / network failure** → abort `reason=property-data-unavailable`.
-- **EPC failure of any kind** — `key-not-registered`, `http-404 (no record)`, `http-429`, `http-5xx`, network failure, EPC MCP not configured — aborts the run. There is no in-band prompt and no benchmark-only mode. The operator's options before re-running are (a) run Task 155 to deploy / register the EPC MCP, or (b) paste `subject.sqft` and `subject.sqft_m2` into the inputs as a deliberate operator override.
-- See `skills/property-preval/SKILL.md` § Hard breakpoints for the full table of abort causes.
-
-## External dependencies
-
-- Requires `real-agent-property-data` enabled on the account with a registered PropertyData API key (`property-data-key-register`).
-- Requires `real-agent-epc` enabled with a registered EPC API key (`epc-key-register`), **or** an operator-supplied `subject.sqft` + `subject.sqft_m2` override pre-baked into the inputs. EPC failures are not silently absorbed.
-- Requires Google Chrome at `/Applications/Google Chrome.app/Contents/MacOS/Google Chrome` for headless `--print-to-pdf`. Same Chrome dependency as `property-market-report`.