v0.8.6

###v0.8.6 (2026-06-07)

• Fix (docker): the /Docker page no longer renders completely blank (no toolbar, no skeleton) when you navigate away and back — especially while a container update or a "check for updates" run is in flight. On the newer Unraid web-component shell the legacy .page body (our mount point) can be injected a tick after our head-loaded bundle runs; boot() did a one-shot querySelector and bailed permanently when the root was absent. It now waits for the mount point via a MutationObserver (10s cap) before giving up.
• Fix (docker): a "check for updates" run now survives navigation. The run is a detached server-side worker (PID lock), but the "Checking…" UI was a per-instance flag that reset on reload, so returning to the page looked idle while the worker kept walking the registry. boot() re-attaches to an in-flight run and resumes polling, so the update badges refresh on completion as if uninterrupted.
• Feat (docker): a transient, dismissible banner now reports the result of a completed update check — N updates available / All containers up to date / a failure note — including the previously-silent "0 updates" case. Fires on both the normal and resumed paths.
• Fix (docker): install.php now appends ?v=<filemtime> to each injected page bundle URL, matching the cache-busting already applied to loader.js + modernui.css. A plugin update could otherwise serve a stale bundle until a hard refresh (the classic blank-page-after-upgrade).
• Chore (docker): added gated debug logging (off by default; enable with ?dockerdebug=1, a per-session sessionStorage flag) across the boot / resync / poll path plus a server-side transient-503 log line, to make this class of "fails to load" report diagnosable from the console. Inert unless enabled. 117 TS docker suites green.