feat(preprod): expose status check data through build details API

[trevor-e]

Exposes this data to our frontend so we can build a success/error UI for posted checks.

[cursor]

Bug: Truthiness check mishandles non-boolean success values

The success field check uses truthiness rather than explicit boolean comparison. This causes {"success": "false"} to be treated as success since the string is truthy, and missing or null success fields to be treated as failures. The check should verify success is True or validate that it's a boolean before branching, ensuring corrupted data is handled consistently with other validation (skipped rather than misinterpreted).

 

[cursor]

Bug: Unvalidated check_id causes Pydantic validation crash

The check_id value is passed directly to StatusCheckResultSuccess without type validation. If corrupted data contains a non-string value like a dict or list, Pydantic raises ValidationError, crashing the endpoint with a 500 error. This contradicts the tests expecting corrupted data to return 200 with posted_status_checks: None. The code should validate check_id is a string or None, or wrap the Pydantic construction in try-except.

 

[codecov]

Codecov Report

❌ Patch coverage is 35.71429% with 18 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...api/models/project_preprod_build_details_models.py	35.71%	18 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #104085      +/-   ##
===========================================
- Coverage   80.61%    80.59%   -0.02%     
===========================================
  Files        9319      9322       +3     
  Lines      397949    398154     +205     
  Branches    25424     25424              
===========================================
+ Hits       320801    320902     +101     
- Misses      76696     76800     +104     
  Partials      452       452