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

@@ -6,7 +6,7 @@
       <meta name="viewport" content="width=device-width, initial-scale=1.0">
       <meta name="title" content="Class HeidenhainSegmenter | HiAPI-C# 2025 ">
       
-      <meta name="description" content="Heidenhain NC block builder. Also support single line NC block.">
+      <meta name="description" content="Heidenhain NC block builder. Also support single line NC block.  Two grouping rules produce multi-line s: Trailing ~ continuation (modern TNC cycle definitions): a line whose last visible character is ~ continues on the next physical line; the chain ends at the first line without a trailing ~. Both corpus spellings are accepted — &quot;… ;STRATEGIE ~&quot; (space before, after a trailing comment) and &quot;DATUM SETTING~&quot; (glued). Continuation lines carry no klartext block number. Configurable via  (default on — files using ~ are simply mis-simulated without it, so legacy XML without the attribute also gets the join).Repeated command head (, default CYCL DEF): consecutive lines sharing the same CYCL DEF n head group into one sentence (7.0/7.1/… style). The ~ characters stay in the raw  (write-back authority); the Parsing bundle strips them from UnparsedText via .">
       <link rel="icon" href="../img/HiAPI.favicon.ico">
       <link rel="stylesheet" href="../public/docfx.min.css">
       <link rel="stylesheet" href="../public/main.css">
@@ -99,6 +99,26 @@ Class HeidenhainSegmenter
 
   <div class="markdown summary"><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>.
+
 </div>
   <div class="markdown conceptual"></div>
 
@@ -217,6 +237,42 @@ Also support single line NC block.</p>
 </h2>
 
 
+  <a id="Hi_NcParsers_Segmenters_HeidenhainSegmenter_JoinTildeContinuations_" data-uid="Hi.NcParsers.Segmenters.HeidenhainSegmenter.JoinTildeContinuations*"></a>
+
+  <h3 id="Hi_NcParsers_Segmenters_HeidenhainSegmenter_JoinTildeContinuations" data-uid="Hi.NcParsers.Segmenters.HeidenhainSegmenter.JoinTildeContinuations">
+  JoinTildeContinuations
+  
+  </h3>
+
+  <div class="markdown level1 summary"><p>Joins lines ending with the TNC <code>~</code> continuation character into
+one sentence. On by default; an XML source without the attribute also
+defaults to on — the join is a capability fix (house.H-style cycle
+definitions are unparsable without it), not a behavioral contract a
+legacy project could depend on.</p>
+</div>
+  <div class="markdown level1 conceptual"></div>
+
+  <div class="codewrapper">
+    <pre><code class="lang-csharp hljs">public bool JoinTildeContinuations { get; set; }</code></pre>
+  </div>
+
+
+
+
+
+  <h4 class="section">Property Value</h4>
+  <dl class="parameters">
+    <dt><a class="xref" href="https://learn.microsoft.com/dotnet/api/system.boolean">bool</a></dt>
+    <dd></dd>
+  </dl>
+
+
+
+
+
+
+
+
   <a id="Hi_NcParsers_Segmenters_HeidenhainSegmenter_Name_" data-uid="Hi.NcParsers.Segmenters.HeidenhainSegmenter.Name*"></a>
 
   <h3 id="Hi_NcParsers_Segmenters_HeidenhainSegmenter_Name" data-uid="Hi.NcParsers.Segmenters.HeidenhainSegmenter.Name">