0.2.80

CLAUDE.md

@@ -722,10 +722,10 @@ caches results per query for the session, so backspacing is instant.
 **Every search the tab performs is recorded, and the gateway is what records it.** It used
 to depend entirely on the television posting to `/v1/search/history` after a result landed,
 which meant a query answered from the client's own cache, one whose post failed, or one
-from a build that predates the call was never written down at all — and the table feeding
-the recent-searches row and future per-user ranking was a partial record of what the
-household looks for. `handleSearch` now calls `recordSearchQuery` itself, before the Redis
-lookup, so a cached answer counts the same as one that reached Emby. Things to preserve:
+from a build that predates the call was never written down at all — and the table the
+console reads back was a partial record of what the household looks for. `handleSearch`
+now calls `recordSearchQuery` itself, before the Redis lookup, so a cached answer counts
+the same as one that reached Emby. Things to preserve:
 
 - **The write is detached from the request context.** Instant search cancels the in-flight
   request on every keystroke, so a write hung off `r.Context()` would be abandoned for