Challenge 2: Editing One Instance Directly Doesn't Update the Others — Solution Walkthrough

The answer:

Per this chapter's own warning box, only editing the main component
itself propagates a change to every instance. Editing an instance
directly just creates a per-instance override on that one copy alone —
it has no effect on the main component or on any other instance,
regardless of how many other instances exist in the file.

Why the colleague's expectation didn't match reality:

The colleague assumed a change made anywhere would somehow flow back
to the shared definition and out to every other copy. The actual
relationship only flows one direction — from the main component
outward to its instances — not from an individual instance back
upward or sideways to its siblings.

What the colleague should have done instead:

Per this chapter's own guidance, the change needed to be made on the
main component itself, not on any individual instance, for it to
propagate to every other instance throughout the file.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that editing an individual instance is correctly
understood as creating a local override only, not a change that
propagates outward to the main component or other instances.