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/fixtures/namekb/deploy/install-guide-a.md

@@ -0,0 +1,9 @@
+# Install Forgejo Guide A
+
+fixture preamble block one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen
+
+install forgejo with the deployment steps install forgejo with the deployment steps install forgejo with the deployment steps install forgejo with the deployment steps
+
+alpha1 alpha2 alpha3 alpha4 alpha5 alpha6
+
+NAMEKB-TAIL-c5d6

tests/fixtures/namekb/deploy/install-guide-b.md

@@ -0,0 +1,9 @@
+# Install Forgejo Guide B
+
+fixture preamble block one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen
+
+install forgejo with the deployment steps install forgejo with the deployment steps install forgejo with the deployment steps
+
+beta1 beta2 beta3 beta4 beta5 beta6
+
+NAMEKB-TAIL-d7e8

tests/fixtures/namekb/deploy/install-guide-c.md

@@ -0,0 +1,9 @@
+# Install Forgejo Guide C
+
+fixture preamble block one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen
+
+install forgejo with the deployment steps install forgejo with the deployment steps
+
+gamma1 gamma2 gamma3 gamma4 gamma5 gamma6
+
+NAMEKB-TAIL-f9a0

tests/fixtures/namekb/deploy/install-guide-d.md

@@ -0,0 +1,9 @@
+# Install Forgejo Guide D
+
+fixture preamble block one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen
+
+install forgejo with the deployment steps
+
+delta1 delta2 delta3 delta4 delta5 delta6
+
+NAMEKB-TAIL-b1c2

tests/fixtures/namekb/forgejo/forgejo-home.md

@@ -0,0 +1,9 @@
+# Zeta Forge One
+
+fixture preamble block one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen
+
+
+
+kilo1 kilo2 kilo3 kilo4 kilo5 kilo6
+
+NAMEKB-TAIL-a1b2

tests/fixtures/namekb/forgejo/forgejo-nginx.md

@@ -0,0 +1,9 @@
+# Zeta Forge Two
+
+fixture preamble block one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen
+
+
+
+lambda1 lambda2 lambda3 lambda4 lambda5 lambda6
+
+NAMEKB-TAIL-b3c4

tests/fixtures/namekb/zz-folder-map.md

@@ -0,0 +1,9 @@
+# Zeta Misc Three
+
+fixture preamble block one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen seventeen eighteen nineteen
+
+
+
+micro1 micro2 micro3 micro4 micro5 micro6
+
+NAMEKB-TAIL-e3f4

tests/fixtures/retrieval_battery.txt

@@ -0,0 +1,17 @@
+# Phase 119 retrieval battery (task 06, D6) — the 1,000-doc live replica.
+#
+# Gate (per the phase overview, post-phase measured numbers):
+#   1-3. each name question's suggested top-5 contains its canonical doc:
+#        gitea  -> deploy/Deployments/reeseapps/gitea/README.md (rank 4)
+#        forgejo-> 5/5 forgejo-tree docs, README #1
+#        gateway-> deploy/Deployments/reeseapps/gateway/README.md (rank 3)
+#   4. the 2026-09-05 incident regression: a qwen3.8-27b quadlet stays in
+#      the suggested top-5 (the digit-bearing prefix rule, unchanged).
+#   5. deflection sanity: the out-of-KB question's gate verdict + fts
+#      count match the pre-phase replica run (HIGH, fts_hits=5) — the
+#      name-hit change must not move it.
+How do I deploy gitea?
+How do I deploy forgejo?
+How do I set up the gateway?
+Do you have notes on the qwen 3.8 27b model?
+What is the capital of Mongolia?