### Goal The assignment explicitly lists state management. The README should name the choice, give the reasons, and say what lives where. Original note: *The assignment lists state management explicitly. README should name it as a choice with reasons and say what lives where (URL / Apollo cache / context).* ### What the code does today (to document and check) - **Server state:** Apollo Client cache (`src/lib/apollo/`), with a field policy that merges pages for "Load more" (`cache.ts`). - **URL state:** the search text, filters and sort on the Elements page, in the address (`useSearchParams`), so a result can be shared and the back button works. - **Login state:** one source, `AuthProvider` / `useAuth()` (React context), fed by the server's answer to `me`. - **Local state:** form fields, open menus and similar, in the component with `useState`. - **Calculator routine:** shared client state planned in #91. ### Checklist - [ ] A "State management" section in the README with a table: kind of state, where it lives, why. - [ ] Say why a separate store (Redux, MobX, Recoil) was **not** added, and that Apollo's cache is the state manager for server data. The assignment names Apollo local state management as one option. - [ ] Describe the choice for the calculator routine when #91 is done. ### Done when - [ ] The README section exists and matches the code. _Text structured with Claude Code in discussion with Ronja. The original request is kept._