Challenge 1: Classify Three Pipeline Descriptions — Possible Solution
====================================================================

(a) "Every PR runs the test suite automatically"
    -> CONTINUOUS INTEGRATION (CI)

    This describes exactly the chapter's own definition of CI: "every
    code change is automatically built and tested — catching
    integration problems early, not at release time." Nothing here
    mentions packaging a release or deploying anywhere — it's purely
    about automatically verifying that a change works, which is the
    core, foundational layer this chapter calls "the single most
    valuable, foundational piece of CI/CD."

(b) "Every passing build is packaged and a team lead clicks Deploy"
    -> CONTINUOUS DELIVERY (CD)

    This matches the chapter's Continuous Delivery definition precisely:
    "every passing build is automatically prepared for release (built,
    tested, packaged) — but a human still approves the actual
    deployment." The build being automatically packaged and READY is
    the "delivery" half; the team lead's manual click is exactly the
    human approval step that distinguishes CD from the next tier up.

(c) "Every merge to main goes live within minutes with no human
    involved"
    -> CONTINUOUS DEPLOYMENT

    This is the chapter's Continuous Deployment definition verbatim:
    "every passing build deploys straight to production with no human
    approval step at all." The explicit "no human involved" detail is
    the deciding factor that pushes this past Continuous Delivery
    (which still requires that human approval) into full Continuous
    Deployment.

WHY THIS WORKS AS AN ANALYSIS
--------------------------------
The distinguishing test across all three is: "how far does automation
go, and where (if anywhere) does a human still have to act?" (a) stops
at verification with no packaging/deployment mentioned at all. (b)
automates everything up through packaging but stops short of the
actual deploy, deliberately leaving a human gate. (c) removes that
human gate entirely. Recognizing exactly WHERE in this spectrum a human
step still exists (or doesn't) is the key skill this chapter's
terminology table is teaching.