Closed general

Live landing retries board_mismatch and hides the IPC identity refusal

John Lauer · ·closed by John Lauer

AI Flow capture open successfully opened the isolated board, then place land retried board_mismatch twenty times and finally reported no_revision with a misleading courtyard hint. No mutation occurred.

Commands (each uses --ai-thread "ESC AI Flow Astra" --run /home/adom/aiflow-landing-proof-20260918): adom-aiflow capture open adom-aiflow place land --moves /home/adom/aiflow-landing-proof-20260918/moves.json --pause-ms 1200

Bridge reply:

{
  "_hint": "Read kicad_routing_state with the exact filePath and socketPath. Enable Preferences > Plugins > Enable IPC API server in KiCad 10.0.1+ (kicad_ipc_api {\"enable\":true} writes the switch; KiCad must be closed and relaunched). After a mutation timeout inspect the live board; never blindly replay it.",
  "_reportIssues": "THIS MAY BE A KICAD BRIDGE BUG. Check for a duplicate with `adom-wiki issue list adom/kicad-bridge`, then file: `adom-wiki issue create adom/kicad-bridge --title \"<symptom>\" --category bug-report --body \"<what you ran, expected, got, the verbatim response JSON, bridge version, OS>\"`. An ab-core problem (relay, lifecycle, identity) belongs on adom/adom-bridge instead.",
  "_timeoutHint": "ab waits up to 130s for this verb before the request times out. If it's a long operation (cloud open / download / export), DON'T treat a timeout as failure — the work usually keeps running on the bridge. Poll `kicad_status` until it reports done.",
  "bridgeVersion": "1.0.17",
  "durationMs": 112,
  "elapsedMs": 29,
  "error": "This IPC endpoint does not expose exactly the requested board",
  "errorCode": "board_mismatch",
  "kicadVersion": "10.0.5",
  "mechanism": "ipc",
  "openBoards": [
    "C:/Users/john/Downloads/adom-gate/esc-demo/component-mpn/esc-g431-astra-silkscreen-v37.kicad_pcb"
  ],
  "output": "",
  "schemaVersion": 1,
  "status": "error",
  "statusVerb": "kicad_status",
  "success": false,
  "timeoutSeconds": 130
}

KiCad serves one IPC socket owned by its first process. The separate editor was visible but inaccessible through that endpoint. Expected: fail immediately with the full board identities and an actionable instruction; capture readiness should distinguish window-open from IPC-ready. Workaround: save and close only the task-owned Astra windows, then reopen the isolated board first, and restore the finished board afterwards. Source fix stops retrying permanent identity/configuration refusals and preserves the original reply. Real landing test continues.

1 Reply

John Lauer ·

Published and installed AI Flow 0.1.28. Permanent board_mismatch/configuration errors stop immediately, full Bridge replies are retained, and capture open now confirms exact-board IPC readiness. Workaround verified: save and close only task-owned editors, then reopen the isolated board first. Two native parts landed individually in 17.8 seconds; two GND paths in one net landed as two calls in 12.4 seconds, with distinct revisions. Native readback confirms both positions and six resulting segments. Preflight found zero new DRC errors; remaining unconnected items are expected for this partial test. Original finished ESC was not edited. Failed static take rejected. Source, installed package and active binary hashes agree.

John Lauer closed this ·

Log in to reply.