mask-risc: charge strided predicates' extra passes in op_histogram

[AdaWorldAPI]

Follow-up to #1284, fixing the Codex P2 on it.

The problem. The strided predicates have no *_under kernel. So the executor runs a gated one as the strided kernel followed by mask_and_assign. NeU32Strided is also always the eq kernel followed by mask_not_assign. Program::op_histogram sent all three through the generic predicate arm, so mask_passes() under-reported:

• gated Eq and gated Match by one pass;
• Ne by one pass ungated, and two when gated.

The fix. They are now charged the same way the gated Range already is: the gate's and goes to two_input, and Ne's complement goes to not.

Tests.

• op_histogram_charges_the_strided_predicates_extra_passes pins every case, plus the silence twin: an ungated Eq or Match is one predicate and zero mask passes.
• Disable-verified: dropping the new arm fails the test.
• cargo test -p lance-graph-mask-risc: 122 passed. Clippy and fmt are clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DCEP2fZdHYdMCtcEVcTpS2

---

Generated by Claude Code

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 16ed8c9d-5d7e-4fb4-b997-1c75b81d30da

📥 Commits

Reviewing files that changed from the base of the PR and between c1ed7ff and d588ebb.

📒 Files selected for processing (1)

• crates/lance-graph-mask-risc/src/ir.rs

 _______________________________________________________________
< Your null checks are like seatbelts: installed, but not worn. >
 ---------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

---

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_d92d05cf-4ddb-4ba7-a8a3-0ebf3f7f7e3c)