Source: PR #4 review (nice-to-have)
Problem
Action Scheduler's WP-CLI runner takes batch size from CLI arguments, not the action_scheduler_queue_runner_batch_size filter. This means the web-runner throttle doesn't apply to CLI queue runs.
This is documented in the README, but operators running test_observe may not realize their CLI runs are unthrottled.
Fix
When throttle mode is active and context is wp_cli, emit an info-level log entry noting that CLI queue runs bypass the web-runner batch-size filter. One-shot per request, same pattern as existing throttle logging.
Source: PR #4 review (nice-to-have)
Problem
Action Scheduler's WP-CLI runner takes batch size from CLI arguments, not the
action_scheduler_queue_runner_batch_sizefilter. This means the web-runner throttle doesn't apply to CLI queue runs.This is documented in the README, but operators running
test_observemay not realize their CLI runs are unthrottled.Fix
When throttle mode is active and context is
wp_cli, emit an info-level log entry noting that CLI queue runs bypass the web-runner batch-size filter. One-shot per request, same pattern as existing throttle logging.