We are working on the implementation for a **{{ operation }}** kernel.  The code is not passing validation and contains a bug.

In addition to logical errors, look for structural errors like missing includes, undefined functions, type mismatches, or syntax errors.  Make sure the code is correctly using pytorch operations and that the usage of pytorch ops matches their actual semantics.

## Verification Failure

**Command run:** `{{ ran_command }}`

**Exit code:** `{{ exit_code }}`

**stdout:**
```
{{ stdout }}
```

**stderr:**
```
{{ stderr }}
```

{% if files %}
## Current Files
{% for file in files %}
### {{ file.filename }}
{% if file.usage %}*{{ file.usage }}*{% endif %}

```python
{{ file.contents }}
```
{% endfor %}
{% endif %}

## Output Format

You must return your analysis as a JSON object with a `suggested_fixes` array. Each fix must be an object with:
- `path`: file path containing the error
- `line_number`: line number(s) with the error (can be a range like "117-118" or single line "117")
- `likely_cause`: brief explanation of the error
- `suggested_fix`: specific actionable solution

Example format:
```json
{
  "suggested_fixes": [
    {
      "path": "tt_eltwise_sfpu2_op.cpp",
      "line_number": "117",
      "likely_cause": "Missing include for reciprocal operations",
      "suggested_fix": "Add #include \"compute_kernel_api/eltwise_unary/recip.h\" and use recip_init() and recip() instead of recip_tile_init() and recip_tile()"
    }
  ]
}
```

**IMPORTANT**: Always return `suggested_fixes` as an array, even if there is only one fix.
