auto-webmcp v0.3.0: React support, richer schemas, and WebMCP spec compliance

When we shipped the first version of auto-webmcp , the pitch was simple: drop one script tag and every form on your page becomes a callable tool for AI agents, no manual JSON Schema writing required. That core idea has not changed. But the past two days have been a sprint through every edge case the real web throws at you: React forms that fight you, inputs that live outside <form> tags, select menus that lie about their options, and a new set of WebMCP spec fields that make your tools dramatically more useful to agents. Here is what shipped. React and framework-managed forms Vanilla forms are easy. React forms are a different story. React intercepts input events using its own synthetic event system. Setting input.value = 'foo' directly does nothing because React's state never updates. The DOM value changes, but React still thinks the field is empty. When the form submits, it sends blank data. auto-webmcp now fills React inputs by dispatching a native input event through HTMLInputEleme