GeezerVison

Problem

Vue Tracer and A11y opened from the Vite DevTools browser extension execute against the hub UI provider document instead of the inspected app. Action setup can also miss the first activation, and stale inspected-page sessions can deactivate newer sessions' actions.

Fix

Add a transport-neutral createInPageChannelRelay and an inspected-page endpoint in @devframes/hub-ui. Page scripts and actions execute in the inspected document; custom renderers stay in the hub UI provider document. Preserve existing panel channel APIs.

Complete action setup before activation, serialize remote activation and teardown, and track action ownership per connection. Preserve main's trusted eager initialization and setup cache while routing eager page/action scripts to the inspected document. Ignore stale page preparation after navigation.

Deduplicate pending document handshakes and retry every second with an attempt-specific identity. Close unclaimed or superseded grant ports and explicitly end their opposite endpoints, including when heartbeat is disabled. Panels send cancellation on close even before receiving a port. Relays match the originating window, origin, and handshake identity before cancelling, stop pending retries, and release late grants. Preserve direct in-page connections alongside relayed panels.

The demo action now performs its work directly on each invocation instead of accumulating activation subscriptions. Actions retain the per-activation execution contract established in #387.

Review follow-up: Vue Tracer

The demo action no longer accumulates activation subscriptions. The Tracer-owned dock and element-click subscription cleanup is implemented separately in antfu/vite-plugin-vue-tracer#13. This preserves the per-activation action contract established in #387; one-time framework setup alone would leave Tracer's inner click-listener leak intact.

Merge and release order

1. Merge fix(devtools): clean up tracer activation subscriptions antfu/vite-plugin-vue-tracer#13 and publish a Tracer release containing the subscription fix.
2. Merge fix(hub-ui): bridge tools to the inspected page #363 and publish the affected Devframe packages, including devframe, @devframes/hub, and @devframes/hub-ui.
3. Upgrade the dependencies used by fix(webext)!: bridge tools to the inspected page vitejs/devtools#563, validate the extension with both published fixes, then merge and release that adapter.

The first two fixes are independently mergeable and may be reviewed in parallel. The recommended order above puts the Tracer lifecycle fix first; the extension integration remains the final step. Published-package validation should include repeated Tracer activation, cancellation, and A11y inspection against the inspected app.

Verification

• pnpm lint and pnpm knip: passed.
• pnpm build: all 28 tasks passed.
• pnpm typecheck: coverage verification and all 40 tasks passed.
• pnpm test --run: 145 test files passed; 1,621 tests passed and 9 skipped, including API snapshots.
• Three cancellation regressions failed before the fix and passed afterward: closing a panel before the page script loads, with a delayed page grant, and with a delayed transport grant. These run with heartbeat disabled.
• Additional coverage rejects cancellation from another window, origin, protocol version, channel, panel, or instance.
• Full Tracer/A11y browser UI end-to-end scenarios were not rerun. Published-package validation remains the extension release gate.