# ⚠ This is a SEED copy — do NOT edit it as if it were live

The **canonical source** for the Adom Desktop Fusion 360 bridge is **not here**. It lives in
its own cloud-owned, git-backed repo:

- **Wiki (canonical, macOS line):** https://wiki.adom.inc/adom/adom-desktop-fusion-bridge-macos
- **GitHub mirror (fork here):** https://github.com/adom-inc/adom-desktop-fusion-bridge
- Wiki manifest AD updates from: `…/api/v1/pages/adom-desktop-fusion-bridge-macos/files/adom-bridge-fusion-manifest.json`
  (declared in this folder's `bridge.json` as `updateManifestUrl`).

## What this folder is

A **first-run SEED / offline fallback** that ships inside the Adom Desktop NSIS installer.
The moment AD can reach the wiki, **`refresh_bridges` streams the newer published version
into the cache** (`%LOCALAPPDATA%\Adom Desktop\bridges-cache\fusion360\`) and that cache copy
**supersedes** this seed (cache-over-bundled precedence, version-aware — newer wins).

## Why you must NOT hand-edit it

This copy WILL go stale and diverge from the wiki. It is periodically **re-bundled FROM the
canonical wiki/GH repo** — any edit you make here is overwritten on the next re-bundle and can
re-introduce drift that makes the laptop run code that doesn't match the published bridge.
Develop the bridge in the cloud-owned repo, publish it to the wiki, and let AD pull it.

## How updates reach users

1. The cloud thread publishes the bridge to its wiki page (manifest + versioned zip).
2. AD's `refresh_bridges` reads this folder's `updateManifestUrl`, fetches the wiki manifest,
   and — if newer than cached/bundled — downloads + sha256-verifies + extracts it into the cache.
3. On-demand pull:
   `adom-desktop bridge_install '{"manifestUrl":"https://wiki.adom.inc/api/v1/pages/adom-desktop-fusion-bridge/files/adom-bridge-fusion-manifest.json"}'`

Current seed: **v1.8.4** (mac line, published 2026-07-24 to `adom-desktop-fusion-bridge-macos`).
1.8.4 adds John's two new skills — `fusion-mcp-and-preferences` (with a macOS-enable-path note;
the Windows page's ROOT SKILL.md was accidentally clobbered by this skill's content, flagged to
John) and `fusion-web-export` (platform-agnostic APS/pup cloud export) — and restores the root
`SKILL.md` + full `skills/` tree to the runtime zip so AD's `verify_bundle` seed-gate passes
without patching in the 1.7.8 copy. The hero is now page-asset-only (out of the pkg tarball).
Base was **v1.8.3** (refreshed 2026-07-24 from the published release), plus the
macOS port carried on top: `handlers/mac_ui.py` (CGWindowList + screencapture + CGEvent +
System Events implementations of the window-automation verbs) and darwin branches in
`fusion_ui.py` / `close_fusion.py` / `dismiss_recovery.py` / `dialog_classify.py` /
`fusion_detect.py` / `install_addin.py` / `server.py` (prefixed-verb shim, /status OS gate).
Until the canonical repo absorbs the mac port, re-seeding from the wiki wholesale will
DROP it — re-apply these files or wait for the upstream merge.

**1.8.3 brought John's new Windows work — what ported cleanly vs. what needs mac follow-up:**
- ✅ Cross-platform, works on mac as-is: the **Autodesk MCP client verbs**
  (`fusion_mcp_status`/`_tools`/`_call`/`_resources`) — pure loopback HTTP to Fusion's
  local MCP server on `127.0.0.1:27182`; the new add-in commands `assembly_bom` +
  `physical_properties` (run in-process via the add-in); `describe.py` / `cloud_documents.py`
  updates. The upstream docked-panel **aspect guard** (tall+narrow windows aren't dialogs)
  was also ported into `mac_ui.find_dialog_windows`.
- ⚠️ Windows-only for now (degraded to an honest manual hint on darwin):
  `fusion_mcp_enable` / `fusion_prefs_open` / `fusion_prefs_close`. They drive Fusion's
  Preferences UI via `Commands.Start PreferencesCommand` (no-op on mac; mac opens prefs with
  Cmd+, or the avatar menu), Windows-measured section coordinates (mac's Preferences is a
  FLAT section list — no nested "API" row), and AD's `desktop_screenshot_window` (which on
  this mac returns `Failed to spawn screencapture` — an AD-core mac bug). The MCP toggle has
  no Autodesk API, so enabling is manual on mac (General → tick "Fusion MCP Server", Apply);
  once on, all `fusion_mcp_*` client verbs work. Full mac automation needs a measured
  Preferences coordinate map + a mac open-path — verified `mac_ui` CAN drive the dialog open
  (avatar click → Preferences → CEF/BitBlt capture), so it's coordinate work, not a blocker.


## 1.8.5 (pending publish — held for Kyle's go)

**macOS-only strip (Kyle's directive, 2026-07-31):** every Windows code path removed — the bridge
is now a macOS-only codebase. fusion_detect rewritten mac-native (bundle-binary completeness
marker, CGWindowList family/licensing detection); handlers/fusion_ui is a thin re-export of
mac_ui; dismiss_recovery/close_fusion/dialog_classify are mac-only; ad_client discovery is the
~/.adom/direct-api-port handshake only; fusion_helper.py and start.bat deleted; the injected
EPG-locator now globs the real mac path (verified on disk:
`<hash>/Autodesk Fusion.app/Contents/Libraries/Neutron/Api/InternalAddins/ElectronicsPackageGenerator`);
Chrome-history OAuth rescue reads ~/Library/Application Support profiles; all C:/ defaults and
"stage to Windows" doc instructions are now local-path/mac instructions. fusion_install_fusion
honestly reports there is no automated mac installer instead of running the Windows streamer.
bridge.json: killImageName dropped, windows detect paths removed, hero/docs/manifest URLs point at
the macos page.