mirror of
https://github.com/d4rken-org/capod.git
synced 2026-09-15 02:36:12 -04:00
darken
dbd1d422c6
Everything that reinterprets what the device reported moves to its own branch (anc-echo-classifier), leaving only changes that stand on their own. The classifier addresses a fault that has never been observed being handled: it reproduced on two of four sessions and none since it was written. It also adds a failure mode that did not exist before, where a report misattributed to our own write makes CAPod show a mode the device is not in. That is a poor trade to carry into main on the strength of tests alone, so it waits until it can be seen working against a live fault. What remains does not depend on the misreport: - the verification deadline was 1000ms while the device answers in 833-1008ms, so a healthy reply could land just after the timer and trigger a bogus divergence plus a redundant re-send; this was captured live - a listening mode request the device did not confirm produced no feedback at all for any mode except Off, which was a gap in the event plumbing rather than a timing artifact - a mode outside the device's listening mode cycle was rendered as an ordinary selectable button whenever it happened to be the current mode - an Off report arriving while a different mode was requested could teach the Allow Off inference, persisting "Off is permitted" into the device profile Also drops effectiveAncMode, which only had an effect while the classifier was present.