No builder fingerprint found

You are working on the codebase behind substack.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.

## Scaffold defaults still in place

### 1. Deploy-platform response headers
Observed on the live site: x-served-by (CDN)

Noted for context only: x-served-by (CDN). Deploy-platform headers say where a site is hosted, not how it was written.

## Default visual styling

### 2. Emoji used as feature icons
Observed on the live site: 4 emoji in page text

Swap the emoji feature icons (4 emoji in page text) for a consistent icon set rendered as SVG. Emoji render differently on every platform and are the most recognisable shorthand for a page assembled quickly.

## 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.

Findings