← Commit history
BRIDGE_VERSION+1−1
@@ -1 +1 @@-0.9.21+0.9.22
Cargo.lock+1−1
@@ -122,7 +122,7 @@ dependencies = [  [[package]] name = "swx-bridge"-version = "0.9.21"+version = "0.9.22" dependencies = [  "miniz_oxide",  "serde",
Cargo.toml+1−1
@@ -1,6 +1,6 @@ [package] name = "swx-bridge"-version = "0.9.21"+version = "0.9.22" edition = "2021" rust-version = "1.80" description = "Adom SOLIDWORKS bridge — swx_* verbs over the SOLIDWORKS COM API, as a single native binary"
README.md+9−1
@@ -483,7 +483,15 @@ not.  ## Roadmap -- v0.9.21 (this): **the sign-in skill says when Visualize asks.** Started through+- v0.9.22 (this): **the skill carries the whole job.** The public+  `solidworks-bridge` skill's everyday flow now covers rendering+  (`swx_render_image`, the measured recipe and `zoomFactor`), SOLIDWORKS+  Visualize (`swx_start {app:"visualize"}`, the first-run folder dialog that is+  the user's to answer), pulling exports back, and keeping the bridge current+  (`refresh_bridges`). Nothing about this bridge is private: what remains in any+  user's own pack is their secret, their machine and their authorizations. Docs+  only; no runtime change.+- v0.9.21: **the sign-in skill says when Visualize asks.** Started through   its platform shortcut while the 3DEXPERIENCE Launcher holds the session,   Visualize raises no login (measured 2026-10-05); the separate login seen on   10-02 came from starting its exe directly, which this edition refuses. Docs
SKILL.md+25−1
@@ -103,9 +103,33 @@ BEFORE you do it: 7. Done: `swx_reset_workspace` closes only what the bridge created and has not    saved; `swx_close_all_safely {reason}` empties the session safely. -Files land on the DESKTOP filesystem; pull exports back with ab's `pull_file`.+8. A picture of the model: `swx_render_image {"width":3840,"height":2160,+   "view":"isometric","displayStyle":"shaded","perspective":true,+   "ambientOcclusion":true,"shadows":true,"zoomToFit":true,"zoomFactor":1.5,+   "reason":"..."}` — a hero-grade PNG in about ten seconds, window minimized or+   not, every display setting put back afterwards (`settings` accounts for each+   one; a setting SOLIDWORKS ignores, RealView on an uncertified GPU for one,+   is reported `setIgnored` with a note, never faked). `zoomFactor` 1.5 fills+   the frame after a fit; 2.0 clipped a tall assembly. Details and the live+   measurements: `docs/RENDERING.md`.+9. SOLIDWORKS Visualize: start it only with `swx_start {"app":"visualize",+   "reason":"..."}` (its platform shortcut; started from its exe this edition+   refuses with "must be opened from the 3DEXPERIENCE Platform"). Its first-run+   dialog, "choose a location for your 'SOLIDWORKS Visualize Content' folder",+   is the user's to answer — the bridge reports+   `waitingOn:"userVisualizeContentFolder"` and never clicks Continue, because+   that creates a folder on their machine. `swx_status.visualize` has the rest.++Files land on the DESKTOP filesystem; pull exports back with ab's `pull_file+{"filePaths":["C:\\...png"]}` (they arrive under /tmp on this machine). The bridge never foregrounds SOLIDWORKS. +Keeping the bridge current: Adom Bridge hosts the released version and updates+it on its own poll; `refresh_bridges {"name":"solidworks"}` pulls the newest+release now. It restarts the bridge process only and never touches SOLIDWORKS+or the data folder (`%LOCALAPPDATA%\adom-solidworks-bridge\`, which also holds+the ledger, ownership records and every recovery sweep).+ ## Verb catalog  `swx_describe '{}'` returns the full machine-readable catalog with per-verb
bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "solidworks",   "displayName": "SOLIDWORKS",-  "version": "0.9.21",+  "version": "0.9.22",   "description": "Bridge for SOLIDWORKS desktop CAD — create and open documents, a modeling DSL, file management (find/open/save/export/Pack and Go), custom properties, BOM generation, design analysis (mass properties, bodies, parameters, interference, rebuild health) and background window/dialog etiquette, over the SOLIDWORKS COM API. Single native binary: no interpreter, no PowerShell, ~10ms cold start.",   "author": "Adom Inc.",   "license": "MIT",
install.sh

  
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "solidworks-bridge",-  "version": "0.9.21",+  "version": "0.9.22",   "type": "app",   "description": "Skills for your container so your AI knows how to drive the SOLIDWORKS bridge (swx_* verbs). The bridge runtime itself is the release zip — a single native swx-bridge.exe; Adom Bridge loads that.",   "tags": [
uninstall.sh