Add fast proportional MCP workflows

[kof]

Problem

Small, well-scoped Webstudio changes can trigger excessive discovery, repeated process startup, full project builds, rendered audits, and other slow verification. Routine corrections that should take seconds can take minutes because MCP lacks one generalized path for finding values, atomic multi-record edits, targeted verification, and consent boundaries for slow work.

Desired outcome

Make small MCP corrections normally complete in approximately 10 seconds through:

focused search → atomic edit → targeted assertions

The default workflow must stop after the fastest verification sufficient for the requested outcome.

Product scope

• Add universal search across editable project data: pages/settings, instances/text/props, bindings/expressions, variables/resources, assets/metadata, Markdown/frontmatter, JSON, styles/tokens, redirects, and project settings.
• Return stable match and entity IDs, current values, locations, affected routes, and reference resolution state.
• Add one atomic semantic update transaction for multiple matches with validation, optimistic concurrency, all-or-nothing commit, affected routes, and resolved/generated values.
• Represent assets, pages, resources, variables, and similar entities through stable semantic IDs; preserve references through imports, migrations, renames, and replacements.
• Add lightweight route-scoped assertions for status, resource resolution/content types, unresolved values, evaluated metadata, generated links, structured data, and expected content.
• Materialize and inspect one route without a complete production build.
• Add cost preflight, explicit confirmation tokens, and time budgets for slow or unpredictable operations.
• Classify workflow guidance by task scope and recommend focused search → atomic edit → targeted assertions for small corrections.
• Reuse a persistent project session across multi-operation workflows.
• Return actionable mutation summaries, validation, uncertainty, and the smallest useful next step.

Constraints

• No operation expected to exceed 10 seconds may start without explicit user confirmation.
• Preflight must report an honest duration range, purpose, and faster alternative.
• A time budget that cannot reasonably be met must return alternatives instead of starting work.
• Small changes must not require whole-document download/upload, full preview, screenshots, broad audits, crawls, dependency installation, or project builds.
• Full preview remains available when visual or runtime behavior requires it.
• Existing project version conflict and transaction guarantees must remain intact.

Acceptance criteria

• A change spanning several matches can be applied in one transaction.
• Search covers Markdown, frontmatter, JSON, bindings, and ordinary Builder data.
• References use stable entity identities and survive supported lifecycle operations.
• Routine changes avoid downloading complete documents.
• One dynamic route can be evaluated without a full build.
• MCP verifies resulting status, metadata, bindings, links, structured data, text/elements, and resources through explicit assertions.
• No operation expected to exceed 10 seconds starts without approval.
• Every slow-operation prompt explains purpose, duration, and a faster alternative.
• Repeated calls can share one persistent project session.
• Mutation results identify changes, affected entities/routes, generated values, validation, uncertainty, and the smallest next step.
• Small known corrections normally complete within approximately 10 seconds.