* Fixed typing of arithmetic methods

* changes based on pr comments

* Changes to typing

* Further typing changes

* fixed test

* added tests

* Went down a rabbit hole

* fixed tests

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* fixed coverage

* fixed precommit issue

* fixed test

* formatting

* Added tests to improve code coverage

* minor changes

* Deprecated using single-value tuple for LinearExpression.from_tuples

* added tests to improve code coverage

* improved code coverage a tiny bit more

* fixed mypy warnign

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* minor changes

---------

Co-authored-by: Robbie Muir <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

* remove python 3.9 deps

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* Fix mypy type checking issues

- Add type assertion in expressions.py to clarify pandas Series type
- Keep necessary type: ignore[assignment] comments in test files where intentional type mismatches are tested
- Remove Python 3.9 from classifiers in pyproject.toml (was part of staged changes)
- Update model.py and expressions.py to use union types with | operator

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* apply type hint convention for python >= 3.10

* fix: remove type hint ignores

* fix: corrent expected exception in test

* add release note

* fix: resolve remaining mypy type errors in COPT solver

Fix type compatibility issues in solvers.py:
- Convert condition to string for Status.from_termination_condition()
- Ensure legacy_status assignment matches expected str type

Resolves the final mypy errors, completing issue #367.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Claude <[email protected]>

* Update pyproject.toml

* remove deprecated fill_value

* Update release_notes.rst

---------

Co-authored-by: Fabian <[email protected]>

* Claude PR Assistant workflow

* Claude Code Review workflow

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* add CLAUDE.mc

* add time limit and filtering conditions for claude code GH actions

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

* fix: Allow COPT solution parsing for IMPRECISE status

Add 'numerical' and 'imprecise' as proper TerminationCondition enum values
and map them to SolverStatus.ok to enable solution extraction for both
COPT solver statuses. 

This fixes issue #460 where COPT solutions with IMPRECISE status were
not being parsed, even though COPT developers confirmed solutions
should be available for OK, NUMERICAL, and IMPRECISE statuses.

Co-authored-by: Fabian Hofmann <[email protected]>

* revert: Remove 'numerical' termination condition, keep only 'imprecise'

Remove 'numerical' enum value and mapping from STATUS_TO_TERMINATION_CONDITION_MAP while preserving the 'imprecise' additions for COPT solver compatibility.

Co-authored-by: Fabian Hofmann <[email protected]>

---------

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Co-authored-by: Fabian Hofmann <[email protected]>

* feat: allow passing a parameter dict to gurobi's env creation

* improve doc and type annotations

* Add type variable for solver's environment type

* Fix code coverage

* Import model fixture from test_io

* [pre-commit.ci] pre-commit autoupdate

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.11.8 → v0.12.2](astral-sh/ruff-pre-commit@v0.11.8...v0.12.2)
- [github.com/keewis/blackdoc: v0.3.9 → v0.4.1](keewis/blackdoc@v0.3.9...v0.4.1)

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

* feat: extend IIS calculation to support Xpress solver

- Add support for Xpress solver IIS computation alongside existing Gurobi support
- Implement _compute_infeasibilities_xpress() method using xpress.iisall() API
- Update compute_infeasibilities() to auto-detect solver type and route appropriately
- Extend test coverage to include both Gurobi and Xpress in infeasibility tests
- Add comprehensive test suite in test_infeasibility.py with various scenarios
- Update documentation to reflect dual solver support in docstrings
- Maintain backward compatibility with existing Gurobi-only code