feat(rules): add component resolution rules to webflow_guide_tool

[kiratchhina]

Summary

When a Webflow site consumes components from a shared library, list_components returns two entries for the same component name — one with readonly: true (shared library) and one site-level. component_builder previously resolved by name and silently picked the site-level version, which disconnects placed instances from upstream design system updates.

This PR encodes the correct resolution behaviour directly into the webflow_guide_tool runtime instructions so that any agent using this MCP server follows safe defaults automatically.

What's different

• Removed the instruction telling agents to "pass the component name (not the ID)" — this was actively unsafe for sites with shared library components
• Added a required list_components call before every component_builder insertion
• Added a resolution priority order: explicit ID → unambiguous readonly match → ambiguous (warn + confirm) → no readonly match (warn + ask)
• Added a standard warning format for name collisions so users always know which version is being used before anything is inserted
• Added pre/post session audit rules to detect and surface any implicit site-level component creation

How it works

All rules live in webflow_guide_tool (src/tools/rules.ts), which agents are already instructed to call first before all other tools. No schema or API changes — this is purely behavioural guidance.

QA Spec

• Agent calls list_components before component_builder on a site with shared library components
• Agent picks the readonly: true entry when a name collision exists
• Agent surfaces the disambiguation warning and waits for confirmation rather than proceeding silently
• Agent performs post-session audit and flags any increase in total component count
• No regression on sites with no shared library components (unambiguous name resolves normally)

Made with Cursor