chore(bb): refresh pinned Chonk IVC inputs after protocol-circuit changes

[AztecBot]

What

Trigger a refresh of the pinned Chonk IVC inputs (barretenberg/cpp/scripts/chonk-inputs.hash) via the ci-refresh-chonk label. CI regenerates the inputs from the current protocol circuits, uploads the new tarball to S3, proves one small refreshed flow in C++ and bb.js, and pushes the updated hash back onto this branch.

The only meaningful diff this PR introduces is the refreshed chonk-inputs.hash (the trailing-newline tweak below is just a placeholder so the branch has a diff for CI to overwrite).

Why — root cause of the nightly debug build failure

Nightly Debug Build run 26676520589 failed in bbapi_tests ChonkPinnedIvcInputsTest.AllPinnedFlows with:

Assertion failed: (kernel_return_data_match)
Reason: kernel_return_data mismatch: proof contains
  { 0x1832...7ea4, 0x0 } but kernel_calldata commitment is { 0x..01, 0x..02 }

This is the databus consistency check in barretenberg/cpp/src/barretenberg/chonk/chonk.cpp (process_public_inputs_and_consistency_checks). It is guarded by BB_ASSERT_DEBUG, which is compiled out of release/default builds — so only the nightly debug build exercises it, which is why regular PR CI was green. The {1,2} commitment is the BN254 generator, i.e. an empty databus column, while the proof carries real return data: the frozen pinned flow no longer reconstructs consistently against the current protocol circuits.

Timeline:

• 2026-05-21 — inputs pinned at hash 209dde8e69a27c9f.
• 2026-05-28 — fix(bb): store pinned Chonk inputs under barretenberg as chonk-pinned-flows, downloaded once at build #23644 switched this debug test from freshly-captured e2e inputs (example-app-ivc-inputs-out) to the frozen S3 tarball (barretenberg/cpp/chonk-pinned-flows).
• 2026-05-29 — breaking protocol-circuit PRs landed without refreshing the pin: feat!: shift remaining protocol-contract addresses to 1-3 #23218 (shift protocol-contract addresses to 1-3), feat!: demote multi_call_entrypoint to non-protocol contract #23197 (demote multi_call_entrypoint), feat(aztec-nr)!: remove set_sender_for_tags oracle, use builder pattern for sender override #23619 (remove set_sender_for_tags oracle), plus constants.nr / address / public-key packing changes. The C++ chonk verifier itself was unchanged in this window.
• 2026-05-30 — nightly debug build fails on the stale pinned inputs.

The pinned inputs are meant to track the protocol circuits; the breaking PRs should have carried ci-refresh-chonk but were merged via release CI where the debug assert is absent. This PR performs the missing refresh.

Verification

CI's ci-refresh-chonk post-action regenerates the inputs and proves the smallest refreshed flow in both C++ and bb.js before committing the new hash, which directly reproduces and clears the failing assertion. After the bot pushes the refreshed hash, confirm the run is green before merging.

---

Created by claudebox · group: slackbot