Predict which values update after a write and which values stay fixed.
A Signal is a small piece of reactive state. Calling it reads the current value; set replaces that value and update computes a replacement from the current one. State created inside the application belongs to that session.
The most useful distinction is between passing a readable object and reading it now. A live template hole can subscribe to a Signal. A plain integer obtained from count() is just an integer, even if it originally came from a Signal.
Understand the moving parts
Create the snapshot before returning the template. The two outputs start at the same value, so initial HTML cannot prove which is reactive. Only a later write exposes the difference. This is why the exercise asks you to interact.
Keep derived work out of event handlers when it can be expressed as a readable value. Your handler should change the source; the renderer can then update every dependent location consistently. Reset is another ordinary write, not a reload.