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.Segmenters.html

@@ -98,6 +98,26 @@ Classes
       <dt><a class="xref" href="Hi.NcParsers.Segmenters.HeidenhainSegmenter.html">HeidenhainSegmenter</a></dt>
       <dd><p>Heidenhain NC block builder.
 Also support single line NC block.</p>
+<p>
+Two grouping rules produce multi-line <a class="xref" href="Hi.NcParsers.Sentence.html">Sentence</a>s:
+<ul><li><b>Trailing <code>~</code> continuation</b> (modern TNC cycle
+definitions): a line whose last visible character is <code>~</code>
+continues on the next physical line; the chain ends at the first
+line without a trailing <code>~</code>. Both corpus spellings are
+accepted — <code>"… ;STRATEGIE ~"</code> (space before, after a trailing
+comment) and <code>"DATUM SETTING~"</code> (glued). Continuation lines
+carry no klartext block number. Configurable via
+<a class="xref" href="Hi.NcParsers.Segmenters.HeidenhainSegmenter.html#Hi_NcParsers_Segmenters_HeidenhainSegmenter_JoinTildeContinuations">JoinTildeContinuations</a> (default on — files using
+<code>~</code> are simply mis-simulated without it, so legacy XML without
+the attribute also gets the join).</li><li><b>Repeated command head</b> (<span class="xref">Hi.NcParsers.Segmenters.HeidenhainSegmenter.BlockKeywordList</span>,
+default <code>CYCL DEF</code>): consecutive lines sharing the same
+<code>CYCL DEF n</code> head group into one sentence
+(<code>7.0/7.1/…</code> style).</li></ul>
+The <code>~</code> characters stay in the raw <a class="xref" href="Hi.NcParsers.Sentence.html#Hi_NcParsers_Sentence_BlockText">BlockText</a>
+(write-back authority); the Parsing bundle strips them from
+<code>UnparsedText</code> via
+<a class="xref" href="Hi.NcParsers.ParsingSyntaxs.Heidenhain.HeidenhainTildeTrimSyntax.html">HeidenhainTildeTrimSyntax</a>.
+
 </dd>
     </dl>
     <dl class="jumplist">