#453 docs: record the call-graph reach check for the missed JS/TS questions

Replaces the last sentence of the paragraph added in #452 (call-graph reach 'has not been tested') with the result of a read-only check on the 19 questions: 5 of 19 reports name an indexed symbol, 1 of 58 needed files is within two hops of them; a looser variant reaches 18 of 58 but returns about 54 files per question. Docs only. #452 is the earlier part.

---

Summary by cubic

Records the result of the call-graph reach check for the 19 missed JavaScript/TypeScript questions in the docs, replacing the earlier claim that it had not been tested.

• Only 5 of the 19 reports name an indexed symbol, and walking two hops from those reaches 1 of the 58 needed files.
• A looser variant that treats every matching word as a starting point reaches 18 of 58 files but returns about 54 files per question versus about 11 today, and was not compared with the existing explore scoring at the same file budget.

Summary by CodeRabbit

• Documentation
  • Updated the retrieval analysis with results showing that two-hop call-graph reach found 1 of 58 needed files, while matching every word as a symbol found 18 and returned about 54 files per question, compared with about 11 today.
  • Clarified that the broader matching approach was not tested at the same file budget, so the added value of graph reach beyond explore remains unresolved.