VG-6 A red about something else is a defect

A gate that goes red for a cause outside the change MUST be filed as a defect of the gate and fixed, by narrowing what it concludes or where it runs, rather than rerun until it passes.

Field	Value
Keyword	MUST
Level	2
Checked	by judgement
Findings	F304
Harness facts	none
Threat	internal: the three remedies differ, so the rule states the aim, not the mechanism
Status	active

Rationale: in Shio, winwright and freewilly a gate went red for a concurrent run, a build that never started, a runner without the needed desktop, or a non-deterministic figure (F304, R3/S3). winwright's CI was red for twenty-odd pushes and never about the tree, and its workflow now runs only the half a hosted runner can answer, because a permanently red badge is one nobody reads. Shio's runner allows one run per gate and records a failed setup as inconclusive; freewilly made its figures deterministic. None of them told the agent to rerun. A red that means nothing costs a diagnosis every time and then hides the true red beside it, which is why D4 calls it a defect to file, not a state to live with.