deploy.

App/wwwroot/HiAPI-docsite/manual/basics/messages-and-logs.html

@@ -152,8 +152,11 @@ last showed stays on the bar after the run has ended; a project change is what e
 takes the strip away with it. A cursor line carries <code>Sn</code> and the sentence index it sits on; a
 message line carries whatever anchor the message supplies. Two limits are worth knowing: the strip
 mirrors the newest message across three of the four lists — nothing from <strong>NC Manipulation</strong> reaches
-it — and it is sampled rather than recorded, so messages arriving faster than it refreshes never
-appear on it at all. The lists on the service drop nothing.</p>
+it — and it is sampled rather than recorded. There is no refresh interval to tune: the service
+sends the newest message and, while that send is still on its way to the browsers, keeps only the
+newest of whatever arrives behind it, so a message that lands inside that window is replaced before
+it was ever sent and never appears on the strip at all. The cursor line is thinned the same way
+under a fast run. The lists on the service drop nothing.</p>
 <h2 id="the-session-message-panel">The session message panel</h2>
 <p>The panel sits on the Execution page, in the middle column, below the 3D Rendering Canvas. Its
 header row reads <strong>Session Messages</strong> and stays visible when the panel is collapsed, so a grey strip
@@ -205,9 +208,9 @@ behind its one line carries a chevron; clicking it opens what the message brough
 a <strong>Reset</strong>. The badge at the right of that toolbar reads two numbers separated by a slash, and they
 count different things — rows currently shown on the left, raw messages on the right, so folding
 alone makes them differ, and on a long session the left number stops at the most recent thousand
-while the right goes on counting. That badge is also the tab's connection indicator: it is outlined
-green only while the connection behind that list is up, and its tooltip names the state. <strong>Export</strong>
-writes the tab's filtered rows to a CSV file.</p>
+rows while the right goes on counting. That badge is also the tab's connection indicator: it is
+outlined green only while the connection behind that list is up, and its tooltip names the state.
+<strong>Export</strong> writes the tab's filtered rows to a CSV file.</p>
 <div class="IMPORTANT">
 <h5>Important</h5>
 <p>Two different controls on this screen answer to <strong>Reset</strong>, and only one of them is labelled with
@@ -249,7 +252,9 @@ file for today.</em>, and both hide the line count entirely — no count is draw
 reading zero, so the caption simply being absent is itself the signal that nothing came back. The
 day badge is what separates them: when the file exists, the day comes from the service's own clock;
 when there is no file at all, it comes from the browser's clock in UTC, which need not name the same
-day.</p>
+day — before eight in the morning in Taipei it names the day before. The service itself never
+leaves the file empty: the day's file comes into being with its first line already in it, so an
+empty file is one that something outside the service emptied.</p>
 <p>A fetch that fails replaces the pane with the reason and a <strong>Retry</strong> button, and posts the reason to
 the footer under the viewer's own name — one of the few lines that reaches the footer without ever
 having been a toast.</p>