Summary by CodeRabbit

Tighten the post-condition in Summary.validate() so .none is fault-worthy only when the attachment also has a payload identifier, preserving the existing idempotent fault deduplication and genuine unresolved-payload behavior. Add a passing sample UI test that records an attachment with XCTest's payload-removing lifetime so prepareTestResults.sh produces a real attachment entry without a payloadRef; keep fixture generation and production parsing unchanged. Strengthen FaultReportingTests by first proving the generated fixture contains that payload-less attachment, then asserting validation does not report it as unresolved, so the regression test cannot pass vacuously.

Verification

• Generate TestResults.xcresult from the sample project and verify the fixture contains at least one attachment whose payloadId is absent and whose rendered content is .none.
• Validate that fixture and verify the payload-less attachment produces no unresolvedAttachment fault; running the CLI against the same fixture must continue to exit 0 without a degradation warning.
• Verify attachments with a non-nil payload reference and successfully exported content remain fault-free in both linking and downsized fixture paths.
• Preserve the existing failure rule and idempotency: an attachment that has a payload reference but resolves to .none is still reported as unresolved, and repeated validation does not duplicate that fault or disturb previously collected faults.

Why

Summary.validate() currently records an unresolvedAttachment fault whenever an attachment's rendering content is .none. Attachment also uses .none for attachments that never had a payloadRef, so a valid payload-less attachment is misclassified as failed resolution and can make the CLI exit 3. The model already retains Attachment.payloadId, which distinguishes an attempted payload resolution from the absence of a payload without adding a new state or test-only abstraction. The current generated fixtures contain no payload-less attachment, leaving this false-positive path untested.

Closes #387

Summary by CodeRabbit

• Bug Fixes

  • Improved attachment validation so attachments without payload references are ignored rather than incorrectly reported as unresolved.
  • Clarified diagnostics for attachments whose payloads cannot be resolved.

• Tests

  • Added coverage for attachments configured to be deleted after successful test completion.
  • Updated test result expectations and validation checks to reflect the expanded sample test coverage.