docs: remove optimistic mutations references after write operations removal

Author: lauragift21

AGENTS.md

@@ -6,14 +6,13 @@ These rules apply to all coding sessions in the GitPulse project.
 
 GitPulse is a GitHub Activity Dashboard built with React + TanStack DB. It showcases
 TanStack DB's realtime features: collections, live queries (filters, joins, sorts,
-aggregates), optimistic mutations, and reactive UI updates.
+aggregates), and reactive UI updates.
 
 ## Architecture
 
 - **Data layer**: TanStack DB collections are the single source of truth
 - **Fetching**: TanStack Query + @tanstack/query-db-collection bridges API data into collections
 - **Queries**: All UI reads go through `useLiveQuery` / `useLiveSuspenseQuery` — never read from Query cache directly
-- **Mutations**: Use `createOptimisticAction` for complex multi-collection mutations, `collection.update()` for simple ones
 - **Routing**: Simple state-based SPA page switching (no URL router)
 
 ## Code Conventions
@@ -33,13 +32,6 @@ aggregates), optimistic mutations, and reactive UI updates.
 - Always pass reactive dependencies as the second argument to `useLiveQuery`
 - Use `useLiveSuspenseQuery` inside Suspense boundaries for initial loads only
 
-### Mutations
-
-- Place optimistic actions in `src/mutations/`
-- Always call `collection.utils.refetch()` inside `mutationFn` after API call
-- Keep `onMutate` synchronous — never await inside it
-- Handle rollback by relying on TanStack DB's automatic rollback on error
-
 ### API Layer
 
 - All GitHub API functions go in `src/api/`
@@ -74,7 +66,6 @@ aggregates), optimistic mutations, and reactive UI updates.
 - `src/collections/` — TanStack DB collection definitions
 - `src/schemas/` — Zod schemas for all entities
 - `src/queries/` — Reusable live query definitions
-- `src/mutations/` — Optimistic action definitions
 - `src/api/` — GitHub REST API client and endpoint functions
 - `src/pages/` — Top-level page components
 - `src/components/` — UI components organized by feature
@@ -96,5 +87,4 @@ Key packages (do not add alternatives without reason):
 
 - Run `npm run build` to verify TypeScript compilation
 - Run `npm run dev` to test locally
-- Verify optimistic mutations show instant UI feedback before API round-trip
 - Test with invalid/expired token to verify error handling

README.md

@@ -27,8 +27,6 @@ queryCollectionOptions() bridge
 TanStack DB Collections (single source of truth)
       ↓
 useLiveQuery() (reactive reads in components)
-      ↓
-createOptimisticAction() (writes → API → refetch)
 ```
 
 The key principle: **all UI reads go through TanStack DB live queries, never directly from the Query cache.**
@@ -42,7 +40,6 @@ The key principle: **all UI reads go through TanStack DB live queries, never dir
 | `src/schemas/`     | Zod schemas for all entities (Repository, Issue, PullRequest, Event, Label, User)           |
 | `src/collections/` | TanStack DB collection definitions - one per entity, bridged via `queryCollectionOptions()` |
 | `src/api/`         | GitHub REST API client (`client.ts` handles auth, rate limiting, errors) + endpoint modules |
-| `src/mutations/`   | Optimistic actions using `createOptimisticAction()` for instant UI updates                  |
 | `src/pages/`       | 6 pages: Setup, Dashboard, ActivityFeed, Issues, PullRequests, Contributors                 |
 | `src/components/`  | Layout (AppShell, Sidebar, Header) + UI primitives (Button, Card, Badge, Avatar, etc.)      |
 | `src/hooks/`       | `useGitHubToken`, `useTrackedRepos`, `useDarkMode`                                          |
@@ -52,14 +49,12 @@ The key principle: **all UI reads go through TanStack DB live queries, never dir
 
 ### Key Patterns
 
-1. **Optimistic mutations** - Every write (`onMutate`) instantly updates the local collection, then the API call fires, then `collection.utils.refetch()` syncs. TanStack DB auto-rolls back on errors.
-
-2. **Resilient multi-repo fetching** - All `fetchAll*()` functions use `Promise.allSettled` so one repo's failure doesn't break others.
+1. **Resilient multi-repo fetching** - All `fetchAll*()` functions use `Promise.allSettled` so one repo's failure doesn't break others.
 
-3. **Live queries with reactive deps** - Filters, sorts, and search terms are passed as the second argument to `useLiveQuery`, making the UI automatically re-render when state changes.
+2. **Live queries with reactive deps** - Filters, sorts, and search terms are passed as the second argument to `useLiveQuery`, making the UI automatically re-render when state changes.
 
-4. **Simple SPA routing** - A `useState<Page>` in `App.tsx` drives navigation, no URL router.
+3. **Simple SPA routing** - A `useState<Page>` in `App.tsx` drives navigation, no URL router.
 
-5. **Stale time strategy** - Labels (10min) > Repos (5min) > Issues/PRs (3min) > Events (2min), reflecting how often each entity changes.
+4. **Stale time strategy** - Labels (10min) > Repos (5min) > Issues/PRs (3min) > Events (2min), reflecting how often each entity changes.
 
-6. **Theming** - CSS custom properties in `globals.css` with a `.dark` class override and Tailwind's `dark:` variant. The design is intentionally monochromatic (black/white).
+5. **Theming** - CSS custom properties in `globals.css` with a `.dark` class override and Tailwind's `dark:` variant. The design is intentionally monochromatic (black/white).