Emit bus constraints in Simple Route JSON

[seveibar]

Summary

• add the <bus /> primitive to the core catalogue and intrinsic JSX types
• resolve bus trace names or port selectors to routing-scope SRJ connection names
• emit bus membership through SimpleRouteJson.buses
• add a visual regression test for the authoring-to-SRJ conversion

Why

The autorouter boundary currently carries individual connections and differential-pair constraints, but it cannot preserve higher-level bus membership. Without that metadata, routers cannot intentionally order or attract related BGA breakout traces.

Bus membership is routing intent, so this keeps it in Simple Route JSON rather than adding a persistent Circuit JSON element.

Developer impact

Custom autorouters receive:

{
  buses: [
    {
      name: "DATA",
      connectionNames: ["source_trace_0", "source_trace_1"]
    }
  ]
}

Dependency

• depends on Add bus routing constraint props props#758

Validation

• bunx tsc --noEmit
• bun run build
• bun test tests/components/primitive-components/bus/trace-name.test.tsx
• git diff --check

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tscircuit-core-benchmarks	Ready	Preview, Comment	Jul 27, 2026 4:38am