cjkas 4f8eac03ac refactor: move the shade's behaviour into ShadeBehaviour ... PR B of SHADE_BEHAVIOUR_PLAN.md. What a shade does with frames, commands, group commands and radio events moves unchanged from SomfyShade into ShadeBehaviour, which builds natively and is pinned by test_shadebehaviour. ShadeBehaviour reads ShadeSettings and RemoteSettings, gets the time on every input, and holds the motion state that other files now read through state(). It sends through MotorLink and reports through ShadeEvents (changes, commands, save wanted, sensor flags) as things happen. SomfyShade wraps it: its MotorLink is SomfyRemote::sendCommandAfter, which now leaves the sender out of the echo and radio hold because the module hears its own frame. lastFrame stays shared with the send path. ConfigFile writes through restore() and clearTilt(), SomfyShadeOps through setPosition(). The pinning tests label where the copies of a rule disagree "today:", for the reconcile phase. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-16 21:21:38 +02:00
..
adr	docs: plan domain modules behind a LoopQueue	2026-10-15 21:38:43 +02:00
KNOWN_ISSUES.md	refactor: split the transports into the modules GLOSSARY.md names	2026-10-16 13:47:56 +02:00
LOOP_QUEUE_PLAN.md	refactor: split the transports into the modules GLOSSARY.md names	2026-10-16 13:47:56 +02:00
NICE_TO_HAVE.md	docs: add agent testing instructions and the RMT transmit idea	2026-10-16 09:11:17 +02:00
SHADE_BEHAVIOUR_PLAN.md	refactor: move the shade's behaviour into ShadeBehaviour	2026-10-16 21:21:38 +02:00
SOMFY_SPLIT_PLAN.md	refactor: move the transports into entryPoints and outputs	2026-10-15 19:41:49 +02:00