Codex review on #400:
- The update check asked the public npm registry about every unpinned Pi
package, even when the environment or an .npmrc sends the package, or
its scope, to another registry. A public package with the same name
could then hide a real update or offer an unrelated version. The check
now reads the npm registry settings for the package and its scope from
the environment, Pi's npm folder and the user .npmrc, and falls back to
checking in Pi when any of them names another registry.
- The row's Update button disappeared as soon as any Agent had the
version the check found, so with one Pi target behind and another up to
date, the one behind lost it. The row now compares each selected Agent
with that version on its own, and updates only the ones behind.