Adom Hydrogen

@@ -212,6 +212,31 @@ reports against the version the PAGE renders. Do this whenever you screenshot or Know its limit, honestly: it catches a stale PAGE, and it PASSES cleanly when the page is current but RENDERING wrong, which is the more common failure. +### Enumerate EVERY instance, not just the one that answers++Measured on fusion, 2026-08-24. A version cross-check that asks a single server is not+enough, because a stale instance answers just as confidently as a fresh one.++Probing the app's port range on the box turned up THREE stale dashboards squatting ports+(1.9.187, 1.9.189, 1.9.193, up to fifteen hours old) and NO current instance: the package had+updated correctly, but that launch's serve step never produced an instance, most likely+because `await: "url"` was watching while `pkg update` still held the step. A dashboard was+"running" in every sense a single probe could detect, and it was the wrong one.++> "The dashboard is current" and "the dashboard the user is looking at is current" are+> different claims.++So: scan your whole port range, ask each instance its version, and bind the webview only to+one that matches the installed build. Adopting a version-matched instance and refusing the+rest is what let fusion's second launch land on the correct server instead of a zombie.+Retire your own stale instances (see the port-ownership rules above) rather than leaving them+to answer someone else's probe.++Related trap from the same investigation: an install step whose `skip_if` is+`command -v <your-cli>` skips `pkg install` whenever ANY version exists, so the app never+updates through the normal path and only a forced update ever moves it. Use the+install-or-update pattern instead.+ ### Regex escapes die inside a JS template literal  The rule that actually catches this class of bug, measured on pup 2026-08-24 by replaying