0.105.0 — Record real crossings between areas

0.105.0 — Record real crossings between areas

Bug fix only. The Connections view never recorded a genuine crossing such as
New Phlan → the Slums. The recorder discarded the departure square on any
frame the probe could not read, and a real gate crossing always shows
"Position unavailable" for a moment while the next area's map loads and is
authenticated. So the arrival never had a departure to pair with.

Unreadable frames now bridge the crossing the same way busy frames already
did. Every guard that stops a shortcut from being invented is unchanged: the
arrival must carry the same travel epoch, exactly one native area change and
a matching departure square, and polling must not pause for more than 1.25
seconds. Loading a save, skipping an area or backgrounding still records
nothing.

Verified by unit tests that replay the crossing as the probe reports it
(departure, three unreadable frames, arrival) and that the epoch, serial and
polling-gap guards still refuse across unreadable frames. Not watched live:
the sandbox emulator spent this session stuck behind the game's copy
protection prompt and normal-shutdown tooling, so the walk from New Phlan into
the Slums was not completed on this build. The app now logs one line per
travel-sample change under , so the first real crossing on a
device will show the departure, the unreadable frames, the arrival and the
recorded edge. If it shows the travel epoch changing across the crossing, the
remaining cause is on the native side and this release will not have fixed it.

Also in this build: the debug-access typing helpers the test harness drives
over JDWP are restored after the loader cleanup removed them; the loader
itself stays gone. 733 Java tests pass.