Confirm a changed one-shot Job template rolls without a stall #668

What to check

When a release first changes a one-shot Job's pod template, the Job rolls without a stall. Since deploy-kit marks those Jobs with Flux's force annotation (kustomize.toolkit.fluxcd.io/force), Flux should recreate them instead of failing on the immutable template.

Why it isn't checked yet

Nothing has changed such a template since. The estate's images lock still pins vault-policy at delivery 0.9.1, so delivery 0.14.0 changed no Job template. Watch the first lock bump of vault-policy (or any catalog image): the unit should reach Ready, with the Job recreated and no field is immutable error in the Kustomization's events.