Fix async matching for repeated footprint pads

[seveibar]

Summary

• invalidate selector caches immediately when the component tree changes
• let async footprint pads see ports inferred during the same render cycle
• rebuild source_component_internal_connection records when async port initialization dirties source attachment
• add an async kicad:-style regression for a four-pad switch with pad numbers 1, 1, 2, 2

Why

When a library footprint loaded asynchronously, the component's cached selectAll("port") result could still contain only the two primary switch ports. The footprint correctly inferred two additional physical ports for the separated duplicate-numbered pads, but pad matching read the stale cache and attached both pad 1 instances to the primary pin 1 (and likewise for pin 2). PcbPortRender then treated each primary port as ambiguous and emitted no PCB ports.

Invalidating selector caches at the tree mutation boundary makes the newly added ports visible before PortMatching. Updating source-parent attachment also records the inferred physical ports as internally connected after the async load.

The regression verifies that all four pads receive unique PCB ports and that the two repeated-number pairs produce two internal connections.

Related draft safeguards:

• Detect traced source ports without matching PCB ports checks#230 detects traced source ports that have no matching PCB port
• test: preserve separated pads with duplicate KiCad numbers kicad-to-circuit-json#175 protects the converter's valid duplicate-pad behavior

Test plan

• bun test tests/footprint/footprint-library-repeated-pad-numbers.test.tsx
• bunx tsc --noEmit
• bun run build
• full bun test suite started locally; the new regression and surrounding footprint tests pass

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tscircuit-core-benchmarks	Ready	Preview	Aug 20, 2026 11:26pm

[tscircuitbot]

---

Thank you for your contribution! 🎉

PR Rating: ⭐⭐
Impact: Minor

Track your contributions and see the leaderboard at: tscircuit Contribution Tracker

---