KiCad - the KiCad Bridge

@@ -512,3 +512,29 @@ one bar is how percent walks backwards. Known gap: verbs that short-circuit before the dispatch chokepoint (`readiness`, `describe`, a few other read-onlys) are not logged. All are sub-second reads; if one ever grows a slow path, move it behind the chokepoint.++## 🅰 The Adom taskbar overlay: what it MEANS (John, 2026-08-22)++The overlay badge on a KiCad taskbar button has exactly one meaning:++> **"Adom is driving KiCad for you, right now."**++Everything about its implementation follows from that sentence:++- **It tracks ACTIVITY, not ownership.** It is stamped at the dispatch+  chokepoint whenever a GUI verb runs, on every live KiCad window - including+  a KiCad the USER launched, because a verb navigating their editor is Adom+  driving it. (The original implementation badged only bridge-spawned windows,+  so driving a user's KiCad via web control showed nothing - the exact case+  the badge exists for.)+- **It comes OFF when the driving stops.** An idle watchdog clears every badge+  5 minutes after the last KiCad verb (`_IDLE_CLEAR_SEC` in win_taskbar.py):+  "Adom is no longer driving KiCad, it's yours." A badge that never clears+  decays into wallpaper and stops meaning anything.+- **Never badge at boot.** A freshly started bridge is driving nothing; boot+  re-badging said otherwise and was retired.+- The 0.9.154 rule survives in its correct scope: never badge a KiCad that+  Adom is NOT touching. Activity semantics satisfy it automatically.+- The badge asset is `resources/adom-overlay-32.png`, mark anchored TOP-RIGHT+  (matching pup); the anchor in the 32px canvas decides the corner.+- Toggle: `overlayBadges` in settings (sticky per box, dashboard gear).