v1.7.0

Changed

• The sign-in page has been rebuilt. It is the one screen of this product a
  stranger reaches by scanning a QR code, on a 192.168.x.x address their
  browser decorates with a warning triangle, and it is where they are asked for
  a password — and it carried no mark of who was asking. It now opens with the
  TigerTag icon, keeps only what is needed to sign in, and ends with a way out:
  a Tiger Studio Manager button, GitHub, Discord and tigersystem.io.
  The password is masked with an eye to reveal it, the Google button carries
  the real Google mark and reads Continue with Google, the accents are back —
  that page is drawn by the phone's browser, so the panel font's ASCII limit
  never applied to it — and the firmware version is printed at the foot, read
  from the version macro rather than typed.
• The Google pairing page was rebuilt with it, and the device joins in. For
  as long as that page is waiting, the TigerSpool shows the same pairing QR and
  code on its own screen — so someone who started on their phone can finish on
  a computer by scanning the box instead of retyping a code, and a box that is
  waiting stops looking like a box that is idle. The page leads with scan the
  QR code on the TigerSpool screen, then the code, then or and a Continue
  with Google button for a browser already signed in. It no longer guesses
  where you are reading it: "open this link on a phone or PC" was advice to
  someone who had already done it, and equally wrong for someone who typed the
  address off the device's screen at a desk.
• Nothing on those pages is fetched from the internet. The phone reading it is
  joined to the device's own access point, where a remote font or logo fails
  silently — an empty box on the one screen where trust is being decided. The
  icon is served from flash by the device itself.

Fixed

• Choosing a language on a new device no longer freezes the screen. After
  the language, the setup QR took several seconds to appear — long enough to
  read as a crash rather than as work. Two causes, both removed: the access
  point ran a full Wi-Fi scan on its way up, synchronously, blocking everything
  behind a list nobody had asked for yet; and the QR was drawn only after the
  radio had finished. The QR now goes up first — its SSID comes from the MAC
  and is known before the radio does anything — and the access point comes up
  behind it, in well under a second. The network list is fetched by the portal
  when it is opened, which is where it is actually needed.