Build verify binaries without debuginfo#1807

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 1b5fa4cb-8d6a-4c0c-9a7d-2d7f555647a8

📥 Commits

Reviewing files that changed from the base of the PR and between 120f54531c5107aedee6d42c3a8cd57e8143600c and c6024d591f19743cfcbc1931cd3634c14e4d58cf.

📒 Files selected for processing: 1

• core/scripts/verify-cluster

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 1 remain after this review.

Summary by CodeRabbit

• Chores
  • Development-profile builds now omit debug information.

The cluster verification build now sets CARGO_PROFILE_DEV_DEBUG=0 for Cargo. It retains the existing build arguments and timeout.

Changes: Cluster verification build

Layer / File(s)	Summary
Set build environment core/scripts/verify-cluster	The build function sets CARGO_PROFILE_DEV_DEBUG=0. Comments state that binaries are stripped and CI uses the same setting.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

This change disables development debug information for the verification build, matching cluster CI. No merge-blocking risk is evident.

Systems and components

• observed — core (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in core/scripts/verify-cluster: build now passes CARGO_PROFILE_DEV_DEBUG=0 to Cargo while retaining the existing build arguments and timeout; the added comments state that binaries are stripped and CI uses the same setting.

^Passed Passed checks: 5 passed

Check name	Status	Explanation
Title check	Passed	The title clearly and concisely describes the main change: disabling debuginfo when building verification binaries.
Description check	Passed	The description explains that the verification build skips debuginfo because the binaries are stripped after compilation, and it provides performance and size measurements.
Docstring Coverage	Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	Passed	Check skipped because no linked issues were found for this pull request.

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.