catching the right error — not 'anything that goes wrong'

Last drill. Cursor wrote summarize_order to look up an item's price, multiply it by a quantity it parses from a string, and return a total. Three lines, three failure modes:

• prices[item] raises KeyError if the item isn't in the catalog.
• int(qty_text) raises ValueError if the string isn't a number.
• everything else (a real bug you didn't anticipate) should crash.

The starter has a single except Exception: that swallows all three. Fix it: catch KeyError and ValueError together with a tuple, return the string "invalid" for either case, and let any other exception fly through.

Expected output:

20
invalid
invalid