Call page.patch_file

Change something on a site by writing its FILES — 'add more space between these cards', 'change the button text to Book a call', 'fix the typo in the footer', 'make the hero heading bigger'. This is the one way every site whose files we hold is changed, however it was made or brought in: copy, styling, layout, a component, a page. Read each file with page.read_file first — start from the selected element's file and line when the turn gives them, or from page.edit's located, or find the words with page.list_files and contains — and copy find text exactly; a hunk that matches nowhere or more than once refuses the whole call and nothing is written. No site id is needed — it works on the site the member has open on screen. One call is ONE saved version, so send a whole change in one call. While a live workbench is showing the site the change appears there in place and no build runs (the result says build_deferred; relay its build_hint); otherwise a build follows and takes a minute or two. The result is the diff (say what it shows, never more), the new source_ref and base_source_ref (page.rollback to it undoes this). Which directories are editable depends on the project: refusals name the reason, so relay them rather than retrying. Dependency manifests and lockfiles, build configuration, generated files, and anything under a build or tooling directory are always refused. A site whose files are READ-ONLY here is refused — page.list_files reports can_write: false for one, so check that before composing a patch. A change the member asked for in this conversation is written at once; only a change nobody asked for — or any change, when the member has asked to see each one first — raises its approval card, which is the member's confirmation, and is not made, saved or built unless they approve it there. Not for rewriting whole named files from an instruction — that is page.edit_file. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.