@aryacode/dsh-engineering 0.4.4 → 0.4.5

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.4.5] - 2026-10-25
+
+### Changed
+
+- **FactoryTalk Optix is vendored, so `dependencies` carries no plugin at all.** The Optix tree
+  (`lib/`, `bridge/StudioMCPBridge.cs`, `templates/`, `locale/`, `icon.svg`) now lives in
+  `packages/optix` and ships under `vendor/optix`; the `optix` row names
+  `@aryacode/dsh-engineering/optix`. `@aryacode/dsh-tool-ft-optix` is gone from the manifest, which
+  leaves one plugin to install and no component package to publish, keep in sync, or retire.
+- The last dependency that remains is Optix's own runtime library, `playwright-core@1.61.1`, declared
+  as a plain registry dependency.
+
+One plugin now covers all four products: 5 rows, 79 tools, both previews, no component packages.
+
 ## [0.4.4] - 2026-10-25
 
 ### Changed

package/cordis.patch.yml

@@ -37,6 +37,7 @@
     # context, so this row is independent of every product row above.
     - id: viewers
       name: '@aryacode/dsh-engineering'
-    # FactoryTalk Optix stays a separate package, mounted as a component row.
+    # FactoryTalk Optix: vendored like the other three products, so one install
+    # carries every surface and no component package is a dependency.
     - id: optix
-      name: '@aryacode/dsh-tool-ft-optix'
+      name: '@aryacode/dsh-engineering/optix'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aryacode/dsh-engineering",
-  "version": "0.4.4",
+  "version": "0.4.5",
   "description": "AryaCode engineering bundle: one install surface for the Studio 5000 L5X, FactoryTalk View ME, MotionWorks IEC and FactoryTalk Optix surfaces, one row per product, with the ladder and display previews.",
   "keywords": [
     "dsh",
@@ -56,9 +56,9 @@
     }
   },
   "dependencies": {
-    "@aryacode/dsh-tool-ft-optix": "0.2.1-rc.3",
     "fast-xml-parser": "5.11.1",
     "fast-xml-validator": "1.4.2",
+    "playwright-core": "1.61.1",
     "st-ethernet-ip": "2.7.5"
   },
   "peerDependencies": {
@@ -79,6 +79,7 @@
     "./l5x": "./entries/l5x.js",
     "./ftview": "./entries/ftview.js",
     "./mwi": "./entries/mwi.js",
+    "./optix": "./vendor/optix/lib/index.js",
     "./l5x/read": "./vendor/l5x/lib/index.js",
     "./l5x/skill": "./vendor/l5x/lib/skill.js",
     "./l5x/editing": "./vendor/l5x/lib/editing.js",

package/vendor/optix/bridge/LICENSE

@@ -0,0 +1,35 @@
+MIT License
+
+Copyright (c) 2026 ASQI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+---
+
+DISCLAIMER OF AFFILIATION
+
+This project is not affiliated with, endorsed by, or sponsored by Rockwell
+Automation, Inc. FactoryTalk and Optix are trademarks of Rockwell Automation,
+Inc. ftx-mcp is an independent integration tool authored against the
+public Studio CLI surface; it is not a Rockwell product.
+
+The FT Optix binaries themselves (FTOptixApplicationUpdateService.exe,
+FTOptixStudio.exe, FTOptixRuntime.exe) are Rockwell Automation products,
+licensed separately. This repository orchestrates them but does not
+redistribute them.