cjkas 5737a58790 fix: command op replies that said ok when nothing was done ... From the review of #100: - setMyPosition on a moving shade replies busy ("The shade is moving"), and setPositions with only a tilt, for a shade without one, replies bad request ("The shade has no tilt"). Both said ok before. - PROTOCOL.md lists where the ops differ from the routes, and how sendRemoteCommand is answered. - The LoopQueue hold comment covers protocol 2 replies and an unpair held through a frequency scan. - One shadeRequestIsForGroup() for the group cases; ProtoOps shares one reader for "one or both" fields and one for ids, and the radio refused text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-24 13:46:00 +02:00
..
adr	docs: ADRs 0005-0007 for socket protocol 2	2026-10-22 20:50:33 +02:00
KNOWN_ISSUES.md	docs: move open known issues to GitHub, drop the finished plans	2026-10-21 13:27:49 +02:00
NICE_TO_HAVE.md	docs: add agent testing instructions and the RMT transmit idea	2026-10-16 09:11:17 +02:00
PROTOCOL.md	fix: command op replies that said ok when nothing was done	2026-10-24 13:46:00 +02:00
SECURITY_PLAN.md	fix: protocol 2 core review findings	2026-10-24 13:17:15 +02:00