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

App/wwwroot/HiAPI-docsite/api/Hi.Milling.MillingTools.html

@@ -102,6 +102,21 @@ Classes
     <dl class="jumplist">
       <dt><a class="xref" href="Hi.Milling.MillingTools.MillingToolEditorDisplayee.html">MillingToolEditorDisplayee</a></dt>
       <dd><p>Display host for a milling tool composed of a cutter and a holder.</p>
+</dd>
+    </dl>
+    <dl class="jumplist">
+      <dt><a class="xref" href="Hi.Milling.MillingTools.MillingToolPhysicsPack.html">MillingToolPhysicsPack</a></dt>
+      <dd><p>The scalar physics derivations of one tool (and one cutting-parameter set), computed
+once on a sequential boundary and frozen. The per-step force build, the sequential
+physics, and the step/shot writers read these values thousands to millions of times
+per play; the tool and cutter objects themselves expose them as deliberately
+<b>uncached pure computations</b>, so hot session paths read this pack instead —
+callers outside a session simply pass <code>null</code> and the pure computation runs on
+use. Owned per session by <code>MachiningSession</code>, keyed by tool id. A pack is never
+updated in place: the paths that change tool/cutter/para state invalidate the
+session's packs explicitly (run-op start, tool change — see
+<code>MachiningSession.InvalidateToolPhysicsPacks</code>), and <a class="xref" href="Hi.Milling.MillingTools.MillingToolPhysicsPack.html#Hi_Milling_MillingTools_MillingToolPhysicsPack_IsStaleFor_Hi_Machining_IMachiningTool_Hi_MillingForces_Fittings_ICuttingPara_">IsStaleFor(IMachiningTool, ICuttingPara)</a>
+re-keys on object replacement.</p>
 </dd>
     </dl>
     <dl class="jumplist">