[plan] Fix expression errors in issue-monster workflow

[github-actions]

Objective

Fix 6 expression errors in the issue-monster workflow where undefined properties are being accessed.

Context

Severity: Error
Tool: actionlint
Issue: Property "search_issues" is not defined in object type
Locations: Lines 2631, 2632, 2633, 2801, 2802, 2803, 3042, 3043, 3044 in the lock file

These expression errors will cause runtime failures when the workflow attempts to access undefined properties.

Approach

1. Locate the issue-monster workflow source file (.github/workflows/issue-monster.md)
2. Search for references to search_issues property
3. Determine the correct property name or add the missing property definition
4. Fix all occurrences of the incorrect property access
5. Recompile the workflow using make recompile
6. Run actionlint to verify errors are resolved

Files to Modify

• Edit: .github/workflows/issue-monster.md (source file)
• Generated: .github/workflows/issue-monster.lock.yml (via recompile)

Investigation Steps

1. Examine the context around each error location
2. Check if search_issues should be:
   • A different property name (typo?)
   • Defined in the workflow configuration/tools
   • Accessed differently (e.g., through a different object)
3. Look at similar workflows for correct patterns

Acceptance Criteria

• Root cause of undefined property identified
• All 6 expression errors fixed in source file
• Workflow recompiled with make recompile
• Actionlint shows no expression errors for issue-monster
• Workflow executes successfully (test if possible)
• No regression in workflow functionality

Why This Matters

• Runtime errors cause workflow failures
• Undefined property access prevents workflow from completing
• Impacts users who depend on this workflow's functionality
• Easy fix with high impact on reliability
  Related to [plan] Address security findings from static analysis scan #5866

AI generated by Plan Command for discussion #5845