The browser

Every plugin is a page that Ovvi serves from its package. The browser cannot be one, because its content is any site:

• Framing. A plugin page can show a site only in an <iframe>. Most sites refuse to be framed (X-Frame-Options, a frame-ancestors policy), and logins in a frame lose their cookies.
• Its own store and proxy. Each machine has its own WebKit data store, and a remote machine's pages go through its SOCKS proxy (D73). Those are properties of a web view, not of a page.
• The Web Inspector docks under the page in the card. It inspects the site itself, not a frame.
• A site gets no bridge. It has no ovvi object and no message handler (Security).

So the browser stays the native card that Browser describes. In the registry it is a kind with native content, with a manifest written in Swift (Registry.browser):

static let browser = PluginManifest(
    id: "browser", name: "Browser", icon: "globe", description: "Web page", keywords: ["web", "url", "localhost"],
    opens: .init(urls: ["http://*", "https://*", "file://*"]), chooser: "Browser", settings: [network],
)

• The fields that apply are a plugin's: id (its label is ovvi:browser#<iid> <url>), name, icon, description, keywords, opens, chooser and settings (the remote network choice, This Mac's network). So the chooser, ⌘K's Open Browser Here and linked opens of web addresses read every kind from one registry.
• No entry means native content. The app draws the browser's own card, its toolbar in row 2 and its address field. It has no header or commands in the manifest: they are the browser's own. Its version is 1.0.0.
• Its id is taken first, so no package can use the id browser.
• Opens. A plugin whose urls match a web address takes it before the browser (What a plugin opens).
• Memory. Browser cards and plugin cards share one limit (Memory).

Terminal and Agent are not in the registry. They are herdr's own panes, with no label, and the chooser lists them first.

Choices

The decision is D103 on the Decisions page.