Exercise 3: Why status === 1 Isn't a Data-Completeness Guarantee — Possible Solution
====================================================================

WHAT data.status === 1 ACTUALLY MEANS
------------------------------
Open Food Facts sets status to 1 to indicate that a product record exists for the given barcode - it confirms the barcode was found in the database at all, nothing more specific than that.

WHY THAT'S NOT THE SAME AS COMPLETE DATA
------------------------------
Because Open Food Facts is crowdsourced and community-maintained, a product record existing doesn't guarantee that record is fully filled in - a valid, found product can still have a missing name, no category, or generally sparse data, since different contributors fill in different amounts of detail.

WHAT THE ROUTE ACTUALLY DOES ABOUT IT
------------------------------
The route reads product_name and categories_tags defensively, falling back to null with the || null pattern whenever either field is missing, rather than assuming they're always present and letting a lookup crash. This pushes the responsibility for handling incomplete data forward to wherever the result is used next - Chapter 5's own add-item form, which has to expect null fields and offer a manual-entry fallback.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly distinguishes "a product record exists" (what status === 1 actually confirms) from "that record is fully populated" (not guaranteed), and correctly describes the route's own defensive null-fallback handling as the concrete mechanism dealing with that gap.