fix: resolve stable static solver names

[seveibar]

Summary\n- add optional BaseSolver.solverName constructor metadata\n- resolve explicit static names before legacy instance methods or constructor.name\n- use the shared resolver throughout the generic debugger UI\n- support package-local solvers that do not implement getSolverName()\n\n## Why\nRunframe minifies its standalone bundles, so JavaScript constructor names can become labels such as aby. Solver packages can now publish a stable readable name without relying on a preserved class identifier or wrappers in core.\n\n## Companion source PRs\n- calculate-packing#123: https://github.com/tscircuit/calculate-packing/pull/123\n- matchpack#222: https://github.com/tscircuit/matchpack/pull/222\n- tscircuit-autorouter#2158: https://github.com/tscircuit/tscircuit-autorouter/pull/2158\n- copper-pour-solver#81: https://github.com/tscircuit/copper-pour-solver/pull/81\n- create-fdm-enclosure#7: https://github.com/tscircuit/create-fdm-enclosure/pull/7\n- fanout-solver#75: https://github.com/tscircuit/fanout-solver/pull/75\n- schematic-trace-solver#824: https://github.com/tscircuit/schematic-trace-solver/pull/824\n\n## Verification\n- bun test (26 passing)\n- bunx tsc --noEmit\n- bun run build\n- bun run format:check\n- built integration check against all 16 solver exports used by core

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
solver-utils	Ready	Preview	Aug 18, 2026 10:29pm

[seveibar]

Closing this in favor of the existing instance getSolverName() contract. GenericSolverDebugger already calls solver.getSolverName() everywhere it displays a class-level solver name, so no solver-utils API change is required.