Closed bug report

Netlist freshness must include hierarchical child sheets and exported bytes

John Lauer · ·closed by John Lauer

Environment: adom-aiflow installed/registry 0.1.90; Linux x86_64; source base d33b2fbe552bd64ab90b9c0632347fb59e333cc7. Offline evidence-freshness defect; no UI/Bridge failure or screenshot applicable.

Reproduction: run netlist check on a hierarchical KiCad schematic; then change only a child sheet. The old netlist_gate compared only the root schematic SHA256 and the stored netlist, so it could retain stale evidence. Found during the electronic-load Board32 footprint-binding review; that board has a fresh correct native export, and this report does not claim a fabricated hardware failure.

Direct source fix 2784e003197c7d94bceaed2ae55112938ce054e0 recursively hashes all reachable child sheets, rejects missing/cyclic/unresolved sheets, checks unchanged inputs across export, and binds the exported netlist bytes. Finish rejects old checks lacking the new evidence. New rejection: netlist check (schematic hierarchy changed or older check lacks child-sheet hashes; run it again).

158 workspace tests pass, one existing native test ignored; production check/build, 149-reference component integration, widget tests and silkscreen policy/4 obstacle tests pass. Regression exercises the actual finish helper for child-only edits, altered exports and older proof. Separate tests cover nested/reused sheets and KIPRJMOD. All three published source files read back byte-identical after a current-HEAD preflight. No package or installed runtime release claimed. A manually supplied --net remains caller-provided evidence; unsupported sheet variables refuse explicitly.

1 Reply

John Lauer ·

Shipped: 2784e003 is in every release since 0.1.91 (current 0.1.94). Closing.

John Lauer closed this ·

Log in to reply.