Summary
#337 (native Rust/IPC Freerouting DSN/SES bridge) and #341 (KiCad-10-native Specctra export bridge) are both closed as COMPLETED, with the closing comments citing merged PRs (#342, #367) and passing acceptance tests including "a KiCad 10.0.5-native DSN routed with the installed Freerouting." But no Specctra/DSN/Freerouting-bridge tool of any kind was present in the installed Konnect 0.11.0's tool surface during a recent PCB design project. Every autorouting cycle went through raw pcbnew.ExportSpecctraDSN/ImportSpecctraSES plus a completely separate freerouting-mcp MCP server, with no Konnect involvement in the routing step at all.
Environment
- Konnect 0.11.0
- KiCad 10.0, macOS
Repro
list_toolboxes() → 19 toolsets, 217 tools total, none named anything
resembling "route"/"specctra"/"dsn"/"freerouting" beyond `pcb_routing`
(traces/vias/netclasses/differential pairs only — no autorouting bridge)
Routing instead required, repeatedly:
pcbnew.ExportSpecctraDSN(board, "board.dsn") # raw pcbnew, closed board
followed by manual session/job management against the separate freerouting-mcp server (create_session → enqueue_job → upload_job_input_from_local_file → update_job_settings → start_job → poll get_job_details → download_job_output_to_local_file), then:
pcbnew.ImportSpecctraSES(board, "board.ses") # raw pcbnew again
Expected
Given #337/#341's closing comments describe a completed, tested bridge, the installed 0.11.0 release should expose it as a Konnect tool.
Actual
No such tool appeared anywhere in the loaded toolset surface, across many separate list_toolboxes calls over the course of the project.
Suggested fix
Confirm whether the #342/#367 work shipped in a tagged release at or before 0.11.0 — if not, this is a "not yet released" gap worth a changelog/roadmap note so users know which version to expect it in. If it did ship in 0.11.0, this is a packaging or toolset-registration gap (tool not wired into the registry's tool count, or gated behind a toolset name that isn't discoverable via list_toolboxes) worth a closer look.
Impact
The entire autorouting workflow for this project — the single most repeated operation across it — never touched Konnect at all, despite apparently-completed work aimed at exactly this.
Related
#337, #341, #253 (all closed as COMPLETED)
Affected versions
Confirmed on Konnect 0.11.0 / KiCad 10.0.
Summary
#337 (native Rust/IPC Freerouting DSN/SES bridge) and #341 (KiCad-10-native Specctra export bridge) are both closed as COMPLETED, with the closing comments citing merged PRs (#342, #367) and passing acceptance tests including "a KiCad 10.0.5-native DSN routed with the installed Freerouting." But no Specctra/DSN/Freerouting-bridge tool of any kind was present in the installed Konnect 0.11.0's tool surface during a recent PCB design project. Every autorouting cycle went through raw
pcbnew.ExportSpecctraDSN/ImportSpecctraSESplus a completely separatefreerouting-mcpMCP server, with no Konnect involvement in the routing step at all.Environment
Repro
Routing instead required, repeatedly:
followed by manual session/job management against the separate
freerouting-mcpserver (create_session→enqueue_job→upload_job_input_from_local_file→update_job_settings→start_job→ pollget_job_details→download_job_output_to_local_file), then:Expected
Given #337/#341's closing comments describe a completed, tested bridge, the installed 0.11.0 release should expose it as a Konnect tool.
Actual
No such tool appeared anywhere in the loaded toolset surface, across many separate
list_toolboxescalls over the course of the project.Suggested fix
Confirm whether the #342/#367 work shipped in a tagged release at or before 0.11.0 — if not, this is a "not yet released" gap worth a changelog/roadmap note so users know which version to expect it in. If it did ship in 0.11.0, this is a packaging or toolset-registration gap (tool not wired into the registry's tool count, or gated behind a toolset name that isn't discoverable via
list_toolboxes) worth a closer look.Impact
The entire autorouting workflow for this project — the single most repeated operation across it — never touched Konnect at all, despite apparently-completed work aimed at exactly this.
Related
#337, #341, #253 (all closed as COMPLETED)
Affected versions
Confirmed on Konnect 0.11.0 / KiCad 10.0.