From c676011d1e5ed073bdc64660c78e950802c1cb22 Mon Sep 17 00:00:00 2001 From: garrytan Date: Tue, 3 Nov 2026 16:23:22 +0000 Subject: [PATCH] docs(troubleshooting): QUEUE_SCREEN_RED names rule cases from the report's failure lines Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/troubleshooting.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index c7854d943..8bc2a911d 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -5707,7 +5707,8 @@ closed PRs. verdict is read from the run itself, never from a lane's report: the `gate-binding-a` artifact evals.yml's report job uploads (verdict, reconcile exit, flaky cases) and the `report-verdict-a` artifact's -`collector-outcomes.json` (the panels that failed the lane and the rule-16 +`collector-outcomes.json` (the panels that failed the lane, the report's `✗` +failure lines, which name rule cases that have no panel, and the rule-16 flaky lines). A case the binding calls red already failed twice inside the run (rule 16 reruns a first failure once), so the red is real. `ready` refuses with this code when the head's recorded screen run is red, whichever