* Identify ICT contacts by the TestPoint ICT variant
ict= now pairs with a dedicated ICT TestPoint variant whose footprint
carries a 3 mm courtyard — KiCad's native courtyard DRC enforces the
interposer pogo pitch on the board itself, with no generated rules.
IPC extraction requires the TestPoint_ICT footprint alongside the Ict
characteristic.
* Let ict= imply the ICT footprint
Existing boards set ict= on ordinary pad variants; erroring would break
their builds. The role now upgrades the footprint to TestPoint_ICT on
any variant, so those boards pick up the courtyard on their next layout
sync, and only an ICT variant without a role is an error. Also formats
the zen per pcb fmt.
* Tighten the changelog entry
* Reject ict= on Keystone test points
The upgrade path would swap in the ICT footprint while the Keystone
branch keeps its commercial MPN and BOM/CPL presence; the combination
is incoherent, so it errors.
* Prune low-value comments
The ict= rationale lives once, in the config help.
TestPoint takes an optional ict config (swd, swdio, swclk, nrst, swo,
gnd, vusb, vtarget, usb_dp, usb_dm, ls) and copies it onto the
footprint as an ict property, so test-fixture tooling can identify
fixture pads without scraping names.
Akhil Velagapudi