Применить правку к разметке сайта
refactor_siteOne named markup transformation — with a predictable result.
The tool PUBLISHES NOTHING. It returns the changed HTML; showing it to
the person, getting consent and calling `publish_site` is your job.
Never rewrite someone's site silently.
Transformations are idempotent: a repeated call changes nothing and
honestly answers `changed=false`. An empty list of changes is not an
error, it means "there was nothing to apply".
⚠️ WHAT IS NOT HERE AND WHY. Fonts from third-party hosts, re-encoding
images to webp and untangling inline styles are NOT included: they need
the files themselves, which the server does not have, or a judgement
about the intended look. `site_issues` names those problems — with a
location and an explanation; whoever holds the files fixes them.
The gain is measured with `check_performance` BEFORE and AFTER the
publish. A difference under three points is measurement noise, not an
improvement — say so.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fix | Yes | `meta` — fill in lang and Open Graph markup from what the page already says. `lazy_images` — defer loading of images below the first screen (the first image is left alone: LCP is measured on it). | |
| html | Yes | The contents of `index.html` — the file on the user's disk. Read the file yourself and pass it here. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fix | Yes | ||
| html | No | ||
| changed | Yes | ||
| changes | Yes | ||
| next_action | Yes | ||
| available_fixes | Yes |