docs(internal): correct the reference-graph ranking comment

_GRAPH_HIT_SCORE said fuzzy scores are capped at 100, so a confirmed reference
ranks at or above every fuzzy name match. The cap lives in _search_in_dict and
bounds the config-body score. The fuzzy name score comes from
_calculate_entity_score, which accumulates its bonuses with no ceiling, so a
name echoing the queried entity's words can pass 100 on its own and outrank a
graph hit's fixed 100.

The exact-mode half of the claim holds and stays. The comment now states what
fuzzy mode does, scoped to graph-ONLY hits (_merge_graph_hits leaves an
already-scored record's score alone) and to the case where visibility
enforcement does not scrub the record.

Also name the scene caller in _individual_fetch_budgeted's deprioritize
paragraph: it passes the set too, alongside automation and script.

Author: Patch76

src/ha_mcp/tools/smart_search/_fetch.py

@@ -201,7 +201,7 @@ async def _individual_fetch_budgeted(
 
         ``deprioritize`` moves the named ids to the BACK of the queue while
         keeping every id in it (relative order preserved within each group).
-        The automation and script callers pass the ids Home Assistant's
+        The automation, script and scene callers pass the ids Home Assistant's
         reference graph already confirmed reference the queried entity: their
         match status is settled without reading the body, so under budget
         pressure the budget belongs to the ids that are NOT in the set, which

src/ha_mcp/tools/smart_search/_graph.py

@@ -357,10 +357,16 @@ async def fetch_related_buckets(client: Any, entity_id: str) -> GraphResult | No
 # Score assigned to a reference-graph hit. In the default exact mode every
 # surviving match scores exactly 100 (``_score_deep_match`` takes the max of
 # two 0-or-100 signals against a threshold of 100), so a graph hit sorts
-# indistinguishably from a body hit. Fuzzy scores are capped at 100 too, so
-# there a confirmed reference ranks at or above every fuzzy name match, which
-# is the intent: HA naming the reference is exact evidence, not an
-# approximate one.
+# indistinguishably from a body hit.
+#
+# Fuzzy mode is not symmetric, and no value here makes it so: the 100 cap
+# belongs to the config-body score (``_search_in_dict``), while the NAME score
+# from ``_calculate_entity_score`` accumulates without a ceiling — a name
+# echoing the queried entity's words can pass 100 on its own. So with
+# ``exact_match=False`` a graph-ONLY hit (``_merge_graph_hits`` leaves an
+# already-scored record's score alone) can sort below a match that merely
+# resembles the query, and land on a later page under a small ``limit``. It is
+# still counted in ``total_matches`` unless visibility enforcement scrubs it.
 _GRAPH_HIT_SCORE = 100