refactor(frontend): trim comments to one line each

Every docblock in the new query layer said in a paragraph what fits on a
line. Now: keys.ts 1 line, staleTime 1, queryClient 2, the converted hooks
1-3 each. DesktopQueryCacheReset keeps the most because the two things it
encodes are both non-obvious — why a key can outlive its backend, and why
resetQueries rather than clear().

No code change.

Author: ConnorYoh

frontend/editor/src/core/api/config.ts

@@ -18,13 +18,12 @@ export async function fetchFooterInfo(): Promise<FooterInfo> {
     );
     return response.data;
   } catch (error) {
-    // Toasts are suppressed here, so without this the failure is silent.
+    // Toasts are suppressed here, so the failure would otherwise be silent.
     console.error("[api/config] footer-info failed:", error);
     throw error;
   }
 }
 
-/** Whether a named backend feature group (ImageMagick, Calibre, ...) is available. */
 export async function fetchGroupEnabled(group: string): Promise<boolean> {
   const response = await apiClient.get<boolean>(
     `/api/v1/config/group-enabled?group=${encodeURIComponent(group)}`,

frontend/editor/src/core/api/users.ts

@@ -3,7 +3,6 @@ import { UserSummary } from "@app/types/signingSession";
 
 export async function fetchUsers(): Promise<UserSummary[]> {
   const response = await apiClient.get<UserSummary[]>("/api/v1/user/users");
-  // A proxy can answer 200 with an HTML login page; callers filter and sort
-  // this, so a non-array body would throw during render.
+  // A proxy can answer 200 with an HTML login page; callers assume an array.
   return Array.isArray(response.data) ? response.data : [];
 }

frontend/editor/src/core/hooks/useFooterInfo.ts

@@ -5,10 +5,9 @@ import { CONFIG_STALE_TIME } from "@app/query/staleTime";
 
 export type { FooterInfo };
 
-/** Analytics off is the safe read when the server can't be asked. */
 const FALLBACK: FooterInfo = { analyticsEnabled: false };
 
-/** Public footer configuration. Shared by Footer and the admin legal section. */
+/** Public footer config, shared by Footer and the admin legal section. */
 export function useFooterInfo() {
   const { data, isPending, error } = useQuery({
     queryKey: qk.footerInfo(),
@@ -17,7 +16,7 @@ export function useFooterInfo() {
   });
 
   return {
-    // Callers read legal links off this, so a failure must still yield an object.
+    // Callers render legal links off this, so a failure must still yield an object.
     footerInfo: data ?? (error ? FALLBACK : null),
     loading: isPending,
     error: (error as Error | null) ?? null,

frontend/editor/src/core/hooks/useGroupEnabled.ts

@@ -6,10 +6,7 @@ import type { GroupEnabledResult } from "@app/types/groupEnabled";
 
 export type { GroupEnabledResult };
 
-/**
- * Whether a named feature group is enabled on the backend.
- * `enabled` is null while loading; a failed check reads as disabled.
- */
+/** Null while loading; a failed check reads as disabled. */
 export function useGroupEnabled(group: string): GroupEnabledResult {
   const { data, isPending } = useQuery({
     queryKey: qk.groupEnabled(group),

frontend/editor/src/core/query/keys.ts

@@ -1,10 +1,4 @@
-/**
- * Query keys for the editor: ["editor", <resource>, ...params].
- *
- * Keys are flavour-agnostic — which backend answers is decided by the api
- * layer, and on desktop by operationRouter at request time. A key therefore
- * does not pin a backend; see DesktopQueryCacheReset.
- */
+/** Editor query keys: ["editor", <resource>, ...params]. */
 export const qk = {
   footerInfo: () => ["editor", "footerInfo"] as const,
   groupEnabled: (group: string) => ["editor", "groupEnabled", group] as const,

frontend/editor/src/core/query/queryClient.ts

@@ -1,13 +1,7 @@
 import { QueryClient, type DefaultOptions } from "@tanstack/react-query";
 
-/**
- * Query defaults for every client in the app, editor and Processor alike.
- *
- * networkMode "always" because navigator.onLine tracks internet reachability,
- * which says nothing about a bundled backend on 127.0.0.1 or a self-hosted
- * server on the LAN. On Query's default, losing Wi-Fi strands every query
- * pending against a backend that is up.
- */
+// networkMode "always": navigator.onLine tracks the internet, not a backend on
+// 127.0.0.1 or the LAN. On the default, losing Wi-Fi strands every query.
 export const baseQueryOptions: DefaultOptions["queries"] = {
   staleTime: 30_000,
   gcTime: 5 * 60_000,

frontend/editor/src/core/query/staleTime.ts

@@ -1,8 +1,2 @@
-/**
- * staleTime for server config lookups. A web build talks to one backend for its
- * whole life, and changing these server-side already needs a restart.
- *
- * Only for values that are the same for every user — there is no invalidation
- * on login/logout. Desktop shadows this; it cannot assume a single backend.
- */
+/** Server config, fixed for the session. Nothing auth-scoped — no login/logout invalidation exists. */
 export const CONFIG_STALE_TIME = Infinity;

frontend/editor/src/desktop/components/AppProviders.tsx

@@ -312,8 +312,7 @@ export function AppProviders({ children }: { children: ReactNode }) {
           autoFetch: false,
         }}
       >
-        {/* Also here: the auth check below switches mode before authChecked
-            flips, and those switches must not be missed. */}
+        {/* Also here: the auth check below switches mode pre-authChecked. */}
         <DesktopQueryCacheReset />
         <div style={{ minHeight: "100vh" }} />
         {updatePopupModal}

frontend/editor/src/desktop/components/DesktopQueryCacheReset.test.tsx

@@ -70,8 +70,7 @@ describe("DesktopQueryCacheReset", () => {
 
     modeListeners.forEach((l) => l({ mode: "selfhosted" }));
 
-    // The mounted observer must be notified and refetch — evicting the entry
-    // without notifying would leave the stale value on screen.
+    // Must refetch, not just evict — this is what clear() got wrong.
     await waitFor(() => expect(seen).toContain("self-hosted-backend"));
     expect(queryFn).toHaveBeenCalledTimes(2);
   });
@@ -96,7 +95,6 @@ describe("DesktopQueryCacheReset", () => {
     renderWithConsumer(queryFn);
     await waitFor(() => expect(queryFn).toHaveBeenCalledTimes(1));
 
-    // No transition happened, so nothing should have been reset.
     expect(queryFn).toHaveBeenCalledTimes(1);
   });
 });

frontend/editor/src/desktop/components/DesktopQueryCacheReset.tsx

@@ -4,26 +4,20 @@ import { connectionModeService } from "@app/services/connectionModeService";
 import { selfHostedServerMonitor } from "@app/services/selfHostedServerMonitor";
 
 /**
- * Discards cached responses when the backend they came from stops being the one
- * the app talks to.
- *
- * A key does not pin a backend on desktop: operationRouter resolves the same
- * path to the bundled backend, a self-hosted server or the SaaS backend. Two
- * things move that target — a connection-mode switch, and the self-hosted
- * server going up or down, which reroutes with no mode event.
- *
- * resetQueries, not clear(): clear() evicts without notifying mounted
- * observers, so a panel keeps rendering the old backend's answer.
+ * Drops cached responses when the backend behind them changes. operationRouter
+ * resolves the same path to the bundled backend, a self-hosted server or SaaS,
+ * so a mode switch or the server going up/down invalidates every key.
  */
 export function DesktopQueryCacheReset() {
   const queryClient = useQueryClient();
 
   useEffect(() => {
+    // resetQueries, not clear(): clear() evicts without notifying mounted
+    // observers, so a panel keeps rendering the old backend's answer.
     const reset = () => void queryClient.resetQueries();
     const unsubscribeMode = connectionModeService.subscribeToModeChanges(reset);
 
-    // Only offline<->reachable matters; the monitor also emits idle and
-    // checking, and replays current state on subscribe.
+    // Ignore idle/checking, and the state replayed on subscribe.
     let wasOffline: boolean | null = null;
     const unsubscribeServer = selfHostedServerMonitor.subscribe(
       ({ status }) => {