VG-2 No gate through a pipe

A gate MUST NOT be run, in any file that tells an agent how to run it, through a pipe or filter that can replace its exit status or discard its output.

Field	Value
Keyword	MUST NOT
Level	2
Checked	automatically
Findings	F302, F300
Harness facts	none
Threat	internal: the failure and its remedy are recorded in one project
Status	active

Rationale: a shell pipeline reports its last command's status, so in Shio a failing test run printed an exit status of 0, and an earlier pipe lost a failure that occurred in one run of six, whose failing class is still unknown because the line "went into a pipe nobody kept" [shio@821f18d74:shio-app/src/test/java/com/viglet/shio/ShTestCommandDocLintTest.java#L33] (F302, R3/S3). Shio's remedy is a runner that keeps the whole output and the suite's own exit code, and a lint over the files that document the suite. The lint does not read the build skill, which at the pin still pipes the suite into a filter (F300), so the rule covers every file an agent reads for the command: instruction files, skills, contributing guides and CI. A script can decide conformance by reading those files.