Fusion - the Fusion 360 Bridge

@@ -1,105 +1,90 @@ --- name: fusion-routing-description: Use when asked to route a net, draw traces, add vias, pour copper or reproduce the Astra routing demos live in Fusion with fusion_routing_state, fusion_route_net, fusion_routing_drc and fusion_plan_route. Two-layer geometric preflight, native Autodesk DRC before and after, manufacturer rules loaded from adom/pcb-design-rules first. Trigger words - route this net, draw a trace, add a via, copper pour, refill, ratsnest, airwires, DRC, design rules, JLCPCB rules, reproduce the routing demo.+description: >-+  Route and review PCB copper in Autodesk Fusion through Fusion Bridge. Use for trace paths,+  vias, manufacturer design rules, power and ground connections, copper pours, thermal+  spreading and copper-ablation layouts. Inspect the actual board and verify native copper,+  connectivity and DRC. Applies to ordinary board work, independently of recording or demos. --- -Parent skill: [fusion-bridge](../../SKILL.md).--Read `fusion_routing_state {expectDocument}` and keep its `boardId` and `revision`.-Use an isolated test board until this development feature is promoted. Existing-user designs and pinned runtimes must be preserved.--Call `fusion_route_net` with the exact `expectDocument`, `boardId`,-`expectedRevision`, `net`, and `points` or `paths`. Coordinates/widths are mm;-copper layers are 1 and 16. Use `{pad:"J1.1"}` for pad coordinates or-`{x:14,y:17,layer:16}` to change outgoing layer with a through via.--`dryRun:true` checks all geometry without adding copper. Geometric preflight is-conservative and incomplete; it refuses unsupported boards. Every actual call-verifies the copper delta by a new Fusion export. Inspect semantic `success`,-`verified`, and `mutationAttempted`. A timeout or mismatch is not authorization-to replay. Commands are not an atomic Undo group.--For live playback, submit one segment/via per call with the consecutive returned-revision. Capture the actual window with `desktop_record_window_start` and-finalize with `desktop_record_window_stop`, including in error paths. Never-replace live copper with a simulated animation. Foreground is opt-in.--Finish with `fusion_routing_drc` using the same identity/revision guards. It-recomputes RATSNEST, runs native Autodesk DRC, and reads all errors including-approved ones. Require `drc.checked`, `drc.clean`, and no remaining nets before-claiming a connected, DRC-clean result. Save/export the final board separately.--See `demo/routing/README.md` for the tested scope, fixture, recorder and evidence.--For the 24-net crossover, see `demo/routing/crossbar/README.md`. Identical-via transitions shared by branches of one request produce one planned via.--For obstacle-aware planning, call `fusion_plan_route` with the same document,-board and revision guards plus `net`, `fromPad`, and `toPad`. It returns a-read-only `plan.route` for `fusion_route_net` and `plan.items` for visible-per-item commits. Grid, via cost, allowVias and bounded node/time limits are-optional. It is a two-pad orthogonal A* planner, not an all-net autorouter.-Use a fresh plan after intervening edits. See `demo/routing/obstacles/README.md`.--## Showing live calculations during a demo--Reuse `AdomActivityPalette`, its branding and close behavior. The repo's-`demo/routing/live_panel.py` serves the shared activity-palette component and SSE-from the container; `prepare_live_panel.py` attaches it to the existing palette.-Show pad endpoints, measured planner output, primitive creation, copper read-back-and native DRC results as they occur. Do not claim every operation has a live UI-unless the caller actually publishes these events. A lost DOM acknowledgment-stops the demo before the next mutation; do not reopen a user-closed palette.--Fusion palettes can be owned popup windows omitted by parent-window capture.-Inspect the popup screenshots and capture its HWND separately if necessary.-Check that both windows are visible, unminimized and large enough before recording.-Preserve raw takes and record synchronization limits when composing two captures.--## Before the first trace: which manufacturer, and whose rules win--Ask the user which board house will build the board before routing anything, unless they-already said. Load that house's rules into the open board and read them back, then keep the-stricter of the rules and the electrical constraints the user states:--```jsonc-fusion_set_design_rules {"action": "list"}                          // the vendors and tiers the wiki page adom/pcb-design-rules carries-fusion_set_design_rules {"fab": "jlcpcb", "layers": "2"}            // the user's answer; process defaults to standard-fusion_set_design_rules {"action": "export", "outputPath": "C:/Users/<you>/Documents/<task>/rules-loaded.edru"}-```--- Read the exported file and quote `mdWireWire` (copper clearance), `msWidth` (minimum width)-  and `msDrill` back to the user before routing; `fusion_alerts {sinceSec:60}` must be empty,-  a refused rule file is an in-canvas toast, not an error.-- Route with `clearance` and `width` no smaller than the loaded rules. A user constraint that-  is stricter (a wider power trace, a larger creepage gap, a keep-out) wins over the vendor-  minimum; the vendor minimum wins over a request to go below it. Say which one you applied.-- `fusion_set_design_rules {}` with no arguments loads the bundled Adom InstaPCB rules. The-  published BQ25792 demos ran on a DIAGNOSTIC copy of those rules (one inherited all-object-  same-net spacing rule disabled on disposable copies); they do not establish compliance with-  the unmodified InstaPCB profile, and neither does a clean `fusion_routing_drc` under any-  profile other than the one the user asked for.--## Checkpoints, and what a save hint is not--Every add-in reply from 1.10.0 carries `documentHygiene` (which open documents need saving)-and, when something does, `_hintDocumentHygiene`. The bridge never saves, closes or discards-on its own. Checkpoint with `fusion_export_eagle_source {outputPath}` (a `.brd` beside your-task folder) or `fusion_save_to_cloud` at milestones and before ending; verify the file exists-and re-read the hint, because an export leaves Fusion's own modified state as it was. Close-only the scratch document this task opened, by its exact name, with-`fusion_close_document {name, save:false}`, after the checkpoint is verified. Never bulk-close.--## Reproducing the published demos from the installed package--The installed package carries these verbs in the bridge runtime and the fixture, plans and-recorders under `demo/routing/` in the page source (`adom-wiki repo clone adom/fusion-bridge`).-`demo/routing/README.md` is the fixture walkthrough; `demo/routing/bq25792/` holds the BQ25792-plans, replay scripts and audits for the videos on adom/codex. `tools/install-routing-dev.ps1`-is a developer helper for hand-installing an exe over a dev-pinned cache; an installed release-never needs it. `demo/routing/bq25792/thermal-reroute/` (video 12) is in the page source since PR #8; its-native scripts need explicit FUSION_DEMO_TARGET, ADOM_API and FUSION_DEMO_OUTPUT, and the-README separates the accepted replay from rejected candidates. One thing is still not-installable: the shared EDA skillpack (adom/eda-engineering) is browseable source only. A-reproduction that needs it must say so.+# Routing and copper engineering in Fusion++Use the installed `fusion-bridge` skill for desktop discovery and application control.+Discover the live `fusion_describe` contract and check `fusion_readiness` before board calls.+If sign-in blocks readiness, resolve sign-in first. Since 1.10.1 a board call made while+Fusion is signing in returns `needs_signin` at once instead of a slow add-in restart diagnosis. Preserve pinned runtimes and existing user documents.+Work within the user's requested scope and save a recoverable checkpoint before replacing routes.++## Establish fabrication and electrical constraints++Honor a manufacturer/process already selected. Otherwise ask which manufacturer the user+wants, offering profiles returned by `fusion_set_design_rules {action:"list"}`. If undecided,+keep current rules explicitly provisional and continue inspection before dependent routing.++Load the selected fab, process and actual layer count with `fusion_set_design_rules`.+Export the loaded profile and inspect the file, including per-layer/per-object rules and+net classes. Compare rules by name and meaning, not file order or a successful command reply.+Legacy EAGLE keys such as `mdWireWire`, `msWidth` and `msDrill` do not describe every native+EDRU rule. Check native alerts for a rejected load. Keep the stricter applicable fabrication+and user/electrical constraints. A process's minimum isolation channel is not a universal+high-voltage clearance; derive insulation constraints from the actual environment and voltage.++Read [electrical priorities](references/electrical-priorities.md) for power paths, sensitive+signals, clean bends and via choices. Read [copper and thermal design](references/copper-thermal.md)+when assigning pours, retaining copper for ablation, or improving heat spreading.++## Select the supported routing path++Read `fusion_routing_state {expectDocument}` and retain its exact `boardId` and `revision`.+`fusion_route_net` requires these plus the exact net and points/paths. Coordinates and widths+are millimeters. Use pad references for endpoints where supported. Layer-changing waypoints+create through vias according to the live contract.++The conservative `fusion_route_net` preflight and bounded `fusion_plan_route` planner support+two-layer boards. The planner is a two-pad orthogonal A* search, not an all-net autorouter.+Do not feed it a four-layer power board or imply it enforces all electrical constraints.+For supported two-layer work, dry-run proposed geometry, inspect its electrical suitability,+then commit with the same guards. Replan after intervening changes.++For inner layers, native pours or other operations outside those verbs, use the documented+`fusion_run_modeling_script` / `fusion_electron_run` extension and the actual board stackup.+Native `LINE`, `VIA`, `POLYGON`, `CHANGE`, `RATSNEST` and `SHOW` are electronics commands,+not invented bridge verbs. These paths need their own identity checks, clearance analysis,+native readback and DRC; they do not inherit the dedicated routing verb's preflight guarantees.+Never transplant a worked example's layer numbers, dimensions or net names without inspection.++## Commit, inspect, and recover++Inspect semantic `success`, `verified`, `mutationAttempted`, returned copper and revision.+Use the next returned revision for the next edit. Operations are not an atomic Undo group.+On timeout or mismatch, inspect the board before deciding whether any operation needs retrying.++On affected Fusion builds a completed net can raise Autodesk's unexpected-condition modal.+If the reply carries `fusionUnexpectedCondition` or a classified `fusion_unexpected_condition`,+treat it as an application fault with possibly committed copper. Verify actual connectivity+and geometry, checkpoint, and inspect remaining alerts before continuing. Do not count modal+dismissal alone as a verified route or blindly repeat the final segment.++Use the existing Adom activity palette for useful progress when requested; respect its close+state and the user's foreground preference. Recording, narration and fixture replay are optional+presentation tasks, not prerequisites for routing a board.++## Validate and save++Refill copper before measuring connectivity. Run native DRC before and after with the same+selected rules, reporting inherited and new violations separately. `fusion_routing_drc` reads+approved errors as well; require `drc.checked`, clean applicable rules and no remaining+connections before calling the result connected and DRC-clean. A diagnostic rule profile+is not certification under the manufacturer's full profile. Check schematic parity/ERC and+power, thermal and signal-integrity requirements separately where relevant.++Inspect `documentHygiene` / `_hintDocumentHygiene`. Export a verified checkpoint with+`fusion_export_eagle_source` or save through the documented native/cloud workflow. Verify+output existence and usable contents. Exporting a file does not necessarily clear Fusion's+modified state. Close only completed task-owned scratch documents by exact name after verifying+the checkpoint; do not bulk-close or discard original user work.++Summarize actual changes, rule provenance, connectivity/DRC results, saved artifacts and remaining+engineering assumptions. Optional board-specific examples live under `demo/routing/` in the+Fusion Bridge wiki source; no example, video, Codex package or particular AI provider is required+to apply this skill.