Exercise 1: Why Delete-Item Doesn't Exist — Possible Solution
====================================================================

WHY DELETE-ITEM FAILS
------------------------------
PowerShell cmdlets are named Verb-Noun, where the verb must come from a fixed, curated "approved verbs" list (viewable with Get-Verb) rather than any word that happens to describe the action in plain English. "Delete" was never added to that approved list, so no cmdlet named Delete-Item was ever created - PowerShell isn't silently rejecting a valid name, the name simply doesn't correspond to anything that exists.

THE ACTUAL CMDLET
------------------------------
Remove-Item is the real cmdlet for deleting a file, folder, registry key, or other item - "Remove" is the approved verb PowerShell actually uses for this class of action.

THE CONCEPT THAT EXPLAINS WHY "DELETE" WAS NEVER VALID
------------------------------
The approved-verb system: every cmdlet, in every module built-in or third-party, is expected to draw its verb from the same fixed list of roughly 100 approved verbs, grouped by intent (Common, Lifecycle, and so on). This isn't arbitrary strictness - it's what makes cmdlet names predictable enough to guess correctly across an entire ecosystem, even in modules you've never used before.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that Delete-Item fails because "Delete" isn't an approved verb (not because of a typo or missing module), correctly names Remove-Item as the real cmdlet, and correctly identifies the approved-verb list as the underlying concept responsible.