[nyannoying1337]

From the Discord list - the "prefer board name when system product is vendor-only" item, adapted to how upstream actually collects this.

The Windows motherboard command selects Manufacturer only, so the value is a bare vendor - ASUSTeK COMPUTER INC. on my machine. Linux already returns board_vendor + board_name, so this looks like Windows being the odd one out rather than a deliberate choice.

That costs twice over:

• The host cycle's top_line and app_id are both motherboard, so the cycle's title and large_text are a vendor name and say nothing about the actual hardware.
• It's also the string get_component_id matches against, so only the vendor's own pattern can ever hit. The board-model patterns already sitting in motherboards.json ((?i)tuf, (?i)Z370XP SLI, (?i)H310M A 2.0, ...) are unreachable on Windows.

Including Product matches the Linux shape:

before: 'ASUSTeK COMPUTER INC.'
after:  'ASUSTeK COMPUTER INC. PRIME B760-PLUS D4'

and a TUF board now resolves to the TUF app id instead of the generic ASUS one. The vendor is still in the string so anything that matched before still matches - there are tests for both directions. Given how much of the tracker is "Unknown motherboard", making more of the existing table reachable seemed worth it on its own.

Not addressed here: the host field (BaseBoard Product on Windows) is collected every snapshot but no cycle in fetchcord_conf.yml references it, so it's a PowerShell call for nothing. Happy to either wire it up or drop it in a follow-up - whichever you'd prefer.