feat(device): wire up the Lamzu Atlantis driver

[bpavlina]

Companion to OpenMouse-Project/mouse-protocol#85, which adds the Lamzu Atlantis generation (CompX vendor id 0x3554) as its own driver.

import { LamzuAtlantisHidClient } from "@openmouse/protocol/drivers/lamzu-atlantis/hid";

const NEEDS_OPEN = [LamzuAtlantisHidClient, TeevolutionHidClient, …] as const;

The client's transport is interrupt reports, so it attaches its inputreport listener in open() — without the NEEDS_OPEN entry the first readStatus() would sit waiting for a reply that nothing is listening for.

What the app shows once the protocol PR lands

Read from a Lamzu Atlantis Mini 4K, firmware 1.24, wired:

Field	Value
Name / brand	Lamzu Atlantis · Lamzu
Firmware	Mouse v1.24
Battery	100%, 4222 mV, Charging
DPI stages	400 / 800 / 2000 / 3200 / 6400, colours #ff0000 #00ffff #00ff00 #ffffff #ffff00
Polling	500 Hz, from 125 / 250 / 500 / 1000
Lift-off · debounce · sleep	Low (1 mm) · 4 ms · 60 s
Processing	motion sync on, angle snapping off, ripple off, competition mode on

Every value matches what Lamzu's own configurator displayed for the same mouse at the same moment.

Not included

No ui/device-images.ts mapping: there is no 3554:* artwork in the bucket, so the Atlantis resolves to unknown-device.png — the same treatment Orbital and moddo get today. Happy to add the mapping once art exists.

🤖 Generated with Claude Code

[snekxs]

CI failure and merge conflict both trace to the same root cause: this PR imports LamzuAtlantisHidClient from @openmouse/protocol/drivers/lamzu-atlantis/hid, but the mouse-protocol repo has no lamzu-atlantis driver module — only src/drivers/lamzu/hid.ts exporting LamzuHidClient (the existing Lamzu Maya-family driver). This looks like the companion protocol-side PR (adding the Atlantis driver class to mouse-protocol) either never landed or landed under a different module path/name than this PR expects.

Not something I want to guess-fix by writing a new HID driver class speculatively — that needs whoever wrote the original Atlantis wire-format work to confirm the report layout. Needs a maintainer to either (a) locate/merge the companion mouse-protocol PR that adds LamzuAtlantisHidClient, or (b) confirm the intended import path if it already shipped under a different name, after which this PR's own merge conflict in src/device/controller.ts (import ordering vs. newer driver entries added on main since) is a small, mechanical rebase.

[snekxs]

The protocol-side driver landed in mouse-protocol#91 after this PR was opened, which unblocked it. Resolved the one conflict (additive in controller.ts, sibling driver registrations) against current main in #249, now merged. Since I can't push to this fork branch, closing this one in favor of #249 — thank you for the Lamzu Atlantis work!