Add source-bound exploded assembly and reassembly plans - Fusion - the Fusion 360 Bridge

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Add source-bound exploded assembly and reassembly plans #14

Closed opened by Drew Owens 2026-10-06

Merges exploded-plans-2026-10-06 → master

Assembly instructions need exploded steps without disturbing the source assembly's placements or joints. exploded_view_plan captures each physical instance's home pose and returns a bounded translation plan with ordered steps, simultaneous moves, titles/instructions, world/parent/local directions, deterministic samples, and reverse playback to the exact home matrices.

Nested instances inherit each ancestor's translation once; explicit child translations add independently. Repeated definitions retain separate instance identities and labels. Component and part-number links are preserved without computing or changing BOM quantities. Directions are fixed to the captured home frames, and the operation requires the current session and exact source revision.

This follows PR #12 on exact commit 9f51bab1f80a4f5660788ef2174c1649d0cf9d8f, which follows foundation PR #11. Merge those dependencies first. The focused 37-file feature patch isolates this checkpoint; all 1,405 downloaded file hashes were verified, including 138 unchanged inherited test reports. Public verbs remain 179; typed mechanical operations increase to 56; release numbers remain unchanged.

Offline validation: 496 Python tests, 17 focused planner tests, 27 native-runner boundary tests, static checks and a fresh Windows build pass. Independent adversarial calculations verified 840 poses in 30 scenarios with noncommuting rotations. Exact frozen source on Fusion 2705.1.30 passed six instances across 60 forward/reverse poses, wrong-session and stale-target refusals, unchanged full model/joint and public BOM state, F3D graph/BOM roundtrip and cleanup (16 native checks). The first campaign stopped before product invocation on an incorrect fixture joint-owner expectation; that original failure is preserved, and a narrowly corrected owner/member oracle passed the second campaign.

This checkpoint generates numerical presentation plans. Geometry previews, trails, native storyboard authoring, collision-free disassembly, rendered frames and video export remain separate work. Installed public routing remains untested. Native checks use a temporary unregistered module in the pinned development runtime; no screenshots or Shotlog uploads are requested.

Diff Skip to comments (2)

No diff was attached to this pull request.

Comments

Drew Owens · 1mo ago

The attached feature patch isolates all 37 exploded-planning changes against the exact PR #12 commit 9f51bab1f80a4f5660788ef2174c1649d0cf9d8f. It applies cleanly to that base and every patched file matches published commit 64ef2fd3e7a2b620b3602ed8e685322dc7bf03dc. Fresh download verified all 1,405 file hashes: 1,267 selected source files plus 138 unchanged inherited test reports.

Merge foundation #11 and scene inspection #12 first. This focused patch keeps the new feature reviewable while those dependencies and historical evidence are also present in the master comparison.

The exact numeric planning function passed all 16 native checks on Fusion 2705.1.30, including 60 poses, unchanged model/joint/BOM state and F3D reopening/cleanup. Installed public routing, visible graphics and rendering remain not run. Original failed fixture-oracle evidence is preserved separately. No images or Shotlog uploads were requested.

exploded-plans-feature.patch

exploded-feature-patch-verification.json

Drew Owens · 14d ago

Closing as superseded by #22, which Colby merged on 2026-10-28. #22 carries this work in its current form: the mechanical layer with its journal, validation and replies owned by the bridge exe (John's pattern), rebased onto 1.12.8. The development history of these builds is in docs/MECHANICAL-HISTORY.md.