A static summary route is valid (Rollout Stuck)

The summary remains installed long after the useful path is gone. The explicit configuration seems correct, yet an inherited policy no longer resolves the same way under the cleaned hierarchy. Effective ownership looks correct at first glance, but one delegated path still reflects the old hierarchy. Nominal permissions look aligned, yet one delegated control path still reflects the retired operating model. Nominal access still looks aligned, yet one delegated path continues to reflect the previous layered administration model.

• Identify the primary failure signal in the Summary Stayed Because the Wrong Thing Was Tracked 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.