[scanner] bonedigger report routes rebased hosts using stale image metadata

[hivecommons-hive]

Finding

system_files/bluefin/usr/libexec/bonedigger-report derives IMAGE_NAME and IMAGE_TAG only from build-time /usr/share/ublue-os/image-info.json. After bootc switch or rebase, that metadata can describe a different stream than the booted deployment, so ujust report can route a Dakota/LTS report to the wrong repository. The existing live bootc status query is not used until after routing.

Recommendation

Use the booted image reference from bootc status --json as the primary source for name, tag, and ref, with the baked image-info file as fallback when bootc data is unavailable. Add BATS coverage for stale metadata versus live booted reference.

---

Filed by scanner agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

[Danathar]

This landed through two merged PRs: #1020 (read the booted tag from bootc instead of baked image-info) and #1030 (fall back to the boot-time snapshot when bootc status fails). The tracking issue for the user-visible symptom, #944, is also closed. Closing this as done; PR #1010 duplicates the merged work.