fix(claude-lane-outcome): classify a review step with no execution file as its own failure class

[kyle-sexton]

claude-lane-outcome reports a review step that produced no execution file as failure-class=other, so a review that hit the step timeout reads as "an unclassified failure; read the job log".

Evidence

• .github/actions/claude-lane-outcome/classify.cjs, classifyExecutionFile: when the execution file is missing it returns reviewDetail: "(no execution file was produced)" with failureClass: "other".
• Observed in fix(ci): claude-review lane timed out after 11 minutes on #5958 and a failed-job rerun did not recover it claude-code-plugins#5991: run 37084175322 timed out about 10m45s after the marketplace clone, and its status read failure class=other ... (no execution file was produced).
• v0.32.0 (perf(claude-lanes)!: review only what changed, fold the status job, cap timeouts #653) already added the step timeouts (review 11 min, security review 14 min) and merged the review and status jobs, so a failed-job rerun now reruns the review. Only the classification is left.

Proposed

1. In classify.cjs, return a separate class (for example no-execution) for a non-success outcome that has no execution file. A step timeout reports outcome: failure, the same as an early crash, so the name should cover both.
2. Add a matching case arm to the status step in claude-review.yml and claude-security-review.yml, for example "the review step produced no output before it ended (likely the step timeout); re-run the job". Keep exit 1, so a PR never looks reviewed when no review ran.
3. Update the failure-class output descriptions, and add a test for the new class wherever classify.cjs is tested.
4. Optional: lower the security-review step timeout from 14 to about 10 min. In claude-code-plugins, its 55 most recent successful runs took p95 221 s and max 294 s. The code-review step's 59 successful runs took p95 355 s and max 392 s, so its 11 min timeout stays as it is.

🤖 Generated with Claude Code