async-patterns-safetylisted

# Async Patterns Safety ## Core rules - Never call a hook-shaped function (`use*`) inside callbacks, loops, conditions, or async helpers. - If a function is imperative, rename from `useSomething` to `somethingWorker` or `fetchSomething`. - Prefer TanStack Query hooks for server state instead of manual `useEffect` + `fetch` orchestration. - Async functions without `await` must not be declared `async`. ## Safe migrations 1. `useEffect(() => { useApiWorker(...) })` -> `useEffect(() => { apiWorker(...) })`. 2. `async function foo() { return x; }` -> `function foo() { return x; }`. 3. Callback-style API wrappers -> typed Promise-based service functions. ## Checklist before final output - No `react-hooks/rules-of-hooks` risk in generated code. - No `@typescript-eslint/require-await` warnings. - Hook names are reserved for real React hooks.