Agent workflow

The order

1. list_flow_sites
   Find the site. Never assume an id from an earlier session.
2. get_flow_webflow_rules
   Fetch the enforced rules rather than working from a remembered copy.
3. Read what you are about to change
   get_flow_page, get_flow_section and get_flow_design_tokens return current content and the revision you will need.
4. Write
   Pass the revision you just read. Section writes are checked against the rulebook before they are stored.
5. audit_flow_site
   Confirm the whole site still passes, and check token consistency.

Revisions are not optional

Every update and delete takes the updated_at revision of the thing it is changing. A write carrying a stale revision is refused.

This is what makes it safe to have an agent and a human editing the same site: the second writer is told their view is out of date instead of silently overwriting the first.

Editing elements rather than whole sections

Rewriting a whole section to change one button is wasteful and risks collateral changes. For precise edits:

• inspect_flow_section first — it returns stable selectors and the element structure.
• Then add_flow_element, update_flow_element or remove_flow_element against one exactly-matched selector.

Each of those can also replace the section's complete CSS and JavaScript in the same call, which is how you keep styles in step with a markup change.

When a write is rejected

A rule violation returns HTFLOW_WEBFLOW_RULES_VIOLATED and the section is not saved. The right response is to regenerate the section so it satisfies the rules — not to retry the same source, and not to work around the check.