You're running the PageHub workflow "Write from my real reviews" on site <your site id>.
- Pass `id: "<your site id>"` on every PageHub tool call (the Stripe and checkout tools name it `siteId: "<your site id>"`).
- Every change stages in the site's draft. Never call `publish_site` unless the user says to publish.
- Finish by showing the proof: Phone screenshots of the home page before and after, the new testimonials with where each quote came from, and the old and new wording for every line of copy changed.
- Keep to about 12 minutes of work. If more is left, list it and stop.
- Draft preview: https://pagehub.dev/view/<your site id>
- This needs the PageHub connector (https://pagehub.dev/api/mcp). If its tools aren't available, tell the user to add it and stop.

Goal: put this business's real reviews on site <your site id> and use the
customers' own words to make the hero and service copy more specific.

The reviews, exactly as the user gave them:

(not given)

The file of reviews: (not given)
Reviews page link: (not given)
Keep exactly as is: (not given)

An attached file arrives in this chat as an "I've attached N file(s)" block
with its contents (tables as a preview, documents in full); those rows or
lines are the reviews, the same as pasted text. A file that is only named or
linked, not attached, you can't read.

The one rule that overrides everything below: every quote, name, date and star
rating on the site must come from the reviews above. Never write a review,
"improve" a quote, merge two reviews, add a name that wasn't given, or show a
star rating that wasn't given. You may shorten a quote by cutting whole
sentences, and mark a cut inside a sentence with "...". If no reviews were
pasted and no file is attached, or what you have aren't reviews, stop and ask
for them.

## 1. Read the reviews and the site (read-only, about 3 minutes)

1. Split the pasted text or the file's rows into separate reviews. For each one note the
   reviewer name as written (or none), the star rating (or none), the source
   (Google, Yelp, email, or unknown) and the date if shown. Leave out reviews
   under 3 stars; never quote a complaint.
2. Pull out the customers' language: the problem they came in with, what they
   praised by name (a person, a service, speed, price, honesty), and phrases
   that more than one review repeats. These are the raw material for copy.
3. `list_pages`, then `read_site_file` on the home page's file to see its
   sections in order.
4. `search_site_files` for "testimonial", "review", "customers say"
   and "what our". Template sites often ship with made-up testimonials (names
   like "Sarah J.", "John D."). `read_site_file` on any file you find.
5. `screenshot_site` of the home page at `width: 390`, `fullPage: true`. This
   is the "before" picture.

## 2. Testimonials (about 5 minutes)

Pick 3 to 6 reviews: the most specific ones, not the most gushing, and cover
different services where you can.

If the site already has a testimonials section:
- Replace its quotes, names and ratings with the real ones in one
  `edit_site_files`. Delete leftover placeholder cards in the same edit so
  nothing made-up stays. If there are fewer real reviews than cards, remove the
  extras rather than repeating a review.
- Remove any star icons on a card whose review had no rating, and any company
  logos or photos of people that don't belong to that reviewer.

If there isn't one, build it:
- `search_blocks` with `category: "testimonials"` and `get_block` on one
  that fits the site's look, as a reference only. Then write the section into
  the home page file with `edit_site_files`, placed after the services or
  features section (before the final call-to-action).
- Match the neighbouring sections: same section root pattern (`w-full`, a
  `bg-*` palette token with its matching `text-*-content`, `px-container-x`,
  the neighbours' `py-space-*` padding, no `md:py-*`) and an inner wrapper with `max-w-page
  mx-auto w-full`. Palette tokens and spatial tokens only. Read
  `get_style_reference` with `topic: "design"` if unsure.
- Each card: the quote in a `<p>`, the name and source in a separate element,
  and stars only when the review gave a rating (that many `tb/TbStarFilled`
  icons through the site's icon filter, in a wrapper with an `aria-label` like
  "5 out of 5 stars"). A source logo, if wanted, comes from `find_icon`.
- Reviews page link given: add an `<a>` "Read more reviews on Google" (or the
  right site) with that `href`, `target="_blank"` and `rel="noopener"`.
- Don't add review or rating JSON-LD. Google ignores reviews a business shows
  about itself and it can count against the site.

## 3. Copy from the customers' words (about 2 minutes)

Change at most 6 lines in total, all on the home page and service sections,
in one `edit_site_files`:
- The hero subheading (not the main headline unless it is generic, like
  "Welcome to our website"): name the problem customers came in with and the
  thing they praise most, in their words.
- Service or feature descriptions that are generic ("Quality service you can
  trust"): rewrite each from what reviews say about that service.
- Never copy a line you are going to quote word for word into the hero; use the
  idea, not the testimonial.
- Keep everything listed under "Keep exactly as is". Keep the same length
  roughly, so the layout doesn't shift, and don't add claims the reviews don't
  support (no "#1 in town", no years in business you weren't told).

## 4. Prove it (about 2 minutes)

1. `audit_accessibility` on the home page with `level: "AA"`, to check the new
   section's contrast and that each star group has a label.
2. Re-take the home page screenshot at `width: 390`, `fullPage: true`, and
   compare with "before". Undo anything that broke the layout.

## 5. Report

Reply with:
- The testimonials now on the site, each with who wrote it and where it came
  from, and which reviews you left out and why.
- Every line of copy you changed: old wording, then new wording.
- The draft preview link (the `Draft preview:` address `screenshot_site` prints; never one you build), and a question: publish these changes now? Only on a
  yes, `publish_site`.
