fix(gui): resolve assets for HID++ 1.0 Unifying devices via WPID fallback

[luisfacarmo]

Summary

HID++ 1.0 Unifying devices (many keyboards like K540/K545, K375s, etc.) report DeviceModelInfo with all-zero model_ids because they lack feature 0x0003. The normal asset resolution path fails for these since neither the strict nor suffix candidates match the registry — even though the registry contains their assets keyed by WPID.

Changes

crates/openlogi-desktop/src/services/assets.rs

• Added resolve_by_wpid() method on AssetResolver that formats the WPID as a 4-hex suffix and matches against the registry via find_by_model_id_suffix. Falls back to codename/displayName matching.

crates/openlogi-desktop/src/state/devices.rs

• In build_device_list(): when cache.resolve(model, codename) returns None, fall back to cache.resolve_by_wpid(paired.wpid, paired.codename). This covers the case where model_info is Some but contains all-zero IDs.
• When asset resolution fails entirely, consult the persisted identity in config to preserve a known display name instead of falling back to "Slot N".

crates/openlogi-desktop/src/state/inventory.rs

• Added anti-downgrade guard in persist_identities(): a resolved identity (one with a real product name) cannot be overwritten by a fallback identity ("Slot 3") when the resolver temporarily fails.
• Added identity_is_resolved() and is_fallback_display_name() helpers.

Testing

Tested on real hardware: Logitech K540/K545 (WPID 0x4076) via Unifying receiver on Debian 13 Trixie.

• Device correctly shows "K540/K545" with front.png asset in carousel and detail view
• Identity remains stable across multiple inventory refresh cycles (2+ minutes tested)
• Config does not regress to "Slot 3" after restarts
• No regression on HID++ 2.0 devices (mouse on same receiver works normally)
• No duplicate device entries created

How to test on hardware:

1. Pair a Unifying keyboard that uses HID++ 1.0 (K540, K545, K375s, etc.)
2. Run OPENLOGI_LOG=debug openlogi list — should show wpid=4076 for the keyboard
3. Open the GUI — device should display its product name and image, not "Slot N"
4. Wait 1-2 minutes — name should remain stable

Fixes #(new issue — HID++ 1.0 Unifying devices show as "Slot N" despite having assets in the registry)

[greptile-apps]

Greptile Summary

This PR adds WPID-based asset resolution for HID++ 1.0 devices and protects resolved device identities from transient fallback values. The attempted receiver-slot reuse fix remains incomplete because the matching guard discards the available WPID before deciding that an unidentified replacement is the previous product.

• Resolves asset registry entries by WPID suffix, with codename fallback.
• Reuses persisted product names during temporary asset-resolution failures.
• Adds anti-downgrade identity persistence and model-comparison guards.

Confidence Score: 4/5

The PR is not yet safe to merge because a same-kind device re-paired into an existing receiver slot can still inherit the previous occupant's identity when codename and model information are unavailable.

The new guard defaults to treating an unidentified same-kind slot occupant as the prior product while omitting the live WPID discriminator, leaving the previously reported stale identity, artwork, and capability metadata reachable.

Files Needing Attention: crates/openlogi-desktop/src/state/inventory.rs and crates/openlogi-desktop/src/state/devices.rs

Important Files Changed

Filename	Overview
crates/openlogi-desktop/src/services/assets.rs	Adds WPID-suffix and codename asset resolution for devices lacking usable HID++ model information.
crates/openlogi-desktop/src/state/devices.rs	Integrates WPID asset fallback and persisted-name reuse, but the identity check cannot use WPID when other model clues are absent.
crates/openlogi-desktop/src/state/inventory.rs	Adds anti-downgrade persistence, but its no-discriminator branch still preserves stale identity after same-kind receiver-slot replacement.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Receiver slot inventory] --> B{Asset resolves by model or WPID?}
  B -->|Yes| C[Build resolved identity]
  B -->|No| D[Build fallback identity]
  D --> E{Codename or model_info distinguishes occupant?}
  E -->|Yes, different| F[Replace persisted identity]
  E -->|No evidence| G[Preserve previous slot identity]
  G --> H[Replacement can show stale product metadata]

Loading

_{Reviews (5): Last reviewed commit: "fix(gui): scope anti-downgrade guard to ..." | Re-trigger Greptile}

[greptile-apps]

Receiver-slot identity remains stale

When a same-kind device is re-paired into an existing receiver slot without a codename or model_info, same_model_identity treats the absence of contradictory evidence as a match even when the live pairing record has a different WPID. The guard then preserves the previous occupant's display name, model metadata, capabilities, and registry identity until another discriminator becomes available.

Knowledge Base Used:

• Core domain and configuration
• Device integration stack