web/communities: drop verbose comments from community search

Removes the descriptive comment blocks flagged in review; keeps only terse notes
for the non-obvious bits (disabling MUI's filter, the sentry test mock).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: kevinortiz43

app/web/features/communities/CommunitiesPage/CommunitySearch.test.tsx

@@ -21,8 +21,7 @@ jest.mock("next/router", () => ({
   }),
 }));
 
-// platform/sentry pulls in @sentry/nextjs, which crashes under jsdom; the test
-// wrapper imports it transitively via AuthProvider, so it must be mocked.
+// mock required: the wrapper pulls in @sentry/nextjs via AuthProvider, which crashes under jsdom.
 jest.mock("platform/sentry", () => {
   const mockCaptureException = jest.fn();
   return {
@@ -52,8 +51,6 @@ const parentedCommunity = (
   communityId,
   name,
   slug,
-  // Ordered root -> immediate parent -> self (the node itself is the last entry,
-  // matching the backend's get_node_parents_recursively output).
   parentsList: [
     {
       community: {
@@ -160,13 +157,11 @@ describe("CommunitySearch", () => {
     const input = screen.getByLabelText(t("communities:search_communities"));
     await user.type(input, "da");
 
-    // Wait for the debounce to apply the filter (Berlin doesn't contain "da").
     await waitFor(() => {
       expect(screen.queryByText("Berlin")).not.toBeInTheDocument();
     });
     expect(screen.getByText("Amsterdam")).toBeInTheDocument();
     expect(screen.getByText("Rotterdam")).toBeInTheDocument();
-    // Short queries must not hit the server (backend requires >= 3 chars)
     expect(mockSearchCommunities).not.toHaveBeenCalled();
   });
 
@@ -192,9 +187,6 @@ describe("CommunitySearch", () => {
   });
 
   it("renders server results in the returned order, not the hidden hierarchy path (issue #9129)", async () => {
-    // Server ranks Pyongyang first. A hidden-path sort would instead put Sydney
-    // first ("Australia" < "North Korea"), so DOM order proves we honor the
-    // server's name-relevance ranking and never re-sort by the parent path.
     mockSearchCommunities.mockResolvedValue(
       searchRes([
         parentedCommunity(5, "Pyongyang", "pyongyang", "North Korea"),
@@ -208,7 +200,6 @@ describe("CommunitySearch", () => {
     const input = screen.getByLabelText(t("communities:search_communities"));
     await user.type(input, "yan");
 
-    // Wait for the debounce + server results to replace the browse list.
     await waitFor(() => {
       expect(screen.getAllByRole("option")).toHaveLength(2);
     });
@@ -282,7 +273,6 @@ describe("CommunitySearch", () => {
     const input = screen.getByLabelText(t("communities:search_communities"));
     await user.type(input, "boom");
 
-    // No crash; the empty-results affordance is shown instead.
     await waitFor(() => {
       expect(
         screen.getByRole("link", { name: "Request this community!" }),

app/web/features/communities/CommunitiesPage/CommunitySearch.tsx

@@ -22,21 +22,14 @@ import { useEffect, useMemo, useState } from "react";
 import { communityCreationFormURL, routeToCommunity } from "routes";
 import { listAllCommunities, searchCommunities } from "service/communities";
 
-// The visible name is what we rank/filter on (issue #9129). We only read the
-// fields both ListAllCommunities (CommunitySummary) and SearchCommunities
-// (Community) responses share.
 type CommunityOption = Pick<
   Community.AsObject,
   "communityId" | "name" | "slug" | "parentsList"
 >;
 
-// Backend SearchCommunities requires >= 3 chars; below that we browse/filter the
-// full list client-side. 400 ms debounce mirrors the confirmed #8837 decision.
 const MIN_SEARCH_LENGTH = 3;
 const COMMUNITY_SEARCH_DEBOUNCE_MS = 400;
 
-// parentsList is ordered root -> ... -> immediate parent -> self (the node itself
-// is the last entry), so the region context is the second-to-last entry.
 const regionOf = (option: CommunityOption): string => {
   const parents = option.parentsList;
   if (!parents || parents.length < 2) return "";
@@ -69,8 +62,6 @@ export default function CommunitySearch() {
   const query = debouncedInput.trim();
   const isSearching = query.length >= MIN_SEARCH_LENGTH;
 
-  // Server-side, name-ranked, typo-tolerant search (pg_trgm). react-query caches
-  // by query string, so re-typing/backspacing hits the cache, not the network.
   const { data: searchData, isLoading: searchLoading } = useQuery<
     SearchCommunitiesRes.AsObject,
     RpcError
@@ -80,7 +71,6 @@ export default function CommunitySearch() {
     enabled: isSearching,
   });
 
-  // Full list for the browse / short-query state (dropdown opened, < 3 chars).
   const { data: browseData, isLoading: browseLoading } = useQuery<
     ListAllCommunitiesRes.AsObject,
     RpcError
@@ -90,9 +80,6 @@ export default function CommunitySearch() {
     enabled: !isSearching,
   });
 
-  // Ranked search results are used verbatim (no client re-sort). Browse results
-  // are filtered by visible name and ordered region -> name so region groups stay
-  // contiguous. Neither path uses the hidden hierarchical path (the #9129 bug).
   const options = useMemo<CommunityOption[]>(() => {
     if (isSearching) {
       return searchData?.communitiesList ?? [];
@@ -141,8 +128,7 @@ export default function CommunitySearch() {
       onInputChange={handleInputChange}
       onChange={handleChange}
       getOptionLabel={(option) => option.name}
-      // Server results are already ranked (and typo-tolerant); browse results are
-      // pre-filtered. Disable MUI's built-in filter so it can't drop/reorder them.
+      // don't let MUI re-filter: it would drop the typo-tolerant server results
       filterOptions={(x) => x}
       groupBy={isSearching ? undefined : (option) => regionOf(option)}
       renderOption={(props, option) => {