v1.0.1

v1.0.1 (2026-10-09)

The engine floor moves to guard-core-go v4.3.2 (the adapter-parity release)

Changed

• The engine floor moves to github.com/rennf93/guard-core-go/v4 v4.3.2: prest-guard now requires the 4.3.2 engine release (live on
  the Go module proxy), the adapter-parity release carrying the ReDoS
  static-safety trio (the pattern_safety corpus goes registry-free,
  94/94 with 0 divergences), the sus-patterns runtime registry with
  pattern events and real dynamic-rules application, the
  custom_response_modifier response pass, the websocket guard surface,
  the fifteen SecurityConfig knobs with the performance-monitor wiring,
  and the lifecycle/state surface (manager exports, IsInitialized, the
  cross-instance middleware state registry, MarkInitialized/
  AgentStats). The floor also brings redis/go-redis/v9 v9.23.0
  transitively, clearing the stdlib-adjacent x/sys exposure;
  govulncheck stays clean. The nethttp-guard floor stays at v1.3.0.
• Post-transfer metadata (e6b262a): repo URLs, docs links, and
  ecosystem references point at the Guard-Core org. Module paths and Go
  imports are deliberately unchanged.

Compatibility

• No API change. The plugin surface (GuardMiddlewareLoad, the
  PREST_GUARD_* configuration keys) is unchanged from 1.0.0; the 1.0.1
  floor bump tracks the engine release the plugin is tested against, per
  the repo's versioning rule (engine bumps follow the guard-core-go
  releases the plugin is tested against).