release(4.3.1): track guard-core 4.0.x, dependency floor to >=4.0.0, agent docs

[rennf93]

Release 4.3.1 (patch)

• Compatibility: guard-core floor moves from >=3.15.0 to >=4.0.0 (no upper bound) so the adapter tracks the guard-core 4.0.x engine line, verified against guard-core 4.0.4. No adapter code changed.
• Docs: AGENTS.md/CLAUDE.md agent guidance, flaskapi-guard package skill, bypass-token note in access-control decorator docs

Delta since 4.3.0 is docs-only apart from the dependency floor, hence the patch bump. Local suite: 228 passed against guard-core 4.0.2, 100% coverage.

Summary by CodeRabbit

• Release
  • Released version 4.3.1, which requires guard-core 4.0 or later and has been verified with guard-core 4.0.4.
• Documentation
  • Updated installation examples and version references to 4.3.1.
  • Clarified that an unknown access-control bypass token generates a warning.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 065f5015-4dae-4155-afa6-204ec97b3355

📥 Commits

Reviewing files that changed from the base of the PR and between 0e83b3c and 0c187ad.

📒 Files selected for processing (6)

• .mike.yml
• CHANGELOG.md
• docs/index.md
• docs/release-notes.md
• docs/versions/versions.json
• pyproject.toml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The project version changes to 4.3.1, and the minimum guard-core requirement changes to 4.0.0. Release notes, the changelog, and documentation version pointers are updated for 4.3.1.

Changes

4.3.1 Release

Layer / File(s)	Summary
Project version and dependency requirement pyproject.toml, CHANGELOG.md, docs/release-notes.md	The project version changes to 4.3.1, and the guard-core minimum changes to >=4.0.0. The changelog and release notes describe the release and state that the adapter was verified against guard-core 4.0.4.
Documentation version pointers .mike.yml, docs/versions/versions.json, docs/index.md	The version catalog and latest aliases change to 4.3.1. The Docker pull example uses the 4.3.1 image tag.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 0c187

The release version and documentation pointers are consistent, and the new dependency minimum supports the project's declared Python versions. No merge-blocking issue is evident.

🚥 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 clearly summarizes the release, the guard-core 4.0.x compatibility update, the dependency floor change, and the added agent documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

---

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