deploy webservice static-file routing for docsite folder URLs, per-instance step-cache db, and constant-height panel title bars.

App/wwwroot/HiAPI-docsite/manual/runtime/step-fields.html

@@ -101,7 +101,7 @@
 </ul>
 <h2 id="time-and-motion">Time and Motion</h2>
 <ul>
-<li>AccumulatedTime: Accumulated simulation time.</li>
+<li>EndTimecode: Simulated end-of-step timecode (formerly <code>AccumulatedTime</code>; step CSVs written with the legacy header are still read).</li>
 <li>StepDuration: Duration of this step (default per-revolution mode: one step equals one spindle revolution).</li>
 <li>BeginSpindleAngle_deg: Spindle angular displacement at the start of this step.</li>
 <li>Cl (Cutter Location): Cutter location point (including IJK normal).</li>
@@ -115,7 +115,11 @@
 <li>IsTouched: Whether cutting engagement occurred.</li>
 <li>CuttingWidth_mm (ae) / CuttingDepth_mm (ap): Cutting width / cutting depth.</li>
 <li>Mrr_mm3ds: Material removal rate.</li>
-<li>ProgramSideCusp_um, SideCuspList_um: Side cusp height and distribution estimated from program feed and radius.</li>
+<li>ProgramSideCusp_um, SideCuspList_um: Side cusp height and distribution estimated from program feed and radius.
+<blockquote>
+<p><strong>Reading tip — a <code>ProgramSideCusp_um</code> spike usually flags a rapid-move (G00) collision, not a finish result.</strong> The program-side cusp is computed from the <em>ideal program feedrate</em> while the cutter is engaged with the workpiece. A rapid traverse is not meant to touch material; when it does, the cusp formula is fed the (very high) rapid feedrate, so the value spikes far above any real cutting cusp. Treat an isolated cusp peak at a rapid/G00 line as a likely gouge/collision to investigate. The same engagement-during-rapid usually shows up alongside it as spikes in the availability ratios (yielding-stress / spindle-torque / spindle-power).</p>
+</blockquote>
+</li>
 </ul>
 <h2 id="chip">Chip</h2>
 <ul>
@@ -138,7 +142,11 @@
 <li>MaxSpindlePowerRatio (maximum spindle power ratio): Input power / instantaneous maximum power based on spindle capability.</li>
 <li>ContinueSpindlePowerRatio (continuous spindle power ratio): Input power / unlimited-duration maximum power based on spindle capability.</li>
 <li>AccumulatedSpindleEnergyConsumption_kWh: Accumulated spindle energy consumption.</li>
-<li>Max/Continue Spindle Torque Ratio: Instantaneous/continuous spindle torque ratios.</li>
+<li>Max/Continue Spindle Torque Ratio: Instantaneous/continuous spindle torque ratios.
+<blockquote>
+<p><strong>Reading tip — a power / torque ratio over 100% means the spindle cannot supply the demanded load at the commanded rpm</strong>, so it droops: with feed held, rpm drops, feed-per-tooth rises, and forces climb further — a runaway loop that, left unchecked, grows the chip until the cutter breaks and the spindle/drive is overstressed and damaged — load damage, not a tool-vs-workpiece collision (see <a href="../analysis/nc-optimization-principles.html">NC optimization</a>). Read it by <em>duration</em>, not just height: a one-revolution (single-cycle) overshoot usually still completes the pass — it just leaves a slightly insufficient cut there — whereas a ratio that stays above 100% across many consecutive spindle revolutions is a genuine overload to fix. A high-load step typically also shows large cutter–workpiece engagement (CWE), large tip deflection, and more vibration/noise. Because the ratio is normalized by the spindle-capability curve, a placeholder/guessed spindle skews it — confirm against the real spindle's speed–power/torque curve before calling it overloaded.</p>
+</blockquote>
+</li>
 </ul>
 <h2 id="thermal-and-temperature">Thermal and Temperature</h2>
 <ul>