GeezerVison

Same fix as uniswap-python#479 — the v1 UNI exchange has no remaining liquidity so
get_price_output raises EVM error InvalidJump on mainnet fork.

Git-Session-Id: 8f77

… grant D3/D4) (#480)

* feat(metrics): adoption baseline snapshot script and daily workflow

Adds scripts/adoption_snapshot.py (stdlib-only) that captures:
- GitHub stars, forks, watchers, open issues
- GitHub Traffic: clones/views (14-day window; requires push-access token
  — the bundled GH Actions workflow captures this automatically)
- PyPI downloads last day/week/month (pypistats.org)
- Recent release versions and dates

Modes:
  Snapshot (default): emits metrics/adoption-YYYY-MM-DD.{json,md}
  Report (--report BASELINE.json): prints deltas vs baseline for D4

Also adds .github/workflows/adoption-snapshot.yml (daily at 06:00 UTC)
that runs with the repo's GITHUB_TOKEN so traffic data accumulates before
the 14-day window rolls off.

Initial bootstrap snapshot included (2026-09-02): 1011 stars, 375 forks,
1044 PyPI downloads/month.

Per-version download splits require BigQuery (documented in script TODO).

Co-authored-by: Erik Bjäreholt <[email protected]>
Git-Session-Id: 3b38

* fix(metrics): fail closed on traffic auth and collector errors

The default Actions GITHUB_TOKEN cannot read /traffic/* (always 403).
The workflow now prefers ADOPTION_GITHUB_TOKEN (PAT), runs --strict so
failed/skipped collectors do not commit N/A snapshots, retries 429s,
and includes traffic deltas in --report. Push path rebases on conflict.

* test: xfail v1 UNI-exchange price-output cases (no liquidity)

Same fix as #479 — the v1 UNI exchange has no remaining liquidity so
get_price_output raises EVM error InvalidJump on mainnet fork.

Git-Session-Id: 8f77

* fix(metrics): reconstruct traffic period totals from daily series

GitHub Traffic is a rolling 14-day window, not a cumulative counter.
Subtracting two windows produced misleading D4 deltas. Store the daily
breakdown (per=day) and union it across snapshots for period clone/view
counts. Unique visitors stay point-in-time — they are not additive.

* fix(metrics): exclude partial current UTC day from period totals

Report mode included today's still-accumulating GitHub Traffic row in
D4 period totals, understating clones/views on every 06:00 UTC run.
Drop that day from the reconstructed range and label it excluded.

* fix(metrics): pin collection clock so midnight cannot include a partial day

complete_period_end() re-read datetime.now() after collect_metrics() had
already stamped snapshot_at. A report that started before UTC midnight and
finished after kept the earlier snapshot day, skipped exclusion, and
published that day's still-accumulating Traffic row as a complete total.

Use one collected_at for snapshot_at, the filename, and period-end
exclusion. When now is omitted, key off the snapshot day rather than a
fresh clock.

---------

Co-authored-by: Erik Bjäreholt <[email protected]>