fix: fetch storage quota from backend on mount

[FSM1]

The quota display stayed at zero after re-login because fetchQuota()
was only called during upload flows. The zustand store initialized with
usedBytes: 0 and nothing triggered a backend sync on app load. Added a
useEffect to StorageQuota that calls fetchQuota() on mount so the
display always reflects persisted usage.

https://claude.ai/code/session_01F11Fe3ZAvUTbt4FHg4V5Ke

Summary by CodeRabbit

• Bug Fixes
  • Fixed storage quota display to automatically refresh quota data on component load, ensuring users see the most current storage usage information.

[coderabbitai]

Warning

Rate limit exceeded

@FSM1 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 2 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

The StorageQuota component now imports useEffect from React and invokes fetchQuota from useQuotaStore on component mount to refresh quota data. The percentage calculation and rendering logic remain unchanged.

Changes

Cohort / File(s)	Summary
Data Fetching on Mount apps/web/src/components/layout/StorageQuota.tsx	Added useEffect hook to call fetchQuota from useQuotaStore on component mount to refresh quota data.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: fetch storage quota from backend on mount' directly and clearly summarizes the main change: adding logic to fetch storage quota data from the backend when the StorageQuota component mounts.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch claude/fix-storage-quota-display-0SnSB

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR ensures the storage quota indicator reflects persisted backend usage after a re-login by triggering a quota sync when the quota UI mounts.

Changes:

• Add a useEffect in StorageQuota to call fetchQuota() on mount.
• Update the component to pull fetchQuota from the quota Zustand store.

[Copilot]

Because this component is rendered inside AppShell even while auth is still isLoading (see FilesPage/SettingsPage), this effect will run before the user is authenticated. That can trigger an unnecessary /vault/quota request (and potentially a refresh-token flow + store resets on refresh failure) when there is no session. Consider gating the call so it only runs once the user is authenticated / has an access token, and add a simple guard to avoid double-fetch in React 18 StrictMode (effects run twice in dev).