Track upstream click dispatch gap for inline onclick fixtures

[fitchmultz]

Summary

External testing still reports click @e... / semanticAction-resolved clicks on buttons with inline onclick="fn()" attributes failing to fire app handlers, while programmatic eval --stdin element.click() works.

Current wrapper state

The extension now handles the wrapper-owned part:

• Top-level click-dispatch diagnostics cover exact CSS/XPath selectors and eligible @e... refs using latest snapshot role/name metadata.
• A miss fails loudly with details.clickDispatch instead of silently reporting success.
• Docs explain inspect-click-dispatch-miss / retry-click-after-dispatch-miss and the static-fixture-only programmatic .click() workaround.
• SUPPORT_MATRIX tracks RQ-0120.

Evidence

• Maintainer minimal direct probe on a simple file fixture showed inline onclick firing for selector and @ref clicks, so inline attributes are not universally broken.
• External richer fixture still fails, and the new diagnostic confirms no trusted DOM event reaches the intended element.

In-scope next action

Keep this issue as the local tracking link for upstream/root-cause follow-up. Need a minimal upstream repro HTML/command set where direct agent-browser click @e... fails but eval --stdin element.click() succeeds. The extension should not auto-replay with element.click() because it changes semantics to an untrusted scripted event and could bypass user stop boundaries.

[fitchmultz]

Orchestrator triage on current main (b7cf5b3, released as 0.2.37): this is valid as a click-dispatch correctness tracker, but the wrapper-owned mitigation is already implemented and verified.

Evidence checked:

• docs/SUPPORT_MATRIX.md tracks RQ-0120 and the earlier RQ-0089: simple direct upstream inline-onclick probes work, while richer reports are likely hit-target/overlay/ref-resolution or upstream browser dispatch gaps.
• extensions/agent-browser/lib/orchestration/browser-run/click-dispatch.ts installs bounded top-level non-Electron click probes for exact CSS/XPath selectors and eligible @e… refs using latest snapshot role/name metadata.
• docs/TOOL_CONTRACT.md documents details.clickDispatch, no in-page replay, next actions, and the static-fixture-only status of programmatic eval --stdin element.click().
• README.md and docs/COMMAND_REFERENCE.md tell agents not to treat scripted .click() as proof of user-like click behavior or as a stop-boundary bypass.
• Regression coverage: test/agent-browser.extension-click-dispatch.test.ts covers ref-click probing and the no-native-event failure path.

Fresh validation run:

• npm run verify ✅
• npm run verify -- real-upstream ✅
• Published package state: npm latest is pi-agent-browser-native@0.2.37, matching current release.

Status: blocked / upstream-boundary / needs-repro. Remaining work needs a minimal upstream repro HTML plus exact direct agent-browser commands where trusted/user-like click @e… fails but explicit eval --stdin element.click() succeeds. If that repro shows a wrapper-specific target-resolution miss, we can reopen local implementation work; otherwise the root fix belongs upstream/browser-side. No further local wrapper code change is justified without that repro.