Browser research for public lookups and accommodation choices, with human handoff

Agreed product scope: Micro is a general-purpose assistant that researches and explains choices, remembers useful facts and sets requested reminders. It must not autonomously book, purchase or make reservations.

Examples:

• Ask for a vehicle registration if not known, check the official MOT service, report the verified expiry with source and checked-at time, remember the explicit vehicle fact and create the requested reminder through existing Events. Do not guess next year's MOT from a stale record.
• Discuss destination/dates/party/budget, retrieve current accommodation availability, return a small shortlist with total price/currency/stay details and cancellation terms plus links. The person completes the booking. Recheck time-sensitive data; do not imply a search result is reserved inventory.

Implementation sequence:

• Extend existing Chromium Read/Shot infrastructure with bounded navigation, page observations and form interaction for public research. Prefer stable APIs where available; no new primary UI destination.
• Use actual isolated browser contexts per task/account, not merely fresh tabs. Never share cookies, storage, downloaded files or screenshots between users. Audit current allocator/context behavior before authenticated browsing.
• Enforce destination/network policy on navigation, redirects and subrequests, including private/metadata addresses. Do not add arbitrary script execution as an agent tool.
• Treat page content as untrusted evidence. Constrain action paths to research; no checkout, booking, sending messages or account changes. Respect challenges/restrictions and return a useful handoff if blocked.
• Bound concurrent browsers, lifetime, steps, observation size and cost. Persist task state/outcomes through existing background work; after restart re-observe rather than blindly replaying actions.
• Return sources, checked-at time, limitations and actionable links in the conversation.
• Exercise MOT expiry lookup -> saved fact -> requested reminder, and accommodation search -> shortlist -> user handoff, before declaring supported.

Existing browser service can read JS-rendered pages and take screenshots; it is not yet a general interactive browser agent. This issue records remaining work, not a shipped capability.

Start by auditing the existing Chromium Read/Shot infrastructure and its allocator/context behavior, then trace the existing background-work and Events paths. The scope includes navigation and network policy, isolation, bounded execution, handoff behavior, and persistence. Done means exercising the MOT lookup-to-reminder and accommodation shortlist-to-handoff flows with sources, timestamps, limitations, and safe behavior when blocked.