deploy.

App/wwwroot/HiAPI-docsite/manual/run/a-mission-that-resumes.html

@@ -90,8 +90,11 @@
 <p>A mission written as one Script runs, and tells you nothing. The same run written as commands reads
 as values, switches a row at a time, and — with two Record Meshed Geometry entries around the
 program — restarts from where the last run got to instead of from the stock.</p>
-<p>This page is the layout that gets you all three. It is a recommendation, not a rule: every command
-is placeable anywhere, and <a href="building-a-mission.html">Building a Mission</a> is the mechanics.</p>
+<p>This page is the layout that gets you all three. <strong>Treat it as the shape a project starts from, not
+as an optimisation to add later</strong> — the two records in particular are part of the layout, and a
+mission built without them replays from the stock every single time. Placement itself is not
+enforced: every command goes anywhere, and <a href="building-a-mission.html">Building a Mission</a> is the
+mechanics.</p>
 <h2 id="the-shape">The shape</h2>
 <table>
 <thead>