@aryacode/dsh-engineering 0.4.7 → 0.4.21

package/vendor/mwi/SKILL.md

@@ -1,16 +1,32 @@
 ---
 name: motionworks-iec
-description: Operate a running Yaskawa MotionWorks IEC 3 Pro IDE through staged projects — find and stage a workspace project, read the live object model and POU code, edit declarations and code, compile, read diagnostics, and verify a staged change.
-whenToUse: The user has MotionWorks IEC 3 Pro open or asks for work in it — a build or compile verdict, the live project model, reading or changing POU code, variable declarations, tasks, or the IDE error list. Also use when a MotionWorks project is mentioned: find which project is in the workspace before answering. For a question about a project outside the workspace, say it cannot be staged.
+description: Operate a running Yaskawa MotionWorks IEC 3 Pro IDE on the real project files — find and open a workspace project (one verified backup first), read the live object model and POU code, edit declarations and code, compile, read diagnostics, and verify the change.
+whenToUse: The user has MotionWorks IEC 3 Pro open or asks for work in it — a build or compile verdict, the live project model, reading or changing POU code, variable declarations, tasks, or the IDE error list. Also use when a MotionWorks project is mentioned: find which project is in the workspace before answering. For a question about a project outside the workspace, say it cannot be opened.
 ---
 
 # MotionWorks IEC workspace editing
 
 ## Boundary
 
-This surface works on a **staged copy** of a workspace project. `mw_project_stage` copies the project
-into this plugin's staging area; `mw_project_open` opens that copy. A real project tree is never opened
-for editing, and nothing here downloads to a controller or commands motion.
+This surface edits the **real workspace project**. `mw_project_open` takes one complete, hash-verified
+backup under `<workspace>/backups/motionworks/` before the IDE opens the project, and reuses that
+backup for later attaches. A project the IDE already has open is attached — the backup is written and
+the project is **not** reloaded, so unsaved editor changes survive. `mw_project_stage` remains
+available as an optional sandbox when you want the IDE to open a copy instead. Nothing here downloads
+to a controller or commands motion.
+
+Every engineering product backs up into the same tree, so a backup means one place whichever surface
+you are in:
+
+```
+<workspace>/backups/<product>/<subject>/<UTC stamp>/
+    backup-manifest.json      every copied file: relative path + SHA-256
+    <the copy>
+```
+
+MotionWorks is the `motionworks` product and the copy holds the project's `.mwt` beside its expanded
+folder. The open already takes it; do not take a second one. `<workspace>/_backups` and
+`<workspace>/backups/<project>/…` are older layouts: never write there, and leave what is there alone.
 
 The native IDE API is the editing path. Desktop input belongs to the computer-use companion and is a
 fallback for operations without a native call, never a substitute for a refused native one.
@@ -20,22 +36,23 @@ present, the MotionWorks rows are not enabled on this host, or the host is not W
 
 ## Start
 
-1. `mw_project_find` lists workspace projects and their staged copies. Nothing else identifies the
-   project you may touch.
-2. `mw_project_stage` copies the intended project and verifies the copy.
-3. `mw_project_open` opens the staged copy. A wrapper that points at the wrong directory is refused;
-   repair it with consent, never by editing files by hand.
-4. `mw_ide_status` reports the project identity, active view, modal dialogs and compile state. Read it
+1. `mw_project_find` lists workspace projects, any staged copy and any existing pre-edit backup.
+   Nothing else identifies the project you may touch.
+2. `mw_project_open` opens the workspace `.mwt` directly. It first writes and verifies the backup, so
+   the edit can always be rolled back. When the IDE already has that exact project open, it records
+   the verified backup and reports `already_open` instead of reloading the files.
+3. `mw_ide_status` reports the project identity, active view, modal dialogs and compile state. Read it
    before and after operations that change the IDE.
 
-Never skip staging to edit the workspace copy directly.
+Use `mw_project_stage` only when the user asks for a sandbox; normal work edits the workspace project.
+A wrapper that points at the wrong directory is refused; repair it with consent, never by hand.
 
 ## Read
 
 - `mw_project_overview` — languages, counts, tasks, warnings and coverage.
 - `mw_list` — POUs, variables, globals, types, tasks, libraries or blocks, filtered and paged.
 - `mw_get` — one POU body with its declarations, one type, task, block interface or I/O map.
-- `mw_search` — literal text across staged POU code.
+- `mw_search` — literal text across the open project's POU code.
 - `mw_references` — where one symbol is read or written across POUs.
 - `mw_review` — scope and type checks, integer bounds, unsupported constructs, graphical listing.
 - `mw_help` — installed help and reviewed references; the index sync is explicit.
@@ -55,16 +72,18 @@ A compile verdict is the vendor engine's. It does not prove runtime behavior or
 
 Only with the edit row enabled. One operation per call:
 
-- `mw_edit_code` replaces one ST or IL body, guarded by an expected body hash.
+- `mw_edit_code` replaces one ST or IL body, guarded by the body it is about to patch. Pass
+  `text_body_sha256` from `mw_get` when you have it; otherwise the tool hashes the current saved
+  body itself before applying the exact find/replace.
 - `mw_edit_variables` adds, edits, deletes or groups one declaration through the native API.
 - `mw_edit_structure` creates, copies, renames, deletes, converts or task-assigns a POU.
 - `mw_insert_block` inserts one FB instance and its bound ST call.
 - `mw_transfer_pou` exports and imports one POU package.
-- `mw_validate` prepares the staged edits and reports findings. Read them before applying.
-- `mw_apply` writes through the IDE, saves, and syncs back only with explicit consent.
+- `mw_validate` prepares the edits and reports findings. Read them before applying.
+- `mw_apply` saves the open project through the IDE, in place. The pre-edit backup is the rollback point.
 
-Never apply a change whose expected hash no longer matches. If the source changed, re-read it and
-stage the edit again.
+Never apply a change whose expected hash no longer matches. If the source changed, re-read the body
+and retry the edit with the new hash.
 
 ## Reporting
 
@@ -81,7 +100,7 @@ completeness.
 
 Read the fix instead of retrying blindly:
 
-- wrong open project or stale wrapper — stage and open again;
+- wrong open project or stale wrapper — open the right project again;
 - modal dialog or minimized IDE — inspect `mw_ide_status`, resolve it deliberately, then retry;
 - a missing row — say the surface is not enabled here;
-- a changed hash — re-read and re-stage.
+- a changed hash — re-read the body and retry.