chore(release): release v0.4.1

[acgetchell]

• Bump version to v0.4.1
• Update changelog with latest changes
• Update benchmark comparison table
• Update documentation for release

Summary by CodeRabbit

• New Features

  • Enhanced benchmarking workflows with cross-library comparisons and result plotting.
  • Expanded property-based testing for exact arithmetic operations.

• Documentation

  • Added comprehensive Design Principles section covering API stability and testing standards.
  • Updated testing and benchmarking workflow documentation.

• Performance

  • Optimized forward elimination through improved arithmetic operations.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR releases version 0.4.1 by updating all metadata files (Cargo.toml, CITATION.cff), documentation (AGENTS.md, CHANGELOG.md, README.md, BENCHMARKING.md), and benchmark results to reflect the new version. Design principles are added to AGENTS.md and benchmark tables are refreshed with updated performance metrics.

Changes

Cohort / File(s)	Summary
Version Metadata Cargo.toml, CITATION.cff	Version incremented from 0.4.0 to 0.4.1 across all package metadata.
Release Documentation CHANGELOG.md	Converts "Unreleased" section to v0.4.1 release entry (2026-04-21) with entries for exact-determinant sign fast-filter proptests, documentation/benchmarks/error-handling finalization, and performance improvements in integer-only forward elimination for gauss_solve.
README & Quickstart README.md	Updates documented crate versions to 0.4.1 in Cargo.toml snippets and refreshes LU solve benchmark table values across dimensions D = 2–64.
Developer Documentation AGENTS.md	Adds new "Design Principles" section covering invariants, API stability, composability, and test coverage. Updates command references from v0.3.0 to v0.4.1, introduces new benchmarking workflow commands (nalgebra/faer comparison, plotting), adds tag-force variant, and refines testing documentation to clarify unit test location and property-based testing approach.
Benchmarking Docs docs/BENCHMARKING.md	Updates just task invocations to reference v0.4.1 baselines for bench-save-baseline and bench-compare commands.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore(release): release v0.4.0 #75 — Performs sequential release updates to the same metadata/docs files in parallel version bump workflow.
• feat: exact linear system solve (solve_exact, solve_exact_f64) #48 — Documents the exact-arithmetic solve_exact refactoring to hybrid Bareiss forward elimination referenced in this release's changelog and design notes.
• test: add adversarial-input coverage for exact arithmetic (#80) #97 — Implements exact-feature benchmarks, prelude re-exports, and adversarial-bench groups that are documented and versioned in this release PR.

Suggested labels

documentation

Poem

🐰 Version bumps and docs align,
0.4.1 shines so bright,
Benchmarks updated, benchmarks fine,
Release ready—what a sight! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(release): release v0.4.1' accurately and clearly describes the main change—a version release bump to v0.4.1, which is reflected across all modified files including Cargo.toml, CHANGELOG.md, CITATION.cff, and documentation updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.4.1

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.40%. Comparing base (150678a) to head (1478c19).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #99   +/-   ##
=======================================
  Coverage   91.40%   91.40%           
=======================================
  Files           5        5           
  Lines         512      512           
=======================================
  Hits          468      468           
  Misses         44       44           

Flag	Coverage Δ
unittests	91.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

CHANGELOG.md (1)

8-52: ⚠️ Potential issue | 🟠 Major

Do not edit CHANGELOG.md manually. Regenerate it via just commands.

These edits should be produced by the changelog tooling, not hand-edited. Please regenerate using just changelog (or just changelog-unreleased <version> when applicable) so the file remains tool-authoritative.

As per coding guidelines, "Never edit CHANGELOG.md directly - it's auto-generated from git commits. Use just changelog to regenerate. Use just changelog-unreleased <version> to prepend unreleased changes."

Also applies to: 277-277

🤖 Prompt for AI Agents

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

In `@CHANGELOG.md` around lines 8 - 52, The CHANGELOG.md was edited manually;
revert manual edits and regenerate the file using the project's changelog
tooling instead — run the just task (either just changelog or just
changelog-unreleased <version> when adding a new version) to produce the
authoritative CHANGELOG.md so it matches the commit history and tooling
expectations.

🤖 Prompt for all review comments with AI agents

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

Outside diff comments:
In `@CHANGELOG.md`:
- Around line 8-52: The CHANGELOG.md was edited manually; revert manual edits
and regenerate the file using the project's changelog tooling instead — run the
just task (either just changelog or just changelog-unreleased <version> when
adding a new version) to produce the authoritative CHANGELOG.md so it matches
the commit history and tooling expectations.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 96f2d3c5-462c-4997-aadf-5b75655f0e7d

📥 Commits

Reviewing files that changed from the base of the PR and between 150678a and 1478c19.

⛔ Files ignored due to path filters (3)

• Cargo.lock is excluded by !**/*.lock
• docs/assets/bench/vs_linalg_lu_solve_median.csv is excluded by !**/*.csv
• docs/assets/bench/vs_linalg_lu_solve_median.svg is excluded by !**/*.svg

📒 Files selected for processing (6)

• AGENTS.md
• CHANGELOG.md
• CITATION.cff
• Cargo.toml
• README.md
• docs/BENCHMARKING.md