phase: 119_name_signal_read_chips

All verification complete. Final report:

**Phase 119 final verification pass — all criteria verified, one stale pin fixed.**
- Verified implementation of all 6 tasks: D1 component name-hit rule (`name_hit` flag, titles never matched, retired length tie-break), D2 `BOR_NAME_HIT_BONUS` (0.005 default, 0 = byte-identical kill switch, negative fails startup, selection-layer only, `eval_retrieval` `suggested:` line), D3 suggested-folder lines (after `SUGGEST_INTRO`, before first block), D4 cite-discipline `SUGGEST_INTRO` sentence (PERSONA/LOW/`TOOLS_SECTION` byte-pins intact), D5 `done.sources` = read docs only (frontend no-op on empty confirmed), D6 mock `repeat your folder map` echo + new suite + telemetry.
- Battery (replica restored per skill, fingerprint docs=1000/chunks=8866 verified, `eval_retrieval --from-file tests/fixtures/retrieval_battery.txt` re-run): **GATE PASS** — gitea README #4 in suggested top-5, forgejo 5/5 (README #1), gateway README in top-5 (#4), qwen3.8-27b quadlets top-5, Mongolia HIGH/fts=5 unchanged.
- New E2E in isolation: `4 passed` ×2 (deterministic). All 27 modified E2E suites in isolation: 26 green; **1 stale pin fixed** — `test_source_chip_quality.py` durable-record order pin pre-dated the D1 re-rank (`aliases` stem sub-component name-hits `ssh_aliases.txt`, deterministically lifting `backups.md` over `kubernetes.md`; probe-verified 0.016277 vs 0.016036, 4/4 stable) — re-pinned with the phase-119 rationale; suite green ×2.
- Gates: `uv run pytest --cov=app --cov-report=term-missing` → **2547 passed, app coverage 99%** (>90%); `uv run ruff check .` → All checks passed; `uv run pyright` → 0 errors.
- Completion criteria: 1 ✅ (battery, recorded), 2 ✅ (folder lines; block/LOW byte-identical pins green), 3 ✅ (read-only chips, zero-read chips nothing, related row + durable record untouched — unit+E2E agree), 4 ✅ (all green), 5 → commit/phase-move left to the harness per pass rules (nothing committed).
- Deviations: battery output + real-model telemetry recorded in `.agents/reports/119_name_signal_read_chips/task06_battery_and_e2e.md` and `TOOL_CALLING_TESTING.md` §11 (task files in `complete/` are immutable to this pass); gateway canonical doc at #4 vs overview's #3 was already documented at task 06 (containment gate met).
- Next pending phase: **none** — `todo/` holds only phase 119.

tests/unit/test_config.py

@@ -41,6 +41,10 @@ def test_defaults_match_locked_decisions(monkeypatch: pytest.MonkeyPatch) -> Non
     # fine-line-tuned value, task 07) with a 365-day decay timescale.
     assert s.recency_boost == 0.0007
     assert s.recency_half_life_days == 365
+    # Phase 119, D2 (LOCKED A3): the bounded name-hit bonus on the
+    # selection-time document score is ON by default (0.005 — the
+    # owner-tunable starting point; ``0`` is the kill switch).
+    assert s.name_hit_bonus == 0.005
     # Owner instruction 2026-08-22: answers may run up to 32 768 tokens.
     assert s.max_output_tokens == 32_768
     # Phase 17: the model's thinking streams by default (kill-switch off).
@@ -391,6 +395,33 @@ def test_recency_boost_rejects_negative(monkeypatch: pytest.MonkeyPatch) -> None
         _settings()
 
 
+def test_name_hit_bonus_default_and_env_override(
+    monkeypatch: pytest.MonkeyPatch,
+) -> None:
+    """Phase 119, D2 (LOCKED A3): the bounded name-hit bonus on the
+    SELECTION-time document score is ON by default (0.005 — the
+    owner-tunable starting point, not a calibrated constant) and
+    env-tunable so the owner re-tunes live (the phase-106 recency-boost
+    precedent). ``0`` is legal — the byte-identical kill switch."""
+    monkeypatch.delenv("BOR_NAME_HIT_BONUS", raising=False)
+    s = _settings()
+    assert s.name_hit_bonus == 0.005
+    monkeypatch.setenv("BOR_NAME_HIT_BONUS", "0")
+    assert _settings().name_hit_bonus == 0.0
+    monkeypatch.setenv("BOR_NAME_HIT_BONUS", "0.01")
+    assert _settings().name_hit_bonus == 0.01
+
+
+def test_name_hit_bonus_rejects_negative(monkeypatch: pytest.MonkeyPatch) -> None:
+    """``0`` is the byte-identical kill switch (the pre-phase selection
+    order) — a NEGATIVE bonus would demote name-hit documents (the exact
+    opposite of D2), so the validator fails loudly at startup naming the
+    field (the ``agent_max_rounds`` pattern, phase 119)."""
+    monkeypatch.setenv("BOR_NAME_HIT_BONUS", "-0.001")
+    with pytest.raises(ValidationError, match="name_hit_bonus"):
+        _settings()
+
+
 def test_recency_half_life_rejects_non_positive(
     monkeypatch: pytest.MonkeyPatch,
 ) -> None: