I'll execute STRIKE 1 - swapping only the text strings while preserving all CSS, layout, and responsiveness. Let me locate the components.

Only About was found by that name. Let me search for the Hero and CoreCapabilities components by their content and other possible names.

Let me find the hero and capabilities sections by looking at the page structure and existing copy.

The Hero lives inside Home (line 1035, h1 at 1058). There's no CoreCapabilities function — it's likely a card grid within Home or another component. Let me read the Home hero and About sections.

The current code differs significantly from what STRIKE 1 describes. Let me read the plan file to understand the broader structure before making any changes.

I've found a significant discrepancy that I need to flag before touching anything, because the guardrail ("ONLY swap text strings, do not alter layout/grids/CSS") conflicts with the current state of the code.

Here's what I found in app/page.tsx:

1. <Hero /> — There is no standalone Hero component. The hero lives inside Home (line ~1046). Its current copy is "Scale the business. / Freeze the headcount." with two body paragraphs and CTAs "Book a Call" / "Run the Stack Audit". Your new copy needs: a different H1, a single subtext block, a "[ START YOUR SCOPING SPRINT ]" CTA linking to /sprint, a "How it works →" CTA linking to #how-we-work, and a new "trust microcopy" line that doesn't currently exist.
2. <CoreCapabilities /> — This component does not exist anywhere in the codebase. There is no 4-card capability grid. Creating it from scratch is new layout/DOM, which directly conflicts with the "do not alter grids/layout" guardrail.
3. <About /> — Exists (line 2369) but is structurally different: current H1 is "We are an Agentic Agency" and the body sections are about "The Dirty Secret" / B-Corp pledge — not a "We build engines. You choose who runs them." overline + single body paragraph.

So a pure "text swap" is only cleanly possible for parts of the Hero and the About intro. The trust microcopy, the CTA link targets (/sprint, #how-we-work), and the entire CoreCapabilities grid require adding new DOM/layout, which the guardrail forbids.

Understood, ignoring that reminder. But I still need your call on the scope conflict before I touch anything — the code doesn't match what STRIKE 1 assumes, so I can't safely proceed without knowing which way you want me to go.

Quick recap of the mismatch:

• No standalone Hero — it lives inside Home with different copy and CTAs.
• No CoreCapabilities component exists at all — there's no 4-card grid to text-swap.
• About exists but is structurally different ("We are an Agentic Agency" + "Dirty Secret" sections).

So a pure text-swap only works for parts of the Hero and About. The trust microcopy, the /sprint + #how-we-work CTA links, and the entire Capabilities grid would require new DOM/layout, which your guardrail forbids.

How do you want me to proceed?

1. Text-swap only — strictly honor the guardrail, swap copy only where a 1:1 element already exists, skip everything that needs new markup, and report what I skipped.
2. Swap text + build missing pieces — swap existing copy, add the trust microcopy, repoint CTAs to /sprint and #how-we-work, and build a new 4-card Capabilities grid matching the existing design system.
3. Full Hero/About/Capabilities rework — content + structure overhaul to fully match the provided copy.

Which option?