[rennf93]

Summary

Tagged maintenance release for the Guard 4.3.0 train. There are no runtime behavior changes: src/ has a zero diff since 3.1.0. The release exists so consumers on the 4.3.0 train pick up the hardened test suite and the repo governance baseline in a tagged, Packagist-published agent artifact.

Changes

• Bump the reported agent version to 3.2.0 (RenzoFranceschini\GuardAgent\Version::VERSION), matching the upcoming v3.2.0 tag; composer.json carries no version field, Packagist derives it from the tag.
• Fill the v3.2.0 CHANGELOG entry: scaffold baseline, Semgrep security-audit and secrets gate, the hard 100 percent reachable-line coverage gate, dev-only phpunit/php-code-coverage, and an explicit compatibility note: the agent intentionally declares no composer dependency on guard-core-php (neither require nor suggest), so no composer-level engine floor applies to this package; the guard-core-php ^4.3.0 floor ships with the adapters that embed the engine (laravel-guard, symfony-guard, slim-guard, psr15-guard), keeping the agent installable alongside any core version, including 4.3.0.
• Refresh the bug-report version placeholder to guard-agent-php 3.2.0 / guard-core-php 4.3.0.

Verification

• make lint: exit 0 (LINT_OK, composer validate --strict clean).
• make test REDIS_HOST=127.0.0.1: exit 0, 625 passed, 0 failed (full suite including the real-Redis integration leg).

Notes

• No-issue release chore.