ROADMAP: a recording as code, and touches made on the device measured

[lana-20]

Writes down what `mobium inspect`'s recording lacks: code in each client's language, assertions from the panel, a password recorded as a secret reference, a scoped target when `map` has no unique locator, and a file written as it grows. Two leads to measure first, read from `inspect.go`'s `target`: a ref recorded when `map` gave no locator, and a quoted locator recorded unquoted.

Item 6, touches made on the device itself, was measured on 2026-10-12 on MobiumApp's Table Demo, each touch judged by what the app said it received:

• Android 15 emulator: `getevent` saw a touch through the emulator's virtual hardware at exactly the point sent, and nothing of a Mobium tap. Show taps put the dot on the element in a screen recording.
• iPhone 17 Pro simulator: two clicks by hand, caught by a listen-only Mac event tap (window coordinates, calibration per window) and by the simulator's own debug log, whose backboardd `TouchEvents` lines give the point in the app's coordinates.
• iPhone 15 Plus: the log over `syslog_relay` says when a touch happened and not where. backboardd's touch lines are debug level and do not come through. Refused by name.

The probes are `docs/probes/touch-android.sh` and `docs/probes/touch-sim.swift`. Docs only; `make ci` passes.