superpowers-sage:debugging

Debugging Sage Blade and Livewire failures requires triaging symptoms into Blade cache, OPcache, or Vite/HMR categories. You run targeted Lando commands to validate configurations, flush caches, and produce a structured diagnosis with root cause evidence and step-by-step fixes.

Acorn boot failures in Lando often stem from environment-specific misconfigurations or WP hook conflicts. You diagnose them by running correct Lando commands to inspect container logs, validating configuration files, and checking autoload regeneration to isolate the root cause.

The best way to fix Vite HMR and ACF registration errors in WordPress is through targeted diagnostics per category. You validate your dev server behavior, perform ACF sync checks, and regenerate autoloads to identify the exact failure point and verify the post-fix.

Resolving Eloquent query and queue job failures in Acorn involves categorizing the symptoms and running targeted diagnostics. You validate database configurations, inspect queue job states, and apply step-by-step fixes followed by a post-fix verification pass to ensure stability.

Yes, you can use this debugging approach for PHP errors and WP hook conflicts in Sage. It applies domain-aware troubleshooting procedures to categorize symptoms, validate configuration files, and produce a structured diagnosis with root cause evidence and verification steps.