v0.10.0

The first release published from CI, and therefore the first with provenance — npm records that the tarball was built by this workflow from this commit.

A relay, offered rather than assumed (#103)

findReachableRelays, readRelayOptIn and writeRelayOptIn are now exported from the package root, and the network measurement is reachable from the root rather than only from ./elements.

That last part is the point: network.js touches no DOM and imports nothing, but living behind the UI entry point meant a consumer who wanted the verdict and not the renderer had to pull in a bundle carrying a QR encoder, CBOR and a camera. One did the reasonable thing and wrote its own smaller probe — candidate found yes or no, no address family, no notion of a symmetric NAT. A thinner verdict for the reader least able to interpret one.

The measuring caption follows the language (#100)

<qr-status> wrote its progress caption once, when the probe started, and never again until it ended — so a strings table assigned mid-probe left that one line in the old language while everything around it changed. A probe takes STUN round trips, which is long enough for somebody to reach a language switch, and the line sits in the middle of the panel.

Found in ablage, which switches language from inside its introduction dialog and so lands in exactly that window.

Also in this release

Three test-side defects fixed, and the rest of the red characterised rather than chased: a test that asserted WebKit had no navigator.share (it does now), an ICE assertion running on the deadline meant for typos, and a suite whose WebKit specs fail a different random test on every parallel run — measured across six runs, all passing alone.

Minor, not patch. New exports are a feature. The bump was cut as 0.9.1 when #100 was the only change, then #103 landed; correcting the number before publishing rather than after, because npm keeps a version forever.