update XML IO pattern.

App/wwwroot/HiAPI-docsite/api/Hi.NcParsers.Keywords.MacroFrame.html

@@ -6,7 +6,7 @@
       <meta name="viewport" content="width=device-width, initial-scale=1.0">
       <meta name="title" content="Class MacroFrame | HiAPI-C# 2025 ">
       
-      <meta name="description" content="Top-level integer marker stamped onto a SyntaxPiece&#39;s JSON to identify which call frame the block belongs to. Brand-agnostic by design — written by  today, reusable by any future call-inlining syntax (Fanuc G66 modal expansion, Heidenhain LBL CALL, …) that needs local-variable isolation across call boundaries.  Semantics: the value is an opaque id; only equality matters. Two blocks with the same  id share a call frame (locals visible across them via single-step carry); two blocks with different ids do not. The id 0 is reserved for the main program frame and is returned by  when the field is absent — so a plain caller block needs no stamp and yet compares distinct from any inlined frame.   Stored as a top-level JSON int (not an object section) so it stays lightweight on every inlined block. Decoupled from : that section is a diagnostic record of the call (what file, what args), while MacroFrame is the purely functional marker the local-variable I/O syntaxes consult.">
+      <meta name="description" content="Top-level integer marker stamped onto a &#39;s JSON to identify which call frame the block belongs to. Brand-agnostic by design — written by  today, reusable by any future call-inlining syntax (Fanuc G66 modal expansion, Heidenhain LBL CALL, …) that needs local-variable isolation across call boundaries.  Semantics: the value is an opaque id; only equality matters. Two blocks with the same  id share a call frame (locals visible across them via single-step carry); two blocks with different ids do not. The id 0 is reserved for the main program frame and is returned by  when the field is absent — so a plain caller block needs no stamp and yet compares distinct from any inlined frame.   Stored as a top-level JSON int (not an object section) so it stays lightweight on every inlined block. Decoupled from : that section is a diagnostic record of the call (what file, what args), while MacroFrame is the purely functional marker the local-variable I/O syntaxes consult.">
       <link rel="icon" href="../img/HiAPI.favicon.ico">
       <link rel="stylesheet" href="../public/docfx.min.css">
       <link rel="stylesheet" href="../public/main.css">
@@ -97,7 +97,7 @@ Class MacroFrame
   <dl><dt>Assembly</dt><dd>HiMech.dll</dd></dl>
   </div>
 
-  <div class="markdown summary"><p>Top-level integer marker stamped onto a SyntaxPiece's JSON
+  <div class="markdown summary"><p>Top-level integer marker stamped onto a <a class="xref" href="Hi.NcParsers.Syntaxs.SyntaxPiece.html">SyntaxPiece</a>'s JSON
 to identify which call frame the block belongs to. Brand-agnostic by
 design — written by <a class="xref" href="Hi.NcParsers.EvaluationSyntaxs.Fanuc.FanucMacroCallSyntax.html">FanucMacroCallSyntax</a>
 today, reusable by any future call-inlining syntax (Fanuc <code>G66</code>