deploy fixed MRR drift and webservice CylindroidHolder buckle branch update issue.

App/wwwroot/HiAPI-docsite/api/Hi.NcParsers.EvaluationSyntaxs.Fanuc.FanucIfThenSyntax.html

@@ -6,7 +6,7 @@
       <meta name="viewport" content="width=device-width, initial-scale=1.0">
       <meta name="title" content="Class FanucIfThenSyntax | HiAPI-C# 2025 ">
       
-      <meta name="description" content="Resolves Fanuc Custom Macro B IF [&amp;lt;cond&amp;gt;] THEN &amp;lt;body&amp;gt; single-block conditionals. Triggered by Parsing.FanucIfThen (written by ); reads the now-resolved  node, decides whether to fire, and on fire lifts the parsing-stage PendingAssignments sub-object into the canonical Parsing.Assignments bucket so the brand-specific reader syntaxes downstream route each entry to its store the same way they would handle an unconditional #nnn = &amp;lt;literal&amp;gt; on a normal block.  Unlike  there is no source splice, no label scan, no iteration watchdog — the spec restricts the body to the current block. The host block is preserved either way (the stamped FanucIfThen section on the host&#39;s top-level JSON keeps the IF-THEN call site visible to cache dumps and diagnostics, with  flipped true only on a successful fire).   Pipeline placement: in the Evaluation bundle after  (so the Condition expression has been substituted in place by pass-2 tree walk, and each PendingAssignments RHS string has been evaluated to a numeric ) and before the reader syntaxes (, , , ) — that ordering lets the lifted entries reach the readers as if they had been written by  on a normal block.   Three condition outcomes mirror the  shape: Truthy non-zero → lift assignments, stamp Applied=true.Truthy zero → fall through silently, Applied=false.Truthy null (evaluator failed, condition still a string or   non-finite) → warn FanucIfThen--ConditionNotEvaluated, do not   lift, Applied=false. A truthy condition with no PendingAssignments (body did not parse as one or more assignments — e.g. a G-code body, currently unsupported) warns FanucIfThen--UnsupportedBody and falls through.">
+      <meta name="description" content="Resolves Fanuc Custom Macro B IF [&amp;lt;cond&amp;gt;] THEN &amp;lt;body&amp;gt; single-block conditionals. Triggered by Parsing.FanucIfThen (written by ); reads the now-resolved  node, decides whether to fire, and on fire lifts the parsing-stage PendingAssignments sub-object into the canonical Parsing.Assignments bucket so the brand-specific reader syntaxes downstream route each entry to its store the same way they would handle an unconditional #nnn = &amp;lt;literal&amp;gt; on a normal block.  Unlike  there is no source splice, no label scan, no iteration watchdog — the spec restricts the body to the current block. The host block is preserved either way (the stamped FanucIfThen section on the host&#39;s top-level JSON keeps the IF-THEN call site visible to cache dumps and diagnostics, with  flipped true only on a successful fire).   Pipeline placement: in the Evaluation bundle after  (so the Condition expression has been substituted in place by pass-2 tree walk, and each PendingAssignments RHS string has been evaluated to a numeric ) and before the reader syntaxes (, , , ) — that ordering lets the lifted entries reach the readers as if they had been written by  on a normal block.   Three condition outcomes mirror the FanucGotoSyntax.ReadCondition shape: Truthy non-zero → lift assignments, stamp Applied=true.Truthy zero → fall through silently, Applied=false.Truthy null (evaluator failed, condition still a string or   non-finite) → warn FanucIfThen--ConditionNotEvaluated, do not   lift, Applied=false. A truthy condition with no PendingAssignments (body did not parse as one or more assignments — e.g. a G-code body, currently unsupported) warns FanucIfThen--UnsupportedBody and falls through.">
       <link rel="icon" href="../img/HiAPI.favicon.ico">
       <link rel="stylesheet" href="../public/docfx.min.css">
       <link rel="stylesheet" href="../public/main.css">
@@ -130,7 +130,7 @@ the lifted entries reach the readers as if they had been written by
 </p>
 <p>
 Three condition outcomes mirror the
-<a class="xref" href="https://learn.microsoft.com/dotnet/api/system.text.json.nodes.jsonnode">ReadCondition(JsonNode)</a> shape:
+<code>FanucGotoSyntax.ReadCondition</code> shape:
 <ul><li>Truthy non-zero → lift assignments, stamp Applied=true.</li><li>Truthy zero → fall through silently, Applied=false.</li><li>Truthy null (evaluator failed, condition still a string or
   non-finite) → warn <code>FanucIfThen--ConditionNotEvaluated</code>, do not
   lift, Applied=false.</li></ul>