chore(stables): remove Dune-backed large-transfer monitor

[spalen0]

Summary

Removes the stables-dune-large-transfers monitor and every reference to Dune in the repo. It was the only script using Dune.

Why

The hourly task fails on every run:

[stables] Dune large-transfer monitor failed while querying Dune: Can't build ExecutionResponse from {'error': 'This performance tier is not available with your subscription. Please upgrade your subscription plan here: https://dune.com/pricing'}

The script already defaulted to the free cluster (DEFAULT_PERFORMANCE_TIER = "free"), so this is a plan/billing limit rather than something a config change fixes. Rather than keep a permanently-failing task, remove it.

Note the failures were never blocking other monitors — automation/runner.py continues on per-task failure and the script caught its own exception — so this is noise cleanup, not an outage fix.

Changes

File	Change
protocols/stables/dune_large_transfers.py	deleted
tests/test_dune_large_transfers.py	deleted
automation/jobs.yaml	dropped the task from the hourly profile
monitoring.yaml	dropped the task path + "Large Transfers" monitor; updated the stables description
.env.example	removed the four DUNE_* vars
pyproject.toml / uv.lock	removed dune-client==1.7.10, lock regenerated

protocols/stables/ has no README, so nothing to update there. The lone remaining "Dune" string is a docstring in utils/address_resolver.py listing hypothetical future label sources — not a dependency.

Coverage impact

This drops >=$5M transfer alerts for cUSD (0xcccc62962d17b8914c62d74ffb843d73b2a3cccc, routed to cap) and iUSD (0x48f9e38f3070ad8945dfeae3fa70987722e3d89c, routed to infinifi). Nothing else in the repo covers large transfers for those tokens. Porting to the Envio-backed pattern in protocols/usdai/large_mints.py is the follow-up if we want the signal back — happy to close this instead if we'd rather upgrade the Dune plan.

Verification

• uv run --extra dev pytest -q -> 855 passed, 4 skipped, 5 subtests passed. The tests/test_monitoring_config.py consistency checks pass, so jobs.yaml and monitoring.yaml stay in sync.
• uv run --extra dev ruff check . -> clean.
• uv lock --check -> in sync, so the deploy's uv sync --frozen won't break.
• python -m automation run hourly --dry-run -> all 25 remaining hourly tasks still listed, Dune gone; other four profiles untouched.
• mypy reports one pre-existing error on main (Duplicate module named "main" between protocols/aave and protocols/3jane), unrelated to this change.

Deploy note

Per the header comment in automation/jobs.yaml, dependency changes still need a manual uv sync --frozen --extra ai + systemctl restart monitoring on the box. DUNE_API_KEY should also be removed from the deployment's real env/secrets.

🤖 Generated with Claude Code