phase: 141_read_range_dedupe_fix

All gates green and verified. Final report:

**Phase 141 final verification pass — complete**

- **Verified (tasks 01–04 already in `complete/`):** `AgentHolder.read_coverage` span recording (all 4 read outcomes, refusals record nothing); coverage dedupe matrix (range read of uncovered lines proceeds, fully-covered re-read → `ALREADY_IN_CONTEXT` with a now-true claim, partial plain re-read → `REREAD_PARTIAL` naming merged spans, `REREAD_TRUNCATED` retired, fast path retired per task 02); `TOOLS_SECTION` re-read sentence re-cut to coverage-true form (prompt lock re-pinned); owner-scenario integration repro (pure + truncated variants) and mock `read two ranges` flow + dedicated E2E — all match the task specs exactly; no code defects found.
- **Tests/lint/coverage:** `uv run pytest --cov=app --cov-report=term-missing` → exit 0, TOTAL 99% (5498 stmts, `app/rag/agent.py` 99%) — run twice, both green; `uv run pytest tests/e2e/test_read_range_dedupe.py -v --no-cov` → 2 passed in isolation; `uv run ruff check . && uv run pyright` → All checks passed / 0 errors.
- **Completion criteria:** (1) two different ranges both reach the model, re-covered re-read refused truthfully — ✅ (integration + E2E); (2) partial plain re-read gets the `offset`/`limit` teaching, false claim gone both directions — ✅; (3) plain-read + phase-131 result shapes byte-identical, existing pins pass unchanged — ✅; (4) all gate commands green, >90% — ✅; (5) no behavior change in completed phases (grep/ls, truncation notice, `read_docs`/`read_truncations` signals) — ✅ (whole project suite green).
- **Documentation:** README.md — fixed pre-existing phase-140 gap: `BOR_PDF_PICTORIAL` / `BOR_PDF_PICTORIAL_MIN_CHARS` were in `.env.example`/Settings but undocumented (README claims every `.env.example` var is covered); added the pictorial-PDF-pass bullet to the PDF section + two config-reference rows. AGENTS.md — verified consistent (rules, quick-ref commands, phase refs all check out) — no changes needed.
- **Notable:** overview's "fast path survives for holder-state rows" note is superseded by task 02's authoritative decision (every dedupe row resolves — "full" needs the true line count); implementation follows task 02. No phase files touched; changes left in the working tree for the harness commit.
- **Next pending phase:** `142_kb_overview_freshness`.

tests/unit/test_prompt_lock.py

@@ -72,12 +72,17 @@ def test_high_and_low_bases_byte_locked() -> None:
 #: phase 118 (task 04, A6, owner directive 2026-09-15): the ``read``
 #: clause was rewritten for the summary-seed mode (the ``<documents>``
 #: section holds SUMMARIES — ``read`` adds the full text; only an
-#: already-read document is refused). Only that clause moved — the
-#: prefix (the ``ls``-clause opening) and the suffix (the
-#: discipline-rules ending) survived byte-identical, so they are the
-#: same anchors as pre-phase-118.
-TOOLS_SECTION_SHA256 = "87ee80faf0170da6ab1de518177313def6460785613fa074312a2a5f9f071750"
-TOOLS_SECTION_LEN = 2465
+#: already-read document is refused). RE-CUT again for phase 141
+#: (task 02): the re-read sentence was re-cut to the coverage-true
+#: form — do not re-read a document read IN FULL (answer from it);
+#: a PARTIAL document (a range read, or a truncated read) is not
+#: complete in the context until read all — read the other parts with
+#: ``offset``/``limit``. Only that sentence moved — the prefix (the
+#: ``ls``-clause opening) and the suffix (the discipline-rules
+#: ending) survived byte-identical, so they are the same anchors as
+#: pre-phase-141.
+TOOLS_SECTION_SHA256 = "3671680bbf4e04efe1186690c18d24869e4974ceb29485cedc3e34a9286bf3b2"
+TOOLS_SECTION_LEN = 2656
 TOOLS_SECTION_PREFIX = (
     "<tools>\n"
     "You may extend your context with three tools. `ls` lists the "