Fix CI/CD pipeline status handling so failed checks are reported as FAILED instead of PASSED WITH WARNINGS.

Current Issue: The pipeline sometimes reports “passed with warnings” even when tests, validations, or critical stages actually fail. This causes incorrect pipeline status reporting and can allow broken code to appear successful.

Requirements:

• Ensure pipeline status strictly reflects actual execution results:

  • Successful execution → PASSED
  • Any failed mandatory stage/check/test → FAILED

• Remove incorrect “passed with warnings” behavior for critical failures.

• Verify all linting, test, coverage, and validation failures correctly propagate non-zero exit codes.

• Ensure shell scripts, Makefiles, pre-push hooks, and CI jobs fail properly when commands fail.

• Add proper error handling for subprocesses and chained commands.

• Validate GitLab/GitHub Actions pipeline configuration does not suppress failures using:

  • || true
  • allow_failure
  • ignored exit codes
  • warning-only handling

• Ensure test coverage threshold failures also fail the pipeline.

• Preserve existing pipeline stages and reporting structure.

• Add/update tests or validation checks if needed to confirm correct pipeline status behavior.

Expected Outcome: The pipeline should display only:

• PASSED → when all required checks succeed
• FAILED → when any required validation/check/test fails