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.Numerical.Args.html

@@ -91,6 +91,33 @@
   <div class="markdown level0 conceptual"></div>
   <div class="markdown level0 remarks"></div>
 
+    <h3 id="classes">
+Classes
+</h3>
+    <dl class="jumplist">
+      <dt><a class="xref" href="Hi.Numerical.Args.PolarPairDef.html">PolarPairDef</a></dt>
+      <dd><p>Axis mapping of a Polar Coordinate Interpolation pair
+(<a class="xref" href="Hi.Numerical.Args.PolarModeDirEnum.html">PolarModeDirEnum</a>): which program/machine axes carry the
+radius, the plane depth, and the rotation.</p>
+<p>
+The polar math itself runs in "triple space" — the Rxcz vector
+(linear/radius, hypothetical, depth) with the plane normal fixed at the
+third component — and is pair-independent; this definition maps the
+triple's ends onto real axes: NC words on the way in, machine
+coordinates on the way out. The plane normal equals the rotary's
+rotation axis (C about Z, A about X, B about Y), so
+<a class="xref" href="Hi.Numerical.Args.PolarPairDef.html#Hi_Numerical_Args_PolarPairDef_NormalIndex">NormalIndex</a> doubles as the ABC component of the angle.
+</p>
+<p>
+The lathe diameter-programming convention (the radius word arrives
+doubled) applies to the X axis only, i.e. the XC pair — mirroring
+HardNc <code>PolarEntry</code>, which halves X unconditionally. HardNc's own
+YA/ZB slots are dead code (never selected); its
+<code>ProgramOrthogonalPlaneNormal</code> table carried swapped normals for
+them, corrected alongside this implementation.
+</p>
+</dd>
+    </dl>
     <h3 id="enums">
 Enums
 </h3>