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.NcParsers.Dependencys.Syntec.html

@@ -105,6 +105,19 @@ but some parameters differ in unit or interpretation.
 For example, Pr4002 (peck retraction) is stored in <b>microns</b>
 whereas Fanuc #4002 stores in mm.
 </p>
+</dd>
+    </dl>
+    <dl class="jumplist">
+      <dt><a class="xref" href="Hi.NcParsers.Dependencys.Syntec.SyntecParameterTableProxy.html">SyntecParameterTableProxy</a></dt>
+      <dd><p>Get-or-create <a class="xref" href="Hi.NcParsers.Dependencys.INcDependencyProxy.html">INcDependencyProxy</a> for <a class="xref" href="Hi.NcParsers.Dependencys.Syntec.SyntecParameterTable.html">SyntecParameterTable</a>:
+the Syntec sibling of <a class="xref" href="Hi.NcParsers.Dependencys.Fanuc.FanucParameterTableProxy.html">FanucParameterTableProxy</a>. Like Fanuc,
+the Syntec parameter table mixes machine config with per-case work-coordinate
+offsets, so the proxy carries a fixed machine-config <a class="xref" href="Hi.NcParsers.Dependencys.Syntec.SyntecParameterTableProxy.html#Hi_NcParsers_Dependencys_Syntec_SyntecParameterTableProxy_Seed">Seed</a>
+serialized into the shared runner file. On wire, the host receives a deep clone
+of the seed only when it has no <a class="xref" href="Hi.NcParsers.Dependencys.Syntec.SyntecParameterTable.html">SyntecParameterTable</a> yet; a loaded
+project's own full table wins. The proxy does not implement the machine-config
+interfaces — consumers go through
+<a class="xref" href="Hi.NcParsers.SoftNcRunner.html#Hi_NcParsers_SoftNcRunner_GetEffectiveNcDependencyList">GetEffectiveNcDependencyList()</a>.</p>
 </dd>
     </dl>