[ENHANCEMENT] Improve child model state tracking during shared artifact parent repair

[op109lvb]

What would you like to be added?

Add better coordination and status visibility when a shared model artifact parent is being repaired or re-downloaded.

Today, a DownloadOverride repair is driven by the child model that triggered it. Other child models that point to the same shared parent may remain Ready, even though the shared parent artifact is being repaired.

Why is this needed?

For shared artifact reuse, multiple model CRs can point to the same node-local parent artifact. If that parent is corrupted and one model triggers repair, all children depend on the same repaired content.

Better tracking would make this behavior clearer and safer by showing that sibling models are affected by the shared parent repair, even if they did not trigger the repair themselves.

Completion requirements

• Design doc (if significant feature)
• API change
• Docs update
• Tests

Can you help us implement this enhancement?

• Yes, I can contribute
• No, but I'm available for testing
• No