fix: default max_items to 1 at runtime to prevent unbounded batch fan-out

[chubes4]

Summary

• Fixes unbounded batch fan-out caused by max_items defaulting to 0 (unlimited) at runtime when flows lack a persisted value
• Changes $config['max_items'] ?? 0 → $config['max_items'] ?? 1 in FetchHandler::get_fetch_data()

Problem

The FetchHandlerSettings UI defines 'default' => 1 for max_items, but that's only a form pre-fill hint — it's never applied when the field is absent from stored config. At runtime, ?? 0 meant unlimited.

Every Ticketmaster/Dice.fm/Reddit fetch returned ALL items, each fanning out into a child job with its own LLM call. Dice.fm Chicago alone returned 99 events → 99 child jobs. Across 46 parent batches, 309 child jobs were created with 261 stuck in processing, flooding the Action Scheduler queue with 331+ pending actions.

Fix

One-line change: runtime fallback matches the settings UI default. Flows that explicitly want batch fan-out must set max_items > 1 in the handler settings UI.

Already hotfixed on production — this PR formalizes the fix.

[github-actions]

Homeboy Results — data-machine

❌ lint (changed files only)

❌ test

• PHPCS: LINT SUMMARY: 212 errors, 199 warnings
• Fixable: 176 | Files with issues: 108 of 346

Top violations

  WordPress.Arrays.ArrayDeclarationSpacing.ArrayItemNoNewLine    93
  WordPress.DB.PreparedSQL.NotPrepared                       55
  Generic.CodeAnalysis.UnusedFunctionParameter.Found         36
  Generic.Formatting.MultipleStatementAlignment.NotSameWarning    35
  WordPress.Arrays.MultipleStatementAlignment.DoubleArrowNotAligned    35

- PHPStan: PHPSTAN SUMMARY: 152 errors at level 5 - BUILD FAILED: PHPUnit tests

Fatal error

Fatal:  Uncaught Error: Class "DataMachine\Engine\AI\System\Tasks\ImageGenerationTask" not found in /home/runner/work/data-machine/data-machine/tests/Unit/AI/System/Tasks/ImageGenerationTaskTest.php:13

❌ audit

---

Homeboy Action v1 — homeboy 0.54.0