docs(internal): say the name score is not capped, not that it is unbounded

The comment described `_calculate_entity_score` as accumulating "without a
ceiling". The function is a finite sum of bounded terms — three
`calculate_*_ratio` helpers that each return 0-100, plus fixed exact/partial
and keyword bonuses — so a bound does exist. What matters for the surrounding
argument is only that the bound is not 100, which is what the sentence now
says. The rest of the comment is unchanged.

Author: Patch76

src/ha_mcp/tools/smart_search/_graph.py

@@ -362,8 +362,8 @@ async def fetch_related_buckets(client: Any, entity_id: str) -> GraphResult | No
 # Fuzzy mode is not symmetric, and no value here makes it so without breaking
 # the tie above: 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
+# is not capped at 100 — 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