VenueMindRuntime boundary
- Contract version 1.6.0 is attached to every published tool.
- Lifecycle states: detecting, registering, ready, failed, unsupported, unregistered.
- Every invocation returns a compact text summary and versioned structured content.
- Mutation receipts retain caller idempotency and correlation metadata.
- Authorization scopes: venue:read, venue:propose, venue:comment, venue:simulate, venue:operate, venue:export.
- Input and output byte limits are published per tool and enforced before data crosses the boundary.
- Sensitive credentials, contact fields, attendee-record keys, and Incident evidence bytes are excluded from structured results.
- Abort signals unregister the page tool suite and cancel active calls where the invoking browser supplies a call signal.
Generated catalog
Each native browser tool has one canonical reference page shared with the standalone MCP surface.