deploy.

App/wwwroot/HiAPI-docsite/api/Hi.MachiningProcs.RapidCutMonitor.html

@@ -6,7 +6,7 @@
       <meta name="viewport" content="width=device-width, initial-scale=1.0">
       <meta name="title" content="Class RapidCutMonitor | HiAPI-C# 2025 ">
       
-      <meta name="description" content="Reports a rapid traverse that removed stock: the steps of one NC line that were commanded as rapid traverse (G00, ) and touched the workpiece fold into one Play-RapidCut&amp;ndash;Detected validation warning, anchored on the line&#39;s first touching step and carrying the line&#39;s total removed volume and its largest cutting depth. A rapid move through material breaks the tool or crashes the machine on a real run, yet with the spindle turning the engine treats it as ordinary cutting: the collision rule (Hi.Machining.MachiningEquipment.Detect) pairs flute and workpiece only while the spindle is stopped, so such a line used to pass with no message at all.  One instance per .  runs on the sequential post-physics stage of every built step (one thread, step order),  closes the last line at the end of a play and  drops a pending line on a session reset; both run on the shell thread after , so no lock is needed.   Folding: consecutive rapid steps with the same  (the NC line number, or the sentence itself where a runner has no line numbers) form one report; a feed step, a different line or the end of the play closes it. A line re-entered later (a subprogram loop) reports again, deliberately. The report is emitted only when the line&#39;s total removed volume reaches  (default 0: any contact). Steps with the spindle stopped are skipped while collision detection is on — that rule owns them and raises Collision--Detected — and counted otherwise.">
+      <meta name="description" content="Reports a rapid traverse that removed stock: the steps of one NC line that were commanded as rapid traverse (G00, ) and touched the workpiece fold into one Play-RapidCut&amp;ndash;Detected validation warning, anchored on the line&#39;s first touching step and carrying the line&#39;s total removed volume and its largest cutting depth. A rapid move through material breaks the tool or crashes the machine on a real run, yet with the spindle turning the engine treats it as ordinary cutting: the collision rule () pairs flute and workpiece only while the spindle is stopped, so such a line used to pass with no message at all.  One instance per .  runs on the sequential post-physics stage of every built step (one thread, step order),  closes the last line at the end of a play and  drops a pending line on a session reset; both run on the shell thread after , so no lock is needed.   Folding: consecutive rapid steps with the same  (the NC line number, or the sentence itself where a runner has no line numbers) form one report; a feed step, a different line or the end of the play closes it. A line re-entered later (a subprogram loop) reports again, deliberately. The report is emitted only when the line&#39;s total removed volume reaches  (default 0: any contact). Steps with the spindle stopped are skipped while collision detection is on — that rule owns them and raises Collision--Detected — and counted otherwise.">
       <link rel="icon" href="../img/HiAPI.favicon.ico">
       <link rel="stylesheet" href="../public/docfx.min.css">
       <link rel="stylesheet" href="../public/main.css">
@@ -105,7 +105,7 @@ the line's first touching step and carrying the line's total removed
 volume and its largest cutting depth. A rapid move through material
 breaks the tool or crashes the machine on a real run, yet with the
 spindle turning the engine treats it as ordinary cutting: the collision
-rule (Hi.Machining.MachiningEquipment.Detect) pairs flute
+rule (<a class="xref" href="Hi.Machining.MachiningEquipmentUtils.MachiningEquipment.html#Hi_Machining_MachiningEquipmentUtils_MachiningEquipment_Detect_System_Boolean_">Detect(bool)</a>) pairs flute
 and workpiece only while the spindle is stopped, so such a line used to
 pass with no message at all.</p>
 <p>