Fix tscircuit main build

[techmannih]

Summary

• upgrade tscircuit from 0.0.2139 to 0.0.2230
• make local TypeScript imports explicit and enable TypeScript-extension imports
• disable unnecessary PCB routing for simulation-only circuits
• cap cloud build concurrency at 2 to avoid Bun memory exhaustion

Root cause

The main-branch release had two failure modes. Rollup intermittently failed to resolve the extensionless PowerModule_TPSM82823.circuit import during transpilation. A later release then spent several minutes autorouting simulation-only circuits and running the TPS63802 SPICE simulation before the build RPC disconnected. Reproducing with four workers locally pushed Bun to roughly 2.4 GB and caused a segmentation fault.

Impact

Release builds now use the current tscircuit CLI/core/autorouter/ngspice stack, resolve source imports deterministically, skip pointless PCB routing for simulation schematics, and run with lower peak memory. Simulation schematics and SPICE outputs remain enabled.

Validation

• npm run typecheck
• npm run format:check
• bunx tscircuit build index.ts --transpile --routing-disabled --ignore-errors --concurrency 1 (ESM, CommonJS, and declarations generated successfully)
• isolated TPS63802 simulation build completed successfully in 231,994 ms

The post-fix full cloud-style build progressed through the component set and into simulations locally, but its terminal result was interrupted by the development session. The PR's external tscircuit/build check is the final end-to-end validation.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.