always enable KJ_IREQUIRE checks

[mikea]

This matches our configuration in production.

[ask-bonk]

The PR has already been approved by two reviewers (danlapid and fhanau). Let me review the actual change one more time carefully:

The change is a 2-line addition to .bazelrc:

1. A comment: # always have KJ_IREQUIRE checks enabled, this matches workers production.
2. A build flag: build --@capnp-cpp//src/kj:kj_enable_irequire=True

This enables KJ_IREQUIRE checks across all build configurations. KJ_IREQUIRE is used in 4 places in the workerd codebase (wait-list.h, string-buffer.h, wrappable.h, actor-cache.h) as internal requirement checks. The PR states this matches production configuration. The config:opt section does not override this flag (unlike debug_memory which is explicitly set to False in opt), meaning KJ_IREQUIRE will remain enabled in optimized/release builds too - which is the correct intent.

This is a straightforward, low-risk configuration change that aligns dev/CI builds with production. No backward compatibility concerns, no security implications, no API changes. Already approved by two collaborators.

LGTM

github run

[codspeed-hq]

Merging this PR will degrade performance by 17.67%

❌ 1 regressed benchmark
✅ 69 untouched benchmarks
⏩ 129 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	Parse[KjHeaders]	44.5 µs	54.1 µs	-17.67%

---

_{Comparing maizatskyi/2026-03-11-enable-irequire (b60f430) with main (755795d)}

Footnotes

1. 129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩