You are working on the codebase behind www.framer.com.

An external scan of the deployed site found the tells listed below — the specific things that make it read as assembled by a website builder rather than built. Fix them in the order given. Each item names the evidence observed on the live page, so you can confirm the problem before you change anything.

Rules for this task:
- Do not redesign the site. Change only what each item asks for.
- Do not change any URL, route or page title beyond what an item explicitly requires.
- If an item does not match what you find in the code, say so and skip it rather than inventing a change.
- Work through the list top to bottom and report what you changed for each.

## Remove builder attribution

### 1. Framer build markers are still in the page
Observed on the live site: framerusercontent.com

Strip every Framer attribution marker from the shipped output. Remove the injected badge element and its stylesheet, delete the platform runtime script tag from index.html, and drop any `data-`/class hooks the platform added. Do not leave the badge hidden with CSS — delete the markup. Markers found: framerusercontent.com.

### 2. A <meta name="generator"> tag names the builder that made the site
Observed on the live site: Framer 49b40c6

Remove the `<meta name="generator">` tag from the document head (currently: Framer 49b40c6). It names the tool that built the site, it is the loudest single tell, and it does nothing for your users.

## When you are done

Re-run the checks yourself before reporting: fetch the deployed page with curl and confirm the markers above are gone from the HTML, that unknown paths return 404, and that `/robots.txt` and `/sitemap.xml` answer 200. Then summarise anything you deliberately did not change and why.