Exercise 1: What Propshaft Does and Deliberately Doesn't Do — Possible Solution
====================================================================

WHAT PROPSHAFT DOES
------------------------------
Per this chapter, Propshaft fingerprints static asset files with a content-based digest for cache-busting, and serves those files to the browser. That's its entire job.

WHAT IT DELIBERATELY DOESN'T DO
------------------------------
Per this chapter, Propshaft doesn't compile Sass, doesn't transpile any language, and doesn't bundle multiple files together into one. Any real compilation an asset might need is delegated to a separate, opt-in tool rather than being part of the default pipeline itself.

HOW THIS COMPARES TO NEXT.JS'S BUILT-IN BUNDLER
------------------------------
Per this chapter, Next.js's own bundler is a mandatory, integral part of how the framework builds and runs an application at all - there's no path around it, and it performs real bundling, transpilation, and optimization as a core framework responsibility. Propshaft, by contrast, is intentionally minimal - a plain file server with cache-busting, not a bundler, and Rails applications that do need real compilation reach for a separate, additional tool rather than relying on Propshaft itself to provide it.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly describes Propshaft's actual job (fingerprinting and serving) and correctly identifies what it doesn't do (compiling, transpiling, bundling), contrasting that minimal scope against Next.js's own mandatory, full-featured built-in bundler.