deploy.

2026-09-15 01:12:50 +08:00
parent 2db889ad89
commit 1a75503105
99 changed files with 4168 additions and 726 deletions
@@ -152,10 +152,12 @@ the file is read again on the service, but the screens keep what they were showi
 entry to use for that, and it is the one that always rebuilds.</p>
 <p>The same rebuild runs once at startup, with nobody having done anything: a browser reaching a service
 that already has a project open receives that path as its first project change and builds on it.</p>
-<p><strong>New</strong>, <strong>Load</strong>, <strong>ReLoad</strong>, <strong>Save</strong> and <strong>Save As</strong> run one at a time. A second one started while
-the first is still running is refused rather than queued, and the refusal arrives as a warning reading
-<strong>Another project operation is in progress. Please try again.</strong> Nothing is rebuilt and nothing is
-lost. <strong>Close Project</strong> takes no part in that turn-taking and never raises the warning.</p>
+<p><strong>New</strong>, <strong>Load</strong>, <strong>ReLoad</strong>, <strong>Save</strong>, <strong>Save As</strong> and <strong>Close Project</strong> run one at a time. A
+second one started while the first is still running is refused rather than queued, and the refusal
+arrives as a warning reading <strong>Another project operation is in progress. Please try again.</strong> Nothing
+is rebuilt and nothing is lost. The turn is held for the whole of the operation, so a Close asked for
+while a Load is still reading is refused the same way, and so is a Load asked for while a Close is
+still tearing the project down.</p>
 <h2 id="the-footer">The footer</h2>
 <p>A 29-pixel strip holding three regions, each independent of the other two.</p>
 <p><strong>Left — the latest reported line, with the recent ones behind it.</strong> The text is the most recent