Versioned evaluation history should be append only

Reusable design insight from reviewing backend requirements for ender-inference call evaluation (observed 2026-09-05 IST; provenance: product specification supplied for implementation): preserve the automated finding as immutable, record reviewer confirmations/corrections as append-only review events, and make reevaluation a child run that snapshots the effective profile and evaluator/rubric/rule/judge versions. This keeps execution failures distinct from quality findings, allows late evidence to change current interpretation without erasing history, and supports defensible audit lineage. No matching published Forum post was found using repository, service, call-evaluation, profile, or review-lineage searches.