fix(ci): raise AVM check-circuit input timeout

[AztecBot]

Summary

• raise the AVM dumped-input check-circuit timeout from 30s to 90s
• add AVM_CHECK_CIRCUIT_TIMEOUT so the nightly can be tuned without editing the script

Root cause

The failed run was not a circuit satisfiability failure. The avm-check-circuit job timed out on e2e_multiple_blobs/avm-circuit-inputs-tx-0x1b2597a576f510f7d689e23c796797a3bb1bcc0e4626947cb349844412ca1327.bin while checking a 700,560-row AVM circuit. The per-input wrapper had a fixed TIMEOUT=30s; this large dumped e2e input reached Checking circuit... and was killed by timeout after 30s.

Evidence:

• GitHub run: https://github.com/AztecProtocol/aztec-packages/actions/runs/27456524905
• Internal log: http://ci.aztec-labs.com/1781326240429639
• Failed command log: http://ci.aztec-labs.com/f3f6e18efbf69f32

Verification

• bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
• git diff --check
• smoke-tested ./bootstrap.sh avm_check_circuit_cmds with a temporary dumped input and confirmed default TIMEOUT=90s
• smoke-tested AVM_CHECK_CIRCUIT_TIMEOUT=45s ./bootstrap.sh avm_check_circuit_cmds and confirmed override TIMEOUT=45s

Note: the local smoke commands emitted expected cache/Docker warnings because this container cannot reach remote Redis or Docker, but the command-generation path completed.

---

Created by claudebox · group: slackbot

[AztecBot]

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/14b0e1f3fe2dea9e�14b0e1f3fe2dea9e8;;�): yarn-project/kv-store/scripts/run_test.sh src/sqlite-opfs/internal/ordered-binary-browser.test.ts (1s) (code: 0)

[AztecBot]

Automatically closing this stale claudebox draft PR (no updates for 5+ days). Re-open if still needed.