feat: change notifications to be a daily summary

[maximopalopoli]

Description

This PR introduces a daily summary script of the proofs submitted by the periodic sender.

This script generates a summary of the file corresponding to the current day in the alerts/notification_logs folder.

To run this script using cron, use the following command:

(crontab -l 2>/dev/null; echo "00 00 * * * /path/to/aligned/repo/alerts/generate_send_summary.sh /path/to/aligned/repo/alerts/.env.devnet") | crontab -

Note that you should change the /path/to/aligned/ placeholder with the actual path to aligned on your computer.

How to test (devnet)

To have some entries to test the generator, first, we are running the periodic sender for a few minutes. To do it, I recommend reducing the sleep_time in the periodic sender before starting. After it, you should fund the account used in the script to send the proofs. You can do it by running:

aligned deposit-to-batcher \
--network devnet \
--rpc_url http://localhost:8545 \                                
--amount 15ether \
--private_key 0x4bbbf85ce3377467afe5d46f804f221813b2bb87f24d81f60f1fcdbf7cbf4356

Now we can run the script by using the following:

./alerts/periodic_sender.sh alerts/.env.devnet

After a few minutes, you should see a few logs in the file alerts/notification_logs/log_2025_11_03.txt (or the one corresponding to the date you test this PR). You can shut down the operator to have unverified proofs in the summary, but it's not really necessary.

To generate the summary, run the following command:

./alerts/generate_send_summary.sh alerts/.env.devnet

This will output the summary on the terminal, but you can test it on Slack by setting the SLACK_WEBHOOK_URL in the .env.devnet file.

Checklist

• “Hotfix” to testnet, everything else to staging
• Linked to Github Issue
• This change depends on code or research by an external entity
  • Acknowledgements were updated to give credit
• Unit tests added
• This change requires new documentation.
  • Documentation has been added/updated.
• This change is an Optimization
  • Benchmarks added/run
• Has a known issue
  • Link to the open issue addressing it
• If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
  • This PR adds compatibility for operator for both versions and do not change crates/docs/examples
  • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible