@aryacode/dsh-engineering 0.0.0-stage → 0.3.0

package/CHANGELOG.md

@@ -0,0 +1,115 @@
+# Changelog
+
+## [0.3.0] - 2026-10-23
+
+### Added
+
+- **FactoryTalk Optix as a bundle component:** the `optix` row mounts `@aryacode/dsh-tool-ft-optix` (Studio discovery, live authoring, validation, templates, preview and OCR) from a released component tarball. The standalone tool plugin is no longer a product entry or an installer dependency.
+- The bundle now registers 79 tools: the 73 generated reference tools plus six Optix tools. Optix stays unlinked to a skill until one exists.
+
+## [0.2.0] - 2026-10-23
+
+### Added
+
+- **MotionWorks IEC rows:** `mwi-session` (find, stage, open, start, status, worksheet, close), `mwi-read` (overview, list, get, search, references, review, help), `mwi-verify` (compile, diagnostics, saved-source baselines) and `mwi-edit` (code, declarations, structure, block insertion, POU packages, validation, apply), plus the `mwi-read-skill` guidance.
+- The redesigned surface is 24 tools over the proven 32-bit COM bridge and the Python saved-model engine. It is verified live against MotionWorks IEC 3 Pro 1.19: stage, start, worksheet, close, saved-project reads, compile diagnostics, code replacement, declaration add, POU create/delete, block insertion and a POU package export/delete/import round trip.
+- The edit row is off by default. Edits write only the staged copy and verify unrelated saved and native state.
+
+### Changed
+
+- The bundle is now 73 tools. MotionWorks IEC mounts here instead of as a separate plugin.
+
+Notable changes to `dsh-engineering`. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.2] - 2026-10-23
+
+### Fixed
+
+- **L5X filesystem contract:** the harness filesystem resolves paths to opaque targets. The session now keeps a target for re-reads and a display path for outputs, so `export_acd_to_l5x`, drafts and SDK tools receive strings again instead of a provider object. Verified against SDK v37: a real ACD exported to a 3.0 MB L5X.
+- **FactoryTalk View filesystem contract:** the read, editing and Studio entries adapt composed string paths to the harness target contract, so opening an export, applying edits and Studio discovery no longer pass raw paths to target-based operations.
+- Link every L5X tool to the `rockwell-l5x` capability by exact name. The rebuilt tools use descriptive names (`open_project`, `draft_apply`, ...), so the `l5x_` prefix alone did not govern them and their schemas stayed visible when the skill was off.
+- Correct the `factorytalk-view` guidance: the editing and Studio entries now exist and are enabled, so the skill no longer calls those operations out of scope.
+
+### Added
+
+- `docs/reference/tools.md` and `tools.json`: a generated reference for all 49 tools, with a test that fails when the committed reference or the policy coverage drifts from the registered definitions.
+- `docs/examples.md`: end-to-end sessions for reading, staged edits, SDK verification, supervised controller access, live reads and FactoryTalk View.
+- `docs/architecture.md`: the row model, service injection, configuration, client faces, distribution and compatibility.
+- Package READMEs for `packages/l5x`, `packages/ftview`, `packages/viewer` and `packages/ftview-viewer`.
+
+### Changed
+
+- Rewrite the README for the current bundle: what it is, the eleven components and their defaults, install, composition, the policy table, tools, requirements, safety and known gaps.
+- Add `docs:tools` and `docs:check` scripts; tests now run through tsx so they can read the TypeScript tool factories.
+
+## [0.1.1] - 2026-10-23
+
+
+
+- Add the FTView Studio entry `ftview-studio`: `ftview_studio_status`, `ftview_studio_preflight`, `ftview_studio_handoff` — discovery of installs, schemas, help and the Add Component utility, changed-file preflight with Studio name restrictions, and the ordered manual import plan. No vendor utility is executed.
+- Add 6 Studio tests: registration, discovery with a simulated install, absent install, changed-file preflight, unsafe-name blocker and the handoff plan. FTView suite is 26 tests.
+
+- Add the FTView editing entry `ftview-edit`: `ftview_draft_display_set`, `ftview_draft_display_add`, `ftview_draft_tag_upsert`, `ftview_validate`, `ftview_apply` — one operation per call, text-preserving transforms, re-parsed validation, and apply to a new folder that never touches the source. Row disabled until the old plugin retires.
+- Add 8 editing tests: display attribute edit end to end, tag row update, display copy, draft clearing, unknown display, duplicate name, and existing-output refusal. FTView suite is 20 tests.
+
+- Fold the FactoryTalk View display preview into the bundle as `dsh-engineering-ftview-viewer`, mounted by the `ftview-viewer` row (disabled until the old plugin retires, because both claim `.xml` previews).
+
+- Add the FactoryTalk View ME read surface as `dsh-engineering-ftview`: six intents (`ftview_open`, `ftview_list`, `ftview_get`, `ftview_find`, `ftview_check`, `ftview_compare`), 3,557 schema characters, and a 2.5 KB `factorytalk-view` skill. No Python engine; display XML and the tag CSV are parsed in TypeScript.
+- Insert `ftview-read` and `ftview-read-skill` disabled until the old FTView plugin retires, because both register the same skill name.
+- Add 12 FTView tests: registration, every parameter described, open, list, get, not-found candidates, find, structural checks, compare and skill registration. Design recorded in `docs/port/ftview.md`.
+
+- Fold the L5X ladder viewer into the bundle as `dsh-engineering-l5x-viewer`, mounted by the `l5x-viewer` row. The package carries the copied client source and the built closure-factory artifact re-registered under the bundle name, so the viewer keeps rendering while the standalone `ui-logix-project-viewer` product entry is retired.
+- Verified in the dev app: after removing the standalone viewer from `PRODUCT_PLUGINS` and rebuilding, the same L5X document still renders its ladder view from the folded package, and the Plugins page no longer lists the standalone viewer card.
+
+- Retire the old L5X plugin from the dev profile: `dsh-tool-l5x` is removed from its dependencies and its `l5x-tools` and `l5x-skill` patch rows are gone. The composed profile carries only this bundle's rows.
+- Verified live after the retirement: the session listed the eleven read tools and the new `rockwell-l5x` description, with no `l5x_*` tool and no old skill text.
+
+- Port the client face: the PLC trend card (`lib/client.js`, 17.2 KB closure-factory bundle) registered for `start_plc_trend`, with its locales, styles and trend model. The card mounts independently of every tool row.
+- Record that the old plugin's `face.ts` and `Studio5000.tsx` were dead code — never imported by its client entry — so the two-rung ladder rail is not a ported feature. A ladder viewer for L5X documents would be new work.
+- Add `dsh.client` metadata, a `tsdown.client.config.ts` bundle with the package name as its registration id, and the host build now emits both halves.
+
+- Add the `l5x-live` entry: `poll_live_tags` and `start_plc_trend`, 2,971 schema characters, inserted disabled. Reads use the package's polling worker and its own EtherNet/IP connection, so no Studio, FactoryLinx or SDK is required.
+- Tags are a real array of flat objects, not the old JSON string: a string is refused with a fix. The trend starts a session-owned job and states that live logic matching the export is unverified.
+- Bring the polling worker and the `st-ethernet-ip` dependency into the package, and dispose owned workers when the plugin unloads.
+- Add 4 live tests: registration, an undeclared tag, a JSON-string refusal and the trend job refusal. Suite is 60 tests.
+
+- Add the supervised controller tools to `l5x-studio`: `controller_approval_status`, `capture_controller_snapshot`, `go_online`, `read_controller_mode`, `read_live_tag`, `change_controller_mode` and `download_project`. The entry is now 13 tools and 7,901 schema characters, still inserted disabled.
+- Port the approval seam as a composition service: the three machine-changing actions refuse with `APPROVAL_UNAVAILABLE` before contacting a controller when the session policy is not `ask`, and proceed only on `allowed-once`. Downloads accept only a `verification_id` this chat produced from a passed build, checked against the built ACD and both L5X hashes.
+- `verify_offline_l5x` and `build_acd_from_draft` now return a `verification_id` when the build passed and the review has no blockers.
+- Add 4 approval-gate tests: status without the service, status with `ask`, a mode change refused before contact, and a download without a verification id. Suite is 56 tests.
+
+- Add the `l5x-studio` entry with its offline half: `studio_sdk_status`, `studio_capabilities`, `export_acd_to_l5x`, `verify_offline_l5x`, `build_acd_from_draft` and `studio_review_evidence`. 3,914 schema characters, inserted disabled because it needs Studio 5000.
+- The entry consumes the read entry's `l5xProjects` service and records ACD exports per chat, so a baseline is accepted only when both the ACD and the L5X hashes still match the export that produced them.
+- Verified locally against the installed SDK: an ACD exported to L5X in 29 s, the export reopened by this parser, and a Studio-exported L5X built offline with `offline_build: passed`. The SDK refused to re-import its own export with `XMLSrv_E_IMPORT_ABORTED_NO_CHANGES`; recorded in the port specification.
+- Add 4 studio tests: registration, SDK preflight, capabilities and the unchanged-routine refusal. Suite is 52 tests.
+
+- Add the draft family as its own `l5x-editing` entry: `draft_rung`, `draft_st`, `draft_routine`, `draft_tag`, `draft_tag_description`, `draft_udt_member`, `draft_udt_description`, `draft_validate`, `draft_apply`. One operation per call, accumulated per chat and project, validated against the project, then written to one new file.
+- The editing entry consumes the read entry's `l5xProjects` service, so a project is opened once for both entries. It is inserted disabled: the read entry stays at 8,107 schema characters and editing costs 7,233 only when enabled.
+- Add 7 draft tests: accumulation, argument refusal, validation hash, application to a new file, source preservation, overwrite refusal and draft handles. Suite is 48 tests.
+- Update the `rockwell-l5x` guidance for drafting: boundary, one-operation-per-call, validate before apply, and the note that editing may be disabled in a profile.
+
+- Port the `rockwell-l5x` guidance into the package: a 2.9 KB decision tree covering the read workflow, AOI and program scope rules, checks, comparison, reporting limits and revision floors. It is registered by `dsh-engineering-l5x/skill` and mounted as the stable `l5x-read-skill` row; the old 27 KB skill row can stay disabled.
+- Add 3 skill tests: registration identity, body budget and frontmatter stripping, and a loud failure when the skills service is missing. Suite is 41 tests.
+- Mount the L5X pilot as a bundle component: `cordis.patch.yml` inserts the stable `l5x-read` row, `dsh-engineering-l5x` is a workspace dependency, and the Plugins card lists the component under Engineering. The dev profile no longer inserts the row itself.
+- Start the L5X port in `packages/l5x`: four offline read tools (`open_project`, `project_overview`, `list_components`, `get_component`), 2,431 schema characters, every parameter described, results carrying `summary`/`data`/`coverage`/`next`, and failures carrying `code`/`message`/`fix`/`candidates`.
+- Add `list_components` because the current 43-tool surface exposes no way to enumerate tags, UDTs, routines or modules; discovery exists only in the legacy twelve-tool API.
+- Add the reference cluster: `search_logic`, `find_references`, `trace_dependencies`, `resolve_tag`, `usage_map`. The five tools that answered "where is this used" in the old surface collapse into two named intents plus address resolution and element mapping; the surface is now 9 tools and 6,154 schema characters with 31 of 31 parameters described.
+- Complete the offline read surface with `run_checks` and `compare_projects`: findings filtered by rule or severity with review caveats, and a component-level diff that ignores timestamps and XML formatting. The surface is now 11 tools and 7,994 schema characters with 41 of 41 parameters described.
+- Document and enforce export revisions: reading accepts any L5X revision 19 or later, flags revisions outside the observed matrix as `untested_revision`, and refuses anything older than 19. The revision-37 floor applies only to a Studio SDK build.
+- Add 7 checks and comparison tests, including a real tag-description change and a zero-change comparison, plus 3 revision tests. Suite is 34 tests.
+- Scope project handles to the chat that opened them. The first two-chat transcript made the second chat see a handle from the first and fail its listing with `AMBIGUOUS_PROJECT`; handles now live per chat.
+- Resolve `AOI_Name::Member` in `trace_dependencies` against the AOI's declaration scope, and refuse an unresolved symbol with `UNRESOLVED_SYMBOL` and the scope fix instead of returning an empty graph. `find_references` coverage now states that external consumers are not visible.
+- Add chat isolation, AOI-qualified tracing and unresolved-symbol tests. Suite is 38 tests.
+- Document the composed layer, the skill-to-namespace policy, the measured tool exposure, the built-in target composition, the retirement list, and the replacement-map requirement for the flip.
+- Record the classification: AryaCode's product catalog lists this bundle as AryaCode-authored with market distribution, so the Plugins page groups it under AryaCode and not Community.
+- Record the switch model: a skill is the single per-product switch for guidance and tools, while the client faces (ladder viewer, ME display renderer, DXF viewer) are separate entries that stay mounted. The port shares one isomorphic parser between the host tools and each viewer.
+- Specify the L5X port from measured failures: 43 tools, 132 undescribed parameters, nine JSON-in-string parameters, 97 error codes, and the overlapping reference, inspection and drafting clusters. The spec splits the product into `l5x-tools` (default), `l5x-studio` and `l5x-live` (both off), the skill and the independent client.
+- Settle the four port decisions: two reference tools rather than one with a mode; `observe_logic` retires; no batch tool; the SDK entry owns the supervised lifecycle and `edit_offline_acd` survives as `build_acd_from_draft`.
+- Add `AGENTS.md`: documentation is updated in the same change as the code it describes, diagrams are part of the contract, and known gaps stay explicit.
+- Add `test/docs.spec.mjs`, which fails when the README policy table, the documented unlinked namespace, the changelog version heading, or the locale key sets disagree with the patch. Verified to fail on a dropped policy row and on a renamed prefix.
+
+## [0.1.0]
+
+- Add the engineering bundle: a phase-1, additive loader layer that targets the existing `tool-capability-policy` row and links `l5x_*`, `ftview_*` and `mw_*` to the skills that govern them.
+- Keep `onDemand: false` so the bundle does not change the product-wide eager tool exposure Arya measured and kept.
+- Insert no plugin rows, so existing profiles and product plugin ids are untouched.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 KonnectSuite
+
+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.

package/README.md

@@ -1,3 +1,229 @@
-# Temporary Holding Version
+# AryaCode Engineering
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+**One bundle for automation-engineering work in AryaCode.** Studio 5000 L5X, FactoryTalk View ME,
+MotionWorks IEC and FactoryTalk Optix sit behind a single install, one row per capability, and one
+switch per product — so the switch removes tool schemas from the request instead of leaving them
+visible after the guidance is off.
+
+`@aryacode/dsh-engineering` · 79 tools · 17 rows · 4 products · MIT
+
+---
+
+## Why a bundle
+
+A general assistant pays for every tool schema on every request. An automation engineer needs deep
+surfaces — reading a 3 MB L5X, comparing two projects, staging ladder edits, talking to a controller —
+but only one or two of them at a time.
+
+This bundle splits those surfaces into independently switchable rows and links each product's tools to
+the skill that governs it. Turning a product off removes **both** its guidance and its schemas:
+
+| State | What the model receives |
+|---|---|
+| `rockwell-l5x` skill **on** | L5X guidance + 35 tool schemas |
+| `rockwell-l5x` skill **off** | neither |
+
+The heavy surfaces are separate rows on purpose. A read-only profile pays for the read tools and
+nothing else, and the viewers are independent of the tools — switching L5X tools off does not remove
+the ladder viewer.
+
+## What it supports
+
+| Product | Tools | Default | Needs |
+|---|---|---|---|
+| **Studio 5000 L5X** | 35 | read on; edit, Studio, live **off** | Node for offline reads; Studio 5000 + Logix Designer SDK for SDK work; a controller for live |
+| **FactoryTalk View ME** | 14 | all on | Node for an export folder; FactoryTalk View Studio ME for discovery and the handoff |
+| **MotionWorks IEC** | 24 | session, read, verify on; edit **off** | MotionWorks IEC 3 Pro installed; verified against 1.19 |
+| **FactoryTalk Optix** | 6 | on | Optix Studio installed |
+
+Tool groups, by product:
+
+- **L5X** — 11 read (`open_project` … `compare_projects`), 9 staged drafts (`draft_*`), 6 Logix
+  Designer SDK, 7 supervised controller, 2 live EtherNet/IP
+- **FactoryTalk View** — 6 read, 5 staged edits, 3 Studio handoff
+- **MotionWorks IEC** — 7 session, 7 saved-project reads, 3 verify, 7 staged edits
+- **Optix** — 6 tools, unlinked to a skill until one exists
+
+## What the policy changes
+
+Each skill governs a product's tools. The capability policy is per-tool, not per-prefix, because the
+rebuilt tools use descriptive names.
+
+| Skill | Governs | Tools |
+|---|---|---|
+| `rockwell-l5x` | `l5x_*` **and** the 35 L5X tools by exact name | 35 |
+| `factorytalk-view` | `ftview_*` | 14 |
+| `motionworks-iec` | `mw_*` | 24 |
+| — | `optix_*` | 6 (always visible: no skill yet) |
+
+`onDemand` stays `false`. Bounded on-demand discovery was measured against eager exposure and kept
+eager, because discovery cost more turns than the schema characters it saved. The context win comes
+from the per-product switches and from splitting the surfaces into rows.
+
+The reference in [docs/reference/tools.md](docs/reference/tools.md) is generated from the registered
+definitions, and `pnpm test` fails when a registered tool is not governed or the committed reference
+drifts.
+
+## Status
+
+Where each surface actually stands, based on what has been exercised.
+
+**Working and verified**
+
+- L5X offline reads, references, usage, checks and comparison against revision 19+ projects
+- Staged L5X editing — nine `draft_*` tools, validation, and one new file on apply
+- Logix Designer SDK: a real ACD exported to a 3.0 MB L5X against SDK v37
+- Supervised controller access — upload, mode change and download behind per-call approval, with
+  downloads accepting only a verification id produced by a passed build
+- Live EtherNet/IP reads and a bounded PLC trend
+- FactoryTalk View ME: export reads, structural checks, comparison, staged display and HMI tag edits
+- MotionWorks IEC: verified live against 3 Pro 1.19 — stage, start, worksheet, close, saved-project
+  reads, compile diagnostics, code replacement, declaration add, POU create/delete, block insertion
+  and a POU package export/delete/import round trip
+- Ladder viewer and FactoryTalk View display preview
+
+**Deliberately off by default** — enabled per profile: `l5x-editing`, `l5x-studio`, `l5x-live`,
+`mwi-edit`. A read-only profile should not pay for nine draft schemas or a controller surface.
+
+**Known limits** — stated in the bundle, not hidden:
+
+- Live reads and SDK builds cannot establish that online logic matches the export; every result says
+  so in `coverage`
+- FBD/SFC semantics are not exercised
+- FactoryTalk View Studio work is a **manual handoff**: the bundle plans the import and preflights
+  changed files, it does not import
+- Optix has no skill, so its 6 tools cannot be switched off
+
+**Not in this repository** — CAD mounts as an independent plugin.
+
+## Milestones
+
+| Version | What landed |
+|---|---|
+| **0.3.0** | FactoryTalk Optix becomes a bundle component; 79 tools total |
+| **0.2.0** | MotionWorks IEC ports into the bundle — 24 tools over the COM bridge and saved-model engine, verified live; edit off by default |
+| **0.1.2** | Harness filesystem contract fixed across L5X and FactoryTalk View; every L5X tool linked to its capability by name; generated tool reference, examples and architecture docs |
+
+## Install
+
+The bundle is a meta-package: it mounts its components by row id and carries the tool-exposure policy.
+Installing a component on its own gives you tools **without** the policy.
+
+```sh
+# in the AryaCode profile
+pnpm add @aryacode/dsh-engineering
+```
+
+```jsonc
+// profile package.json
+"dsh": { "profile": { "bundles": ["@aryacode/dsh-engineering"] } }
+```
+
+Then, in the application, the **Engineering** card lists each row as a component. Per-row enable state
+lives in the profile, so disabling a row survives the next update.
+
+For development, clone this repository, `pnpm install`, and link it into a profile bundle list; the
+development home mounts the same rows.
+
+## How it composes
+
+The bundle adds one loader layer after the Web app. It patches the existing `tool-capability-policy`
+row and inserts its own rows; it never replaces a product plugin id.
+
+```mermaid
+flowchart TB
+  Profile["Profile bundle list"] --> Bundle["@aryacode/dsh-engineering"]
+  Bundle -->|"id-targeted config override"| Policy["tool-capability-policy"]
+  Bundle -->|insert| L5XRead["l5x-read (on)"]
+  L5XRead --> L5XSkill["l5x-read-skill (on)"]
+  Bundle -->|insert| L5XEdit["l5x-editing (off)"]
+  Bundle -->|insert| L5XStudio["l5x-studio (off)"]
+  Bundle -->|insert| L5XLive["l5x-live (off)"]
+  Bundle -->|insert| L5XViewer["l5x-viewer (on)"]
+  Bundle -->|insert| FTV["ftview-read / edit / studio / viewer (on)"]
+  Bundle -->|insert| MWI["mwi-session / read / verify (on), edit (off)"]
+  Bundle -->|insert| Optix["optix (on)"]
+  Policy -->|"rockwell-l5x governs 35 tools"| L5XRead
+  Policy -->|"factorytalk-view governs ftview_*"| FTV
+  Policy -->|"motionworks-iec governs mw_*"| MWI
+```
+
+Row ids are stable. Profiles and patches address these ids, so per-row enable state survives upgrades
+even when the implementation behind a row is replaced.
+
+| Row id | Package entry | Default |
+|---|---|---|
+| `l5x-read` | `dsh-engineering-l5x` | on |
+| `l5x-read-skill` | `dsh-engineering-l5x/skill` | on |
+| `l5x-editing` | `dsh-engineering-l5x/editing` | off |
+| `l5x-studio` | `dsh-engineering-l5x/studio` | off |
+| `l5x-live` | `dsh-engineering-l5x/live` | off |
+| `l5x-viewer` | `dsh-engineering-l5x-viewer` | on |
+| `ftview-read` | `dsh-engineering-ftview` | on |
+| `ftview-read-skill` | `dsh-engineering-ftview/skill` | on |
+| `ftview-edit` | `dsh-engineering-ftview/edit` | on |
+| `ftview-studio` | `dsh-engineering-ftview/studio` | on |
+| `ftview-viewer` | `dsh-engineering-ftview-viewer` | on |
+| `mwi-session` | `dsh-engineering-mwi` | on |
+| `mwi-read` | `dsh-engineering-mwi/read` | on |
+| `mwi-read-skill` | `dsh-engineering-mwi/skill` | on |
+| `mwi-verify` | `dsh-engineering-mwi/verify` | on |
+| `mwi-edit` | `dsh-engineering-mwi/edit` | off |
+| `optix` | `@aryacode/dsh-tool-ft-optix` | on |
+
+## Safety
+
+- **Read-only by default.** Reading, checks, comparison and the viewers never change a controller.
+- **Edits write new files.** `draft_apply` writes one new L5X beside the source and refuses to
+  overwrite; `ftview_apply` writes a new export folder and leaves the source untouched. MotionWorks
+  edits write only the staged copy and verify unrelated saved and native state.
+- **Controller changes need a human.** Upload, mode change and download require per-call approval and
+  a session policy that permits asking. The tools refuse before contacting a controller when approval
+  is unavailable, and a download accepts only a verification id produced by a passed build.
+- **No hidden vendor execution.** The FactoryTalk View Studio handoff returns a manual import plan; it
+  does not run a vendor utility.
+- **Coverage is stated.** Every result names what it cannot establish, including whether online logic
+  matches the export.
+
+## Requirements
+
+| Surface | Needs |
+|---|---|
+| L5X read, references, checks, drafts | Node only; reads `.L5X` revision 19 or later |
+| L5X Studio SDK | Studio 5000 with the Logix Designer SDK service, FactoryTalk Linx, .NET |
+| L5X controller | Reachable controller, FactoryTalk Linx, a matching uploaded ACD |
+| L5X live | A reachable controller over EtherNet/IP; no Studio, Linx or ACD |
+| FactoryTalk View read, edit | Node only; a FactoryTalk View ME export folder |
+| FactoryTalk View Studio | FactoryTalk View Studio ME for discovery and the manual import |
+| MotionWorks IEC | MotionWorks IEC 3 Pro; the 32-bit COM bridge and the Python saved-model engine |
+| Optix | FactoryTalk Optix Studio |
+
+## Documentation
+
+| Document | Owns |
+|---|---|
+| [Tool reference](docs/reference/tools.md) | Every tool, parameter and description (generated) |
+| [Examples](docs/examples.md) | End-to-end sessions per product |
+| [Architecture](docs/architecture.md) | Composition, row model, configuration, client faces, packaging |
+| [L5X port](docs/port/l5x.md) | L5X port decisions and measurements |
+| [FTView port](docs/port/ftview.md) | FactoryTalk View port decisions |
+| [MotionWorks IEC port](docs/port/mwi.md) | MWI migration design, phases and inventory |
+| [Packaging](docs/port/packaging.md) | How the bundle is packed and pinned |
+| [Retirement](docs/port/retirement.md) | What "gone" means for a retired plugin |
+| [Changelog](CHANGELOG.md) | Released and unreleased changes |
+
+## Development
+
+```sh
+pnpm install
+pnpm test          # patch, docs, tool-reference and manifest checks
+pnpm docs:tools    # regenerate the tool reference from the registered definitions
+pnpm docs:check    # fail if the committed reference has drifted
+```
+
+Tests run through `tsx` so they can read the TypeScript tool factories. A registered tool that no
+skill governs fails the suite — the policy is a test, not a convention.
+
+## Licence
+
+MIT. See [LICENSE](LICENSE).

package/cordis.patch.yml

@@ -0,0 +1,122 @@
+# AryaCode engineering bundle.
+#
+# Two layers live here.
+#
+# 1. Tool exposure. Targets the existing `tool-capability-policy` row and links
+#    each engineering product's tool namespace to the skill that governs it, so
+#    the Skills page switch controls the guidance and the tools together instead
+#    of leaving the tool schemas exposed after the skill is off.
+#
+#    `onDemand` stays false. Arya measured bounded on-demand discovery against
+#    eager exposure and kept eager exposure because discovery cost more turns
+#    than the schema characters it saved. The context gain comes from per-product
+#    switches and from trimming the product schemas.
+#
+#    Optix has no skill yet, so `optix_*` stays unlinked and always visible. Link
+#    it here once a FactoryTalk Optix skill registers one.
+#
+# 2. The product rows. Mounts the rebuilt L5X and FactoryTalk View surfaces and
+#    their guidance as components of this bundle. The row ids are stable, so per-entry enable
+#    state survives upgrades even as the package behind them is rebuilt.
+- id: tool-capability-policy
+  config:
+    policyOnly: true
+    toolPolicy:
+      onDemand: false
+      capabilities:
+        - skill: rockwell-l5x
+          # The rebuilt L5X tools keep descriptive names (open_project,
+          # draft_apply, ...). This exact list is what the skill switch
+          # governs; `l5x_` stays linked for any prefixed tool added later.
+          tools:
+            - open_project
+            - project_overview
+            - list_components
+            - get_component
+            - search_logic
+            - find_references
+            - trace_dependencies
+            - resolve_tag
+            - usage_map
+            - run_checks
+            - compare_projects
+            - draft_rung
+            - draft_st
+            - draft_routine
+            - draft_tag
+            - draft_tag_description
+            - draft_udt_member
+            - draft_udt_description
+            - draft_validate
+            - draft_apply
+            - studio_sdk_status
+            - studio_capabilities
+            - export_acd_to_l5x
+            - verify_offline_l5x
+            - build_acd_from_draft
+            - studio_review_evidence
+            - controller_approval_status
+            - capture_controller_snapshot
+            - go_online
+            - read_controller_mode
+            - read_live_tag
+            - change_controller_mode
+            - download_project
+            - poll_live_tags
+            - start_plc_trend
+          prefixes:
+            - l5x_
+        - skill: factorytalk-view
+          prefixes:
+            - ftview_
+        - skill: motionworks-iec
+          prefixes:
+            - mw_
+- insert:
+    - id: l5x-read
+      name: '@aryacode/dsh-engineering/l5x'
+    - id: l5x-read-skill
+      name: '@aryacode/dsh-engineering/l5x/skill'
+    # Editing is its own entry so a read-only profile does not pay for nine
+    # draft schemas. It consumes the read entry's project service.
+    - id: l5x-editing
+      name: '@aryacode/dsh-engineering/l5x/editing'
+      disabled: true
+    # The SDK entry needs Studio 5000 installed, so it stays off until asked for.
+    - id: l5x-studio
+      name: '@aryacode/dsh-engineering/l5x/studio'
+      disabled: true
+    # Live reads need a controller address; the row is the switch.
+    - id: l5x-live
+      name: '@aryacode/dsh-engineering/l5x/live'
+      disabled: true
+    # The ladder viewer is the bundle's own client face, independent of the tools.
+    - id: l5x-viewer
+      name: '@aryacode/dsh-engineering/l5x-viewer'
+    # FactoryTalk View ME: read, edit and Studio entries plus the display
+    # preview. The old plugin is retired, so these mount by default.
+    - id: ftview-read
+      name: '@aryacode/dsh-engineering/ftview'
+    - id: ftview-read-skill
+      name: '@aryacode/dsh-engineering/ftview/skill'
+    - id: ftview-edit
+      name: '@aryacode/dsh-engineering/ftview/edit'
+    - id: ftview-studio
+      name: '@aryacode/dsh-engineering/ftview/studio'
+    - id: ftview-viewer
+      name: '@aryacode/dsh-engineering/ftview-viewer'
+    # MotionWorks IEC: the redesigned rows. Editing is off by default, like L5X.
+    - id: mwi-session
+      name: '@aryacode/dsh-engineering/mwi'
+    - id: mwi-read
+      name: '@aryacode/dsh-engineering/mwi/read'
+    - id: mwi-read-skill
+      name: '@aryacode/dsh-engineering/mwi/skill'
+    - id: mwi-verify
+      name: '@aryacode/dsh-engineering/mwi/verify'
+    - id: mwi-edit
+      name: '@aryacode/dsh-engineering/mwi/edit'
+      disabled: true
+    # FactoryTalk Optix stays a separate package, mounted as a component row.
+    - id: optix
+      name: '@deepseek-ai/dsh-tool-ft-optix'

package/locale/en.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "Engineering",
+    "description": "Automation-engineering plugins for Studio 5000, FactoryTalk View, FactoryTalk Optix, MotionWorks IEC and CAD drawings."
+  }
+}

package/locale/zh.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "工程",
+    "description": "面向 Studio 5000、FactoryTalk View、FactoryTalk Optix、MotionWorks IEC 与 CAD 图纸的自动化工程插件。"
+  }
+}

package/package.json

@@ -1,6 +1,80 @@
 {
   "name": "@aryacode/dsh-engineering",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
+  "version": "0.3.0",
+  "description": "AryaCode engineering bundle: one install surface and one tool-exposure policy for the Studio 5000 L5X, FactoryTalk View and MotionWorks IEC plugins, with skill links for Optix and CAD.",
+  "keywords": [
+    "dsh",
+    "deepseek-harness",
+    "cordis",
+    "plugin",
+    "bundle",
+    "engineering",
+    "automation",
+    "plc",
+    "studio-5000",
+    "factorytalk",
+    "motionworks"
+  ],
+  "license": "MIT",
+  "type": "module",
+  "engines": {
+    "node": "^22.19.0 || >=24.0.0"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/KonnectSuite/dsh-engineering.git"
+  },
+  "homepage": "https://github.com/KonnectSuite/dsh-engineering#readme",
+  "bugs": {
+    "url": "https://github.com/KonnectSuite/dsh-engineering/issues"
+  },
+  "files": [
+    "cordis.patch.yml",
+    "locale/*.json",
+    "vendor/**/*",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE"
+  ],
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    }
+  },
+  "dependencies": {
+    "@deepseek-ai/dsh-tool-ft-optix": "https://github.com/KonnectSuite/KonnectSuite.github.io/releases/download/plugins-v0.3.0/deepseek-ai-dsh-tool-ft-optix-0.2.1-rc.3.tgz",
+    "@aryacode/dsh-engineering-l5x-viewer": "0.1.2",
+    "@aryacode/dsh-engineering-ftview-viewer": "0.1.2"
+  },
+  "peerDependencies": {
+    "@deepseek-ai/cordis": "~4.0.4",
+    "@deepseek-ai/dsh-tool-skill": "^0.2.0-rc.2"
+  },
+  "devDependencies": {
+    "js-yaml": "^4.1.0",
+    "tsx": "^4.23.15"
+  },
+  "exports": {
+    ".": "./cordis.patch.yml",
+    "./l5x": "./vendor/l5x/lib/index.js",
+    "./l5x/skill": "./vendor/l5x/lib/skill.js",
+    "./l5x/editing": "./vendor/l5x/lib/editing.js",
+    "./l5x/live": "./vendor/l5x/lib/live.js",
+    "./l5x/studio": "./vendor/l5x/lib/studio.js",
+    "./ftview": "./vendor/ftview/lib/index.js",
+    "./ftview/skill": "./vendor/ftview/lib/skill.js",
+    "./ftview/edit": "./vendor/ftview/lib/edit.js",
+    "./ftview/studio": "./vendor/ftview/lib/studio.js",
+    "./mwi": "./vendor/mwi/lib/index.js",
+    "./mwi/read": "./vendor/mwi/lib/read.js",
+    "./mwi/skill": "./vendor/mwi/lib/skill.js",
+    "./mwi/verify": "./vendor/mwi/lib/verify.js",
+    "./mwi/edit": "./vendor/mwi/lib/edit.js"
+  },
+  "scripts": {
+    "test": "node --import tsx --test test/patch.spec.mjs test/docs.spec.mjs test/tool-reference.spec.mjs test/manifests.spec.mjs",
+    "docs:tools": "tsx scripts/gen-tool-reference.ts",
+    "docs:check": "tsx scripts/gen-tool-reference.ts --check",
+    "assemble": "node scripts/assemble.mjs"
+  }
 }

package/vendor/ftview/README.md

@@ -0,0 +1,55 @@
+# dsh-engineering-ftview
+
+FactoryTalk View ME tools for the `dsh-engineering` bundle. Three loader entries share one package:
+
+| Entry | Tools | Purpose |
+|---|---|---|
+| `dsh-engineering-ftview` | 6 read tools | Open an export folder, list and read displays and HMI tags, search, check, compare |
+| `dsh-engineering-ftview/edit` | 5 tools | Stage display and tag changes, validate, apply to a new folder |
+| `dsh-engineering-ftview/studio` | 3 tools | Discover Studio, preflight changed files, plan the manual import |
+
+The `factorytalk-view` guidance ships as the separate `dsh-engineering-ftview/skill` entry.
+
+## Read surface
+
+`ftview_open` scans one export folder and returns a `view_id`. `ftview_list` pages displays or tags,
+`ftview_get` reads one display (named objects) or one tag row, `ftview_find` searches names and text,
+`ftview_check` reports tag CSV integrity, duplicate names and unparsed files, and `ftview_compare`
+diffs two exports by display name, tag name and file hash.
+
+This is a TypeScript redesign, not a port of the old Python plugin: no `engine.py`, no `lxml`, no
+`ftview_project_start`/`environment`/`stage_register` tools.
+
+## Editing
+
+`ftview_draft_display_set`, `ftview_draft_display_add` and `ftview_draft_tag_upsert` stage one change
+per call; `ftview_validate` applies the staged edits to a re-parsed copy and reports changed files;
+`ftview_apply` writes a new export folder, leaving the source untouched.
+
+## Studio
+
+`ftview_studio_status` discovers installed FactoryTalk View ME tooling and schemas.
+`ftview_studio_preflight` checks changed files for import problems, including Studio name
+restrictions. `ftview_studio_handoff` returns the ordered manual import plan. No vendor utility runs.
+
+## Configuration
+
+| Entry | Option | Default |
+|---|---|---|
+| read | `maxFiles` | 2000 |
+| edit | `maxDraftOperations` | 100 |
+| studio | `searchRoots` | the two Rockwell Programs folders |
+
+## Boundary
+
+The surface parses documented text exports (display XML and the HMI tag CSV). It does not decode MER
+or MED, contact a terminal, validate against vendor XSD, bind tags to a PLC, or drive Studio.
+FactoryTalk View SE and FactoryTalk Optix are different products and are not analyzed here.
+
+## Develop
+
+```sh
+pnpm install
+pnpm run build
+pnpm test
+```