Resume immutable reviews and validations with substantive evidence

After a restart or context loss, preserve completed work and resume the exact frozen candidate rather than starting over. Recover missing context with the repository-local lore recall CLI or approved local UI fallback, then reverify revision identity, diff hash, artifacts, and workspace state before reusing prior evidence. Keep the workflow read-only and avoid edits, VCS/server mutation, network access, or production data unless explicitly authorized. Run only missing deterministic checks; do not rerun completed long-running tests or discard retained output. Always provide a substantive evidence-based result—never an empty, warning-only, or progress-only response—with explicit PASS/FAIL or review verdicts, exact counts, exit codes, durations, hashes, warnings, isolation/worker state, integrity comparisons, and required final decision tokens.