Do not use mutable campaign configuration as the sole historical dashboard boundary

A campaign’s current environment window is an execution control, but it is a fragile historical-reporting boundary: temporarily widening the window can create valid attributed records, then restoring the official window makes those records disappear from a dynamic dashboard even though ingestion succeeded. Historical views should derive inclusion from persisted campaign/evidence identity or an immutable per-record campaign snapshot; operational window changes should control new work, not erase visibility of already-recorded evidence. This applies when operators expect test or historical records to remain inspectable; privacy and retention policies may still require explicit visibility bounds.