Repository navigation
v0.28.0
Upgrade notes / behaviour changes
-
kct exportcan newly exit non-zero (Issue #8203). Environments without thereportextra must installkicad-tools[report]or pass--no-report. -
kct optimize-tracesnow loads the board for collision checking (Issue #8214). A board the router loader cannot handle (for example one with no Edge.Cuts outline) now exits 1 with a clear error instead of being optimized unchecked; the loader's cost is also paid on--dry-run. -
New
redundant_copperwarnings; readiness cleanup step (Issue #8218). Boards may newly showredundant_copper_*warnings (never errors).kct readiness --generatenow mutates the candidate PCB by removing exact-duplicate copper; pass--skip-cleanupto opt out (the skip is recorded inREADME.txt). -
kct creepage --waive-same-footprintcan newly fail (Issue #8232). Net pairs whose minimum issame_footprintnow carry an extraboardrow; if that board-level approach is below the requirement the gate fails despite the waiver. JSON/table output may contain two rows for one net pair. -
--waive-attach-zonecan now fail boards that passed (Issue #8292). Foreign copper outside a part's attach zone that is closer than the requirement to the part's in-zone pad now gates the pair. Move that copper or review the newresidual_witness_mm. -
kct optimize-traces --netis now an exact, case-sensitive match (Issue #8299). It previously matched any net whose name contained the text, case-insensitively. Scripts relying on that should switch to--net-pattern '*GND*'(--netand--net-patternare mutually exclusive). -
kct route-linkcommit mode now needs the pinned kicad-cli (Issue #8314). Without--probeit refuses (exit 2, nothing written) when the pinned KiCad toolchain is unavailable; setKCT_KICAD_DOCKER=1to use the pinned image.--probeis unchanged. -
kct optimize-traces --drc-awarecan now exit 2 (Issue #8322) when kicad-cli reports more clearance errors on the written board than on the input. The board is still written. -
pcb prune --current-pathsdefault changed:--wideis now net-relative when omitted (was an absolute 0.5 mm). Pass--wide 0.5to restore the old behaviour. -
Action needed if you run
pcb prune,optimize-traces --drc-awareorstitch --drcon a board with no.kicad_pro/.kicad_drubeside it (Issue #8369). They now fail instead of silently checking against KiCad default rules. Pass--project PATH.kicad_pro, or--allow-default-rulesto keep the old behavior. -
pour_slotis a newkct checkwarning category and never fails strict board gates (Issue #8435). It is listed inNON_GATING_RULE_PREFIXESalongsideredundant_copper, so board gates that fail on any warning (board 04, board 05) count it as an advisory. Runkct check --skip pour_slotto silence it; board 04's two current hits (USER_LED/NRST,GND/SWDIOon F.Cu, 0.31–0.33 mm gaps) are ordinary track spacing, not a missing plane. -
Pour-slot packing is now opt-in (Issue #8457). Add
--pour-slots-packtokct optimize-traces --pour-slots(orpack=Truetocleanup_pour_slots) to keep the old pack fallback. -
Recorded waivers go stale once (Issue #8517).
EVIDENCE_HASH_VERSIONis
nowev3(mistake hashesev3.m1), so everyev2waiver reports
STALE waiver (outdated evidence version), even on boards whose origin is
(0, 0). Re-review and re-record withkct check --waive. -
Ampacity rules in the exported
.kicad_druchange shape (Issue #8527). Per-net targets now emitA.NetName == '...'rules rather than oneA.NetClassrule at the class maximum, and widths follow the stackup copper weight. Re-runkicad-cli pcb drcagainst the shipped DRU after re-exporting. -
Regenerate any dual-row header footprint previously made with
kct footprint generate pin-header --rows 2: its pad numbering was column-major and is now row-major (stock KiCad numbering). (Issue #8529)
Fixed
-
kct exportfails when thereportextra is missing (Issue #8203). A missing report dependency used to log one warning and exit 0 with noreport.md/images/; it now records an error naming the module that failed to import plus thekicad-tools[report]install hint, and exits non-zero. -
kct report generatenow loads the committed net-class-map sidecar (Issue #8204). Sidecar-gated DRC rules (diffpair_length_skew,diffpair_routing_continuity,diffpair_uncoupled_length,match_group_length_skew) no longer run inactive in the report's DRC section, matchingkct exportandkct check. -
kct optimize-traces --drc-awarereports attempted vs kept nets and why nets rolled back (Issue #8207). Summary now reads "Nets attempted: N (kept: K, rolled back: R)";-vand--format jsonlist per-netnew_violationsby rule id, the failsafe warning names the rules above baseline, and a fully reverted run writes the input board byte-for-byte. -
kct parts availabilitynow matcheskct exportand accounts for every BOM line (Issue #8208). LCSC-less lines are auto-matched like export (opt out with--no-auto-lcsc; matches are labelledlcsc_sourcein JSON and[auto-matched]in the table), and the table/summary now report and list stock-unverified, lookup-unavailable and discontinued parts so the counts sum to the total. -
kct optimize-tracesnow works on KiCad-10 name-only boards (Issue #8209).
On a board with no(net N "name")header table,replace_segmentsremoved
none of the original segments and appended the optimized copper as(net 0)
no-net segments, which created shorts. Under--drc-aware, every net was
rolled back. Segments are now matched by resolved net name and written in the
board's own(net "NAME")dialect. -
kct optimize-tracescollision-checks every rewrite on finished boards (Issue #8214). The CLI now builds a collision checker from the board's own copper and clearances, so unsafe chamfers/zigzag/staircase rewrites are skipped individually instead of--drc-awarerolling back whole nets. Each net's accepted rewrite is synced into the checker's grid before the next net is checked, and KiCad-10 name-only boards are keyed to the grid's net ids. If the checker cannot be built the command fails instead of falling back to unchecked rewrites. -
Via minimisation no longer strands pad/pour connections (Issue #8215).
kct routenow gives the via optimiser pad positions and same-net zone layers, and via-pair elimination is connectivity-checked.kct optimize-tracesnever runs via minimisation. -
kct optimize-tracesnow shortens detours between fixed points (Issue #8217). Theshorten_detour_passthatkct routealready ran now also runs fromoptimize-traces(incl.--net), using the loaded board's pads and vias as anchors and its copper as the obstacle model. Length-matched nets are skipped. -
kct optimize-tracesoff-angle warnings name the net and no longer repeat (Issue #8219).OffAngleSegmentWarningnow reportsnet GNDinstead ofnet 0on name-only boards, and intermediate DRC-trial serializations no longer re-warn for each segment. -
deploy-site.shleaves a clean git tree (Issue #8220). Tracked renders
rewritten bykct renderare restored after the site build (published bytes
unchanged),.wrangler/is gitignored, and a warn-level check reports any
remaining uncommitted paths so Pages commit provenance stays accurate. -
kct creepageno longer hides board-level approaches behind asame_footprintrow (Issue #8232). When a net pair's minimum gap is component-internal, the census now also emits a secondboardrow with the smallest residual board-level creepage (sharing footprint's pads masked out), so--waive-same-footprintwaives only the intra-footprint row. -
PCB.saveno longer adds a numbered net table to name-only boards (Issue #8239). Loading and saving a KiCad-10 board with no(net N "name")header now leaves it header-less;kct pcb pruneinherits the fix. -
kct pcb prune --no-drc --unverifiedno longer leaves a dangling end or cuts an arc-fed pad (Issue #8249). Removal now rejects groups that strand a neighbouring track end resting on a removed body, and copper arcs protect any segment whose body reaches them. -
kct optimize-tracesno longer breaks connectivity on finished boards (Issue #8250). The 45° pass leaves corners that a via, pad or T-junction branch attaches to; keepout rule areas and NPTH holes are now honoured by the collision check; a net whose rewrite would split previously-joined pads is discarded and reported (nets_connectivity_discarded); and--drc-awareno longer rolls nets back onclearance_segment_zone, which is measured against stale stored zone fills. Pad-to-zone connections are not covered by the connectivity gate. -
kct route --timeoutreport no longer names a moved checkpoint (Issue #8258). With a relative-o,<stem>.timeout.jsoncheckpointnow points at the quarantined_timeout_unverified_file, and--export-failed-netsrecords in the report when it was skipped on timeout. The report names the search-failures sidecar only if one was written before the deadline, and gives a reason otherwise. -
kct pcb pruneremoves a redundant branch whose free end rests on a via by overlap only (Issue #8259). An anchorless track end whose capsule overlaps a same-net via/pad is now overlap-held (soft protection) instead of a hard free end; the overlap is still never counted as a join. When the branch goes, the inner-layer end that shared the overlap is moved onto the via/pad centre, or, if that would tilt a 45-degree track, gets a short same-layer stub from the centre (newstubs_addedstat). -
kct check --outputJSON now carriessummary.attach_zone_exemption(Issue #8262). The file report previously omitted the attach-zone exemption state (and_reason/_unexemptedwhen suppressed) that the stdout JSON emits, so gates reading the file (tapeout, readiness) could not see a suppressed exemption. -
kct optimize-tracesno longer strands T-joined branches or mid-chain pads (Issue #8269, part of #8250). After every pass, a chain's rewrite is kept only if it still touches every anchor it touched before: the net's pads and vias, and the endpoints of the net's other chains on that layer. On a finished boardcompress_staircasehad collapsed a chain 0.34 mm off a same-net branch that ended on its body, leaving the branch dangling (track_danglingin kicad-cli). The detour and jog passes use the same anchors. -
kct optimize-traceschecks rewrites against the board's declared clearance (Issue #8269). The collision checker was built from the.kicad_pcbalone, so a KiCad 6+ board (netclasses in.kicad_pro, rules in.kicad_dru) was checked at the 0.20 mm dataclass default. The router's own name-based net classes were also merged in as per-net floors, though the board's files never declared them. On a 0.1016 mm board both made the checker reject even unchanged copper. It now resolves the base from the project, DRU andproject.kctfab floor (resolve_routing_clearances, zero target), keeps only the project's own stricter netclasses as floors (load_pcb_for_routing(router_class_floors=False), default unchanged forkct route), and leaves a board that declares nothing on the old behaviour. -
Timeout/best-so-far checkpoints are editable (Issue #8270). All three
checkpoint writers now fuse collinear same-width/same-layer per-grid-cell
segments (copper unchanged, live routes untouched) before serialising, so a
17k-segment checkpoint no longer needs hand-merging in KiCad.
The_partialinterrupt/timeout output is merged the same way, route ends
that reached a pad through a sub-grid jog now join the exact pad centre
(only when clearance-legal), and the.timeout.jsonpartial-savestage
lists dangling stubs of partially routed nets aspartial_net_stubs(ends
matched within 1e-3 mm; a via only connects when same-net copper meets it on
another layer). -
kct optimize-tracesno longer emits exact-duplicate segments (Issue #8271). Duplicates introduced by a rewrite are dropped per net before output; the count is reported asduplicates_removedin--format jsonstats and in the text summary. -
kct routeHV pairwise gate no longer waives traces that leave a rated footprint's attach zone (Issue #8277). The in-run audit tested the attach-zone exemption on the closest-gap midpoint only, so a segment running past a rated connector pad (e.g. 0.85 mm from a neutral pin against a 1.6 mm requirement) was waived whilekct creepage --waive-attach-zonefailed it. The gate now applies the census rule: both nearest points must lie in the zone and the copper outside it must still clear.kct creepagealso prints why anattach-znrow that still gates is not waived. Each verdict is taken on fused collinear trace runs, so the route-time check judges the same copper as the final gate (a trace split into grid-step fragments is no longer rejected for a fragment that ends just outside the zone). -
kct export/kct auditampacity follows the board's declared stackup copper (Issue #8278). The audit's DRC pass ignored(setup (stackup ...))and evaluated inner layers at the fab profile's 0.5 oz default, so a 1 oz-inner board such as Board 05 showed 1186 spuriousampacityerrors and a NOT_READY report thatkct checkdid not. -
kct pcb prunenow clears router grid-step copper it used to leave behind (Issue #8278).
On Board 05,redundant_copper_*warnings went from 372 to 4 (the remaining
four track detours were re-routed in #8308); native DRC stayed 0/0 and LVS
stayed clean.- A straight run is no longer skipped when the only copper touching its body
is already joined to it through modelled joins (for example the diagonal
corner of a staircase). - A second, validated pass merges runs whose joints also sit on a via, pad or
zone. It collapses the run on the model and keeps the merge only if the
terminal partition is unchanged, every touched item stays joined, every
zone keeps an anchor and no via/pad loses a centred track end. - Runs that a longer track already spans are dropped instead of duplicated.
Runs that form a loop to nowhere are kept. - Loop removal no longer deletes a via's only centred joint on a layer
(which created aredundant_copper_via_offcentrefinding). - Locked tracks are now honoured.
Segmentnever read(locked yes)(or
KiCad 6's(segment locked ...)), so prune's "never touch a locked track"
guard was dead and a locked track could be removed, snapped or merged.
- A straight run is no longer skipped when the only copper touching its body
-
Exempt BOM refs no longer pick up an LCSC from the CSV merge source (Issue #8282). Refs declared
exempt:in the spec are excluded from the existing-BOM /--merge-lcsc-frommerge in both export and preflight, and from sibling propagation in the default--auto-lcscenrichment. Exclusions where the source would have supplied a number are logged and printed bykct export. -
kct optimize-tracesrefills zones after writing (Issue #8286). The rewritten board no longer carries a stale zone fill that madekct checkreport phantomclearance_segment_zoneerrors. Output (text and JSONzones_refilled/zones_refill_error) states whether the refill ran; without kicad-cli a warning is printed and the exit code is unchanged. -
kct creepage --waive-attach-zoneno longer hides out-of-zone approaches to in-zone pads (Issue #8292). The attach-zone residual now also measures each copper item whose nearest point to the other net lies outside the zone (e.g. a via or trace stub skimming the zone edge), matching the router's pairwise audit; an attach trace approaching its own pad inside the zone stays waived. -
_partialcheckpoints no longer contain off-angle pad joins (Issue #8296). The pad-centre join now emits a 45-aligned dogleg for the end jog only, never re-angles a merged run, and skips the join when it would not clear; strict 45-degree mode no longer loses the partial copper. -
kct optimize-traceswrites a reproducible board (Issue #8297). Segments and vias the optimizer emits now get deterministic UUIDs (seeded from the input board and--netfilter, so a filtered re-run on optimized output never duplicates UUIDs), so the post-write zone refill (which re-saves items in UUID order) no longer makes the output differ between runs. -
optimize-traces/pcb pruneleave fewer wiggles (Issue #8298). A net whose rewrite fails the pad-connectivity check now keeps each independent safe edit (reported as "Partly kept");pcb prunemodels KiCad's anchor-in-body joins (track end or via/pad centre inside a track body). -
kct creepage --waive-attach-zoneverdict no longer depends on trace segmentation (Issue #8303). The census cross terms now fuse contiguous collinear same-width trace runs before judging item pairs, sharing the router's collinearity test, so a straight HV trace split into fragments is waived exactly like the unsplit trace. -
Board 05 ships with zero manufacturer-check warnings and an in-stock D3 (Issue #8308).
The four router track detours left after #8278's copper cleanup
(redundant_copper_detouron +5V x2, VM and MOSI) are re-routed in
redesign/routing.jsoninstead of being recorded as known issues: MOSI
crosses RUN under U1's TQFP body and joins the J4 run directly (copper on
the net ~46 mm -> 24 mm), U3.8 gets its own via onto the B.Cu VM feed, and
the redundant +5V loops between In2-plane vias are removed. D3 is now
NCD0805R1/ C84256 (Issue #8267), so the bundle exports under
--strict-preflightagain. Native refill DRC 0/0, LVS clean,kct check --mfr jlcpcb0 errors / 0 warnings. -
kctpcb retune no longer reissues UUIDs already on the board (Issue #8321). The deterministic UUID seed is now derived from the input board hash and the selected nets instead of a constant, so retuning a second selection on an already-retuned board cannot duplicate UUIDs; identical input and selection still give byte-identical output.settings.uuid_seedin the provenance JSON reports the derived seed. -
kct optimize-traces --drc-awareno longer claims "no regressions" on the in-process referee alone (Issue #8322). It now runs kicad-cli on the input and on the written board and reportskicad-cli clearance errors: before -> after(text andkicad_cli_drcin--format json). A kicad-cli increase prints a REGRESSION line and exits 2; when kicad-cli is unavailable and the board has a.kicad_dru, the summary says the referee does not evaluate project.kicad_drurules. -
kct pcb pruneDRC referee no longer masks a new rule violation behind a fixed one (Issue #8323). Violations are now compared by rule and nets, not just type, so a new custom-.kicad_druclearance error cannot hide behind an unrelated fix; when no.kicad_dru/.kicad_prosits next to the board,drc_notenow says custom rules were not evaluated. -
kct optimize-tracesstraightens a sidestep just before a pad (Issue #8325). A new pad-entry pass extends the run into the pad when a short two-piece jog (at most half the trace width off the pad centre) precedes it, and the connectivity gate's free-end check now uses the samemax(tolerance, w/2)pad-touch radius as its component labelling, so the edit is no longer discarded. Board 06 drops from 165 to 152 segments; 05 and 07 are unchanged or better. -
HV
kct route --completeno longer strands a net at a rated
two-terminal part's own pad (Issue #8327). The search-time attach-zone
waiver added by #8277 skippedroundrectpads (nearly every SMD pad) and
fell back to "the whole segment must sit inside one zone", so an edge
entering a rated footprint's zone near that footprint's other pad was
refused although the commit gate accepts it. Roundrect pads are now
measured with their corner radius (or as their rectangle when the ratio is
unknown), and the waiver clips the zone exactly as the trace-vs-pad gate
does (no end-cap overhang). On the softstart rev-D HV-scoped run the AC/HV
nets routed go from 7/11 to 10/11, inside the link budget. -
kct creepage --waive-attach-zoneclassifies the same-footprint residual row (Issue #8332). The #8232boardresidual row emitted after asame_footprintminimum now gets the sameattach_zoneclassification and residual fields as a primaryboardminimum when its witness lies in an exempting #4506 zone, so the census agrees with the router kernel. -
kct pcb pruneno longer deletes every track on a one-pad net (Issue #8333). Loop removal is now skipped for nets with fewer than two terminals, where the "partition unchanged" safety check was vacuous; snap and collinear-merge still run. -
kct pcb strip --from-reportnow accepts realkct creepage --witnessoutput (Issue #8346). Rows are located fromwitness.point_a_mm/point_b_mm(side A first) instead of all being skipped asno location; passing and waived pairs are no longer treated as cut requests. -
kct pcb strip --from-reportno longer refuses its own clearance fix (Issue #8347). The post-edit DRC gate now ignorestrack_dangling/via_danglinggrowth on the nets the strip cut (cutting copper leaves stubs that--danglingremoves) and, in--from-reportmode only,unconnectedgrowth; the oldunconnectedexemption silently matched nothing since #8323 widened the signature key. Dangling growth on untouched nets,unconnectedgrowth in--danglingmode, and growth in any other violation type still refuse the write. -
kct pcb prunemerges collinear runs across sub-micron end gaps (Issue #8356). Straight-through track ends up to 0.75 µm apart (router float noise, 250x the 2 nm join tolerance) are now treated as one joint when planning collinear merges;JOIN_TOLis unchanged. -
Board 05's committed
.kicad_druis what its recipe emits (Issue #8357).
boards/05-bldc-motor-controllernow ships the #8048 attach-zone
router-class exemptions (42kct attach zone - <ref>rules) that
design.pywrites, with zone fills and readiness evidence re-pinned on the
pinned KiCad image. A new test replays the recipe's three.kicad_dru
writes on the committed board and fails if the two ever drift again. -
kct pcb prune --current-pathsno longer leaves a via held only off-centre (Issue #8358). The declared-net / via-closed loop cut now applies the same via-side centring guard as the generic loop pass: when breaking a loop would remove a via's only centred track end on a layer, that cut is refused and the loop is broken elsewhere. Previously this could leave aredundant_copper_via_offcentrejoint. -
-ooutputs now carry the input's.kicad_pro/.kicad_dru(Issue #8366).stitch(previously.kicad_proonly),pcb dedupe|prune|reinforce|stripandoptimize-tracescopy both project sidecars verbatim via a sharedcopy_project_sidecarshelper, so later kicad-cli DRC stages no longer fall back to default rules. An existing, differing destination sidecar is kept, not overwritten. -
optimize-traces --drc-awareno longer reverts every net when the per-net rollback cannot reach the DRC baseline (Issue #8367). It now re-admits changed nets one at a time and rejects only those whose own edits add errors; the all-revert fail-safe fires only if no net survives. -
optimize-traces --drc-awareno longer discards every net when the in-process referee cannot see.kicad_drurules (Issue #8367). When a project.kicad_druexists and the in-process re-admit keeps 0 changed nets, kicad-cli (--refill-zones, project rules) arbitrates: all changed nets are tried, then the set is bisected so only genuinely bad nets are rolled back. Without a rules file or kicad-cli, behaviour is unchanged. -
pcb prune --current-pathsnow works on wide power nets by default (Issue #8368). Without--wide, each loop's narrowest segment is cut whatever its width, provided the branch left behind still meets the declared current's IPC-2221 width; refused loops are reported with the reason. An explicit--wide MMkeeps the absolute behaviour.pcb current-paths-auditnow names a witness segment/via (text andwitnessJSON field) for every loop/parallel ambiguity. -
pcb prune --current-pathsandpcb current-paths-auditagree on loops
(Issue #8368). Prune now removes a track lying wholly inside a collinear,
no-narrower same-net track (covered copper the audit read as a parallel
path) -- but never when that would leave another track's end landing
mid-span on the remaining track, which kicad-cli reports as dangling; it
then keeps the track and reports the loop. It also treats a track end on another track's centreline and a via centred
on a track as joins, sees mid-span same-layer crossings when looking for
loops, and reports any loop the audit still finds with the audit's witness
instead of claiming none remain. The net-relative--wideampacity check
now sizes each branch for its own layer (external forF.Cu/B.Cu) at the
board stackup's copper weight, instead of internal-layer 1 oz everywhere. -
Python-fallback repeat skip is keyed per pad-pair, not per net (Issue #8377). A drained pair on a multi-pad net no longer suppresses the first Python fallback attempt of a never-tried pair on the same net.
-
Board 01 commits the
.kicad_druits recipe emits (Issue #8385). The
routed DRU now carries the #8048 attach-zone block (4 rules) along with the
current fab-floor rules (Max Hole Size, front and back silkscreen text),
and the zones were refilled against it. Copper is unchanged and the evidence
was re-pinned on the pinned KiCad 10.0.6 toolchain. A new replay test guards
boards 01, 02 and 04. Boards 02, 04 and 07 are blocked on #8399. -
optimize-tracescuts chains at interior vias again (Issue #8386), so detour shortening replaces a 45-degree tent that ends at a through-via. Layer-aware chain sorting (#8330) had stopped cutting a route at a via it passes straight through on one layer. Pad centres are not cut. -
kct exportkeeps net-class-map ampacity rules in the shipped.kicad_dru(Issue #8393). Export now loads the same net-class-map sidecar askct check --emit-dru, so the exported file no longer drops the per-classtrack_widthfloors. -
kct pcb pruneandkct optimize-traceshonourKCT_KICAD_DOCKER=1(Issue #8395). Their kicad-cli DRC referee/summary now runs on the pinned KiCad image instead of the host kicad-cli; unchanged when the variable is unset. A missing Docker is an error, not a silent host fallback. -
kct route --completerolls back links that break pairwise HV creepage (Issue #8396). With--voltage-map, any completion link whose copper adds a pairwise shortfall (the gatekct creepageis scored against) is dropped before the board is written, and--complete-reportlists it ascreepage-rolled-backwith the blocking net pair and required vs measured mm. -
Router and
pcb dedupeno longer keep zero-length copper segments (Issue #8397).
PCB.dedupe_copper(reported underremoved.segments), the optimizer's
dedupe_segmentsand the route consolidation pass now drop segments whose
start equals their end (to ~1 µm). Staircase compression is covered under--timeoutpressure by the entry below. -
kct route --timeoutno longer writes grid staircases (Issue #8397).
When the time budget makes the full trace optimizer skip, a cheap
staircase-only compression pass still runs before the board is saved. -
kct route --completeno longer writes grid staircases on the added links (Issue #8397).
The lattice engine skips the geometric post-passes, so completion links kept
one-cell staircases; the staircase-only pass now runs on them, with the new and
preserved copper marked into the grid so its collision checks see real obstacles. -
Boards 02 and 04 no longer carry avoidable
redundant_copper_*router copper (Issue #8399). Their recipes now run a newkicad_tools.pcb_prune.cleanup_copper(dedupe + DRC-verified prune to a fixed point) and the committed routed PCBs and readiness evidence were re-pinned; the three residual genuine detours are recorded as reviewedknown_issueswarning allowances. Board 07's hash-bound reviewed routing is unchanged (see the PR). -
Board 06 (
06-diffpair-test) is regenerated fromassembled-demo/build.pyon the pinned toolchain (Issue #8404). The committed routed board,.kicad_dru(now carrying the #8048 attach-zone block), Gerbers, renders and the hash-bound manufacturing bundle are the recipe's own output (100% routed, native DRC 0, LVS pass), the board is covered bytests/test_board_recipe_dru_reproduces_8385.py, andrefresh_bundles_6404.pygains a board-06 configuration. The board's pour-escape search now ignores the (relax-only) attach-zone block instead of failing closed. The recipe also writes board 06's native LVDS pair gap/skew block (kct router diff-pair gaps) from the board's own pairs, sincebuild.pyroutes only IN/OUT andkct routenever engages them; the committed DRU keeps the fourkct diff pair skewrules from #6443/#7894. -
Lattice trace/via attach-zone waivers now match the HV gate (Issue #8408).
exempt_seg_seg,exempt_seg_ptandexempt_pt_ptwaive a pair only when both nearest points lie in one zone and the copper outside it still clears, so the search stops committing copper the end-of-run pairwise audit rejects. -
Timeout receipt keeps the fallback diagnostics when no snapshot is saved (Issue #8413).
.timeout.jsonnow always carriespython_fallback_top_nets,python_fallback_repeat_skips,python_fallback_proven_skips,python_fallback_seconds_savedandfallback_count(nullwhen unavailable), even withsnapshot_saved: false. -
Post-negotiation sweep now honours its announced bound (Issue #8414). The
PIN_ACCESSsub-grid and via-conflict retries insideroute_netrun on the remaining per-net budget instead of unbudgeted, the whole sweep is installed as awall_deadlineso nested searches clamp to it, and the log prints the measured sweep time next to the bound. Deterministic-budget runs are unchanged. -
Post-negotiation sweep no longer runs its DRC pre-check past the sweep bound (Issue #8414). Once the sweep budget is spent, a rescued net is rolled back instead of paying for an uncapped geometry scan.
-
kct route --completeno longer emits zero-length link tracks (Issue #8417). The link router drops start == end segments and its exact clearance check measures a degenerate segment as a disc of the trace width. -
kct optimize-tracesno longer disconnects fine-pitch pads (Issue #8419). The
connectivity guard now measures pad copper (not just the pad centre), so a track that
ends at a pad edge is recognised as attached and edits that would detach it are dropped.
TheDRC errors:line is labelled as an in-process advisory count, instead ofN new errors, when kicad-cli arbitrated and reports no regression. -
kct pcb prunefinds loops closed by a trace overlapping a same-net via or pad (Issue #8436). A trace body that overlaps a via disc or pad shape with its centre outside the body now counts toward loop detection (cycle-finding only), so the redundancy is reported. It never justifies a removal. -
kct prunejoins off-centre ends with an on-grid stub (Issue #8437). When snapping a track end onto a via/pad centre would tilt it off the 0/45/90° set, prune now adds a one- or two-piece 0/45/90° stub to the centre instead of leaving the end overlap-held, soredundant_copper_via_offcentreno longer rises. -
kct build-native --checkreports placement/DRC backends clearly (Issue #8439). An unbuilt backend now readsnot built (build with: kct build-native)with the reasonextension <name> not builtinstead of the misleading "partially initialized module / circular import" text, and--format jsongainsplacementanddrckeys (router keys unchanged). -
kct routeno longer turns a converged route into a timeout via placement-delta feedback (Issue #8480). Each placement-delta trial now re-reads the stage time left, is skipped (pd_budget_exhausted) when too little remains, and is abandoned after iteration 0 when it routes more than 3 nets fewer than the accepted result, so the stage ends normally instead of exit 124 /partial. -
kct routeno longer fuses a vertical/horizontal run with a 1 µm jog into an off-angle segment (Issue #8488).merge_collinear_same_widthnow fuses a chain only when the fused segment is 45°-legal, soOffAngleSegmentWarningis not raised for the fused copper. -
kct optimize-tracesno longer renames nets on name-only KiCad 10 boards (Issue #8492). A numeric(net N)reference with no header table to resolve it was re-serialized as an invented(net "Net<N>"); such blocks are now left untouched with a warning. -
kct checkandkct pcb reinforcereport coordinates in one frame (Issue #8493).
netclass_clearance_copperlocations, via messages (via_in_pad,
via_type_capability, silkscreen via labels) andpcb reinforcerefusal
coordinates are now sheet-absolute KiCad coordinates, matching kicad-cli DRC,
on boards whose Edge.Cuts does not start at (0, 0). -
kct pcb reinforcehonours.kicad_druconditional clearance rules (Issue #8494). Anchor-via candidates are now checked against the board's custom rules (e.g. aA.NetClass == 'HV'clearance) with kicad-cli semantics; refusals report the newdru_conditionalrule. -
kct route --completeno longer writes zero-length tracks (Issue #8495). The
closer's degenerate-segment guard now compares coordinates after the board file's
0.01 mm rounding, so a sub-resolution sliver can't be serialized as a point
segment that kicad-cli reports astracks_crossing. -
kct pcb prunereaches a fixed point: it no longer re-adds a via/pad stub
that already exists (Issue #8501). Stub pieces are now checked against the
net's existing copper by distance (either direction), so a coordinate on a
half-quantum of the dedup rounding no longer reads as new copper, and a
plan whose stubs are all present is no longer reported as accepted. Board
05's copper cleanup converges again. -
pour_slotno longer reports a slot once per copy of duplicated copper
(Issue #8503). Exact duplicate segments (already flagged by
redundant_copper_duplicate) are collapsed before pairing, so each distinct
track pair is reported once; board 03 drops from 82 to 39 findings. -
kct routeno longer emits a same-net stub twice (Issue #8505). When two routes of one net ran the same pad-to-via stretch, both copies survived trace optimization, duplicating copper and inflatingTotal length. Board 02 NODE_A drops 1.18 mm of duplicate copper (316.39 -> 315.21 mm). -
Evidence hash version bumped to
ev3(Issue #8517). Locations for
netclass_clearance_copper, via and silkscreen findings became
sheet-absolute in #8493, which moved their evidence hashes on origin-offset
boards. Old waivers now reportoutdated_evidence_versioninstead of a
misleadingevidence_changed. -
kct parts availabilityrefetches stale-unverified stock and gains--no-cache(Issue #8518). Cache entries older than the 24 h verification window are refetched live instead of reportedunknown; refetch failures are named per item;summary.low_stock/availablenow match per-item statuses. -
kct build-nativeno longer leaves placement/DRC silently unbuilt (Issue #8519).
A build that finishes with placement/DRC source present but no installed
extension now warns (router-only fallback vs. compile failure), and the
--checkhint says "optional; Python fallback in use" whenkct build-native
cannot build that backend. -
kct route-linkwrites(net "name")refs on name-only boards and merges staircases (Issue #8523). Link copper no longer carries bare numeric(net N)refs thatoptimize-tracesskips (#8492), and collinear runs / grid staircases are collapsed before commit (falling back to the raw route if the DRC gate refuses the collapsed one). -
kct route-linkDRC gate now refills zones (Issue #8525). The per-link gate ran
DRC against the stale plane fill, so every new via on a board with filled inner
planes was rolled back with phantomclearance/hole_clearancefindings. Baseline
and candidate are now checked with--refill-zones(KiCad 10+), and the rollback
reason names the first few offending items, not only their types. -
kct exportno longer turns a per-nettarget_ampacityinto a class-widetrack_widthfloor (Issue #8527). Nets that declare their own target get net-scoped (A.NetName) ampacity rules, ampacity widths use the board's declared stackup copper weight instead of a hard-coded 1 oz, and export warns when it changes the ampacity block of an existing.kicad_dru. -
kct footprint generate pin-header --rows 2numbered pads column by column (Issue #8529). Dual-row headers now alternate columns (odd pins left, even pins right, stepping together) like KiCad's stockPinHeader_2xNand the Pi GPIO header, so pin N lands where a real header's pin N is. -
kct submit-jlcpcb --dry-runno longer refuses bundles whose BOMFootprintand CPLPackagediffer only by aLibrary:prefix (Issue #8538). The preflight ignores the prefix when comparing (so older and stock bundles pass), and a genuine mismatch names the reference plus the BOM and CPL values. The export writers are unchanged. -
kct submit-jlcpcbworks without JLC OpenAPI credentials (Issue #8539). The stock
gate falls back to anonymous LCSC reads (provenance.source=lcsc-anonymous) and, with
no source at all, says "no inventory source: JLC OpenAPI credentials not set" instead of
transport-error.--guidednow runs regardless of the stock gate and prints its state;
--uploadstill requires credentials.--match-mappingis documented as the CSV column schema. -
kct checkresolves circular courtyards and stops warning on hidden fiducial refs (Issue #8540).fp_circlecourtyards (stockFiducial:parts) now resolve into outlines socourtyard_overlapis checked instead of reportingcourtyard_outline_unresolved, andsilk_ref_obscuredno longer warns for hidden references on fiducials (pads withpad_prop_fiducial_glob/_loc, orboard_only+exclude_from_pos_files). -
kct creepagenow treats net-0 copper as floating conductors (Issue #8548). A netless pad or trace between an HV net and another net can shorten the creepage/clearance path (HV → island → other); the census now measures that single hop, names the island in a newvia_floatingwitness key on the affected row, and reportsnetless_items/netless_treatment("floating"; single-hop only, chains of islands are not searched) at report level. Net-0 zone fills are not collected and so are not modelled. Copperless NPTH mounting holes are excluded; the island hop also applies to the same-footprint board row and attach-zone residual. -
kct exportpreflightbom_pcb_matchno longer warns on fiducials (Issue #8549). Footprints
flaggedexclude_from_bomorboard_onlyare exempt from the "on PCB but not in BOM" warning;
genuine mismatches still warn, and BOM refs missing from the PCB still fail. -
kct pcb sync-netlistkeeps nets on KiCad 10 boards (Issue #8550). Pads on name-only boards are written as(net "name")and no top-level net table is added, so KiCad no longer reports<no net>. -
kct pcb sync-netlist --remove-orphansno longer deletesboard_onlyfootprints (Issue #8551). Fiducials, mounting holes and logos marked(attr board_only)are not orphans and are skipped (also in thekct syncreconciler). -
Readiness refresh no longer refuses on advisory
pour_slotwarnings (Issue #8559).match_warning_allowancenow skipsNON_GATING_RULE_PREFIXES, matchingunaccepted_warnings, so board 04/05/07 refresh and dry-run replays stop failing onpour_slotfindings; other unlisted warnings still refuse. -
Silk DRC now sees board-level
gr_text/gr_*silk on origin-offset boards (Issue #8561).silk_over_copperandsilk_overlap(and sokct check) compared sheet-absolute board-level silk against board-relative footprint geometry and missed it on any board whose origin is not (0,0);silkscreen/place_refshad the same mismatch for its static-silk obstacles. -
Stitch/pour-weld copper uses the board's net dialect (Issue #8563). On
KiCad 10 name-only boards,kct stitchand the pour-oracle weld now write
(net "NAME")instead of a legacy(net <n>)that KiCad reads as no net.
Withdrawn weld closures also record each stub against its own via so no
stub is left behind. -
kct routesays why a net was routed wider than its class width (Issue #8564). Nets sized by impedance (declared target, or one synthesized from a validator default such as.*CLK$) now log one warning-level line with the width, target Ω and origin, and the route decision rationale carries the same reason.kct routenow records and saves route decisions to<board>.decisions.json, sokct decisions explain-route <net>returns that reason. Also fixes route decisions never being recorded (an emptyDecisionStoreis falsy) and the decision length metric crashing on real segments. Routed widths are unchanged. -
kct routeplacement-delta feedback no longer keeps moves that overlap neighbouring parts (Issue #8566). A delta is now reverted when it adds pad-to-pad or courtyard overlaps between the moved footprint and other footprints, and a--nets-limited pass skips deltas for parts that carry nets outside the requested set. -
kct export --mfr jlcpcbBOMFootprintand CPLPackagenow agree (Issue #8569).
When one file carried a bare footprint name and the otherlib:namefor the
same ref, both now use the qualified form; genuinely different footprints are
left untouched. -
kct readiness --verifynames the missingmanufacturing.zip(Issue #8571). Theartifactsblocker now saysbundle has no manufacturing.zip next to <dir>/with the remedy instead of a temp-dir path, and/kct:tapeoutdocuments the bundle layout readiness needs. -
kct route-linkrelaxes map-derived floors inside attach zones and re-checks collapsed routes (Issue #8573). With--voltage-map, copper inside a footprint attach zone shared with the link net keeps only the base clearance (the waiverkct creepage --waive-attach-zoneapplies); outside the zone the full floor holds. A collapsed route that violates a per-net floor (--net-clearanceor map-derived) now falls back to the uncollapsed route. -
Creepage census searches chains of floating net-0 islands (Issue #8579). A bridge through several netless copper islands is now found by a shortest-path search per layer instead of a single
HV -> island -> otherhop, so reported creepage is no longer optimistic for multi-island bridges. The IEC 60664-1 X-rule for floating segments is not applied: the standard text could not be verified. -
Tapeout sign-off no longer stales the readiness receipt (Issue #8580).
output/manufacturing/manifest.jsonis now hashed in a canonical form
(top-leveltapeoutkey removed, sorted keys) by bothkct readinessand the
reader; other inputs keep raw-byte hashes. Receipts written earlier keep
validating until the manifest changes. -
PCB.add_footprint(..., layer="B.Cu")now places a real back-side footprint (Issue #8581). Pads,fp_*graphics, texts and embedded zones used to stay onF.*while only the footprint's(layer)node saidB.Cu, so back-side parts got front copper/mask (and the footprint swap inkct pcb sync/PCBWorkflow.add_componentinherited it). Every side-specific layer is now flipped, local geometry is mirrored and texts get(justify mirror), matching pcbnew'sFlip.F.Cuplacement output is unchanged. -
kct repair-creepagehardening (Issue #8585). A pair that vanishes from the post-move census is now rejected as "not verified" instead of kept as cleared with margin 0; unrepaired floating-island (via_floating) rows name the island; text output says "PARTIALLY REPAIRED" when some moves were written but pairs remain; the count-only DRC gate is documented in the help. -
kct stitchhonours keep-out rule areas (Issue #8587). Via sites and
pad-to-via stubs are no longer placed inside(tracks not_allowed)/
(vias not_allowed)rule areas (board-level and footprint-embedded, per
layer); a pad with no legal site is skipped with a reason naming the area,
instead of kicad-cli reportingitems_not_allowed. -
kct stitchno longer rejects via sites inside a foreign net's inner-layer plane (Issue #8591). Only outer-layer (F.Cu/B.Cu) foreign fill blocks a via or stub; a through via crossing an inner plane is legal because KiCad cuts an antipad on refill. Keep-out rule areas still block on every layer. -
kct readiness --verify→kct tapeout-sign-offhandoff works for any bundle layout (Issue #8592). The Ready gate accepts<board>/manufacturing/manifest.jsonas well asoutput/manufacturing/manifest.json;tapeout-sign-off --readinessaccepts the--verifyreceipt atoutput/readiness-verification/readiness.jsonand resolves relative paths first.
Added
-
kct pcb pruneremoves redundant copper (Issue #8216). Builds per-net connectivity the way KiCad does (endpoint-anchored track joins, track ends inside the full pad/via shape — never capsule overlap), and is deliberately conservative: a removal must keep every live neighbour connected through track/via/pad joins (a zone outline is never relied on, since its fill can void), keep every pad/zone terminal connected, and never leave a track end joined only by overlap. Off-centre ends are snapped onto the via/pad centre together with every end that shares the joint. Withkicad-cli, edits that add violations underpcb drc --refill-zones(run with the board's own.kicad_pro) are dropped; without a DRC check (--no-drcor nokicad-cli) the file is not written unless--unverifiedis passed. A redundant branch whose copper merely touches other same-net copper without a shared endpoint (such as the spur beside a via) is removed too, but only when connectivity also holds over those body-touching neighbours. -
kct routeshortens long "tent" detours (Issue #8217). New
shorten_detour_passreplaces a whole chain of 3+ segments with a straight or
single-bend 45° path between its endpoints when it is shorter, collision-clear
and still passes over every same-net pad/via the chain touched. Controlled by
OptimizationConfig.shorten_detours(default on). Wired into thekct route
post-route optimizer only (it needs the router's board model); nets declaring a
length_match_group, committed coupled diff pairs and Kelvin branches are
left alone.kct optimize-tracesis unchanged for now. -
kct checkreports avoidable copper;kct readinessdedupes it first (Issue #8218). Newredundant_coppercategory (warnings only;--skip redundant_copper) flags exact-duplicate segments, runs of very short segments, long detours and track ends off a via centre.kct readiness --generatenow runspcb dedupebefore refill/check and records the removed counts inREADME.txt; thetapeoutskill gains the same Gate 0. -
kct pcb prunemerges collinear grid-step runs (Issue #8236). A straight, end-to-end run of same-net/layer/width segments whose joints are pure two-segment endpoint joins (no via, pad, zone or third segment) collapses into one segment covering identical copper. Runs containing a protected segment, or whose bodies touch same-net copper outside the run, are left alone; the existing per-netpcb drc --refill-zonescheck still applies. -
kct export --merge-lcsc-from <bom.csv>names the LCSC merge source (Issue #8260). The LCSC merge previously read only<output-dir>/bom_<mfr>.csv, so a fresh bundle directory silently got a worse BOM than the previous verified one. The new flag takes an explicit CSV (a missing file is an error;--no-merge-lcscwins), the export summary now prints the merge source used or "no existing BOM to merge", and theexport --helptext and tapeout / manufacturing-readiness skills document the behaviour. -
Declare deliberately non-LCSC BOM refs in the
.kctspec (Issue #8261).bom_entriesacceptexempt(consigned|hand_solder|dnp_by_intent) with a requiredexempt_reason;bom_lcsc_values/bom_lcsc_stockreport them in anexempt (declared)segment instead ofunverified, and tapeout Gate 4 accepts only declared exemptions. -
kct optimize-tracesremoves lateral jogs (Issue #8269). A new pass slides a short sideways step between two parallel runs (the router's grid-pitch "wiggle", e.g. a 45-degree run that steps 0.05 mm sideways and continues) to the next corner, where it merges into a segment parallel to it. Angles stay in the 0/45/90 set, total length never grows, chain endpoints never move, and each rewrite must be collision-clear and keep every same-net pad/via it touched on the copper. Runs after pull-tight;OptimizationConfig.remove_jogs/max_jog_length(default 1.0 mm), CLI opt-out--no-jogs. Like detour shortening it needs a collision checker and net anchors, so it is a no-op without them. -
Explicit per-board non-HV declarations for the HV vacuity guard (Issue #8278).
A board's net-class map may now carry a reservednon_hv_netsblock
({"FUSED": "12-24 V fused motor supply, SELV"}) that exempts mains-named
nets from the name-based isolation vacuity guard (#4354). A reason is
required, a malformed block fails closed, a mains-level working voltage still
trips the guard, and nets resolved HV by class or voltage are never removed.
Every exemption is listed in the isolation JSON (declared_non_hv_nets), the
kct audittable and the report's action items. -
known_issuescan name track-copper warnings by location (Issue #8278).
redundant_copper_*findings have no ref/pad, so they now key as
{rule, at: [x_mm, y_mm]}(CLI:--known-issue N:summary:advisory:redundant_copper_detour@x/y).
Only those rules accept a located warning identity. -
kct creepagehonoursnon_hv_nets(Issue #8278), the same
declarationkct auditreads, so the two no longer disagree on a board such
as Board 05. Exempted nets are printed to stderr. A malformed block is an
error (exit 1). Undeclared mains-named nets and a mains-level
--working-voltagestill exit 2. -
kct optimize-traceshonours HV creepage with--voltage-map(Issue #8300). New--voltage-map,--creepage-standard,--pollution-degree,--material-groupand--hv-thresholdflags (same semantics and defaults askct route). Each candidate edit that would bring a net pair below its pairwise creepage requirement (against foreign traces, vias and pads, with the same rated-footprint attach-zone exemptionkct routeuses) is rejected on its own while other edits on the net still apply; the text and--format jsonsummaries report skipped edits by net pair. Without--voltage-mapbehaviour is unchanged. -
kct creepagelocates each failing pair (Issue #8301). Every row in
--format jsonnow carries awitness(point_a_mm,point_b_mm,item_a,
item_b: padREF.pin,segment:/via:/zone:<uuid>, orEdge.Cuts), and the
new--witnessflag adds the same to the text tables. Points are straight-line
closest points, so for slot-detour rows they mark the clearance gap. -
kct pcb strip --from-report/--dangling(Issue #8309).--from-reportcuts one victim track/via perclearance/shorting_itemsfinding in a kicad-cli DRC JSON (or locatedkct creepagerows), honouring--protect-netsand--radius;--danglingrepeatedly removestrack_dangling/via_danglingcopper, keeping anchor vias at or above--keep-via-minand refusing a pass that raises the unconnected count. Writes are verified withkicad-cli --refill-zonesDRC unless--unverified. -
kct route-linkroutes individual links between chosen endpoints (Issue #8310). Repeatable--link "NET REF.PAD|x,y[@layer] REF.PAD|x,y[@layer]", with--via-at x,y(forced waypoint via) and--link-layers(per-link layer allow-list) applying to the preceding--link.--probereports a path (length, via count) or the nearest blocking item per link and writes nothing; exit 1 if any link is unroutable. It reusesrouter.link_router.route_link, so the router and the HV census share one rule set. Per-link DRC/creepage gating and rollback are tracked in #8314. -
kct pcb transplant SRC DST --nets A,B -o OUT(Issue #8311). Copies the tracks and vias of the named nets from one revision of a placement onto another, matching nets by name; refuses when pad positions differ. Supports--dry-run(rendered as apcb diff),--drc, andREV:pathspecs. -
kct fix-silkscreen --clip-to-padstrims silk lines too close to pads (Issue #8312). Opt-in flag
that shortens or removes footprintfp_linestrokes within the manufacturer's silk-to-pad clearance
(using the same geometry as thesilk_pad_clearancecheck), so stock 0402 outlines stop failing it.
Pin-1 / polarity markers are never edited and are reported as skipped;--dry-runlists each edit. -
kct pcb prune --current-paths FILE [--wide MM]breaks loops on declared power nets (Issue #8313). On the nets named in the current-path specs, each copper loop, including loops closed through vias, is broken by removing its narrowest segment below--wide(default 0.5 mm) and any stub that cut leaves dead-ended, socurrent-paths-auditstops calling the run ambiguous andpcb reinforceaccepts it. Vias a cut leaves with nothing attached are removed with it (a cut that would leave a via on a single layer is refused). Pads and zones are never disconnected; loops whose segments are all at or above--wideare left in place and listed (uncut_loopsin--format json). Note that with--current-pathsthe generic pass keeps wide redundant copper on declared nets, so those nets can see less pruning than without the flag. -
kct checkflags parallel traces too close for the zone fill (Issue #8435). New advisorypour_slotcategory (skippable with--skip pour_slot): different-net track pairs on a poured layer whose gap is under2 × clearance + min_thicknessleave a slot in the plane. Findings are warnings. -
kct optimize-traces --pour-slotsrepairs pour slots (Issue #8440). New opt-in pass that
spreads (or, failing that, packs) the parallel different-net tracks flagged by thepour_slot
advisory (#8435). Each edit is refereed by kicad-cli with zone refill and reverted if any DRC
or unconnected count rises; without kicad-cli the pass refuses and edits nothing. -
Pour-slot cleanup re-pitches parallel buses (Issue #8460). 3+ parallel same-layer runs are spread jointly as one refereed edit; a boxed-in bus reports
channel too narrow: needs X mm, has Y mm. -
kct submit-jlcpcbprepares a JLCPCB PCBA submission (Issue #8466, part of #8465). Offline
preflight of the tapeout bundle (manifest hashes, human sign-off, board sha), a frozen plan, a live
stock gate (short or unknown lines block; inventory-covered lines are explicit), an optional API
upload leg and a review page, plus the/kct:submit-jlcpcbskill.--dry-runnever uploads; the
command never checks out, pays or marks anything ordered. -
kct submit-jlcpcb --websiteholds a one-driver-per-browser lock (Issue #8465). A second
run against the same--cdp-portrefuses withABORTED at lockuntil the first exits (or its
lock is two hours old or its process is dead), so two agents can never interleave on one
signed-in session.--lock-diroverrides~/.kct/locks.--dry-run --websiteis now refused
before the preflight, since a dry run never touches the website; a blocked stock gate says the
website leg was skipped. -
kct submit-jlcpcb --websitedrives your own Chrome to a saved JLCPCB cart (Issue #8468, part
of #8465). Attended only (TTY plus your signed-in CDP profile), one action at a time, never
requests a robots.txt-disallowed path, and stops at the cart. Fields it cannot map exactly abort
with a screenshot; a part-matching export that omits, adds, substitutes or leaves a line
unselected blocks the cart.--guidedprints the manual checklist. The review page gains the
cart URL, quote, lead time, file hashes, match diff and remaining human steps. Selectors are
unverified against the live site. -
pip install 'kicad-tools[submit]'installs the JLCPCB site driver's Playwright dependency (Issue #8481). New opt-insubmitextra (not part ofall); no browser download is needed because the driver attaches to your system Chrome over CDP. The "playwright is not installed" abort now names the extra. -
kct footprint generate rpi-hat(Issue #8529). Generates a Raspberry Pi HAT part: the 2x20 header (pin 1 at the origin) plus four unnumbered 2.75 mm NPTH mounting holes (58 x 49 mm), copper keep-outs on*.Cusized to the spec's 6.2 mm minimum land (--keepout-diameter) and the 65 x 56.5 mm outline on F.Fab, so the holes cannot drift from the header. Theconnector_edge_distanceinventory now also coversJ-reference footprints outsideConnector_*libraries (such composite parts were silently dropped), andcreate_hat_regions()defaults to the 65 x 56.5 mm HAT size (56.0 is also allowed by the spec). -
kct pcb add-fiducialsplaces global fiducials (Issue #8531, part of #8530). Puts
asymmetric, non-collinearFiducialfootprints at copper-free sites near the
board corners on each requested side, flaggedboard_only,
exclude_from_bomandexclude_from_pos_files. Supports--sides,
--count,--keepout,--edge-marginand--dry-run; fails without
writing when no free site exists. -
kct pcb add-board-infostamps project/rev/date on silkscreen (Issue #8533). Fields come from the PCB title block ({project}falls back to the.kicad_prostem) and an unresolvable field is an error;--autopicks a free region clear of pads, silk, courtyards and the board edge,--layer B.SilkSmirrors the text, and--order-placeholderadds a fab order-number marker. -
kct tapeout-sign-offrecords the human sign-offsubmit-jlcpcbrequires (Issue #8537). It verifies the bundle against its manifest and refuses unless a passingkct readinessreceipt (--readiness) is bound to--boardand covers every bundle file, then writestapeout.{board_sha256, readiness_sha256, human_signoff}; preflight requires the receipt hash. Preflight now reports a missing record key, a sha256 mismatch and a size mismatch separately, and selectsgerbers/gerbers.zipoverkicad_project.zipin a stockkct exportbundle. -
kct repair-creepagetranslates wide HV copper to clear a creepage shortfall (Issue #8545). For each failing, unwaivedkct creepagepair it moves the track segment (then via) along the census witness normal by the shortfall plus--margin, keeping width and joints. A move is kept only if the pair passes, no other pair gets worse and the kicad-cli--refill-zonesDRC does not regress; otherwise it is rolled back and reported.--dry-runlists moves with witness coordinates; unrepairable pairs exit non-zero. -
kct route-linkis HV-aware (Issue #8546). New--voltage-map,
--creepage-standard,--pollution-degreeand--material-groupderive each
link's per-neighbour clearance floor from the pairwise creepage requirement, and
the per-link creepage gate uses the same requirements (attach-zone pairs whose
outside copper clears are waived).--net-clearancenow binds to the preceding
--link(before any--linkit stays run-global; with a voltage map the larger
floor wins), and an unroutable link squeezed between two foreign conductors
reports the corridor-width bound instead of a generic reason. Without the new
flags behaviour is unchanged. -
Scoped cleanup on signed-off boards (Issue #8547).
kct place-silk-refs --refs R1,R2
moves only the named references (others stay put as obstacles);kct pcb prune --nets NET[,NET] [--region x1,y1,x2,y2]prunes only those nets, applying a net's plan only when
every edit lies inside the box (otherwise it is reported asregion_skipped). JSON output
records the scope used. -
kct readinessaccepts--voltage-map,--waive-same-footprintand--waive-attach-zone(Issue #8570). Thehv_isolationgate can now run the same per-pair voltage-derived census askct creepage, so non-isolated mains boards no longer false-fail on same-potential pairs and divider pads. The map's sha256, the waiver flags, the waived-pair count andgate_passedare recorded inhv-isolation.json; the map is hash-bound in the report inputs. The flat--hv-*path is unchanged.
Changed
-
Relief rescue explains "no relief path" and stops repeating futile rescues (Issue #8248). The log states the corridor the victim needs, access-loss witnesses mark each closer as rip-able or fixed, and a victim whose relief found no path under an identical witness in the previous iteration is skipped (logged once).
-
Relief-rescue log lines now explain themselves (Issue #8256). The "no relief path" line replaces
freed width unknownwith a lower bound on the corridor the ripped blockers vacated (narrowest ripped segment plus twice the smallest gap any neighbour could legally hold: the blocker's resolved minimum clearance raised only to its own authored floor, an unripped diff-pair partner's intra-pair gap, its class clearance to fixed fills, and measured gaps to foreign pads, the board edge and unripped copper; "not measured" when one cannot be resolved) and an upper bound on the shortfall in mm. When no blocker was ripped yet, it says so instead of printing a shortfall. It also states whether copper placed since the rip re-occupied that corridor, naming the net.Targeted rip-up resolved X/Ynow carries a per-net reason count when X < Y: rolled back, rip skipped, refused by the rip-up guard, no blockers found, or fewer than 2 pads. Diagnostics only; routing is unchanged. -
kct optimize-tracesno longer reads routes on two layers as junctions (Issue #8298). Chain building keys vertices by copper layer, so two routes that share their vertices on both layers of a through-hole pad stay whole chains, and branch anchors for the per-pass guard come from same-layer chains only. A twin route on the other layer no longer pins a lateral jog in place. -
kct optimize-tracesexposes every pass and matches--netexactly (Issue #8299). New--no-staircase,--no-pull-tightand--no-detourflags join the existing four, so "all passes disabled" really leaves the geometry untouched; all seven passes are listed in "Optimizations enabled" and the JSONoptimizationsobject.--netis now an exact, case-sensitive net-name match (GNDno longer editsPGND); the new--net-pattern GLOBgives glob matching. The summary (text and JSONstats.nets_touched) always lists the nets whose geometry changed. -
kct route-linkgates each committed link (Issue #8314). Without--probe, links are committed one at a time; kicad-cli DRC (pinned toolchain) and the pairwise creepage census (--min,--net-class-map,--net-class) run after each, and a link that adds a violation is rolled back alone, byte-exactly. Reports gain per-linkstatus/failed_check; exit 1 if any link is rolled back or unroutable, exit 2 (nothing written) when the pinned kicad-cli is unavailable. -
optimize-traces --drc-awarereferees at the board's own clearance (Issue #8367). The in-process DRC used the--mfrpreset clearance, counting hundreds of clearance errors kicad-cli (project rules) did not, so every net was rolled back. It now uses the clearance resolved from the board's.kicad_pro/.kicad_dru. -
DRC-verified commands accept
--projectand refuse default-rules verification (Issue #8369).pcb prune,optimize-traces --drc-awareandstitch --drctake--project PATH.kicad_pro(its sibling.kicad_druis used) and exit non-zero when no project rules are found, unless--allow-default-rulesis passed.pcb reinforcedoes not verify via kicad-cli and is unchanged. -
kct pcb prunesplits a container to drop a covered track a third track lands on (Issue #8406). When a track ends at an interior end of a covered segment, the longer same-width track is cut there into collinear pieces so the landing becomes a shared endpoint (notrack_dangling), then the covered track is removed. No copper changes; locked or arc-adjacent containers are never split.--jsonstats gainsegments_splitwhen this fires. -
kct optimize-traceswarns when the creepage gate is inactive (Issue #8433). Without--voltage-mapit now prints a warning to stderr (suppressed by--quiet), and--format jsonoutput gains"creepage_gate": "inactive"|"active"plus a"warnings"entry when inactive. -
optimize-traces --pour-slotsno longer packs by default (Issue #8457). Packing removes a pour slot by removing the ground strip between the tracks, so a pass that only packed looked like success. It is now opt-in via--pour-slots-pack; the summary notes packed pairs keep theirpour_slotadvisory, andleft_aloneis reported per reason (left_alone_by_reasonin JSON), counting each pair once instead of each attempt. -
Pour-slot cleanup spreads via-ended runs (Issue #8459). A run ending on a same-net via keeps that end on the via and reaches the shifted line through a 45° jog leg; vias never move, every edit is still kicad-cli refereed, and non-axis-aligned or blocked jogs are left alone with a reason.
Performance
-
Relief "no relief path" diagnostics no longer scan the whole board per blocker segment (Issue #8295). The measured-gap scan indexes the ripped blocker's segments on a spatial grid (results unchanged), and a negative gap now reads
ripped N2 overlaps Net_7 copperinstead ofoverlaps measured gap to Net_7 copper. -
Negotiated routing stops re-running the pure-Python A on nets it already drained* (Issue #8370). After a C++
NO_PATH/PAIRWISE_BLOCKEDgive-up, the first hand-off of a net still falls back; once the Python A* has drained for that net, later hand-offs are skipped even though rip-up changed the grid (opt out:KICAD_ROUTER_SKIP_REPEAT_FALLBACK=0).fallback_statsgainspython_fallback_seconds_by_netandpython_fallback_repeat_skips, and the timeout receipt listspython_fallback_top_nets. -
Repeat pure-Python A fallbacks no longer re-run at the full per-net budget* (Issue #8485). A fallback that fails without draining its open set (for example, one ended by the per-net deadline) is now recorded for its pad pair. A repeat of that request runs on 10% of the first attempt's time, with a 5 s floor (under
--deterministic-budget, 10% of the iteration cap instead). A timed negotiated stage also caps its total fallback time at 15% of--timeout; once the cap is spent, repeats are skipped. First attempts of new requests always keep their full budget. The timeout receipt now reportspython_fallback_reduced_repeats,python_fallback_stage_budget_s,python_fallback_stage_spent_sandpython_fallback_stage_budget_skips. To restore the old behaviour, setKICAD_ROUTER_SKIP_REPEAT_FALLBACK=0. -
Negotiated routing stops re-paying for nets already known to fail (Issue
#8486). The overflow-silent rescue (targeted rip-up plus relief) is no longer
re-run for a net whose last rescue resolved nothing while its seal is
unchanged. A net that spent its whole per-net search cap with no path in two
consecutive iterations under the same seal has its next cap halved (each
further such iteration halves it again, floor 5 s; reset when the net routes,
fails fast, or its seal changes). Nets with no sealed pad are now keyed on the
exact foreign copper around them, so the #8248 repeat-relief skip covers them
too. Failed nets are still reported as before, and the negotiated summary now
prints aKnown-failing netsline with the seconds spent on them per
iteration. The deterministic budget arm (no wall-clock cap) is unaffected by
the back-off.