Fix: render_terminal_png.py leaks raw traceback for missing input file

[AchieverSana]

Fixes render_terminal_png.py to handle missing input files cleanly instead of leaking a raw Python traceback.

Summary

Handles missing input files gracefully by printing error: <path> not found to stderr and exiting with code 2, matching the script's existing usage-error behavior.

Type

• Audit
• Explainer
• Bug fix
• Other

---

Audit checklist

• I opened or linked a corresponding issue first
• The folder is named after the domain, not the dataset
• unfair.py includes protected attributes and prints the required output format
• fair.py removes protected attributes and identified proxy variables
• Both scripts use random_state=42 and an 80/20 train/test split
• Proxy variables were actually tested, not just guessed
• unfair.png and fair.png are included as PNG screenshots
• The dataset is public and accessible without login or payment
• The dataset file is included, or DATA.md is included if the file is too large
• README.md includes the new results row and audit section
• A notebook was added if the audit benefits from one

Before fairness gap:

After fairness gap:

Reduction:

Protected attribute(s):

Proxy variables dropped:

---

Explainer checklist

• The file is in explainers/ and uses lowercase hyphenated naming
• It includes a plain-language definition
• It uses a real example from this repo or a documented real-world case
• It includes runnable Python detection or measurement code
• It acknowledges limitations or trade-offs
• It links to related explainers or repo projects
• It includes 2-3 primary sources
• The Explainers table in README.md was updated

---

Linked issue

Closes #460

[vercel]

@AchieverSana is attempting to deploy a commit to the yashkewlani2020-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Hey @AchieverSana, your first PR on Fair Code, that's awesome, thank you.

This project is about making AI more accountable, and contributions like yours are what keep that work going. We'll review your changes shortly.

If you haven't already, give the contributing guide a quick read: it covers how audits are structured and what we look for in a review.

And if you're finding Fair Code useful or interesting, a star on the repo genuinely helps more people find it - no pressure, just appreciated.

[github-actions]

@yakew7 @ahmdkaml - new PR touching a path you own, please review.

[ahmdkaml]

the description of the issue requires a regression test but the implementation is ok