deploy.

App/EngineMessages/engine-messages.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 1,
-  "engineVersion": "3.2.28.0",
-  "filesParsed": 1280,
-  "siteCount": 365,
+  "engineVersion": "3.2.29.0",
+  "filesParsed": 1282,
+  "siteCount": 366,
   "sites": [
     {
       "id": "AddTimeDataByFile--Start",
@@ -1099,6 +1099,11 @@
       "template": "Physics is enabled and {0} steps touched the workpiece, but no touched step produced a physics result. Check that a tool is bound to the spindle, that the spindle rotates through the cuts (M03/M04), and that the workpiece cutting parameter is loaded. Force results are empty for the whole play; if the engagements were not built either (no tool, or spindle never rotating), milling-parameter training will skip every touched step.",
       "file": "HiMech/MachiningProcs/MachiningSession.cs"
     },
+    {
+      "id": "Play-RapidCut--Detected",
+      "template": "Rapid traverse at line {0} (from step {1}) removed {2} mm³ of stock over {3} steps, cutting depth up to {4} mm. On a real machine a rapid move through material breaks the tool or crashes the machine: check the approach clearance, the work offset, the tool length offset and the stock size. Set RapidCutVolumeThreshold_mm3 on the project to ignore grazing contact.",
+      "file": "HiMech/MachiningProcs/RapidCutMonitor.cs"
+    },
     {
       "id": "Play-YieldingStress--None",
       "template": "Tool {0}: physics produced results but the yielding stress ratio could not be evaluated on any touched step (NaN). Check that the cutter is a milling cutter with a flute material, and that its beam geometry has sections outside the tip zone (a section counts only where its height above the tip exceeds its radius). The NcOpt yielding constraint is off for these tools.",