Exercise 3: Why Push Notifications Are Still Out of Scope — Possible Solution
====================================================================

WHY THE SCHEDULED FUNCTION ALONE ISN'T THE SAME AS PUSH NOTIFICATIONS
------------------------------
Chapter 7's dailyExpiryCheck scheduled Cloud Function only checks Firestore for items expiring soon and was described in that chapter as an optional stretch feature - the chapter itself left what happens with that information (writing a notification document, or sending via Firebase Cloud Messaging) as a sketch, not a fully built feature. Actually delivering a push notification to a user's device requires additional real work: registering and storing each device's FCM token, handling token refresh and invalidation, and actually sending a message through Firebase Cloud Messaging - none of which this course built out.

WHY THIS IS HONESTLY CALLED OUT RATHER THAN ASSUMED DONE
------------------------------
Having the scheduled function that CHECKS for expiring items is a genuinely different and smaller piece of work than having a complete pipeline that DELIVERS a notification to a real device. Since only the checking half was ever built, and the delivery half was explicitly left as a sketch rather than implemented, the capstone's scope note calls this out directly rather than letting a reader assume push notifications are already working just because a scheduled function exists.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly distinguishes between checking for expiring items (built, in Chapter 7) and actually delivering a push notification (never built, only sketched), explaining why the honest scope note specifically excludes push-notification delivery despite the scheduled function's existence.