Don't pass test file contents that fail to fetch to be used in the coverage evaluation prompts.

[DanielRyanSmith]

Currently, the prompts contain some guardrail text to ignore bad data, but now that we're fetching both the test file contents and their dependency file contents, we can simply remove the text about failures from the prompts and not generate the prompts with the error text.

Optionally, it may be useful to add a caveat to the final report that "Failed to fetch the contents of X files", along with listing their file path.

[KAkhinish2108]

Hi, @DanielRyanSmith , This is Akhinish , I would like to work on this issue. I'd like you to see the approach and solutions and would be glad if you allow me to work accordingly.
both the test file contents and their dependency file contents are being fetched reliably, the existing guardrail text in the prompts that handles failure scenarios has become redundant and can be safely removed.

Approach:

i. Identify and review all prompt templates where guardrail or fallback text related to failed file fetching is injected.

ii. Refactor prompt generation logic to exclude any error-handling or failure-related text when valid file contents are available.

iii. Ensure prompts are generated only with successfully fetched file contents, keeping them concise and signal-focused.

iv. Validate that prompt behavior remains correct across normal and edge cases after removing this defensive text.

Solution:

i. Remove failure-related guardrail text from the prompt templates.
ii. Skip prompt generation for files whose contents could not be fetched, instead of injecting error text into the prompt.
iii. Optionally, add a summary section in the final report stating:
“Failed to fetch the contents of X files”, followed by a list of their file paths.

This keeps the prompts clean and improves output quality, while still preserving transparency at the reporting level.

This change simplifies prompt construction, reduces noise for the model, and cleanly separates error reporting from prompt generation.

[pranjalisr]

@DanielRyanSmith I’ve raised a PR addressing this issue. Would appreciate your review. Thanks!

[pranjalisr]

@DanielRyanSmith Just following up to kindly request a review of this PR when you have availability.
Thank you.