Display model name used

[robvanderveer]

Code was fully Cursor generated and reviewd by me

[PRAteek-singHWY]

Hey @robvanderveer @northdpole 👋
I recently ran into the same recurring PYTHON_BLACK lint failures and opened PR #707 to standardize Python formatting using pre-commit.
I thought it might be helpful context here — please let me know if this looks like the right long-term approach or if you’d suggest adjustments.
Thanks as well — hitting this error after solid PR work made it clear this was worth fixing 🙂

[robvanderveer]

Thanks @PRAteek-singHWY, this is indeed a nuisance it seems.

[PRAteek-singHWY]

Thanks @PRAteek-singHWY, this is indeed a nuisance it seems.

Thanks for confirming, @robvanderveer — appreciate it.

[northdpole]

Hey @robvanderveer @northdpole 👋 I recently ran into the same recurring PYTHON_BLACK lint failures and opened PR #707 to standardize Python formatting using pre-commit. I thought it might be helpful context here — please let me know if this looks like the right long-term approach or if you’d suggest adjustments. Thanks as well — hitting this error after solid PR work made it clear this was worth fixing 🙂

I'\d love for this to be pre-commit hooks, using it in the github ci can be a pain since in rare cases linting can produce non-functional code

We can easily make this pre-commit hooks using a pre-commit framework however, that'd be great

[PRAteek-singHWY]

Hey @robvanderveer @northdpole 👋 I recently ran into the same recurring PYTHON_BLACK lint failures and opened PR #707 to standardize Python formatting using pre-commit. I thought it might be helpful context here — please let me know if this looks like the right long-term approach or if you’d suggest adjustments. Thanks as well — hitting this error after solid PR work made it clear this was worth fixing 🙂

I'\d love for this to be pre-commit hooks, using it in the github ci can be a pain since in rare cases linting can produce non-functional code

We can easily make this pre-commit hooks using a pre-commit framework however, that'd be great

@northdpole Thanks for the feedback! I completely understand the concern about CI modifying code or breaking builds.

To address this, I’ve updated the PR to pivot to a local-only approach:

1. ❌ Removed CI Enforcement: Deleted the GitHub Actions workflows (auto-format.yml, pre-commit-check.yml). This ensures zero risk to the CI pipeline and no automatic code changes.
2. ✅ Kept Local Config: Retained .pre-commit-config.yaml so contributors can optionally use it to lint locally.
3. 📝 Updated Documentation: Rewrote CONTRIBUTING.md to recommend pre-commit as a helpful local tool rather than a required CI step.

This creates a purely opt-in developer capability with no impact on the repository's build stability.

Ready for review!