Doc and release notes updates

[rgsl888prabhu]

Description

This PR adds Release notes updates and documentation updates which goes in as last PR in the release.

Checklist

• I am familiar with the Contributing Guidelines.
• Testing
  • New or existing tests cover these changes
  • Added tests
  • Created an issue to follow-up
  • NA
• Documentation
  • The documentation is up to date with these changes
  • Added new documentation
  • NA

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Inserted a new top-level "Release Notes 26.04" section at the start of RELEASE-NOTES.md, adding populated subsections for New Features, Improvements, Bug Fixes, and empty headings for Breaking Changes and Documentation. No code, API, or exported-entity changes.

Changes

Cohort / File(s)	Summary
Release Notes — top section RELEASE-NOTES.md	Added "Release Notes 26.04" with populated New Features (26.04), Improvements (26.04), and Bug Fixes (26.04) bullets (solver behaviors, new MIP cuts, PDLP option, numerics/reliability branching changes, runtime/variable reductions, specific fixes). Added empty Breaking Changes (26.04) and Documentation (26.04) headings. Markdown-only; no code/API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Doc and release notes updates' is directly related to the changeset, which adds a new Release Notes 26.04 section and documentation updates to RELEASE-NOTES.md.
Description check	✅ Passed	The description clearly indicates this PR adds release notes updates and documentation updates, which aligns with the changes shown in the raw summary of RELEASE-NOTES.md modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@RELEASE-NOTES.md`:
- Around line 3-14: Populate the "## Release Notes 26.04" block by filling each
subsection header (### New Features (26.04), ### Breaking Changes (26.04), ###
Improvements (26.04), ### Bug Fixes (26.04), ### Documentation (26.04)) with the
actual changes introduced by this PR: list new features added (feature names and
brief bullets), enumerate breaking changes with affected APIs/signatures and
migration notes, summarize performance or UX improvements, describe bug fixes
with component names and brief symptom/fix lines, and note documentation updates
(pages or topics updated); mirror the style and level of detail used in the
existing "Release Notes 26.02" entries so readers can understand what changed in
26.04.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a0093db2-4d7e-4206-b29f-3af572083578

📥 Commits

Reviewing files that changed from the base of the PR and between 9f50244 and 3cd5d8a.

📒 Files selected for processing (1)

• RELEASE-NOTES.md

[anandhkb]

Change to:

Do not run relaxation heuristics before presolve

[chris-maes]

It's correct as written. A "No relaxation" heuristic is one that runs without solving the LP relaxation.

[anandhkb]

Change to:

Expose parameters for tuning heuristics

[anandhkb]

Change to:

Add new MIP cuts: clique cuts and implied bounds cuts