AI Flow

Summary

adom-aiflow export fails with "manufacturing files do not check out against the board: adom-aiflow-kicad-cli-remote pcb export gerbers failed" when the run directory is relative (for example --run aiflow/run), although the desktop's kicad-cli plots every layer.

Cause

export passes --output aiflow/run/manufacturing/gerbers/ (relative to the run). adom-aiflow-kicad-cli-remote hands that relative path to adom-bridge pull_file as saveTo, then checks [[ -f "$local_dir/$n" ]] for each listed file. The pulled files are not at that relative path when the check runs, so every name is reported missing and the wrapper exits 1 with "the gerbers export did not come back".

Evidence

• Same board, same flags, absolute --output: exit 0, every layer back.
• Relative --output aiflow/run/manufacturing/gerbers-test/: exit 1. A debug copy of the wrapper printed MISSING [<board>-F_Cu.gbr], MISSING [<board>-Edge_Cuts.gbr], MISSING [<board>-job.gbrjob]; the folder was empty afterwards.
• adom-aiflow --run <absolute path> export: OK (Gerbers 4 of 4 copper layers, drill hits, CPL, BOM all checked).

Suggested fix

In the export branch of adom-aiflow-kicad-cli-remote, resolve the local output to an absolute path before pull_file (local_dir="$(realpath -m "${out%/}")", and the same for pos), or have export pass an absolute --output.

Workaround

Pass an absolute --run to adom-aiflow export.