deploy: 39c3f7b25c

ota_protocol/index.html

@@ -4343,6 +4343,11 @@ fetches a <code>.mota</code> off the mesh and streams it onto the host as <code>
 against firmware you don't have. Resume is bookkeeping-free: <code>BEGIN</code> 0xFF-fills the file and, on reconnect
 after a link drop (the fetch PAUSES, holding progress on the host - no RAM/flash fallback), <code>STAT</code>+<code>SREAD</code>
 let the fetcher recompute and refill only the missing blocks.
+TCP disconnect preserves the selected MID, target, and destination across dynamic-context idle cleanup.
+Metadata initialization or seed leaf-diff restarts from the manifest on reconnect; an initialized transfer
+reopens and rehashes the same MID before requesting missing blocks. Host I/O failure during final verification
+or publication pauses too; a genuine Merkle mismatch remains a failed transfer. Explicit cancel/detach still
+releases the session, and a different host transport cannot take over a paused capture without cancellation.
 The phone-oriented BLE link is deliberately source-only and does not register
 a folder destination.</p>
 <h3 id="101-the-motasource-abstraction-otasourceh">10.1 The <code>MotaSource</code> abstraction (<code>OtaSource.h</code>)</h3>

ota_user_guide/index.html

@@ -3440,7 +3440,10 @@ response. Mesh repeaters carry the packets only while their temporary-radio wind
 Check progress with <code>ota status</code>.</p>
 <p>If a <code>folder</code> pull loses its link mid-transfer, <code>ota status</code> shows <strong>paused</strong> - the host keeps the
 partial and the pull resumes (filling only what's missing) the moment you reconnect motatool; it never
-falls back to flash. To <strong>stop</strong> a download you no longer want:</p>
+falls back to flash. A TCP disconnect preserves the selected image even if it happens before its manifest
+arrives or during the final save. Reconnect through the same transport; an interrupted manifest or seed
+comparison restarts initialization, while a partial transfer rechecks its stored blocks. The paused capture
+keeps its OTA workspace until reconnection or cancellation. To <strong>stop</strong> a download you no longer want:</p>
 <pre><code>ota cancel
 </code></pre>
 <p>For a download staged on the node, success means current firmware also