Exercise 1: A Broken System After pacman -S Without a Full Upgrade First — Possible Solution
====================================================================

WHAT ACTUALLY HAPPENED
------------------------------
Per this chapter's own warn-box, "on a rolling-release system, installed
packages and their shared libraries are tightly version-coupled -
installing a single new package (pacman -S somepackage) without first
fully syncing and upgrading the entire system (pacman -Syu) can pull in
a package built against library versions newer than what's currently
installed, producing a genuinely broken partial state." Running
pacman -S directly fetched the newest available version of that one
package from the repository, but the rest of the system's own
libraries hadn't been updated to match - the new package was likely
built expecting newer versions of shared libraries the system doesn't
yet have installed, breaking either that package, something depending
on the same libraries, or both.

WHY THIS IS SPECIFIC TO ARCH'S OWN ROLLING MODEL
------------------------------
This connects directly to Chapter 4's own rolling-release material -
because Arch has no discrete, frozen releases, every package is always
tracking the latest upstream version continuously. A single package
installed in isolation is being pulled from "the current moment" in
that continuous stream, while the rest of the system may still reflect
an earlier moment - a mismatch that simply can't occur the same way on
a point-release system where everything within one release stays
version-locked together until the next full release.

WHY THIS ISN'T A BUG IN pacman ITSELF
------------------------------
Per this chapter, this is "a real, well-documented policy, not
overcaution" - Arch's own documentation explicitly names partial
upgrades as unsupported, meaning this outcome is a known, expected
consequence of not following that policy, not an unpredictable pacman
malfunction.

THE CORRECT HABIT GOING FORWARD
------------------------------
Per this chapter, "the correct habit on Arch specifically is always
running a full -Syu before installing anything new, never syncing the
index just to grab one specific package in isolation." Running
pacman -Syu first, letting the entire system's packages and libraries
update together as a consistent set, and only then installing the new
package, keeps everything on the system mutually consistent rather than
mixing versions from different points in time.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains the specific mechanism (library version mismatch) behind
the breakage using this chapter's own warn-box, ties it to Chapter 4's
own rolling-release material to explain why this is Arch-specific, and
states the exact corrective habit this chapter recommends rather than a
vague "be more careful" answer.