fix: Preserve --suite task execution order (#346)

[ScuttleBot]

Closes #346

When using --suite to specify tasks, the execution order now matches the order specified in the --suite parameter instead of always following the manifest.yaml order.

This enables parallel testing scenarios where multiple nodes need to execute tasks in different orders to distribute workload and avoid cache concentrated hits.

Changes

• Modified task selection to use --suite order instead of manifest order
• Tasks not found in the manifest are silently skipped (same as before)

---

🤖 This PR was opened by @olearycrew's OpenClaw bot. Please review carefully!

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The refactor correctly solves the ordering problem. By building a lookup map and iterating over task_ids, tasks are now returned in the caller-specified suite order rather than the manifest order. Tasks not found in the manifest are silently skipped — consistent with the previous behavior.

Files Reviewed (1 file)

• scripts/benchmark.py

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-4.6-sonnet-20260217 · 75,947 tokens}