phase: 150_drop_sync_result

**Phase 150 final verification pass — complete, 100% green.** All 6 task files were already in `complete/`, so this was verification + doc pass.

- Verified: `#sync-progress` is the sole sync text surface + sole `aria-live` region (`role="status"`, polite, no `aria-hidden`); `span#sync-result` gone from HTML/JS/CSS/tests (incl. runtime-built `RETIRED_ID` absence pins in the unit suites); `setSyncProgress` single writer with text-driven visibility; running-only box write in `setSyncLabel`; all 9 settle/cancel sites routed; `requestCancel` pre-fetch clear is a NO-OP.
- Tests: `uv run pytest` → **3463 passed**; `uv run pytest --cov=app` → **99% on app/** (>90%); `uv run ruff check .` + `uv run pyright` → clean (0 errors); `tests/e2e/test_sync_progress_box.py --no-cov` → **8 passed in isolation**; all 18 migrated sync/image-PDF E2E files green in isolation (77 tests).
- Completion criteria: 1) grep clean ✅ 2) sole live region, attrs correct ✅ 3) in-flight/settle/cancel/idle box states proven by E2E + unit pins ✅ 4) icon-only running button + restore ✅ 5) full gates green ✅ 6) no completed-phase behavior change (18 family suites + full suite green) ✅ 7) commit — left to harness per pass instructions (working tree untouched, no `git add`/`commit`).
- Documentation: README.md fixed 2 pre-existing inconsistencies (stale `~/Homelab`+`~/Deployments` source model in the intro — retired in phase 61 — now describes the git/local/archive Sources model; "Requires AIPI_KEY" in retrieval-quality now states `BOR_LLM_API_KEY` in `.env` or `$AIPI_KEY`, matching the scripts' real convention). Everything else (URL table, env defaults vs `app/config.py`, sync/phase-150 copy, prod claims) verified accurate. AGENTS.md: verified consistent — no changes needed.
- Notable: no code changes were required — the phase implementation was correct as left; no live infrastructure touched.
- Next pending phase: `151_pdf_image_extraction` in `.agents/phases/todo/`.

tests/e2e/test_upload_no_scan.py

@@ -24,8 +24,9 @@ check + import), so its background run settles in milliseconds and the
 2 s status poll settles one tick after the 202. The sync leg is short
 (2 files + 1 ignored → a handful of mock-LLM requests), so instead of
 racing a timer the suite polls the RAG page's settled sync UI
-(``#sync-label`` "Synced HH:MM" + ``#sync-result`` counts) with generous
-timeouts — the live "Syncing… <file> (n/m)" label is the
+(``#sync-label`` "Synced HH:MM" + the ``#sync-progress`` box's counts
+line — phase 150: the box is the single sync text surface) with
+generous timeouts — the live "Syncing… <file> (n/m)" label is the
 ``test_sync_upload_progress.py`` suite's subject, not this one's.
 
 The archive is **built in-test** with Python's ``tarfile``:
@@ -559,7 +560,7 @@ def test_ignore_list_then_sync_scans(
     expect(page.locator("#sync-label")).to_have_text(
         SYNCED_LABEL, timeout=SYNC_TIMEOUT_MS
     )
-    expect(page.locator("#sync-result")).to_have_text("2 added", timeout=SYNC_TIMEOUT_MS)
+    expect(page.locator("#sync-progress-text")).to_have_text("2 added", timeout=SYNC_TIMEOUT_MS)
     expect(page.locator("#sync-btn")).to_be_enabled()
     expect(page.locator("#sync-btn")).not_to_have_attribute("aria-busy")