Adopt the approved runtime before the V1 benchmark #6073

🤖 Generated by the Agentic Engineer

Objective

Adopt and verify the reviewed V1 retirement runtime before running the Longhorn baseline benchmark or accepting its cleanup path in #6030.

Details

#6050 built the migration runtime with the patched Go compiler and its protected publication completed. Publication does not install that runtime. At #6030 head 721d7286474ba21af9761a841585da749120541e, captureBenchmarkV1Runtime requires an approved immutable retirement image and verified serving instance-manager identities before scratch creation. A read-only acceptance check on 2026-11-11 confirms this deployment prerequisite is still unmet; detailed runtime evidence stays in the private operator record.

This affects the baseline and interrupted-benchmark recovery in #5665. Keep #6030's cleanup trial separate from runtime publication and adoption.

Checklist

• Choose a reviewed, protected deployment path for the published runtime, bound to its immutable signed image and exact source revision.
• Preserve existing volume health, redundancy and recovery data during rollout; hold on ambiguous ownership, replacement identities or incomplete observations.
• Verify the configured default and every required serving instance-manager epoch against that approved image using read-only acceptance checks.
• Record adoption evidence and the remaining trial conditions on fix(storage): safely retire the Longhorn V1 benchmark storage #6030; only then run its separately authorized benchmark/cleanup acceptance.
• Remove the temporary runtime through a reviewed change when its migration purpose is complete.

Dependencies

Part of #5665, within #5582. #6050 supplies the published runtime. This issue is the deployment prerequisite for #6030, not evidence that either runtime adoption or benchmark cleanup has passed.

Notes

Size: medium. Use GitOps and the existing protected workflow surfaces. Do not patch the live default image, restart storage managers by hand, retire data, or weaken the benchmark's runtime and cleanup checks to clear this prerequisite.