A pipeline pins the runner image (Rollout Stuck)

The execution environment is frozen and its policy input is not. The workload kept its own settings, but the refreshed platform baseline now changes a lower layer assumption. The application itself changed little, but the refreshed baseline now interprets one dependency more strictly. The workload changed very little, but the new baseline now interprets one lower-layer dependency more aggressively. The workload barely changed, but the refreshed control plane now evaluates one supporting dependency more strictly than before.

• Identify the primary failure signal in the Pinned Runner, Floating Policy Bundle scenario.
• Separate visible symptoms from the underlying technical dependency.
• Describe the safest recovery path and the follow-up prevention work.

1. Summarize the current impact and the last known change.
2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
3. Separate immediate recovery from permanent prevention work.

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.