feat: add Maple GovernorTimelock to timelock monitoring

[spalen0]

Summary

• Add Maple GovernorTimelock (0x2eFFf88747EB5a3FF00d4d8d0f0800E306C0426b) to cross-protocol timelock monitoring
• Handles Maple timelock type with absolute timestamp delay (like Compound/Puffer) and proposalId display
• Add --protocol flag to filter events by protocol (e.g. --protocol MAPLE)
• Updates timelock README: add Maple to all type lists, complete monitored timelocks table with full addresses, fix docs defaults

Dependency

• Requires Envio indexer update: feat: add Maple GovernorTimelock indexing chain-events/yearn-indexing-test#5 (must be deployed first)

Connection

The flow is:

1. Envio indexer indexes ProposalScheduled events from Maple GovernorTimelock → stores as TimelockEvent with timelockType: "Maple"
2. This script (timelock_alerts.py) queries Envio for TimelockEvent where timelockAddress matches → formats alert with proposalId and delay → sends to TELEGRAM_CHAT_ID_MAPLE

Test results

Verified Envio indexer returns all Maple events:

$ uv run python -m timelock.timelock_alerts --protocol MAPLE --no-cache --since-seconds 31536000 --log-level DEBUG --limit 500

Filtering to protocol MAPLE: 1 timelocks
Fetched 12 TimelockEvent events
Processing 12 operations from 12 events

All 12 ProposalScheduled events (proposals 1–12) fetched successfully, matching on-chain data. Alert formatting works correctly with proposal IDs and executable delay display.

Test plan

• Deploy indexer update (feat: add Maple GovernorTimelock indexing chain-events/yearn-indexing-test#5)
• Verify events appear in Envio GraphQL for the Maple address (12 events confirmed)
• Run --protocol MAPLE --no-cache --since-seconds 31536000 --log-level DEBUG — 12 events fetched and formatted

🤖 Generated with Claude Code