fix: use per-command matching for expected-patterns check

Addresses Cursor Bugbot feedback — expected-patterns was matching against
the concatenated joined string, which could match across command boundaries.
Now uses allCommands.some() consistent with anti-patterns check.

Author: BYK

test/skill-eval/helpers/judge.ts

@@ -26,7 +26,6 @@ function evaluateDeterministic(
   plan: AgentPlan
 ): CriterionResult {
   const allCommands = plan.commands.map((c) => c.command.toLowerCase());
-  const joined = allCommands.join(" ");
 
   // Check anti-patterns: none of these strings should appear in any command
   if (def["anti-patterns"]) {
@@ -47,7 +46,8 @@ function evaluateDeterministic(
   // Check expected patterns: at least one command must contain each pattern
   if (def["expected-patterns"]) {
     for (const pattern of def["expected-patterns"]) {
-      if (!joined.includes(pattern.toLowerCase())) {
+      const lowerPattern = pattern.toLowerCase();
+      if (!allCommands.some((cmd) => cmd.includes(lowerPattern))) {
         return {
           name,
           pass: false,