feat: add AJAZZ AJ179 PRO artwork mapping

[artembaechka]

Summary

Companion driver support: OpenMouse-Project/mouse-protocol#169

Add AJAZZ AJ179 PRO artwork resolution by the model name returned by the GearHub driver, not the shared VID/PID. Receiver, USB, and Bluetooth therefore resolve the same filename without overwriting artwork for sibling devices.

• Match both AJAZZ AJ179 PRO and AJAZZ AJ179PRO; do not match PRO MAX or unresolved receiver names.
• Add regression coverage for all three connection PIDs and sibling-model isolation.
• Record the official render's source and unresolved redistribution rights in the artwork README.

No CSS, layout, application architecture, dependency manifest, lockfile, or generated supported-device catalog is changed.

Artwork / maintainer action

Following this repository's artwork workflow, no vendor PNG or new local override is included. Please review licensing and upload ajazz-aj179-pro.png to the device-image bucket, or substitute redistributable artwork. Until then, the reserved URL uses the existing missing-image fallback.

Suggested source: installed AJAZZ Driver (R) 2.1.94, relative resource path resources/app/company/company_AJAZZMOUSE/dev/mouse_pan1080_g182_ajazz_3395_1k_8k.png. Its catalog maps the resource to AJ179 PRO / device id 1851. The source is a transparent 200x288 black top-down render; the local development preview places it on a transparent 300x400 canvas without rescaling.

Original SHA-256: 679d089ecc7faa11cadb210916a9ca82426e8c61f91f3c1f56b686ab06a2a463.

Redistribution permission has not been established; the vendor application's ISC manifest field is not taken as a license for product artwork. Official driver catalog: https://www.a-jazz.com/h-col-156.html

Verification

npm run check passed: production build and 267/267 tests, using the sibling local protocol package. Existing bundler warnings are non-fatal. The protocol dependency is intentionally not bumped before its release.

[snekxs]

Reverted in #613 — and to be clear about why, since this looks like a missing-asset problem but is actually a process one.

Device artwork is not stored in this repository. The images are hosted on my Cloudflare R2 bucket and served from img.openmouse.app, and I upload each render there myself. So https://img.openmouse.app/ajazz-aj179-pro.png returning 404 is expected: no PR can add a working image by adding a mapping, because the mapping and the asset are provisioned separately.

That is also why sibling reservations like noir-m2-nex.png and noir-s1.png look the same way — they are placeholders for renders I have not placed in R2 yet.

Nothing is wrong with the code here. The model-name resolution (matching AJAZZ AJ179 PRO and AJAZZ AJ179PRO), the PRO MAX exclusion and the shared-VID/PID sibling guard all checked out, and I reviewed the companion driver in mouse-protocol#169 separately — that one is unaffected and still on track.

What happens next:

• I upload the AJAZZ AJ179 PRO render to R2 so the URL resolves.
• Then this mapping can be re-landed (re-open this PR or open a fresh one — same three files) together with mouse-protocol#169.

If you have the render's PNG on hand, attach it here and it will save me having to source one.

[artembaechka]

Here is the official AJ179 PRO render for the artwork upload discussed in this PR:

Download PNG · suggested bucket filename: ajazz-aj179-pro.png.

Transparent 300×400 canvas, containing the original 200×288 render without rescaling. Extracted from AJAZZ Driver (R) 2.1.94: resources/app/company/company_AJAZZMOUSE/dev/mouse_pan1080_g182_ajazz_3395_1k_8k.png; the vendor catalog associates it with AJ179 PRO, device id 1851.

Redistribution rights have not been established; please review licensing before publishing it in the shared bucket. The PNG is hosted in my fork for this comment, not added to the already-merged upstream PR.