piped-tail-masks-script-exit-code

When verifying a script’s exit code by piping output through tail (e.g., python3 script.py | tail -5; echo $?), $? captures tail’s exit code, not the script’s. This caused a false C2 finding claiming lint scripts exit 0 on failure when they actually exit 1 correctly. Always check exit codes with direct execution or PIPESTATUS[0].

Related

• pipe-tail-corrupts-exit-code-verification
• hypervisor-steal-time-misread-as-process-cpu
• 2026-04-04-oracle-001-self-architecture-analysis
• helix-skills-dir-env-var-enables-portable-lint-execution
• docker-unless-stopped-insufficient-for-critical-services
• pipe-tail-captures-tail-exit-not-script-exit
• pipe-tail-masks-script-exit-code
• prose-pointer-lint-must-check-skills-root-docs
• tail-pipe-corrupts-exit-code-verification
• pipe-through-tail-masks-script-exit-code
• piped-command-exit-code-masks-primary-script-result
• pipe-through-tail-captures-tails-exit-code-not-scripts