The repair kiosk needs a small set of dependable controls before its pilot. Each task gives you a fresh app and changed quantities. Read the control and property names again rather than copying the last visible answer. The work mixes arithmetic, input cleanup, conditional states and app-context reasoning.
Check what happens when someone edits a value after your first result appears. Zero quantities, blank references and exact thresholds should have deliberate outcomes. Keep the display formula separate from the button behavior you will study later. If you use a constant to match the initial screen, the changed-input check will expose it. Finish with a result another maker can inspect and explain from the property formula.