NuvioWeb v0.1.4

NuvioWeb v0.1.4

Trakt sign-in works for the first time, installed apps take new builds again,
and auto stream selection no longer shows the screens it exists to skip.

New

• A second way back from an external player. A Shortcuts Automation opens
  NuvioWeb when the player closes, needing nothing installed or configured on
  the server. Quick Setup asks how you want to come back and starts with no
  answer rather than a guessed one.

Fixes

• Auto stream selection showed the screens it exists to skip. Selection ran
  on the stream screen, so the picker stayed up for the whole fetch, and
  Continue Watching painted the Detail page before replacing it. All three steps
  now paint one waiting screen. Which stream wins is unchanged.
• Trakt authorization could never have worked. The bridge required a client
  secret Trakt no longer issues, requests reached Cloudflare with no User-Agent
  and came back 403, and the dev server never mounted the bridge — so neither
  fault could be found outside a container.
• An installed app stopped taking new builds. The service worker filled each
  new cache through the browser's HTTP cache, so a new build's cache filled with
  week-old bytes.
• A failed stream said nothing at all — no error, no reason, no offer of
  another source. The player's error handler threw before it could render, and
  silently.
• Changing the Library Source threw after saving it. The value persisted,
  the confirmation never came, and five screens went on showing the old source.

For self-hosting

• TRAKT_CLIENT_SECRET is no longer required. Trakt stopped issuing one to
  applications that sign users in, so an application created today never has
  one. It is sent when it exists and left out when it does not, so an existing
  deployment keeps behaving exactly as it did.
• The Trakt bridge is mounted by npm run serve, so sign-in can be exercised
  without building a container.

Internal

• npm run lint covered thirty files out of three hundred, and services/**,
  sw.js and boot-guard.js matched no configuration entry at all — not
  lightly linted, never linted. It now runs against the repository.
• Two of the bugs above were no-undef, which lint reports in under a second,
  and a third lived in the directory with no rules. Thirty-six problems were
  cleared to get there.