fix: queue manual refresh while busy

[ericweichun]

Summary

• queue one manual refresh when the user clicks Refresh while a background refresh is already running
• clear the in-flight flag in a finally block so UI update failures do not permanently block future refreshes
• run the queued refresh immediately after the current refresh result is applied

Test plan

• .venv/bin/python -m ruff check menubar.py tests/test_menubar.py
• .venv/bin/python -m mypy .
• .venv/bin/python -m pytest tests/test_menubar.py

Notes for reviewer

This only changes explicit manual refresh behavior. Timer and FSEvents refresh calls still coalesce while a refresh is in flight.

[aqua5230]

Behavior change is solid and the tests are real. One blocker against current main: _applyRefreshResult_ in v0.11.6
(commit ba66688) now also writes self.codex_model, and the ivar declaration on AppDelegate added codex_model.
Could you rebase onto main and make sure the queued-refresh finally block preserves both self.codex_model = result.get("codex_model", "unknown") and the existing language-injection step? After rebase this should be straight to
merge.

[ericweichun]

Updated, thanks. I rebased onto current main and resolved the refresh queue patch around the v0.11.6 state update path. The queued-refresh finally block now preserves both self.codex_model = result.get("codex_model", "unknown") and the existing language injection step before clearing the busy flag and draining one queued refresh.\n\nValidation run locally:\n- .venv/bin/python -m pytest tests/test_menubar.py\n- .venv/bin/python -m ruff check menubar.py tests/test_menubar.py\n- .venv/bin/python -m mypy .