phase: 193_sync_remaining_count

**Phase 193 — final verification pass: all gates green.**

- **Verified (all 3 tasks already complete in `complete/193_sync_remaining_count/`):** `fmtSyncLabel`'s count part is `total > 0 && total - done > 0 ? \`${total - done} remaining\` : ""` (plain int, hidden at `N==0`, `total===0` → no part); docstrings updated; chunk/image/summaries parts + `counts_line` terminal + `app/` byte-untouched (`git diff --stat`: no `app/` files).
- **Completion criteria:** `N remaining` shape + marker pins ✅ · upload shares the builder (E2E upload arm) ✅ · chunk/image/summaries pins green ✅ · terminal `counts_line` green unedited + A4 title/`#sync-progress` pin ✅ · suite green, coverage 99% ✅ · lint/types clean ✅ · commit + `todo/→complete/` left to the harness (no git index/history commands run).
- `uv run pytest -q --cov=app --cov-report=term-missing` → **exit 0**, junit: **4792 tests, 0 failures/errors/skipped**, `TOTAL 7181 16 → 99%` (>90%)
- `uv run pytest tests/e2e/test_sync_remaining_count.py -v --no-cov` → **3 passed** (isolated, 53 s)
- Isolated `--no-cov` sweep of the 14 sync-lineage suites (label_mobile, upload_progress, chunk_progress, image_progress, progress_box, summary_visibility, archive_upload_sources, status_freshness, upload_no_scan, peak_memory_visible, session_reset, fast_path_deferred_content, git_freeze, smoke) → **14/14 exit 0**
- `uv run ruff check .` → All checks passed · `uv run pyright` → **0 errors**
- **Docs:** README.md reviewed in full (all 2408 lines) + AGENTS.md. Fixed 2 inconsistencies: the sync running-label clause claimed the upload label shows the count — now states it shares the ONE builder/shape but reports no counts since phase 90 (renders bare); phase-190's "the other ~72 rows" → "the other 83 rows of the panel's 86-row catalogue" (mechanically: 86 CATALOG rows, 84 overridable). `N remaining` already in the sync paragraph; task-01's `(n/m)` examples gone. AGENTS.md verified consistent (no clause names the running count part → unchanged per the phase's "do not add if absent"). Mechanically re-verified: all 86 `BOR_*` settings documented + defaults match, `.env.example` 88 vars covered, 0 broken README anchors, all cited file paths exist, 17 palette colors, migrations head `0030`, pages/shell routes, ports 8123/8901, E2E port allocations (new suite's 8211/8914 unique).
- **Notable:** task 02's documented deviation stands — `files_done` is the importer's 1-based *current* file, so the phase doc's `[1-4]` range is unreachable; count-bearing frames are `1 … N−1` (pinned). Pre-existing, untouched: `E2E_APP_PORT_TOOLBUDGET`/`SAVEDOC` both 8129 and `SYNCUP`/`SYCNCEL` both 8133 — harmless under the one-suite-at-a-time rule.
- **Next pending phase:** none — `193_sync_remaining_count` is the last entry in `.agents/phases/todo/`.

tests/e2e/test_archive_upload_sources.py

@@ -31,7 +31,8 @@ poll and the phase-64 slow-LLM proxy is GONE from this suite. The
 "Uploading… → Processing… → restored" lifecycle is made observable the
 old way (the POST is held in the browser via ``page.route``) plus a
 held FIRST status GET, so the bare "Processing…" in-run label (no
-file, no "(n/m)") is asserted across the whole background run.
+file, no `N remaining` count) is asserted across the whole background
+run.
 
 The archives are **built in-test** with Python's ``tarfile`` over
 ``tmp_path`` fixture files carrying markdown sentinels (``ALPHA-…`` /
@@ -65,7 +66,7 @@ Contract under test:
   "Uploading…" while the POST is in flight (held via ``page.route``);
   at the 202 the "Successfully uploaded — <source>" toast fires; the
   button then carries the BARE "Processing…" label for the whole
-  background run (no file, no "(n/m)" — the first status GET is held
+  background run (no file, no `N remaining` count — the first status GET is held
   so the in-run window outlives the 2 s poll) until the status
   ``success`` lands: the result line reads "Uploaded e2e-upload
   (<stamp>) — press Sync sources to import it." (the phase-154
@@ -373,7 +374,7 @@ def _hold_first_status_fetch(page: Page, hold_s: float) -> None:
     AFTER the page's boot re-attach fetch, before the submit. The
     poll's first tick fires 2 s after the 202; holding its fetch keeps
     the button in the in-run state long enough to assert the bare
-    "Processing…" label (no file, no "(n/m)") across the whole
+    "Processing…" label (no file, no `N remaining` count) across the whole
     background run — phase 90's run settles in milliseconds, so without
     the hold the in-run window is only the 2 s pre-tick gap."""
     state = {"held": False}
@@ -449,7 +450,7 @@ def test_upload_registers_without_indexing(
     button is disabled and reads "Uploading…"; at the 202 the
     "Successfully uploaded — <source>" toast fires (A2); the button
     then carries the BARE "Processing…" label for the whole background
-    run (no file, no "(n/m)" — phase 90 A2, proven across a held first
+    run (no file, no `N remaining` count — phase 90 A2, proven across a held first
     status GET); when the status ``success`` lands the result line
     reads "Uploaded <source> (<stamp>) — press Sync sources to
     import it." (A3 — the phase-154 completion stamp), the button
@@ -499,7 +500,7 @@ def test_upload_registers_without_indexing(
     # The run is in flight (or just settled) server-side — and the
     # label STAYS bare across the whole background run: the first
     # status GET is held, so the tick that should settle the button is
-    # in flight — the label carries no file and no "(n/m)".
+    # in flight — the label carries no file and no `N remaining` count.
     time.sleep(2.5)  # just past the poll's first tick (the fetch is held)
     expect(btn).to_have_text("Processing…")