fix(statusline): fix f-string syntax error silently breaking reset time display

[jlacour-git]

Summary

• Fixes a Python f-string SyntaxError in the batch usage reset time eval that silently breaks all four reset-time variables (reset_5h, reset_7d, clock_5h, clock_7d) for all users with valid OAuth tokens
• The error is swallowed by 2>/dev/null, so users see ↻— instead of a real reset time with no indication anything is wrong

Closes #779

Root Cause

# Before — SyntaxError: double quotes inside double-quoted f-string (Python < 3.12)
print(f"clock_5h='{clock_time(r5h, "hourly")}'")
print(f"clock_7d='{clock_time(r7d, "weekly")}'")

Because the entire python3 -c "..." invocation is wrapped in 2>/dev/null, the SyntaxError is silently discarded. The eval receives no output, all variables stay empty, and the statusline falls back to — for every reset time.

Fix

# After — single quotes inside double-quoted f-string, valid Python 3.6+
print(f"clock_5h='{clock_time(r5h, 'hourly')}'")
print(f"clock_7d='{clock_time(r7d, 'weekly')}'")

Single-quoted string literals inside a f"..." f-string are valid since Python 3.6. No behavior change — just fixes the silent crash.

Test Plan

• Confirm reset_5h and reset_7d are populated after the eval (e.g. 4h32m, 2d23h)
• Confirm statusline usage line shows ↻4h32m instead of ↻—
• Verify no regression when OAuth token is absent (falls back to — as before)

🤖 Generated with Claude Code

[kaimagnus]

Good catch on the nested quoting — this is fixed in v4.0.1. Changed the escaped double quotes to single quotes inside the f-strings. Closing as the fix is included in the release.