CI/CD Artifact Verification Handler

Problem Description

A software company runs a CI/CD pipeline that builds and packages their desktop application. The build step completes without error codes, but the team has noticed that sometimes the output directory is empty or the expected installer file is simply missing — no error was thrown, but there is also no proof that the build succeeded. The pipeline previously just reported "success" based on exit code alone, which led to shipping a release with a broken artifact.

The engineering team wants a Python script that checks a build output directory after a build step completes and implements a robust response when success cannot be confirmed. The script should integrate into their pipeline as a post-build validation step, decide how to handle missing or incomplete outputs, and produce a structured record of what it found and what action it took.

Output Specification

Write a Python script post_build_checker.py that:

• Accepts a directory path as a command-line argument
• Checks for the presence of expected output files
• Implements appropriate handling when outputs are absent or incomplete
• Writes a triage_result.json file with a structured record of the check outcome

Also write a INTEGRATION.md file explaining how to integrate this script into a CI pipeline and what each field in triage_result.json means.

Input Files

The following files are provided as inputs. Extract them before beginning.

=============== FILE: inputs/expected_files.txt =============== installer.exe installer.dmg checksums.sha256 release_notes.txt