fix: [AI-7675] accept reused/unknown run statuses in run_results v1-v5 parsers

[Sourabhchrs93]

Summary

Closes the residual of AI-7675 finding #2: the reused-status shim shipped for run_results v6 in 0.3.2 (AI-7435, PR #106) was never applied to v1–v5. Any run status outside success/error/skipped still raises a ValidationError on those schema versions, and the backend ingestion worker silently drops the entire run_results.json (batch stays green — same silent-drop failure mode as AI-7435/AI-7856).

Changes

Exact mirror of the v6 fix, applied to run_results_v{1..5}.py:

• Status becomes str, Enum, gains reused, and gains the _missing_ forward-compat fallback — unknown future dbt statuses parse as real members instead of failing validation.
• RunResultOutput.status union reordered to Union[Status1, Status2, Status] so test/freshness statuses (pass/fail/warn/runtime error) keep resolving via the strict enums; the permissive run Status is tried last.
• Freshness-specific enums (Status3/Status4 in v3/v4) untouched — matching the v6 fix scope.

Tests

New tests/test_vendor/test_run_results_pre_v6.py, parameterized over v1–v5, mirroring test_run_results_v6.py:

PYTHONPATH=src pytest tests/test_vendor/ -q
36 passed

Also verified against a real sunrun v4 production artifact (run_498571806 from S3): parses to RunResultsV4 with all results intact. Adjacent consumers (tests/clients/altimate/test_utils.py, tests/core/platform/dbt/test_artifact_loaders.py) pass. ruff clean on the new test; zero new violations in the generated vendor files (pre-existing UP007 counts unchanged).

Scope notes

• v1/v2/v3 are included alongside v4/v5: identical generated code, identical latent bug — patching only two of five sibling files perpetuates the whack-a-mole this ticket calls out.
• This is the point-fix track of AI-7675. The durable dict-first lenient reader (finding feat: datapilot initial commit #1 + design consolidation) is a separate work item and is unaffected by this change.
• After release + backend version bump, v1–v5 tenants get the same protection docusign (v6) already has.

🤖 Generated with Claude Code

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (6 files)

• src/vendor/dbt_artifacts_parser/parsers/run_results/run_results_v1.py
• src/vendor/dbt_artifacts_parser/parsers/run_results/run_results_v2.py
• src/vendor/dbt_artifacts_parser/parsers/run_results/run_results_v3.py
• src/vendor/dbt_artifacts_parser/parsers/run_results/run_results_v4.py
• src/vendor/dbt_artifacts_parser/parsers/run_results/run_results_v5.py
• tests/test_vendor/test_run_results_pre_v6.py

The Status shim (str, Enum base + reused member + _missing_ forward-compat fallback) and the Union[Status1, Status2, Status] reordering are applied identically across all five pre-v6 schema files and match the approved, production v6 reference exactly. The freshness-specific Status3/Status4 enums in v3/v4 are correctly left untouched. The new parameterized test faithfully mirrors test_run_results_v6.py and uses correct schema-version URLs for routing. No downstream consumer in this repo relies on the run-status enum type/identity, so the reordering carries no regression risk.

---

_{Reviewed by glm-5.2 · Input: 35.7K · Output: 8.4K · Cached: 432.3K}