fix: clarify saved upload completion UI

The previous page showed a static "Server online" pill even though it did not
track backend liveness. It also left the selected file in an uploadable state
after completion, which made it too easy to start the same file again and then
land in a saved record that could only fail with "complete file already
exists".

Remove the misleading server-status UI and make saved uploads describe their
next action. Records with every chunk uploaded now show a Finish action, stale
server records are cleared, and a terminal "complete file already exists"
response clears the saved browser progress instead of inviting another resume.
A successful completion also clears the active file selection so the primary
actions settle back to idle.

Test Plan:
- just check

Refs: none

static/index.html

@@ -15,7 +15,6 @@
             <h1 id="app-title">upl</h1>
             <p class="subtle">Resumable uploads to this machine.</p>
           </div>
-          <span class="status-pill" id="connection-status">Server online</span>
         </div>
 
         <div class="file-picker">
@@ -40,7 +39,7 @@
         </div>
 
         <section class="pending-section" id="pending-section" hidden>
-          <h2>Pending uploads</h2>
+          <h2>Saved upload progress</h2>
           <ul class="pending-list" id="pending-list"></ul>
         </section>