v0.8.0 - Org-Managed Copilot Support

New Features

• Org-managed Copilot usage — Falls back to the authenticated Copilot settings page when the personal billing API is unavailable, so Chrome profiles on organization-managed Copilot report premium request usage. (PR #13 by @gustavobragac) (v0.7.1)
• All Chromium profiles in the Copilot fallback — The fallback now walks every profile under ~/.config/google-chrome and the Chromium and Brave equivalents, using the first one whose settings page renders the usage section instead of only Default. Enterprise seats living in a secondary profile no longer report "no copilot usage section found". (PR #15 by @gustavobragac) (v0.7.2)

Bug Fixes

• Codex request fingerprint — Requests impersonate the browser the cookies came from rather than always impersonating Chrome. (PR #16 by @bdbd2yy) (v0.7.3)
• Codex usage windows — The 5-hour and weekly windows are identified by limit_window_seconds instead of the API's primary_window/secondary_window ordering, and the weekly window is used when the 5-hour one is absent. (PR #17 by @bdbd2yy) (v0.7.4)
• Firefox cookies alongside a stale legacy profile — The XDG fallback also runs when browser_cookie3 returns an empty jar, which happens when ~/.mozilla/firefox holds a readable profile with no cookies for the domain while the real profile lives under ~/.config/mozilla/firefox. (PR #18 by @zackkitzmiller)

Other

• Copilot: lowercased the "no copilot usage section" message so it matches the auth-error check (PR #15 by @gustavobragac)
• README overhaul with the formatting reference extracted, plus an AUR version badge
• release.sh now refreshes uv.lock, which had been pinned at 0.6.2