Additive against 0.5.0; existing embeds are untouched.
<qr-status> picks its own rows. rows takes any subset of browser ipv4 ipv6 camera overall; the default stays ipv4 ipv6 overall, so nothing changes unless you ask for it.
<qr-status auto rows="browser ipv4 ipv6 camera overall"></qr-status>Two new probes behind it. probeBrowser builds a throwaway peer connection and a negotiated data channel — a browser that cannot do WebRTC fails before any question about NAT is meaningful. probeCamera reads the Permissions API and never calls getUserMedia: checking by trying would raise the very prompt the chip exists to report on, at page load. Where the state is not exposed (Safari) the chip is amber and says the answer shows itself only on the attempt.
Docs. docs/connection-security.md explains why skipEncryption is sound with a signed SDP, and when it is not. Two corrections in the README while there: skipEncryption skips Noise, not encryption — DTLS never stops — and oversized payloads have been animated BC-UR sequences since 0.3.0, not a copy/paste fallback.