KiCad lane gaps: no silkscreen proof writer, no export command, ffprobe-missing marks all clips blank, adopt voids copper evidence

Overview Files Skills Discover Packages Releases Dependencies Issues6 Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 7d ago ·closed by John Lauer

From a full KiCad run on adom-aiflow 0.1.91: a 6-layer OCP NIC 3.0 to OCuLink riser, routed by my own router inside the flow (high-speed section), run ocp-oculink-riser-claude-20261012-2119, page john/oculink-aiom-riser. These are the places the KiCad lane had to be worked around:

No KiCad command records the silkscreen proof. flows/board.json requires it, but only the Fusion lane writes it (fusion silkscreen / fusion-project.py prove). silkscreen-audit runs and passes without recording anything. I wrote <run>/proofs/silkscreen.json from my own tool (audit pass + native DRC + label plan + event log). A silkscreen land (or audit with --record) would close it.
No export command for KiCad. The flow text says "adom-aiflow export (Fusion: fusion export)", but 0.1.91 has no export subcommand. I used kicad-cli gerbers/drill/pos, re-read every file against the board (6 copper layers; PTH hits = vias + plated pads; NPTH hits; CPL and BOM refs = placed parts) and wrote proofs/export.json. The script is in the page's design/gen/export_fab.py; happy to turn it into the crate command.
Every clip is flagged "looks blank: no frames" when ffprobe is missing, and compose then skips those clips: the video had 2 of 18 step visits. The clips were fine (e.g. 3481 frames at 3818x2052). Missing ffprobe should be an error naming the tool, not a blank verdict on the footage.
adopt-board voids gate/land/measure/analyses, as documented. The fields re-solve after each silk-only or test-point adoption cost about 28 min at 0.1 mm. A silk-only adoption (copper unchanged, verifiable by comparing tracks/vias/zones/pads) could keep the copper evidence.
tour fields clip blank when the Fields app opens in a pup window on the test box (--on ConfRoomROG), although the URL answered 200 from Windows. Possibly the same ffprobe cause; worth checking once (3) is fixed.
Stalled-step WARNING fires during long legitimate solves (current: about 2 h waiting on the 6-layer fields work). Fine as a nudge; maybe skip it while an exec is running.

Filed separately: #45 (etch planner), #47 (rules/plan shape), adom/kicad-bridge#125/#126, adom/adom-fields#11.

2 Replies

John Lauer · 5d ago

adom-aiflow 0.1.94 covers items 1, 2, 3 and 6:

silkscreen-audit --record [--board <pcb>] records the silkscreen proof only when the audit passes, its inventory names every footprint by reference (R1, R1:body, R1-value), every via has an item, and there are at least 0.5 visible labels per footprint (finish's minimum). It stores counts and the board, audit and input hashes.
export (KiCad lane): Gerbers, drill and CPL through ADOM_AIFLOW_KICAD_CLI, BOM from the board, into <run>/manufacturing, then re-read: copper layer count from the Gerbers, both masks, silks and outline, drill hits against vias plus drilled pads, CPL and BOM references against placed parts (DNP and exclude attributes, sides, top rotations, quantities, values). Proof only when everything matches. Checked on real KiCad 10.0.5 through adom-aiflow-kicad-cli-remote (which now carries pcb export gerbers|drill|pos).
A missing ffprobe/ffmpeg is an error naming the tool; the clip is left unjudged, recut/compose refuse with the tool's name, and a later recut clears blank flags left by the old check.
The over-budget warning is held while an exec for the run is still running (tracked by id and pid; a dead exec does not hold it).

Still open: item 4 (keep copper evidence through a silk-only adopt-board). Copper evidence is bound to a whole-board hash in several checks, including the Fields report; it needs a copper-only fingerprint across all of them. Item 5 should be rechecked now that 3 is fixed.

John Lauer · 2d ago

The last open item (4) is done in adom-aiflow 0.2.3. adopt-board computes a copper fingerprint: tracks, vias, zones with their settings and fills, pads with geometry, net and drill, footprint pad placement, outline, stackup and project rule files. When it is unchanged (for example a silkscreen-only edit), the gate, landing, measurement, analyses and Fields evidence carry over, recorded with both board hashes. Every check that compared a whole-board hash accepts carried-over evidence only through that recorded match. Silkscreen evidence is still redone. Items 1, 2, 3 and 6 shipped in 0.1.94. Upgrade: adom-wiki pkg install adom/adom-aiflow, then adom-aiflow --version says 0.2.3.