Exercise 3: Confirming Zero Processing — Possible Solution
====================================================================

STEPS
------------------------------
1. Note the exact byte size and contents of public/css/global.css
   directly on disk (e.g. via a text editor or `wc -c` in a terminal).

2. Fetch the same file as served by Express:

     curl http://localhost:3000/css/global.css

3. Compare the fetched output against the source file's own contents
   byte for byte.

RESULT
------------------------------
The served content is character-for-character identical to the
source file on disk - no minification, no added content-hash in the
filename or headers beyond standard caching headers, no
transformation of any kind. What's on disk is exactly what's served.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly compares the raw source file against the actual served
response, and correctly confirms they're identical - concrete proof
that express.static() performs genuinely zero processing, unlike
Rails' own Propshaft, which at minimum fingerprints the filename for
cache-busting purposes.