Exercise 1: Why Linux-First Installation Order Tends to Need a Repair — Possible Solution
====================================================================

Explanation:

Per the chapter's own material, the two operating systems' installers
behave very differently toward each other. Linux's installer -- and
GRUB's own os-prober specifically -- is deliberately built to detect
an already-installed Windows system and add a cooperative menu entry
for it, meaning Linux installed AFTER Windows genuinely accounts for
Windows's presence and incorporates it. Windows's installer has no
equivalent cooperative behavior toward Linux at all -- the chapter is
explicit that it "is not cooperative about detecting other operating
systems and will happily overwrite the boot sector or EFI boot entries
without asking."

If Linux is installed first and Windows is installed second, Windows's
own installer will write its own bootloader into the boot sector (on
BIOS/MBR) or reset itself as the primary UEFI boot entry (on UEFI),
with no awareness that GRUB was already there controlling the boot
process. This directly overwrites or displaces GRUB, exactly the same
mechanism as the chapter's own "Windows Update breaks GRUB" gotcha,
just triggered by the Windows installer itself rather than a later
update. The Linux installation, and GRUB along with it, effectively
becomes unreachable from the boot menu -- requiring the same kind of
repair (reinstalling GRUB, fixing the boot order) the chapter
describes for the Windows-Update scenario.

WHY THIS WORKS AS AN ANSWER
------------------------------
This explains the asymmetry directly from the chapter's own stated
installer behaviors (Linux is cooperative toward Windows, Windows is
not cooperative toward Linux) rather than just asserting "wrong order
breaks things," and connects the resulting failure to the same
mechanism as the chapter's own Windows-Update gotcha.