Exercise 1: Mistyped Passwords Aren't Errors — Possible Solution
====================================================================

WHY LOGGING THIS AS ERROR IS A MISUSE
------------------------------
Per this chapter, ERROR means "a specific operation failed - the
request or task genuinely did not complete as intended," reserved for
genuine failures. A mistyped password during login is explicitly named
in this chapter as "completely routine, not a system failure" - the
login system is working exactly as designed by correctly rejecting
invalid credentials. Nothing about the system itself failed; a user
simply entered the wrong password, which the system correctly detected.

WHY THE "IT DID FAIL" ARGUMENT MISSES THE POINT
------------------------------
Per this chapter, the level is meant to capture whether something is
actually wrong with the SYSTEM, not merely whether a particular
individual attempt didn't succeed. Conflating "this specific login
attempt was rejected" with "the system has a problem" is exactly the
kind of ERROR-level misuse the chapter warns leads to alert fatigue -
if every routine rejected login became an ERROR, real errors would be
buried in a flood of routine, expected events.

WHAT LEVEL FITS BETTER
------------------------------
Per this chapter's own level table, this fits INFO - "normal, expected
events... nothing wrong, just a record that something happened." A
failed login attempt due to a wrong password is a normal, anticipated
outcome of a login system, worth recording for audit/security purposes,
but not indicating any actual system malfunction.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains why a mistyped password doesn't represent a
system failure, correctly identifies the conflation the "it did fail"
argument makes, and correctly names INFO as the fitting level per this
chapter's own table.