fix: meter actual contract snapshot size

[MuncleUscles]

What changed

• meter current_state.data directly for the daily contract snapshot quota
• remove the extra 2× multiplier because the row already contains accepted and finalized state
• update unit and database-backed regression expectations

Why

Production measurements show current_state.data and transactions.contract_snapshot are approximately the same size. The previous multiplier double-counted the expected storage cost.

Impact

Quota values now correspond to actual stored snapshot bytes. This enables a 256 MiB/day production budget that applies meaningful backpressure without fully disabling the existing large contract.

Validation

• .venv/bin/python -m pytest -q tests/unit/test_contract_storage_quota.py — 9 passed
• commit hooks: Black, autoflake, whitespace, merge-conflict and file-size checks passed
• database-backed quota tests left to CI because local POSTGRES_URL is not configured

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 54737906-5405-41cb-aefb-e213c01725a0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
80.7% Coverage on New Code
1.4% Duplication on New Code

See analysis details on SonarQube Cloud