Refactor: Centralize localStorage Operations in a Storage Utility

[zaibamachhaliya]

Problem

AppContext.jsx currently contains direct localStorage operations for:

• PAT (oe_pat)
• Rate limit (oe_rate_limit)
• Recent searches (oe_recent)

This couples storage logic with application state and makes it harder to maintain.

Proposed Solution

Create a reusable storage utility at:

src/utils/storage.js

The utility should:

• Centralize localStorage access
• Define storage keys using STORAGE_KEYS
• Provide get, set, and remove methods

Then update src/context/AppContext.jsx to use the storage utility instead of accessing localStorage directly.

Expected Result

• No direct localStorage calls in AppContext.jsx
• Storage keys have a single source of truth
• Existing PAT, rate-limit, and recent-search behaviour remains unchanged

Type: Code Quality Improvement

[zaibamachhaliya]

@Ri1tik, if you think this refactor would genuinely improve the structure and maintainability of AppContext.jsx, I’d be happy to take this up and implement it. If you agree, could you please assign this issue to me?