Respect downward-only net labels during trace recovery

[seveibar]

Summary

• prevent three-pin long-distance recovery when a connection is constrained to downward-only net labels
• keep the USB-C flashlight ground endpoints represented by two local labels
• preserve the physical recovery introduced by Route isolated peripherals into component rails #809 when horizontal label placement is also available

Stack

Stacked on #810, which contains the exact tscircuit/core reproduction and records the existing runaway route.

Root cause

The three-pin recovery path ignored availableNetLabelOrientations. In the core fixture, the affected connection is constrained to y-, meaning its schematic representation should remain a downward rail label. Recovery instead created a long physical trace from the LED, past the switch, and across to the USB-C rail.

The fix uses the existing orientation constraint. It does not inspect identifier text and does not add duplicate ground metadata. A connection with exactly one allowed orientation of y- remains label-based; a connection with alternatives such as y- and x+ remains eligible for physical recovery.

Impact

• USB-C flashlight fixture: zero long downward-constrained traces and two local labels
• original Route isolated peripherals into component rails #809 Type-C recovery fixture: physical trace remains and one label remains

Verification

• targeted reproduction and Route isolated peripherals into component rails #809 regression tests — 2 passed
• bun test — 182 passed, 4 skipped
• bunx tsc --noEmit
• bun run format:check
• bun run build
• headless pipeline render inspected
• git diff --check

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
schematic-trace-solver	Ready	Preview	Aug 15, 2026 7:01pm