Install the Buying Buddy IDX Plugin in HighLevel Ai Studio With AI

Before you do anything, ask me for my Buying Buddy Activation Key (also called my ACID) and wait for my answer. It is on the Add Plugin tab of my Buying Buddy dashboard. Do NOT guess it or proceed without it. Everywhere the instructions below show [YOUR_ACTIVATION_KEY], use exactly the key I give you.

You are installing the Buying Buddy real-estate IDX plugin in this React (Vite + TypeScript) project. This is the STEP-1 prompt of a 5-step install - it ONLY installs the package and the provider. Do NOT create any pages or place any widgets yet; those come in the next prompts.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

ACTIVATION KEY: [YOUR_ACTIVATION_KEY]

BEFORE YOU START - check the existing setup and STOP if any of these are true:
1. The Buying Buddy package is ALREADY installed - the npm package "@buyingbuddy/react" is present in package.json. If so, STOP: do not install anything or change any files. Tell me Buying Buddy is already installed, and that I should use the "Update" prompt to update it, or continue with the later step prompts in my Buying Buddy dashboard.
2. The older JavaScript plugin is installed - a Buying Buddy <script> tag in the site's custom code / page head, and/or widgets placed as <bb-widget> elements (for example <bb-widget data-type="SearchResults">). If so, STOP: do not change any files. Tell me I must use the Buying Buddy Migration prompt to convert the old JavaScript install, and point me to the "Fix Incorrect Installation" options in the Utility Prompts section of this Add Plugin tab.
If any case above applies, output only that message and do nothing else. If none apply, continue with the install below.

Do ALL of the following (mandatory):
1. Install the npm package: @buyingbuddy/react
2. Wrap the whole app in the provider at the app root (src/main.tsx or src/App.tsx):
   <BuyingBuddyProvider activationKey="[YOUR_ACTIVATION_KEY]"> ... </BuyingBuddyProvider>
3. Confirm the project still builds with no errors. If the install introduced a build error, tell me exactly what it is and STOP - do not refactor anything to fix it.

Do NOT ask me any questions - perform the steps above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

End your reply with this exact line:
➡️ Next Step! Copy the Step-2 prompt from the Add Plugin tab in your Buying Buddy dashboard and paste it here.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are continuing the Buying Buddy plugin install in this project. This is the STEP-2 prompt of a 5-step install - it creates the two foundation pages and the footer disclaimer. The package and provider were installed by the Step-1 prompt.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

BEFORE YOU START - verify the Step-1 prompt was completed. Check that BOTH of these are true:
1. The npm package "@buyingbuddy/react" is present in package.json.
2. A <BuyingBuddyProvider> wraps the app at the app root.
If either is missing, STOP: make no changes, and tell me to run the Step-1 prompt from my Buying Buddy dashboard first.
Also STOP (make no changes, and tell me this prompt has already been run) if a route already exists at "/listing-results" or "/listing-details" rendering a Buying Buddy widget.
If no STOP case applies, continue with the steps below.

Do ALL of the following (mandatory):
1. Create a Search Results foundation route at "/listing-results". Render it inside the site's existing page layout so the normal header, navigation, and footer still appear (use the same layout / <main> wrapper as the rest of the site - do NOT produce a bare standalone page). Add a page heading - an <h1> such as "Search Results" - inside a normal constrained container. Immediately below the heading, place the widget inside a FULL-WIDTH container so it can span 100% of the viewport, and add standard responsive horizontal padding to that container so the widget does not bleed to the screen edges (e.g. <div className="w-full px-4 sm:px-6 lg:px-8">). This widget is the only Buying Buddy / listing component on the page - do not hand-build any listing UI around it:
   <BuyingBuddyWidget type="ListingResults" />
2. Create a Property Details foundation route at "/listing-details" the same way - inside the existing site layout (header, navigation, footer), with an <h1> such as "Property Details" inside a normal constrained container, and the widget placed immediately below it within that same standard constrained container (do NOT use a full-width container for this page - keep it constrained). This widget is the only Buying Buddy / listing component on the page:
   <BuyingBuddyWidget type="SearchDetails" />
3. Add the disclaimer to the site footer so it shows on every page:
   <BuyingBuddyWidget type="Disclaimer" />

Do NOT ask me any questions - perform the steps above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

End your reply with this exact line:
➡️ Next Step! Copy the Step-3 prompt from the Add Plugin tab in your Buying Buddy dashboard and paste it here.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are finishing the Buying Buddy plugin install in this project. This is the STEP-3 prompt of a 5-step install - it adds the home-page search form, measures the header offsets, and ends with the settings I must enter in my Buying Buddy dashboard.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

BEFORE YOU START - verify the Step-1 and Step-2 prompts were completed. Check that ALL of these are true:
1. The npm package "@buyingbuddy/react" is present in package.json.
2. A <BuyingBuddyProvider> wraps the app at the app root.
3. The two foundation pages exist (a Search Results route rendering <BuyingBuddyWidget type="ListingResults" /> and a Property Details route rendering <BuyingBuddyWidget type="SearchDetails" />).
If anything is missing, STOP: make no changes, and tell me which earlier step prompt I need to run first.
If everything is present, continue with the steps below.

Do ALL of the following (mandatory):
1. Add a property search form to the existing home page, rendered inside the normal site layout (header, navigation, footer). Use the QuickSearch widget:
   <BuyingBuddyWidget type="QuickSearch" filter="formType:simple1+formBackground:204,204,204,0.17+formBorder:204,204,204,0.40+advancedSearch:on" />
   - You MAY change ONLY the RGBA values of formBackground and formBorder inside the filter string above, so the search panel visibly stands out against the home page background. Do NOT add any CSS, styled wrappers, or any other visual changes to the home page - placing this widget and tuning those two filter values is the entire scope of this step.
2. Determine whether this site has a STICKY or FIXED header (a header/nav bar that stays pinned to the top of the screen while scrolling - typically position:fixed or position:sticky).
   - If it does NOT, no header offset is needed - you will omit the Widget Header Offset item from the final block below, exactly as its instructions describe.
   - If it DOES, measure the rendered height of that header in pixels at three viewport widths: Mobile (viewport < 768px), Tablet (viewport 768px-991px), Desktop (viewport >= 992px). If the height is the same at all sizes, use the same number three times. These values prevent map widgets (which are sticky) from being hidden under the header. Do NOT report these numbers separately or inline anywhere - report them ONLY inside the final block described below.

Do NOT ask me any questions - perform the steps above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

The Buying Buddy widgets only load on authorized domains, so my preview will show blank widgets until I finish setup in my Buying Buddy dashboard.

BEFORE you show the final block, derive these two values (do NOT skip this):
(a) My Vibe Preview Domain. Every Ai Studio project has a preview domain with the exact syntax preview-{PROJECT_ID}.vibepreview.com, where {PROJECT_ID} is this project's long, purely numeric project ID (roughly 19 digits). Find the project ID by looking in this project (start with index.html) for any asset URL on `vibe.filesafe.space` - the long all-digits segment in that URL is the project ID (ignore the shorter alphanumeric segment). Example: an image URL like `https://vibe.filesafe.space/4f0ngmsfff/1780794507926176087/image.jpg` gives a Vibe Preview Domain of `preview-1780794507926176087.vibepreview.com` (no https://). Verify your result matches the pattern preview-<digits>.vibepreview.com exactly before using it. If you cannot find any `vibe.filesafe.space` URL in this project, do NOT guess or invent an ID: in item 2 of the final block, output this instruction instead of a domain: "Click the Open-in-new-tab icon on your Ai Studio preview - the domain it opens (preview-{PROJECT_ID}.vibepreview.com) is your Vibe Preview Domain."
(b) The three Widget Header Offset numbers (Mobile, Tablet, Desktop) you measured above - only if this site has a sticky or fixed header.

You MUST end your response with the block below - this is required, not optional. Replace every bracketed placeholder (the [TOKENS_IN_CAPS]) with the real value you derived. Do NOT print the placeholder text itself, and do NOT wrap the values in any kind of brackets in your output. If this site has NO sticky or fixed header, omit item 3 entirely and show only items 1 and 2.

⚠️ Important: Action Required Before Previewing
The Buying Buddy widgets only load on authorized domains, so your preview will show blank widgets until you complete these steps. In your Buying Buddy dashboard, open "Website Options" and set the following (all three are on that one page):

1. Website Type
   Set this to: HighLevel Ai Studio

2. Vibe Preview Domain (no https://):
   [VIBE_PREVIEW_DOMAIN]

3. Widget Header Offset values:
   Mobile: [MOBILE_OFFSET], Tablet: [TABLET_OFFSET], Desktop: [DESKTOP_OFFSET]

➡️ Next Step! Enter the settings above in your Buying Buddy dashboard, then copy the Step-5 "Add Recommended Widgets" prompt from the Add Plugin tab and paste it here. You will be able to select which widgets to add.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are adding recommended Buying Buddy widgets to a website that ALREADY has the Buying Buddy plugin installed (the @buyingbuddy/react package and a <BuyingBuddyProvider> at the app root). This is the FINAL (Step-5) prompt of the install - do NOT reinstall the package or repeat the base install.

BEFORE YOU START: confirm the Buying Buddy package is installed - check package.json for "@buyingbuddy/react". If it is NOT present, STOP and tell me to run the Step-1 install prompt from my Buying Buddy dashboard first. Do not make any changes.

Important - how Buying Buddy widgets are styled (read before touching any CSS): Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles, so there is NO styling conflict to prevent. Do NOT rename, remap, prefix, scope, or modify any site CSS, design tokens, CSS variables, Tailwind config, theme, or shared UI components. In THIS prompt you MAY add new pages, add links to the site navigation menu, and add one small bar to the site header - and nothing else structural. If this project has no conventional navigation menu or site header to edit (for example a bare codebase), do NOT invent one - tell me which item you could not place, skip it, and continue with the rest.

ASK ME which widgets to add before making any changes. Present the choice exactly as follows - do not design your own format:
- If your chat environment can render interactive checkboxes, show a checkbox list with one checkbox per widget, ALL PRE-CHECKED, using exactly these six labels in this order: Search Page / Featured Listings / Home Value Form / Contact Me Form / About Me Page / Register & Login Bar. Add this one line above the list: "These are all recommended - uncheck any you don't want, then confirm."
- If interactive checkboxes are NOT available, show the same six labels as a numbered list (1-6) and ask me to reply with "all" or the numbers I want.
Wait for my selection, then add ONLY the widgets I selected and skip the others entirely.

For EACH PAGE widget (items 1-5), follow these rules every time:
- Create a NEW page, rendered inside the existing site layout (header, navigation, footer). Add a page heading - an <h1> equal to the page title shown in quotes - and place the widget directly below it inside the normal CONSTRAINED page container (NOT full-width).
- Add the new page to the site navigation menu.
- CONFLICT HANDLING: never modify an existing page. If a page with the same title or URL/slug already exists, create a NEW page with a modified name instead - append a short suffix to BOTH the title and the slug (for example "Contact Me" -> "Contact Me (Buying Buddy)", slug "/contact-me" -> "/contact-me-bb") - and add that new page to the menu.

1. Page title "Search" - a property search page. This is IN ADDITION TO the search form already on the home page; do NOT remove or change the home page search form:
   <BuyingBuddyWidget type="SearchForm" />
2. Page title "Featured Listings":
   <BuyingBuddyWidget type="FeaturedGallery" />
3. Page title "Home Value" - a home valuation lead-capture form:
   <BuyingBuddyWidget type="LcForm" filter="form:cmashort+title:Do You Know What Your Home Is Worth+description:Values have increased in your area. Find out how much your home is worth now!" />
4. Page title "Contact Me" - a contact lead-capture form:
   <BuyingBuddyWidget type="LcForm" filter="form:contactme+title:Send A Message" />
5. Page title "About Me" - shows the agent bio, profile and listings:
   <BuyingBuddyWidget type="Brokers" />

6. Register / Login bar - this is NOT a page. Add it to the site header:
   <BuyingBuddyWidget type="LoginPanel" filter="layout:registerlinks" />
   - Create a small top utility bar as a NEW ROW above the existing header content and place this widget in it (typically aligned to the right). It shows a "Register | Login" link.
   - The font-size of the container you place this widget in must be no larger than the font-size of the main menu items.

After making the changes:
- If you added the top utility bar (item 6) and it changed the height of the site header, recalculate the Widget Header Offset values: measure the rendered header height in pixels at three viewport widths and give me the three numbers to enter in my Buying Buddy dashboard - Mobile (viewport < 768px), Tablet (viewport 768px-991px), Desktop (viewport >= 992px). Report them exactly like this: "Header Offset -> Mobile: 56, Tablet: 64, Desktop: 72" (if the height is the same at all sizes, give the same number three times). If item 6 was not added, or the header height did not change, tell me no header offset change is needed.
- Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and then publish or deploy it when I am ready.

Constraints:
- Do NOT change existing routing or unrelated code, and do NOT modify any existing pages.
- Do NOT edit, rename, remap, or reorganize CSS variables / design tokens, global stylesheets, tailwind config, theme files, or shared UI components. Buying Buddy widgets are shadow-DOM isolated. The ONLY structural changes allowed are: adding the new pages, adding their links to the navigation menu, and adding the small top utility bar for the login widget.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

Please update the Buying Buddy package in this project to the latest version. Do exactly this and nothing else:

1. Run: npm install @buyingbuddy/react@latest
2. Confirm the new version that was installed (tell me the version number from package.json).
3. Do not change any of my code — do not modify, move, or "improve" my <BuyingBuddyProvider>, my <BuyingBuddyWidget> components, my routes, my CSS, design tokens, Tailwind config, or any other files. This is a package version update only.
4. Confirm the project still builds with no errors. If the update introduced a build error, tell me what it is and stop — do not start refactoring to fix it.
5. Do not publish the site. I will preview and publish myself.

When you're done, give me a short summary: the version you upgraded from and to, and confirmation that the build passes and no other files changed.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are adding the Buying Buddy MLS Disclaimer widget to a website that ALREADY has the Buying Buddy plugin installed. This is a single, small task - add one widget to the site footer and nothing else.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

BEFORE YOU START - check that BOTH of these are true:
1. The npm package "@buyingbuddy/react" is present in package.json.
2. A <BuyingBuddyProvider> wraps the app at the app root.
If either is missing, STOP: make no changes, and tell me to run the Step-1 install prompt from my Buying Buddy dashboard first.
Also STOP (make no changes, and tell me it is already in place) if the site footer already contains <BuyingBuddyWidget type="Disclaimer" />.
If no STOP case applies, continue below.

Do the following (mandatory):
1. Add the disclaimer to the site footer so it shows on every page:
   <BuyingBuddyWidget type="Disclaimer" />

Do NOT ask me any questions - perform the step above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are running a READ-ONLY audit of this HighLevel Ai Studio (React + Vite + TypeScript) project. Your job is to find every Buying Buddy component that has been added and produce a single report I can copy and send to Buying Buddy support. You will CHANGE NOTHING.

IMPORTANT - this prompt is READ-ONLY. Do NOT create, edit, move, rename, delete, install, uninstall, reformat, refactor, or "fix" anything. Do NOT run npm install, a build, a publish, or a deploy. There is nothing for me to approve, because you will make no changes. If you spot something that looks wrong or broken, DESCRIBE it in the report - do not act on it.

Do NOT ask me any questions - inspect the project and produce the report automatically.

WHAT TO LOOK FOR

Search the whole project (start with index.html and the src/ tree) for each of the following. For every item, note the file path and - where you can tell - the location: which page/route it belongs to, or whether it is in a shared header, footer, or layout component.

1. The Buying Buddy JavaScript plugin block. This normally sits in index.html (in the <head>) and looks similar to this (values will differ):

       <!-- Buying Buddy plugin v5.02 for HighLevel; Authorized Domain: example.com -->
       <!-- ** DO NOT DEFER ** This must load at the top of the page, e.g. in the page head. -->
       <script src="https://www.mbb2.com/version3/css/theme/acid/XXXXXXXX"></script>
       <script>
         var MBB = {seo : "false", data:{ acid : "XXXXXXXX" } };
         function mbbMapLoaded(){ MBB.googleMaps = true; };
       </script>
       <script src="https://maps.googleapis.com/maps/api/js?callback=mbbMapLoaded&libraries=places&key=AIza..."></script>
       <script src="https://d2w6u17ngtanmy.cloudfront.net/scripts/my-buying-buddy.5.0.js.gz"></script>
       <!-- End Buying Buddy Plugin. Copyright 2003-2025 -->

   Report which parts are present, even if only some of them are - a partial or leftover block still matters. For each part, give the file. Specifically look for:
   - The comment markers ("Buying Buddy plugin ..." and "End Buying Buddy Plugin").
   - The theme script (mbb2.com/version3/css/theme/acid/...). From its URL, and from the var MBB = {... acid : "..." ...} line, extract my Activation Key (the acid value) and include it in the report.
   - The Authorized Domain shown in the opening comment, if present.
   - The var MBB = {...} config script and the mbbMapLoaded() function.
   - The my-buying-buddy.5.0.js.gz script.
   - The Google Maps loader script (maps.googleapis.com/.../js?...). Report that it is present, but do NOT print the full API key - show only that a key is present and its last 4 characters (for example "key present, ends ...aB3d"). This report may be pasted into a support message, so the key MUST be redacted.
   State whether the block looks complete or only partial (and which parts are missing).

2. <bb-widget ...> elements (the old JavaScript-plugin widgets). List EVERY one, grouped by file. For each: the file, the location (page/route, or header/footer/layout), the data-type value, and the data-filter value if present.

3. <div id="MBBv3_..."> elements (an older legacy form of the same widgets). List EVERY one, grouped by file. For each: the file, the location, the full id value, and any data-filter / filter value.

4. The npm package @buyingbuddy/react (the modern React package). Check package.json and package-lock.json. Report whether it is present and its exact version. Also report whether a <BuyingBuddyProvider> wraps the app at the app root, and in which file - it pairs with the package.

5. <BuyingBuddyWidget ...> components (the modern React widgets). List EVERY one, grouped by file. For each: the file, the location (page/route, or header/footer/layout), the type value, and the filter value if present.

6. Anything else worth noting for support:
   - Foundation pages: is there a Search Results page (a ListingResults widget, or data-type="SearchResults", or id="MBBv3_ListingResults") and a Property Details page (SearchDetails, or id="MBBv3_SearchDetails")? Note the file and route for each you find.
   - Possible invalid or foreign widgets: elements like <div className="bb-widget" data-bb-widget="idx" data-bb-id="..."> use a different attribute structure (data-bb-id) and are NOT valid Buying Buddy widgets. List the files - do NOT include them in the counts for items 2, 3, or 5.
   - Any other Buying Buddy references you find that do not fit the categories above (for example other mbb2.com URLs, or stray "MBBv3", "bb-widget", or "buyingbuddy" mentions). List the file and a short description.

DECIDE THE INSTALL METHOD

From what you found, pick the ONE line that best describes this site and put it at the top of the report:
- JavaScript plugin only (old method): a plugin <script> block and/or <bb-widget> / <div id="MBBv3_..."> elements are present, and @buyingbuddy/react is NOT installed.
- React package only (correct method): @buyingbuddy/react and <BuyingBuddyWidget> components are present, and there is NO old <script> block or <bb-widget> element.
- Mixed: BOTH an old JavaScript plugin AND the @buyingbuddy/react package are present.
- None found: no Buying Buddy components of any kind.

THE REPORT

Produce ONE self-contained report that I can copy in a single action and send to Buying Buddy support. Putting the whole report inside one fenced code block is ideal so I can copy it in one tap. Use exactly these sections, in this order:

=== BUYING BUDDY AUDIT ===
Install method: <one of the four lines above>
Activation Key (acid): <value, or "not found">
Authorized Domain (from plugin comment): <value, or "not found">

JavaScript plugin block: <complete / partial / not found> - file(s): <...>
  Parts present: <which of: comment markers, theme script, MBB config, my-buying-buddy.5.0.js.gz>
  Google Maps loader: <present, key redacted (ends ...XXXX) / not found>

bb-widget elements: <count>
  <one line per element: file - location - data-type - data-filter>

MBBv3 div elements: <count>
  <one line per element: file - location - id - filter>

@buyingbuddy/react package: <present, version X.Y.Z / not found>
  BuyingBuddyProvider: <present in FILE / not found>

BuyingBuddyWidget components: <count>
  <one line per component: file - location - type - filter>

Foundation pages: Search Results <yes: file/route | no>, Property Details <yes: file/route | no>
Invalid/foreign (data-bb-id) widgets: <count / none> - file(s): <...>
Other Buying Buddy references: <none, or a short list>
=== END AUDIT ===

Only include the findings above. Do NOT include full API keys, tokens, or any other secret in the report.

RULES FOR THE WHOLE JOB
- This audit is READ-ONLY. Make no changes of any kind - no edits, no installs, no builds, no publish or deploy.
- Redact secrets: never print a full Google Maps API key (or any other key/token) - show only its last 4 characters.
- Report exactly what is there. Do not fix, "tidy", guess, or infer beyond what you can see in the files.
- If you are unsure whether something is a Buying Buddy component, include it under "Other Buying Buddy references" rather than leaving it out.
- Do NOT ask me any questions - just produce the report.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are migrating an existing Buying Buddy real-estate IDX installation in this HighLevel Ai Studio (React + Vite + TypeScript) project from the old JavaScript-plugin method to the official @buyingbuddy/react package. Work carefully and do NOT change anything until I have approved your plan.

IMPORTANT - how Buying Buddy widgets are styled (read this before you touch any CSS): Buying Buddy widgets render their content inside a SHADOW DOM. Each widget attaches a shadow root and renders its UI there, with fully encapsulated styles. This means the widget's CSS cannot leak out into my site, and my site's CSS does not reach inside the widget. There is therefore NO styling conflict to prevent between Buying Buddy and my site. Do NOT rename, remap, prefix, scope, or otherwise modify any of my site's CSS, design tokens, CSS variables, Tailwind config, or theme in an attempt to "avoid conflicts" - there are none, and doing so will break my site's colors and components. Your job is to convert widgets, not to defend my styles against them.

Step 0 - Tell me my Vibe Preview domain and my header offsets

0a. Vibe Preview domain. Derive my Vibe Preview domain by extracting the numeric project ID from the vibe.filesafe.space image URLs in index.html (or any other file in this project) and outputting it as preview-[PROJECT_ID].vibepreview.com - the literal text preview- followed by that project ID, then .vibepreview.com, without the leading https://. This is the permanent address for previewing my unpublished site. It is OPTIONAL - I only need to add it in my Buying Buddy dashboard if I want to preview the migrated site before publishing. Tell me clearly that it is optional and that if I plan to publish straight away I can skip it. If you cannot determine the project ID from the image URLs, tell me, and I will copy the domain from the preview URL shown in my Ai Studio editor.

0b. Widget Header Offset. Check whether this site has a STICKY or FIXED header (a header bar that stays pinned to the top of the screen while scrolling - typically position: fixed or position: sticky on the header/nav element).
- If it does NOT have a sticky/fixed header, tell me no header offset is needed and skip to the confirmation below.
- If it DOES, measure the rendered height of that header (in pixels) at three viewport widths and give me the three numbers to enter in my Buying Buddy dashboard:
   - Mobile (viewport < 768px)
   - Tablet (viewport 768px - 991px)
   - Desktop (viewport >= 992px)
- Report them clearly, for example: "Header Offset - Mobile: 56, Tablet: 64, Desktop: 72". If the header height is the same across sizes, give the same number for each. These go in the Widget Header Offset fields in my Buying Buddy dashboard.

Then ask me to confirm I have completed these in my Buying Buddy dashboard before you continue:
- REQUIRED: my Website Type is set to "HighLevel Ai Studio"
- OPTIONAL (recommended so I can preview before publishing): added the Vibe Preview domain you derived above
- (If a header offset was needed) entered the three offset values above

Do NOT proceed to Step 1 until I confirm the Website Type is set. (The Vibe Preview domain is optional - only needed if I want to preview before publishing. The header offset can be entered now or after the migration - it only affects how map widgets sit under my header, not whether widgets load.)

Step 1 - Verify the current setup (inspect only, change nothing)

Confirm the project matches the expected pattern and report what you find:

1. There is an old Buying Buddy plugin block, normally in index.html (in the <head>). It looks similar to this (values will differ):

       <!-- Buying Buddy plugin v5.02 for HighLevel; Authorized Domain: example.com -->
       <!-- ** DO NOT DEFER ** This must load at the top of the page, e.g. in the page head. -->
       <script src="https://www.mbb2.com/version3/css/theme/acid/XXXXXXXX"></script>
       <script>
         var MBB = {seo : "false", data:{ acid : "XXXXXXXX" } };
         function mbbMapLoaded(){ MBB.googleMaps = true; };
       </script>
       <script src="https://maps.googleapis.com/maps/api/js?callback=mbbMapLoaded&libraries=places&key=AIza..."></script>
       <script src="https://d2w6u17ngtanmy.cloudfront.net/scripts/my-buying-buddy.5.0.js.gz"></script>
       <!-- End Buying Buddy Plugin. Copyright 2003-2025 -->

2. Extract my Activation Key from the var MBB = {... acid : "XXXXXXXX" ...} line - the value of acid is my activation key. Show it to me.
3. Find EVERY widget element used anywhere in the project. There are three forms to look for:
   - Standard widgets: <bb-widget data-type="..." data-filter="..."> - for each, note the file, the data-type value, and the full data-filter value (if present).
   - Legacy widgets: <div id="MBBv3_..."> - for each, note the file and the id value. These are an older form of the same Buying Buddy widgets and WILL be converted (see Step 5).
   - Possible invalid/foreign widgets: elements like <div className="bb-widget" data-bb-widget="idx" data-bb-id="..."> - these use a different attribute structure (data-bb-id) and are NOT valid Buying Buddy widgets. Note the file for each. These will NOT be converted; you will list them for me to review manually (see Step 5).
4. Confirm whether a Disclaimer widget is present in the site footer (either as <bb-widget data-type="Disclaimer"> or <div id="MBBv3_Disclaimer">). If it is missing, you will need to add it in Step 5.
5. Confirm whether the site has the two foundation pages:
   - A Search Results page - uses <bb-widget data-type="SearchResults"> or <div id="MBBv3_ListingResults"> (both forms map to the same ListingResults widget).
   - A Property Details page - uses <bb-widget data-type="SearchDetails"> or <div id="MBBv3_SearchDetails">.

   For each one you find, note its file path and route path. Explicitly call out either foundation page that is missing - you will need to create it in Step 5.

Step 2 - Count and categorize

Report:
- The total number of files/pages that contain widgets, and the total number of widgets overall - counting both standard <bb-widget> elements and legacy <div id="MBBv3_..."> elements (both will be converted).
- A separate list of any files containing possible invalid/foreign widgets (data-bb-id style) that you will NOT convert and are flagging for manual review.
- Which pages are the foundation pages - the Search Results page (uses ListingResults) and the Property Details page (uses SearchDetails) - versus ordinary content pages that contain one or more widgets mixed in with page content (for example, community/neighborhood pages with MarketStats and InteractiveMap).

Step 3 - Summarize your plan and ask for my approval

Before changing anything, give me a clear summary of exactly what you will do (the steps in Step 5), including:
- That you will remove the entire old plugin block, INSTALL @buyingbuddy/react, WRAP the app root in the provider, and CONVERT all <bb-widget> elements to <BuyingBuddyWidget> components.
- The count of pages and widgets you will change.
- Any foundation pages or the Disclaimer widget that you will need to CREATE because they are missing (from your Step 1 findings), and where you will create them.

Also tell me clearly:
- "I will not publish your site. After the migration you should preview it on your Vibe Preview domain - where widgets will now work because you authorized that domain - and publish it yourself only when you are happy."
- "If anything is wrong, you can revert by restoring the backup created in the next step."

Then STOP and wait for my explicit approval ("yes, proceed") before doing anything.

Step 4 - Create a backup

After I approve, create a backup / restore point / version snapshot of the current site so I can roll back if needed, and tell me you have done so. If you are NOT able to create a backup yourself, stop and tell me to create one manually (or publish a restore point) before you continue - and wait for me to confirm.

Step 5 - Execute the migration

Make these changes:

1. Remove the old plugin block entirely from index.html (and anywhere else it appears): all of the Buying Buddy comment markers, the mbb2.com/.../acid/... theme <script>, the var MBB = {...} / mbbMapLoaded() config <script>, and the my-buying-buddy.5.0.js.gz <script>.
   - The block also includes a Google Maps API <script> (maps.googleapis.com/.../js?...key=...). Remove it as part of the Buying Buddy block, but FLAG THIS TO ME - if I use that same Google Maps API key for any other map on my site, I need to know it was removed.
2. Install the npm package @buyingbuddy/react.
3. Wrap the whole app in the Buying Buddy provider at the app root (src/main.tsx or src/App.tsx), using the activation key you extracted in Step 1:

       import { BuyingBuddyProvider } from "@buyingbuddy/react"

       <BuyingBuddyProvider activationKey="YOUR_ACTIVATION_KEY">
           {/* the rest of the app */}
       </BuyingBuddyProvider>

4. Convert the widgets to the React component <BuyingBuddyWidget>, following these rules exactly.

   Standard widgets (<bb-widget ...>):
   - data-type="X" becomes type="X".
   - data-filter="..." becomes filter="...". PRESERVE THE FILTER VALUE BYTE-FOR-BYTE - do not reformat, reorder, re-encode, "tidy", or change any character. The +-joined tokens, colons, commas, spaces, decimals, and negative numbers must all stay exactly as they were.

   Legacy widgets (<div id="MBBv3_...">):
   - The widget type is the value of id="..." with the MBBv3_ prefix removed. For example, <div id="MBBv3_ListingResults"> becomes <BuyingBuddyWidget type="ListingResults" />, and <div id="MBBv3_Calculator"> becomes <BuyingBuddyWidget type="Calculator" />.
   - If the element also has a data-filter="..." or filter="..." attribute, migrate its value to filter="..." - again, BYTE-FOR-BYTE, with no changes.

   For all converted widgets:
   - Add import { BuyingBuddyWidget } from "@buyingbuddy/react" to every file that now uses the component.
   - Leave all surrounding page content exactly as it is. Only the widget elements change - the text, layout, and everything else on each page must stay untouched.

   Do NOT convert invalid/foreign widgets. Elements like <div className="bb-widget" data-bb-widget="idx" data-bb-id="..."> use a different attribute structure (data-bb-id) and are NOT Buying Buddy widgets. Leave them exactly as they are, and list the files that contain them in your final summary, marked for my manual review. Do not guess a mapping for them.

   Example conversion:

       before:
       <bb-widget data-type="MarketStats" data-filter="reportType:totals+mls_id:md257+listing_status:active,coming-soon,under-contract,sold+sub_area:Fitler Square+prop_img:true+state:pa"></bb-widget>

       after:
       <BuyingBuddyWidget type="MarketStats" filter="reportType:totals+mls_id:md257+listing_status:active,coming-soon,under-contract,sold+sub_area:Fitler Square+prop_img:true+state:pa" />

5. Foundation pages. Make sure the site has BOTH foundation pages, matching the install prompt's pattern. On each foundation page, the widget is the ONLY Buying Buddy / listing component - do not hand-build any listing UI around it.
   - Search Results page (<BuyingBuddyWidget type="ListingResults" />):
     - If it exists (converted from the old <bb-widget data-type="SearchResults"> or <div id="MBBv3_ListingResults">): make its page content conform to the pattern below.
     - If it does not exist: create a new route for it. Use the slug /listing-results unless you have clear evidence of a different slug already in use.
     - Render it inside the existing site layout (header, navigation, footer). Add a page heading - an <h1> such as "Search Results" - inside a normal constrained container. Immediately below the heading, place the widget inside a FULL-WIDTH container with standard responsive horizontal padding so it does not bleed to the screen edges (e.g. <div className="w-full px-4 sm:px-6 lg:px-8">).
   - Property Details page (<BuyingBuddyWidget type="SearchDetails" />):
     - If it exists (converted from the old <bb-widget data-type="SearchDetails"> or <div id="MBBv3_SearchDetails">): make its page content conform to the pattern below.
     - If it does not exist: create a new route for it. Use the slug /listing-details unless you have clear evidence of a different slug already in use.
     - Render it inside the existing site layout the same way, with an <h1> such as "Property Details" inside a normal constrained container, and the widget placed immediately below it within that SAME standard constrained container (NOT full-width - keep it constrained).
   - On all other (content) pages, convert each widget in place and keep the page's content around it.
6. Disclaimer. The MLS disclaimer must appear in the site footer so it shows on every page.
   - If a disclaimer widget exists (converted from <bb-widget data-type="Disclaimer"> or <div id="MBBv3_Disclaimer">): keep it in the footer.
   - If it does not exist: add <BuyingBuddyWidget type="Disclaimer" /> to the site footer so it appears on every page.
7. Verify the build and that you changed nothing else. After making all changes, confirm the project still compiles/builds with no errors, and confirm you did NOT modify any global stylesheet, design tokens/CSS variables, Tailwind config, theme, or shared UI components. If your edits introduced any syntax or import errors, fix them before reporting. Do not report the migration as complete until the build succeeds and the only changes are widget conversions plus removal of the old plugin block.

Step 6 - Report and hand back to me

Do NOT publish the site. When finished, give me a summary that includes:
- How many widgets you converted and in how many files (note how many were standard <bb-widget> and how many were legacy <div id="MBBv3_...">).
- Whether either foundation page (Search Results, Property Details) or the Disclaimer widget had to be CREATED because it was missing (vs. converted from an existing widget) - if so, where you placed them and what slugs/routes you used.
- Any files containing invalid/foreign widgets (data-bb-id style) that you left unchanged and are flagging for my manual review. If there were none, say so.
- Confirmation that the old plugin block (and the Google Maps loader) was removed, with the Google Maps note repeated.
- That the package is installed and the provider wraps the app root.
- Confirmation that the project builds with no errors.
- Confirmation that you did NOT change any of my site's styling, design tokens, Tailwind config, theme, or shared UI components.
- A reminder if a header offset was needed: "If you haven't yet, enter the Widget Header Offset values I gave you (Step 0) in your Buying Buddy dashboard so map widgets aren't hidden under your sticky header."
- Clear next steps for me: "Preview your site on your Vibe Preview domain - the widgets will now load because you authorized that domain. When everything looks right, publish your site. If anything is wrong, restore the backup from Step 4."

Rules for the whole job

- Do NOT change any routing, navigation, styling, or other code unrelated to this migration.
- Do NOT touch my site's styling or design system. Specifically: do NOT edit, rename, remap, prefix, or reorganize any CSS variables/design tokens (e.g. --primary, --secondary), src/index.css (or any global stylesheet), tailwind.config.*, theme files, or shared layout/header/button/UI components. Buying Buddy widgets are shadow-DOM isolated, so there is never a reason to modify my styles "to avoid conflicts." The ONLY style-related change you may make is removing the old plugin's own theme <script>/<link> as part of removing the old plugin block (Step 5).
- Do NOT alter any data-filter / filter values.
- Do NOT convert invalid/foreign (data-bb-id) widgets - leave them and list them for manual review.
- Do NOT publish the site - I will preview and publish myself.
- If you are unsure about anything, stop and ask me rather than guessing.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are removing ONLY the Buying Buddy JavaScript plugin code block from this HighLevel Ai Studio (React + Vite + TypeScript) project. This is a deliberately narrow job: the plugin block goes, and NOTHING ELSE in the project changes. Work carefully and do NOT change anything until I have approved your plan.

IMPORTANT - what this prompt does NOT do. You are NOT removing pages, routes, navigation links, widget elements, the footer disclaimer, or any component. You are NOT installing anything. Any Buying Buddy widget elements already on my pages (<bb-widget ...> or <div id="MBBv3_...">) STAY EXACTLY WHERE THEY ARE - you will list them for me, but you will not delete, convert, move, or edit a single one. If you think something else "should" be cleaned up as well, mention it in your summary and LEAVE IT ALONE.

IMPORTANT - do not touch my site's styling. Do NOT rename, remap, prefix, scope, or otherwise modify any of my site's CSS, design tokens, CSS variables, Tailwind config, theme, or shared UI components. The ONLY style-related change you may make is removing the old Buying Buddy plugin's own theme <script> as part of removing the plugin block (Step 5).

Step 1 - Find the plugin block (inspect only, change nothing)

The plugin block is normally in index.html (in the <head>). It looks similar to this (values will differ):

       <!-- Buying Buddy plugin v5.02 for HighLevel; Authorized Domain: example.com -->
       <!-- ** DO NOT DEFER ** This must load at the top of the page, e.g. in the page head. -->
       <script src="https://www.mbb2.com/version3/css/theme/acid/XXXXXXXX"></script>
       <script>
         var MBB = {seo : "false", data:{ acid : "XXXXXXXX" } };
         function mbbMapLoaded(){ MBB.googleMaps = true; };
       </script>
       <script src="https://maps.googleapis.com/maps/api/js?callback=mbbMapLoaded&libraries=places&key=AIza..."></script>
       <script src="https://d2w6u17ngtanmy.cloudfront.net/scripts/my-buying-buddy.5.0.js.gz"></script>
       <!-- End Buying Buddy Plugin. Copyright 2003-2025 -->

Report the file and the exact lines you found. If the block appears in more than one file, list every occurrence. If you cannot find it anywhere, STOP and tell me - do NOT go looking for other Buying Buddy things to remove instead.

Step 2 - Tell me what will stop working (inspect only, change nothing)

Removing the plugin block stops the old JavaScript widgets from loading. Before I approve, I need to know exactly what that affects, so list:
- Every <bb-widget data-type="..."> element in the project - the file and the data-type value.
- Every legacy <div id="MBBv3_..."> element - the file and the id value.
- Whether a Disclaimer widget is present, and in which file.

Then tell me plainly: "These elements will stay in your pages, but once the plugin block is removed they will no longer display anything."

Also check whether the newer package is installed - @buyingbuddy/react in package.json, a <BuyingBuddyProvider> at the app root, or any <BuyingBuddyWidget> components:
- If it IS installed, tell me. That is the expected situation when the old script was left behind after moving to the package: the <BuyingBuddyWidget> components keep working normally, and only the old <bb-widget> / <div id="MBBv3_..."> elements listed above go blank. Removing the leftover script block is exactly the right fix - continue.
- If it is NOT installed, tell me that after this removal the site will have no working Buying Buddy widgets at all, and that I should run the Install prompt from my Buying Buddy dashboard if I want them back.

Step 3 - Summarize your plan and ask for my approval

Give me a short, clear summary:
- The file(s) and lines you will remove.
- The exact count of widget elements that will be left in place and will stop displaying.
- Whether the @buyingbuddy/react package is present.

Also tell me clearly:
- "I will remove the plugin block only. I will not delete or edit any page, route, navigation link, widget element, disclaimer, or component."
- "I will not install anything, and I will not publish your site."
- "If anything is wrong, you can revert by restoring the backup created in the next step."

Then STOP and wait for my explicit approval ("yes, proceed") before doing anything.

Step 4 - Create a backup

After I approve, create a backup / restore point / version snapshot of the current site so I can roll back if needed, and tell me you have done so. If you are NOT able to create a backup yourself, stop and tell me to create one manually (or publish a restore point) before you continue - and wait for me to confirm.

Step 5 - Execute the removal

Remove the plugin block entirely from index.html (and from any other file where you found it in Step 1): all of the Buying Buddy comment markers, the mbb2.com/.../acid/... theme <script>, the var MBB = {...} / mbbMapLoaded() config <script>, and the my-buying-buddy.5.0.js.gz <script>.
- The block also includes a Google Maps API <script> (maps.googleapis.com/.../js?...key=...). Remove it as part of the Buying Buddy block, but FLAG THIS TO ME - if I use that same Google Maps API key for any other map on my site, I need to know it was removed.
- If removing the block leaves an empty line or an orphaned blank <head> gap, tidying that whitespace is fine. Nothing else in the file changes.

That is the entire change. Do NOT touch anything else.

Step 6 - Verify and report

Confirm the project still compiles/builds with no errors. If removing the block introduced an error, fix that error and tell me - do NOT start refactoring anything.

Then give me a summary that includes:
- Confirmation that the plugin block was removed, and from which file(s).
- The Google Maps note repeated.
- The list of widget elements you LEFT IN PLACE that will now display nothing, with their files - so I can decide what to do with them later.
- Confirmation that you did not delete or edit any page, route, navigation link, widget element, disclaimer, or component.
- Confirmation that you did NOT change any of my site's styling, design tokens, Tailwind config, theme, or shared UI components.
- Confirmation that the project builds with no errors.
- Next steps for me: "Preview your site to confirm everything looks right, then publish when you are happy. If anything is wrong, restore the backup from Step 4."

Rules for the whole job

- The ONLY thing you may remove is the Buying Buddy plugin block described in Step 1.
- Do NOT delete, convert, move, or edit any page, route, navigation link, widget element (<bb-widget> or <div id="MBBv3_...">), the footer disclaimer, or any component - even if it will now display nothing. Leaving dead widget markup in place is the intended outcome of this prompt.
- Do NOT touch my site's styling or design system. Specifically: do NOT edit, rename, remap, prefix, or reorganize any CSS variables/design tokens (e.g. --primary, --secondary), src/index.css (or any global stylesheet), tailwind.config.*, theme files, or shared layout/header/button/UI components.
- Do NOT install any new packages.
- Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", or "Go Live" action your environment offers. I will preview the site myself and publish or deploy it when I am ready.
- If you are unsure about anything, stop and ask me rather than guessing.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.

You are completely REMOVING an existing Buying Buddy installation from this HighLevel Ai Studio (React + Vite + TypeScript) project. Work carefully and do NOT change anything until I have approved your plan.

IMPORTANT - do not touch my site's styling. I am only removing Buying Buddy assets. Do NOT rename, remap, prefix, scope, or otherwise modify any of my site's CSS, design tokens, CSS variables, Tailwind config, theme, or shared UI components. The ONLY style-related change you may make is removing the old Buying Buddy plugin's own theme <script> as part of removing the plugin block (Step 5).

Step 1 - Verify the current setup (inspect only, change nothing)

Confirm the project matches the expected pattern and report what you find:

1. The old plugin block, normally in index.html (in the <head>). It looks similar to this (values will differ):

       <!-- Buying Buddy plugin v5.02 for HighLevel; Authorized Domain: example.com -->
       <!-- ** DO NOT DEFER ** This must load at the top of the page, e.g. in the page head. -->
       <script src="https://www.mbb2.com/version3/css/theme/acid/XXXXXXXX"></script>
       <script>
         var MBB = {seo : "false", data:{ acid : "XXXXXXXX" } };
         function mbbMapLoaded(){ MBB.googleMaps = true; };
       </script>
       <script src="https://maps.googleapis.com/maps/api/js?callback=mbbMapLoaded&libraries=places&key=AIza..."></script>
       <script src="https://d2w6u17ngtanmy.cloudfront.net/scripts/my-buying-buddy.5.0.js.gz"></script>
       <!-- End Buying Buddy Plugin. Copyright 2003-2025 -->

2. The foundation pages:
   - The Search Results page - the route/page that contains <bb-widget data-type="SearchResults"> or <div id="MBBv3_ListingResults">.
   - The Property Details page - the route/page that contains <bb-widget data-type="SearchDetails"> or <div id="MBBv3_SearchDetails">.
   - For each: note the file path, the route path it is mounted at (e.g. /listings, /property/:id), and any navigation menu items that link to it.
3. The Disclaimer widget (<bb-widget data-type="Disclaimer"> or <div id="MBBv3_Disclaimer">), typically in a shared footer component.
4. Every other widget element used anywhere else in the project. Two forms to look for:
   - Standard widgets: <bb-widget data-type="..." ...> - for each, note the file and the data-type value.
   - Legacy widgets: <div id="MBBv3_..."> - for each, note the file and the id value. These are an older form of the same Buying Buddy widgets and WILL be deleted the same as standard ones.
5. Possible invalid/foreign widgets: elements like <div className="bb-widget" data-bb-widget="idx" data-bb-id="..."> use a different attribute structure (data-bb-id) and are NOT valid Buying Buddy widgets. Note the file for each. These will NOT be deleted; you will list them for me to review manually.

SAFETY CHECK - abort if this is a mixed install. If you find any of the following, the site has (or partially has) the NEW @buyingbuddy/react package and this Removal prompt is NOT the right tool. STOP, report what you found, and tell me to use a different prompt:
- @buyingbuddy/react in package.json or package-lock.json.
- A BuyingBuddyProvider wrapper anywhere in src/main.tsx, src/App.tsx, or similar app root files.
- Any <BuyingBuddyWidget ...> components in the project.

Step 2 - Count and categorize

Report:
- The total number of files/pages that contain widgets, and the total number of widgets overall (counting both standard <bb-widget> and legacy <div id="MBBv3_...">).
- Which pages are the foundation pages (Search Results, Property Details) - these will be DELETED IN FULL - versus content pages that contain one or more widgets mixed in with page content (each widget will be removed in place; surrounding content kept).
- The footer location of the Disclaimer widget (file/component).
- A separate list of any invalid/foreign widgets (data-bb-id style) that you will NOT touch and are flagging for manual review.

Step 3 - Summarize your plan and ask for my approval

Before changing anything, give me a clear summary of exactly what you will do:
- Remove the entire old plugin block from index.html (and anywhere else it appears).
- Delete the Search Results foundation page (and its route, and any navigation links to it).
- Delete the Property Details foundation page (and its route, and any navigation links to it).
- Delete the Disclaimer widget from the footer.
- Delete every other Buying Buddy widget from each content page, leaving the surrounding page content untouched.
- Include the counts: pages and widgets affected.

Also tell me clearly:
- "I will not install anything new. This prompt only removes Buying Buddy."
- "I will not publish your site. After the removal you should preview the site yourself and publish only when you are happy."
- "If anything is wrong, you can revert by restoring the backup created in the next step."

Then STOP and wait for my explicit approval ("yes, proceed") before doing anything.

Step 4 - Create a backup

After I approve, create a backup / restore point / version snapshot of the current site so I can roll back if needed, and tell me you have done so. If you are NOT able to create a backup yourself, stop and tell me to create one manually (or publish a restore point) before you continue - and wait for me to confirm.

Step 5 - Execute the removal

Make these changes:

1. Remove the old plugin block entirely from index.html (and anywhere else it appears): all of the Buying Buddy comment markers, the mbb2.com/.../acid/... theme <script>, the var MBB = {...} / mbbMapLoaded() config <script>, and the my-buying-buddy.5.0.js.gz <script>.
   - The block also includes a Google Maps API <script> (maps.googleapis.com/.../js?...key=...). Remove it as part of the Buying Buddy block, but FLAG THIS TO ME - if I use that same Google Maps API key for any other map on my site, I need to know it was removed.

2. Delete the foundation pages:
   - Delete the Search Results page component file in full (the file containing <bb-widget data-type="SearchResults"> or <div id="MBBv3_ListingResults">).
   - Delete the Property Details page component file in full (the file containing <bb-widget data-type="SearchDetails"> or <div id="MBBv3_SearchDetails">).
   - Remove their route entries from the router configuration (e.g. the <Route path="..." element={...}> lines, or the equivalent in the project's routing setup), and remove the corresponding navigation menu links if any exist.
   - Clean up any now-unused import statements for the deleted page components, but do NOT touch any other imports or unrelated code in the router/nav files.

3. Delete the Disclaimer widget from the footer (and anywhere else it appears). Remove ONLY the disclaimer element - the rest of the footer (links, copyright, layout, columns) must be left exactly as it is.

4. Delete every other Buying Buddy widget from each content page:
   - For each <bb-widget ...> element and each <div id="MBBv3_..."> element on a content page, delete just the element. Leave the surrounding page content - text, headings, images, layout, columns - exactly as it was.
   - If a wrapper <div> was added purely to host a single widget and would now be empty, you may remove that wrapper too. Otherwise leave wrappers alone.

5. Do NOT delete invalid/foreign widgets. Elements like <div className="bb-widget" data-bb-widget="idx" data-bb-id="..."> use a different attribute structure and are NOT Buying Buddy widgets. Leave them exactly as they are, and list the files that contain them in your final summary for my manual review.

6. Verify the build and that you changed nothing else. After making all changes, confirm the project still compiles/builds with no errors, and confirm you did NOT modify any global stylesheet, design tokens/CSS variables, Tailwind config, theme, or shared UI components. If your edits introduced any syntax or import errors, fix them before reporting. Do not report the removal as complete until the build succeeds and the only changes are the items listed above.

Step 6 - Report and hand back to me

Do NOT publish the site. When finished, give me a summary that includes:
- Confirmation that the old plugin block (and the Google Maps loader) was removed, with the Google Maps note repeated.
- Confirmation that the Search Results and Property Details foundation pages have been deleted, along with their routes and any navigation links.
- Confirmation that the Disclaimer widget has been removed from the footer.
- How many other widgets were deleted and from how many files (note how many were standard <bb-widget> and how many were legacy <div id="MBBv3_...">).
- Any files containing invalid/foreign widgets (data-bb-id style) that you left unchanged and are flagging for my manual review. If there were none, say so.
- Confirmation that the project builds with no errors.
- Confirmation that you did NOT change any of my site's styling, design tokens, Tailwind config, theme, or shared UI components.
- Clear next steps for me: "Preview your site to confirm everything looks right. If you want to reinstall Buying Buddy with the new package, run the Install prompt from your Buying Buddy dashboard (the 'Get the AI Install Prompt - Step 1 of 3' button on the Add Plugin tab). If anything is wrong, restore the backup from Step 4."

Rules for the whole job

- Do NOT change any routing, navigation, styling, or other code unrelated to this removal. The ONLY routing/nav changes allowed are removing the routes and links that point to the deleted foundation pages.
- Do NOT touch my site's styling or design system. Specifically: do NOT edit, rename, remap, prefix, or reorganize any CSS variables/design tokens (e.g. --primary, --secondary), src/index.css (or any global stylesheet), tailwind.config.*, theme files, or shared layout/header/button/UI components. The ONLY style-related change you may make is removing the old plugin's own theme <script> as part of removing the old plugin block (Step 5).
- Do NOT install any new packages.
- Do NOT delete invalid/foreign (data-bb-id) widgets - leave them and list them for manual review.
- Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", or "Go Live" action your environment offers. I will preview the site myself and publish or deploy it when I am ready.
- If you are unsure about anything, stop and ask me rather than guessing.

This is the demo version. When you install from your own Buying Buddy dashboard, the prompt arrives with your activation key and your page addresses already filled in.