Support implicit single-pin component selectors for traces (localized fallback)

[seveibar]

Motivation

• Users should be able to refer to single-pin components by name (e.g. TP1) when connecting traces without changing global selector semantics.
• Prior attempt modified selectOne/caching broadly and was fragile; a minimal, localized approach is safer.

Description

• Add a localized fallback in Trace__findConnectedPorts that, when a trace endpoint selector fails to resolve as a port and does not explicitly contain a port token, resolves the selector as a component and returns its sole Port if the component has exactly one port.
• The fallback is implemented as resolveImplicitSinglePort(selector) and is only used when selectOne(selector, { type: 'port' }) returns null.
• Add tests to cover the intended behavior: single-pin-component-implies-pin1.test.tsx (accept single-pin implicit selector) and multi-pin-component-no-implied-pin1-trace-error.test.tsx (ensure multi-pin components do not imply pin1).
• Add updated PCB/schematic snapshot artifacts for the single-pin test.

Testing

• Ran BUN_UPDATE_SNAPSHOTS=1 bun test tests/components/base-components/single-pin-component-implies-pin1.test.tsx and the test passed with snapshots created.
• Ran bun test tests/components/base-components/multi-pin-component-no-implied-pin1-trace-error.test.tsx tests/components/base-components/trace-port-selector-errors.test.tsx tests/components/base-components/shorthand-selector.test.tsx and all tests passed.
• Ran bunx tsc --noEmit for type-checking and bun run format; both completed successfully.

---

Codex Task

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tscircuit-core-benchmarks	Ready	Preview, Comment	Mar 4, 2026 11:42pm

[tscircuitbot]

---

Thank you for your contribution! 🎉

PR Rating: ⭐⭐
Impact: Minor

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

---