Exercise 3: Audit Your Installed Extensions — Possible Solution
====================================================================

STEPS
------------------------------
1. Press Ctrl+Shift+X to open the Extensions view.
2. Click the dropdown/filter icon at the top of the view and select
   "Installed" (or scroll down — installed extensions are grouped
   separately from search results by default).
3. Go through the full list one at a time. For each extension, ask
   honestly: "Have I actually used this feature in the last month?"

EXAMPLE AUDIT (illustrative — yours will differ)
------------------------------
- Prettier          -> used daily (Format on Save)      -> KEEP
- GitLens            -> used weekly for blame/history     -> KEEP
- Docker             -> installed months ago, never opened -> UNINSTALL
- A random theme pack -> switched away from it long ago    -> UNINSTALL
- ESLint             -> used on every JS project           -> KEEP

4. For each item marked UNINSTALL, click the gear icon (or right-
   click) next to it and choose "Uninstall."

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies the chapter's own "Extension Bloat"
section — the honest last-month-usage test is exactly the practical
version of the chapter's more abstract point that "a handful of
well-chosen extensions genuinely used every day beats a large pile
installed just in case."

Doing this periodically (not just once) matters because the warn-box's
security point compounds over time: every extension left installed,
used or not, is still an ongoing piece of code with real permissions
running on your machine, and still needs updates tracked and trust
maintained — removing ones that provide no ongoing value reduces that
surface area for no real cost.