Update site from docs source repo

Author: Exploding Labs Bot

superstack/migrations/index.html

@@ -612,11 +612,19 @@ <h2 id="applying-migrations">▶️ Applying Migrations</h2>
 <p>To apply your migrations, run:</p>
 <div class="highlight"><pre><span></span><code>bin/postgres<span class="w"> </span>migrate
 </code></pre></div>
+<p>This command will:
+Apply new migrations – runs any migration files (in filename order) that haven’t been applied yet.
+Record applied migrations – logs each successfully applied migration in a .applied_migrations file so it won’t run again.
+Persist migration history with your database – the .applied_migrations file lives inside the postgres_data Docker volume alongside the database files.
+If the postgres_data volume is deleted or recreated, both the database and the migration history are reset, so migrations will run again from scratch.</p>
 <p>This will:</p>
 <ol>
-<li>Run any migration files that haven’t been applied yet (in filename order)</li>
-<li>Record each successfully applied file in <code>.applied_migrations</code> (this
-   file lives in the postgres data volume)</li>
+<li><strong>Apply new migrations,</strong> in filename order.</li>
+<li><strong>Record applied migrations</strong> in a file named <code>.applied_migrations</code>. This
+   plain-text file keeps a record of successfully applied migrations so they
+   aren't applied again next time. It lives in the same volume as the database
+   files, so when that volume is removed or recreated, the
+   <code>.applied_migrations</code> file goes with it and you start over.</li>
 </ol>
 <p>Already-applied scripts are skipped on subsequent runs.</p>
 <blockquote>
@@ -639,9 +647,9 @@ <h2 id="applying-migrations">▶️ Applying Migrations</h2>
 <span class="k">commit</span><span class="p">;</span>
 </code></pre></div>
 <h2 id="transactions">🔁 Transactions</h2>
-<p>Use <code>begin;</code> and <code>commit;</code> to wrap statements in a transaction. This
-ensures that all changes are applied atomically. Any statements outside of
-transactions will be auto-committed.</p>
+<p>Use <code>begin;</code> and <code>commit;</code> to wrap statements in a transaction. This ensures
+that all changes are applied atomically. Any statements outside of transactions
+will be auto-committed.</p>
 <p>Avoid wrapping non-transactional operations in a transaction — these will
 cause errors if used inside <code>begin ... commit</code>. Examples of
 non-transactional statements include:</p>