release(4.3.2): block response Content-Type, guard-core 4.1.0 tracking

[rennf93]

Release commit for 4.3.2: carries the block-response text/plain Content-Type fix (#22, merged after the 4.3.1 cut) and raises the guard-core floor to >=4.1.0, tracking the guard-core 4.1.0 engine (exempt_ips skip-list, recon leading-separator gate, raw-view recon scan, cross-engine interop harness). Version bump, changelog, release notes, mike/versions.json and the example image tag.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: cef98657-1e79-499f-93df-4bd414586ab0

---

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

[github-actions]

Thanks for opening your first pull request on djangoapi-guard!

Quick checklist before review (most of these are enforced by CI, but worth a glance):

• make lint — ruff format, ruff check, mypy, and vulture
• make test (or make local-test) — full test suite passes with 100% coverage
• make security — bandit, safety, and pip-audit all clean
• make quality — radon and xenon complexity thresholds respected
• No # noqa / # type: ignore shortcuts; pre-existing violations in touched files are fixed
• Added an entry under ## Unreleased in CHANGELOG.md
• If you touched a public API, updated the relevant page under docs/
• If the change involves engine logic, the corresponding fix landed in guard-core first

See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow.

Welcome aboard — a maintainer will review shortly.