State management

The frontend uses two complementary state systems:

JWT context — session, user profile, login/logout (React context + useReducer)
Redux Toolkit — shared app flags and cached admin data

Redux store — `store/index.ts`

const persistConfig = {
  key: 'root',
  storage,
  whitelist: ['users']
};

Slice	File	State	Persisted
`users`	`store/reducers/users.ts`	Admin user list cache	Yes
`zerodha`	`store/reducers/zerodha.ts`	`isZerodhaConnected`	No

Typed hooks are re-exported:

export { store, persister, useSelector, useDispatch };

Header — reads/writes zerodha.isZerodhaConnected after Zerodha status checks
User list page — dispatches getUsersDetails after fetching users
Dashboard user — useSelector(selectZerodhaStatus) before placing orders

Auth is not in Redux. JWTProvider holds:

Method	API	Notes
`login`	`POST /user/login`	Sets token, connects socket
`logout`	`POST /user/logout/:id`	Clears token, disconnects socket
`fetchUser`	`GET /user`	Refreshes profile
`updateProfile`	`PUT /user/`	Updates profile in state
`register`	Legacy mock path	Not used in production flow

Token storage key: localStorage.serviceToken.

Auth in context — token lifecycle tied to axios interceptors and socket connection in one place
Zerodha flag in Redux — multiple components (Header, DashboardUser) need the same connection status without prop drilling
Users in Redux + persist — admin table survives refresh without refetch