Framework support

This table records framework surfaces actually built and checked in this package. It is not a compatibility promise for every release in a listed major version.

The Astro integration uses the documented astro:config:setup page-script injection hook and astro:config:done output diagnostic. mode: 'on-demand' permits Astro's server build mode while the application owns its routes and adapter; it does not create either. E01 preserves a wholly static build. E02 preserves prerendered pages and human navigation while live /agent-native/v1/* and /mcp routes reuse the framework-neutral HTTP/MCP handlers.

The experimental existing-project init can patch only an Astro config with the recognized literal static shape. It records a reviewed sidecar origin and generates a browser entry, then verifies the built E01 site from a local package tarball. More complex Astro config, on-demand configs, and other frameworks require manual integration. Detection reports on-demand routes, a missing server adapter, and protocol-looking static files; it never recommends the historical output: 'hybrid' value.

The browser capability host remains experimental. E01 exercises a simulated WebMCP API in Node tests, not a real browser or agent. Other Astro releases, server output, deployment providers, and real-host WebMCP behavior are unverified. E02 proves only the pinned local Node standalone adapter; it is not a claim about other adapters or external hosts.

E05 follows Hono's official Node adapter shape: the Hono router receives Fetch API requests and @hono/node-server owns the Node HTTP socket. The package's createHttpHandler and createMcpHandler remain framework-neutral and are mounted into the same Hono app. The fixture checks HTTP and the official MCP client against one registry, binds loopback by default, and handles SIGINT/SIGTERM and listen errors. This verifies the pinned fixture only, not every Hono release or a deployed host.

Astro references: integration hooks and ClientRouter lifecycle. Hono reference: official Node.js adapter guide.

Verify the Hono mount

With Node.js 22 or newer, run npm ci and npm run example:e05 from the package root. The standalone export mounts the package HTTP and MCP handlers into one pinned Hono app:

app.all('/agent-native/*', (context) => httpHandler(context.req.raw));
app.all('/mcp', (context) => mcpHandler(context.req.raw));

View tested source

The harness checks the ordinary HTTP result and an official MCP client call on loopback. If the listen address is occupied, stop the other process or choose another PORT; the fixture reports server_error=address-in-use. See the E05 application instructions for local start, stop, and shell-only credential cleanup.