Challenge 3: Explaining Three Chapter-Attribution Rows — Possible Solution
====================================================================

ROW 1: "Choosing Vite instead of a webpack.config.js" -> build-tooling1-3
------------------------------
This capstone deliberately never writes a webpack.config.js at all —
there's no loaders array, no plugins array in the Webpack sense. That
absence is itself the point: build-tooling1-3 named Webpack's own
real cost (verbose configuration, slower dev rebuilds) as the exact
trade-off that motivated the rest of this course's own progression.
Building this capstone with Vite instead is a direct, practical
consequence of that chapter's own findings, not an arbitrary tool
choice.

ROW 2: "vite.config.js, npm run dev / npm run build" -> build-tooling1-5
------------------------------
The two package.json scripts (dev running plain `vite`, build running
`vite build`) directly exercise build-tooling1-5's own central point:
these aren't two modes of one pipeline, they're two genuinely
different tools under the hood — native ESM serving plus esbuild
pre-bundling for `vite`, and a real Rollup build for `vite build`.
The capstone's own vite.config.js (setting outDir and sourcemap) is
the concrete configuration surface that chapter introduced.

ROW 3: "postcss.config.js, Dashboard.module.css" -> build-tooling1-7
------------------------------
The postcss.config.js file configuring autoprefixer, and the
Dashboard.module.css file whose .settingsButton class gets rewritten
into a unique, scoped name at build time, are both direct
applications of build-tooling1-7's own material — PostCSS as an
empty plugin pipeline that autoprefixer fills in, and CSS Modules as
the structural fix for CSS's own severe global-scope problem, applied
here to prevent .settingsButton from colliding with any other class
of the same name elsewhere in a larger real project.

WHY THIS WORKS AS AN ANSWER
------------------------------
It picks three specific rows, names the exact piece of capstone
configuration each one refers to, and explains — using each earlier
chapter's own stated material — precisely why that configuration
choice traces back to that chapter's own concept, rather than
restating the table's own wording without connecting it to the
actual files.