Exercise 1: A Hardcoded jQuery Tag Alongside a Properly Enqueued One — Possible Solution
====================================================================

WHAT ACTUALLY HAPPENS ON THE PAGE
------------------------------
jQuery gets loaded twice - once from the theme's own hardcoded
<script src="jquery.js"> tag in header.php, and once from the plugin's
own properly enqueued copy via wp_enqueue_script() with 'jquery' as
its own handle/dependency.

WHY WORDPRESS'S DEPENDENCY SYSTEM DOESN'T PREVENT THIS
------------------------------
Per this chapter, WordPress's built-in deduplication only works through
its own registered-handle system - "if jQuery is already enqueued by
anything else... WordPress won't load a second copy." That protection
only applies to copies of jQuery loaded THROUGH wp_enqueue_script()
using the shared 'jquery' handle. The theme's hardcoded script tag
never goes through that system at all - it's a plain, static HTML tag
WordPress has no visibility into, no way to detect, and no way to
deduplicate against. WordPress's own dependency tracking simply doesn't
know the hardcoded tag exists.

WHY THIS MATCHES THIS CHAPTER'S OWN WARNING
------------------------------
Per this chapter's own warn-box, "two plugins each hardcoding their own
<script src='jquery.js'> tag, with no shared handle and no dependency
system involved, can genuinely load two separate copies of jQuery on
the same page - wasted bandwidth at best, and real, hard-to-diagnose
JavaScript conflicts at worst, since two independently-loaded copies of
the same library don't share state with each other." This scenario is
exactly that situation, just with one hardcoded copy and one properly
enqueued copy instead of two hardcoded copies - the underlying problem
(the hardcoded copy bypassing WordPress's own tracking entirely) is
identical.

WHY THIS COULD CAUSE REAL, CONFUSING BUGS
------------------------------
Because the two jQuery copies don't share internal state, JavaScript
code relying on jQuery plugins or event bindings registered against one
copy might silently fail to work when interacting with elements
handled by the other copy - a genuinely confusing bug with no obvious
connection back to "there are two separate jQuery instances running."

WHY THIS WORKS AS AN ANSWER
------------------------------
It states the concrete outcome (jQuery loaded twice), explains
precisely why WordPress's own deduplication system fails to catch this
specific case (the hardcoded tag bypasses it entirely), and connects
the scenario directly to this chapter's own warn-box about the real
risks of duplicate library loads.