fix(logger): route warn-level events to Hypercart_Logger::warning()

[mrtwebdesign]

Summary

QueryGuard's logging bridge checked for and called a warn() method, but the Hypercart Helper logger (Hypercart-Helper-WP-plugin/includes/class-hypercart-logger.php) exposes warning(). The method_exists() guard therefore always returned false, so every warn-level event — including slow_query, the most common event in observe mode — silently fell back to error_log() instead of landing in wp-content/hypercart-logs/. info and error routed correctly; only warn was broken.

This was confirmed against ~48h of binoidcbd production logs: 551 slow_query events, all in the WP Engine PHP error log, none in the Helper log files.

Changes

• hypercart-query-guard.php — bridge now prefers Hypercart_Logger::warning(), with warn() kept as a fallback for any string-only/legacy logger. Docblock attribution corrected to the Helper plugin.
• class-hcqg-mutex-guard.php — same bridge bug fixed (it logs kill/mutex events).
• README.md — logging section now credits the Hypercart Helper plugin, not the Performance Monitor.
• Tests — mock Hypercart_Logger made faithful to the real class (warning), new test_warn_level_routes_to_hypercart_logger_warning regression, and the end-to-end DbDropinTest assertion updated. Full suite green: 86 tests, 166 assertions.

Scope notes

• Conservative on purpose: no internal warn→warning rename and the public WARN_THRESHOLD_MS / HYPERCART_QUERY_GUARD_WARN_THRESHOLD_MS config constant is untouched.
• The early-load concern was investigated and is a non-issue: slow-query and kill logging fire on the shutdown hook, well after the Helper plugin loads, so Hypercart_Logger is available when these events are written.
• Deployment reminder: to see logs land on a site, the fixed plugin files must be deployed (not just db.php) and the Hypercart Helper plugin must be active.

Issues

Closes #7
Closes #6

🤖 Generated with Claude Code