v1.83.1

[1.83.1] - 2026-09-08 — Alnilam

Fixed

• A production recommendation no longer degrades the config health check. HealthService::checkConfiguration()
  folded every SecurityManager recommendation (an empty CSP_HEADER, say) into its
  warning status, so a deliberately configured host reported degraded health to every
  monitor. Recommendations now ride along under their own recommendations key on the check
  while the status stays ok; production warnings still fail the check as before.
• Production recommendations are logged once per boot cache, not once per request.
  PHP-FPM boots the framework per request, so every applicable [security] RECOMMENDATION
  (e.g. an empty CSP_HEADER) landed in the error log on every hit. RecommendationLog keeps
  a marker under the app's storage/cache: the same set stays silent until it changes or the
  cache is cleared; an empty set drops the marker so a regression is logged again. Warnings
  keep their per-request logging.