Challenge 1: Changing Every Button Across 40 Screens at Once — Solution Walkthrough

The answer:

Per this chapter's own material, the correct approach is to edit the
main component itself — the single master button definition — rather
than touching any individual instance. Changing the main component's
color from blue to green automatically propagates that change to every
instance of it throughout the entire file, instantly, across all 40
screens at once.

Why this is dramatically faster than editing each button separately:

Without this master/instance relationship, changing 40 separate
buttons would mean finding and manually editing each one individually
— a slow, error-prone process where it would be easy to miss one.
Editing the single main component instead means the update happens in
one place and ripples out everywhere its instances exist.

Why this is the actual point of components:

This chapter describes this exact scenario as "the real payoff" of the
master/instance relationship — a single edit to one shared definition
updating every reused copy, rather than needing to track down and
update each individual usage by hand.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that a global styling change is correctly matched
to editing the main component, relying on automatic propagation to
every instance rather than editing each instance individually.