Verification checklist — Brother QL / PT

Hardware verification now runs through the harness app. It walks through device detection, prints a diagnostic, and submits a hardware report issue automatically — no manual CLI transcription, no scattered captures.

Browser harness

Open https://thermal-label.github.io/harness/brother-ql/ in a Chromium-class browser, click Pair, select your QL or PT printer, and follow the prompts. The harness runs the identity probe, prints the diagnostic, and prefills a GitHub issue when you're done.

CLI harness

For TCP-9100 network models (QL-720NW, QL-810W, QL-820NWB / NWBc, QL-1110NWB / 1115NWB, QL-580N, QL-1060N) and any transport the browser can't reach, run from a checkout of the harness monorepo:

pnpm --filter verify-cli verify brother-ql <model-key>

Fallback

Hand-rolled report? Open the hardware verification issue template directly.

Driver-specific notes for the verifier

• PT-* models are first-verifier territory. The PT-P / PT-E registry is built from nbuchwitz/ptouch's transcription of Brother's spec PDFs. If you have a PT, you are the first reporter on that chassis — flag this in the issue so the maintainer knows to scrutinise.
• PT-E550W cutter quirk. The encoder guard automates this, but if a print with { autoCut: true, compress: false } does not throw on your unit, capture that — it would mean the firmware behaviour drifted from the documented quirk (see DECISIONS.md D14).
• Mass-storage PIDs are missing for most PT models. Only PT-P750W's mass-storage PID is currently in the registry. If your PT unit ever enumerates as mass storage on a PID different from its printer-class PID, capture that PID via lsusb / Device Manager / System Information and add it to the report.