KiCad - the KiCad Bridge

@@ -78,17 +78,24 @@ matrix. Any live verb that is neither tested nor on the explicit skip list Prefer running while the box is idle anyway: GUI phases open ~6 KiCad windows in the background, which is churn the user can feel in the taskbar. -## Daily automation--Cron line for the container (matches the contract-drift-check pattern —-failures should turn into a wiki issue, not scrollback):--```cron-30 11 * * * [ "$(TZ=America/Chicago date +\%H)" = "06" ] && cd /home/adom/project/adom-desktop-kicad-bridge && python3 skills/kicad-bridge-test/run_verb_tests.py --target AdomLapper > /tmp/kicad-verbtest/cron.log 2>&1 || adom-wiki issue create adom/kicad-bridge --title "Daily verb test FAILED $(date +\%F)" --body-file /tmp/kicad-verbtest/report.md-```--Manual daily driving works too: run it, read `report.md`, file an issue per-new failure with the `response_head` from `report.json`.+## Daily automation (INSTALLED on gallia, 2026-08-14)++The daily run is live on John's main container:++- **Wrapper**: `/home/adom/bin/kicad-daily-verbtest.sh` — runs the full suite+  at 6:30am Central (DST-gated cron, fires 11:30+12:30 UTC), then files a wiki+  issue on adom/kicad-bridge ONLY for **NEW** failures relative to+  `~/.kicad-verbtest-baseline.json` — so an already-triaged failure (tracked in+  its own issue) doesn't spam a fresh ticket every morning. A suite that can't+  run at all (bridge/relay down) files too, with the log tail.+- **Baseline**: `~/.kicad-verbtest-baseline.json` `{"known_failures":[...]}`.+  When you triage a daily failure into a real issue, ADD it to the baseline;+  when you fix one, the wrapper auto-shrinks the baseline on the next green run.+  Baseline as of install: open_symbol_editor + open_footprint_editor (issue #21,+  plugin no longer binds in editors).+- Logs: `/tmp/kicad-verbtest/cron.log` (suite) and `cron-wrapper.log` (wrapper).++Manual driving unchanged: run the one command, read `report.md`.  ## Interpreting failures