[JaredP94]

Description

Browse events re-enrich every peer but deliberately never self, and self was enriched only at startup, on service (un)registration and after identity/address changes. The local node's VRAM, CPU and memory in the discovery snapshot — the one the scheduler reads — stayed at startup values while every peer's view of it moved. The fork's live telemetry loop refreshes only utilization.

Self is now re-enriched over loopback on the existing 15 s peer-refresh tick, and emits only when the entry changed beyond LastSeen, so an idle node adds no notifications.

Fixes NVIDIA#4; adapted from NVIDIA#5, which emitted every tick.

Validation

go test ./... in nvpair-node-scanner, with a new test: unchanged → no emit, VRAM change → refreshed and one emit.

Risk

Low. scanner 1.2.1.

Checklist

• I have read the Contributing Guidelines.
• Every commit is signed off (git commit -s), certifying the Developer Certificate of Origin.
• New or existing tests cover the change.
• Relevant documentation is updated.
• I checked the diff, changed filenames, and commit messages for credentials, private data, internal URLs, internal issue identifiers, and generated artifacts.
• I recorded the validation commands and results above.
• I bumped any affected component in services/versions.json, and described user-visible changes above so they reach the release notes.

Part of the upstream issue/PR review. Each branch is independent off main; they all bump services/versions.json, so the second one merged will need a trivial conflict resolution there.