test(zigux): add lane16 findNextAndBit replay runner

[adybag14-cyber]

Summary

• add zigux/tests/phase1_find_next_and_bit_bench_replay_build.zig as the dedicated Lane 16 build shard for the existing findNextAndBit(...) bench replay on PR test(zigux): add lane16 find_next_and_bit bench replay #13551
• expose a named phase1-find-next-and-bit-bench-replay route plus a plain test alias
• keep the change one-file scoped and stacked, with no edits to the replay body, helper implementations, aggregate Phase 1 bench files, checker scripts, docs, fixtures, or workflows

Why This Lane

• Lane 16 owns Phase 1 hardening gates around bench-sensitive helper packets
• PR test(zigux): add lane16 find_next_and_bit bench replay #13551 already carries the standalone phase1_find_next_and_bit_bench_replay.zig witness, but that replay did not yet have the newer direct zig build route pattern
• this runner makes the findNextAndBit(...) replay directly runnable without widening zigux/tests/phase1_bench_build.zig or tools/lib/find_bit.zig

Validation

• authenticated base PR reread confirmed zigux/tests/phase1_find_next_and_bit_bench_replay.zig exists on branch zigux-builder/lane16-find-next-and-bit-bench-replay-current-master-20260528t0933z
• authenticated search found no existing phase1_find_next_and_bit_bench_replay_build PR before this publication
• focused scratch validation used the attached Zigux-master.zip scaffold plus the attached Zig 0.17.0-dev.87+9b177a7d2 toolchain because direct live checkout remains blocked in this scheduled runtime
• zig fmt --check zigux/tests/phase1_find_next_and_bit_bench_replay.zig zigux/tests/phase1_find_next_and_bit_bench_replay_build.zig tools/lib/find_bit.zig
• cd zigux/tests && zig build --build-file phase1_find_next_and_bit_bench_replay_build.zig --list-steps
  • result: step list includes phase1-find-next-and-bit-bench-replay and test
• cd zigux/tests && zig build phase1-find-next-and-bit-bench-replay --build-file phase1_find_next_and_bit_bench_replay_build.zig --summary all
  • result: Build Summary: 3/3 steps succeeded; 2/2 tests passed
• cd zigux/tests && zig build test --build-file phase1_find_next_and_bit_bench_replay_build.zig --summary all
  • result: Build Summary: 3/3 steps succeeded; 2/2 tests passed
• authenticated compare after publication against PR test(zigux): add lane16 find_next_and_bit bench replay #13551 branch:
  • changed files: 1
  • result: ahead_by: 1
  • result: behind_by: 0
  • result: status: ahead

Scope

• lane: Lane 16 — Phase 1 hardening gates
• session issue: Zigux session 2026-05-29 09:30 UTC lane16 findNextAndBit runner #14976
• base PR: test(zigux): add lane16 find_next_and_bit bench replay #13551
• branch: zigux-builder/lane16-find-next-and-bit-replay-runner-20260529t0930z
• file:
  • zigux/tests/phase1_find_next_and_bit_bench_replay_build.zig

Coordination

• keep PR test(zigux): add lane16 find_next_and_bit bench replay #13551 as the replay-body base for this stacked runner
• keep PR test(zigux): add lane16 find_next_zero_bit bench replay runner #14031 as the separate findNextZeroBit(...) replay runner frontier
• keep PR test(zigux): add lane16 find_bit edge bench replay runner #13915 as the separate find-bit edge replay runner frontier
• keep PR test(zigux): add lane16 rbtree findAddCached replay runner #14922 as the separate rbtree findAddCached(...) replay runner frontier
• keep PR test(zigux): add lane16 rbtree findAdd replay runner #14806 as the separate non-cached rbtree findAdd(...) replay runner frontier
• keep PR test(zigux): add lane16 rbtree postorder replay runner #14749 as the separate rbtree postorder replay runner frontier
• keep checker and aggregate bench packet fronts untouched

Validation Boundary

Direct live checkout remains unavailable in this scheduled container, so live repo grounding and publication used authenticated GitHub reads/writes plus focused snapshot-backed local validation.

[coderabbitai]

Important

Review skipped

Draft detected.

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 590d8fa5-2387-4c05-b238-a7e4bae07091

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch zigux-builder/lane16-find-next-and-bit-replay-runner-20260529t0930z

---

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 and usage tips.}