Fixture provenance for quse==0.0.17 (the `gemini` provider)

Source package: the PyPI wheel quse-0.0.17-py3-none-any.whl
PyPI upload: 2026-10-02T08:56:21Z
Wheel SHA-256: 4baff11a89650db44d89908fd43cdac3357f369a062a9f6eb0f7d581f62884ea
Upstream change: the `gemini` provider (aliases `antigravity` / `agy`),
  querying the Antigravity CLI (`agy`) non-interactive harness; its 5-hour
  and weekly quota buckets map to the canonical `5h` / `7d` windows, and
  `details.groups` carries the per-group bucket breakdown.

Capture command (using the wheel bundled with pocketshell 0.5.8 after the
tool-venv quse was upgraded to 0.0.17):
  ~/.local/share/uv/tools/pocketshell/bin/quse gemini --json
Captured: 2026-10-04 on the maintainer's hetzner dev box (real live quota).

Observed published contract:
  providers (single-provider capture): gemini
  record fields: details, error, status, windows
  the record carries the canonical top-level `windows` map keyed by
  quse.usage.CANONICAL_WINDOWS = ("5h", "7d", "monthly"); the `5h` entry also
  carries `rolling: false`. A span that does not apply to the provider is
  present with `percent_remaining: null` rather than omitted.
  no `short_term` / `long_term` fields on the record
  `details.groups` is provider-owned detail — `normalize_usage_stdout`
  forwards it verbatim, exactly like every other provider's details.

This capture is the passthrough fixture for the seventh provider: the host
boundary injects the `provider` key and forwards the record unchanged, so the
usage panel (phone and desktop) renders Antigravity without PocketShell-side
provider logic.
