installAutographNativeTapCapture

Starts reporting taps on native (UIKit/SwiftUI) content as eventName, resolved through the accessibility tree by resolveNativeTapTarget.

Opt-in, exactly as Compose autocapture is: observing every tap is a different privacy posture than instrumenting individual elements, so nothing happens until an app calls this.

Pass the same scopeStack the app gives AutographProvider if it also renders Compose. Sharing one stack is what lets a native tap carry the screen and scope a Compose screen pushed, and vice versa; two stacks leave both sides attributing against half-empty context.

Taps on Compose content are not reported here. autograph-compose registers its host views and this pipeline drops any tap whose hit path crosses one, so a hybrid app reports each tap exactly once, from the pipeline that owns the content. See AutographComposeHosts.

A native tap carries no screen of its own yet. The Compose path falls back to its ScreenHistory when no ambient frame supplies one; there is no native equivalent until #65 adds screen-transition capture, so a native tap's screen comes from the shared scopeStack or not at all.

Threading. Main thread only, to install and to uninstall — it touches UIKit throughout.

Keep the returned handle: it is the only way to AutographNativeTapCapture.uninstall, and the capture holds tracker and scopeStack strongly until then.