Fix schematic trace net hover highlighting

[tonghuaxingdsb]

Summary

• highlight every schematic trace segment connected to the hovered trace's net
• use source net ids first, with connected source ports as a fallback for older circuit JSON
• support solver-generated schematic trace ids by resolving solver endpoints back to source ports and connectivity keys
• keep hover listeners in sync when the generated SVG changes
• add a dedicated manual verification fixture for same-net trace hover
• add focused coverage for direct net, port fallback, and solver endpoint grouping

Tests

• bun test tests/use-highlight-connected-traces-on-hover.test.ts
• bun x biome check lib/hooks/useHighlightConnectedTracesOnHover.ts tests/use-highlight-connected-traces-on-hover.test.ts
• bun x biome check examples/example21-connected-trace-hover.fixture.tsx
• bun x tsc --noEmit
• bun run build
• git diff --check

/claim tscircuit/tscircuit#1130
Fixes tscircuit/tscircuit#1130

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
schematic-viewer	Ready	Preview, Comment	Jun 5, 2026 1:17pm

[tonghuaxingdsb]

/claim tscircuit/tscircuit#1130

[tonghuaxingdsb]

Added a dedicated manual verification fixture: examples/example21-connected-trace-hover.fixture.tsx.

It creates several independent schematic traces connected to net.GND, so the Vercel preview can be used to hover one GND trace and verify the rest of the same-net trace segments highlight together.

Additional local verification after this update:

• bun x biome check examples/example21-connected-trace-hover.fixture.tsx
• bun x tsc --noEmit
• bun run build

[tonghuaxingdsb]

Added a fallback for schematic traces whose source_trace_id is generated by the schematic solver, e.g. solver_R1.1-U1.4.

In those cases the generated schematic trace id does not directly match a source_trace.source_trace_id, so the hook now resolves the solver endpoints back to source ports and groups traces through subcircuit_connectivity_map_key. This makes the same-net hover behavior work for generated schematic routes as well as direct source trace ids.

Additional local verification:

• bun x biome check lib/hooks/useHighlightConnectedTracesOnHover.ts
• bun x tsc --noEmit
• bun run build

[tonghuaxingdsb]

Added focused unit coverage for the trace grouping logic:

• direct grouping through connected_source_net_ids
• fallback grouping through connected_source_port_ids
• solver-generated schematic trace ids such as solver_R1.1-U1.4, resolved through source port connectivity keys

Additional verification:

• bun test tests/use-highlight-connected-traces-on-hover.test.ts
• bun x biome check lib/hooks/useHighlightConnectedTracesOnHover.ts tests/use-highlight-connected-traces-on-hover.test.ts
• bun x tsc --noEmit
• bun run build
• git diff --check

[tonghuaxingdsb]

Added a short demo recording for the connected-trace hover behavior:

• Video: https://github.com/tonghuaxingdsb/schematic-viewer/releases/download/pr219-trace-hover-demo/page%40dbe32ca2162175011d24ef69193268fe.webm
• Fixture preview: https://schematic-viewer-git-fork-tonghuaxingdsb-codex-664e6c-tscircuit.vercel.app/?fixtureId=%7B%22path%22%3A%22examples%2Fexample21-connected-trace-hover.fixture.tsx%22%7D

The recording uses a real mouse move over the rendered SVG path. In the captured run, hovering schematic_trace_1 marks the connected same-net trace group (schematic_trace_1 and schematic_trace_2) with data-schematic-trace-net-hover=true, making the connected traces switch color together.