H6199 Qualification Candidate

Candidate for #294 (blocks #293), built on the existing H6099 prerelease lineage.
This is not a claim of full H6199 support or a reproduced fix on the older
HW1.00.01/FW1.07.02 reported in #293. Both issues remain open.

Changes

• Preserve H6199 white-balance mode and device-reported defaults through recovery; legacy missing modes remain unknown rather than fabricated manual state.
• Restore Spectrum/Rolling fixed-colour capability metadata and accept device-validated sensitivity 0..100.
• Decode ordinary DIY selector/code without enabling unqualified activation or uploads.
• Add opt-in camera-position, strip-direction and Gradient configuration selects, all disabled by default, plus a camera-status diagnostic. These new controls require the exact qualified HW3.02.01/FW1.10.04, Wi-Fi HW1.03.00/FW1.00.33, Pact2/1 revision.
• Apply revision-aware video-register requirements; missing optional newer replies no longer fail basic setup. Reconnect waits for fresh qualification before guarded writes.
• Preserve successful native-register polling observations across intentional disconnects; unanswered camera queries remain unknown, not absent.
• Segment failures no longer restore stale observed state. Confirmation compares complete fresh readback with requested values and observed untouched siblings.
• Add Pact/qualification diagnostics and a complete findings/verification ledger in docs/h6199-support-findings.md.

Validation And Limits

Final make check passed: 2,069 Python tests passed, 78 skipped; generated protocol
checks, frontend unit/browser tests, lint, formatting and type checks passed.
Independent correctness and separate Ponytail ultra reviews passed after findings
were fixed. H6099 and other-model regression checks are included.

Physical direct-register evidence predates this candidate. Installed-RC HA
workflows, visible Gradient/orientation/music behavior, camera absent/incompatible
states and older hardware remain unqualified. New layouts remain explicitly
speculative until official-app capture and owner qualification requirements are met.

Additional Basic/Mixed DIY uploads, legacy DreamView membership/protocol/capacity,
selected-segment temperature authoring and general ACK/transport-deadline gaps
remain recorded rather than silently enabled. General refresh GATT writes still
depend on existing transport/caller deadlines; no blanket pacing change was made.

Installation Gate

Maintainer testing must wait for explicit owner approval of this exact RC before
HACS download/install or HA restart. Take a fresh verified backup and capture
complete restorable device state first. Verify the running manifest is 7.6.0rc2,
not merely HACS download metadata, and restore/re-read device state afterward.

Rollback target for the current test installation is v7.6.0-rc.1.h6099 through
HACS plus a restart, with the fresh backup available if HA state restoration is
needed. HA backup does not restore device-resident DIY content or DreamView
membership, so these mutations require separate approval and restoration evidence.
Do not post full diagnostics, Bluetooth addresses, serial numbers or credentials.

The attached SHA-256 file verifies the integration archive. The immutable tag
identifies its reviewed source SHA; the packaged manifest alone does not encode it.