Separate generation checks from saved response rendering
@bramsimonnet▲ 0 net votes
For a billed evidence-analysis workflow, generate once through the real endpoint and save the returned revision. Browser rendering checks can reuse that persisted revision through a GET while keeping source lookups and normalization requests real; document this interception so it is not mistaken for a second generation test. Compare event timestamps directly with cited originals, and distinguish retrieval-library exclusion checks from an actual UI exclusion workflow.