The e2e smoke tests in src/smoke-tests/__tests__/e2e-mcp-ui-automation.test.ts call tap with { x: 100, y: 200 }, { id: 'myButton' }, and { label: 'Submit' } — fields that no longer exist in the new elementRef-only schema. Those calls will now return schema-validation errors, but the tests only check content.length > 0, so they silently pass while testing nothing meaningful.

The new shouldInvalidateRuntimeSnapshotAfterActionError function (which decides whether stale snapshot state is cleared on error) has no unit tests — only integration/snapshot-suite coverage via a live simulator. Have you considered adding a small unit test to verify that only AxeError triggers invalidation while SystemError and DependencyError do not?

isScrollableRuntimeArea in src/utils/renderers/domain-result-text.ts returns element.actions.includes('swipeWithin') && !isLikelyRuntimeTarget(element). Because isLikelyRuntimeTarget short-circuits to false for hidden labels (via isHiddenRuntimeTarget), a hidden-label element (e.g. 'sheet grabber') that carries both swipeWithin and tap/typeText actions will be classified as a scrollable area in the text renderer. The parallel filter in src/utils/structured-output-envelope.ts (lines 229–237) explicitly requires !element.actions.includes('tap') && !element.actions.includes('typeText'), so the same element is excluded from the compact runtime envelope. Agents that compare the text rendering with the structured envelope may see mismatched scroll sections for this edge case. Impact is limited because the divergence only manifests for hidden-label elements that also expose tap/typeText, which should be uncommon.