`new Error(...)` inside catch (error) references error but omits `{ cause: error }` — the original stack trace will be lost. Add `{ cause: error }` as the second argument

Wrap fs.appendFileSync(logPath) in try/catch — synchronous fs methods throw on I/O errors (missing file, permission denied, disk full) and will crash the action if unhandled

`new Error(...)` inside catch (err) references err but omits `{ cause: err }` — the original stack trace will be lost. Add `{ cause: err }` as the second argument

Wrap fs.writeFileSync(tmpPatch) in try/catch — synchronous fs methods throw on I/O errors (missing file, permission denied, disk full) and will crash the action if unhandled

`new Error(...)` inside catch (err) references err but omits `{ cause: err }` — the original stack trace will be lost. Add `{ cause: err }` as the second argument

Wrap fs.readFileSync(agentOutputFile) in try/catch — synchronous fs methods throw on I/O errors (missing file, permission denied, disk full) and will crash the action if unhandled

Avoid using a string concatenation expression as the route argument of github.request(). Use the typed placeholder form instead — e.g. github.request("GET /repos/{owner}/{repo}", { owner, repo }) — to preserve typed dispatch and prevent malformed paths

Avoid using a template literal with interpolations as the route argument of github.request(). Use the typed placeholder form instead — e.g. github.request("GET /repos/{owner}/{repo}", { owner, repo }) — to preserve typed dispatch and prevent malformed paths

Avoid using a template literal with interpolations as the route argument of github.request(). Use the typed placeholder form instead — e.g. github.request("GET /repos/{owner}/{repo}", { owner, repo }) — to preserve typed dispatch and prevent malformed paths