fix(suggest): let the dropdown out of the hero panel

.heroPanel had overflow: hidden to clip its artwork and scrim to the
rounded corners. It clipped the suggestion dropdown too. Measured on
staging with the flag on: the list runs 482 to 802, the panel ends at
624 — so 178px of 320 was cut off, about half the options, with nothing
on screen to say anything was missing.

The two things that actually needed clipping now round themselves:
.heroArt gets border-radius: inherit plus its own overflow, and the
::before scrim inherits the radius. Below 860px the artwork is a band
flush with the top of the panel rather than a layer covering it, so it
takes the top two corners only — inheriting all four would leave it
floating with rounded corners against the copy.

Nothing else depended on the panel clipping: .valueProps below it is
entirely static, so a positioned dropdown paints above it without a
z-index fight.

The regression test asserts the LAST option is the element actually
painted at its own coordinates. toBeVisible() would not have caught
this — it checks for a non-empty box and visibility, and an ancestor's
overflow clips neither. elementFromPoint catches clipping and occlusion
alike.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015mWQnpye9F299NVRCCSRvj

docs/DEPLOY.md

@@ -206,30 +206,11 @@ registry is orphaned and nothing reads it.
    variable, and set `UNLEASH_URL` to `http://<UNLEASH_IP>:4242/api`.
 5. Redeploy the application stacks.
 
-### Adding a flag to Unleash
-
-**Unleash does not create flags by itself.** The SDK reads definitions from the
-server and never registers anything, and metrics for a flag the server has
-never heard of are discarded. So a flag declared in `backend/flags.py` will be
-evaluated on every request, stay `False` forever, and never appear in the UI
-until someone creates it there by hand.
-
-For each flag in the registry, create one in Unleash with:
-
-- **Name** — character for character what `backend/flags.py` declares.
-  snake_case, no hyphens or spaces. A typo produces a flag that looks correct
-  in the UI and is read by nothing.
-- **Type** — Release. No strategies, constraints or variants: these are plain
-  on/off switches, by design.
-
 ### Turning a feature on
 
-Toggle the flag in the environment matching the stack you mean: **development**
-for staging, **production** for prod. The token in each stack is scoped to one
-environment, so toggling the other one has no visible effect.
-
-The SDK refreshes every 15 seconds, so the API reflects the change almost at
-once; the pages follow on their own schedule, below.
+Toggle the flag in the environment you want. Flags appear in the Unleash UI
+after the backend has evaluated them once, so a newly declared flag shows up
+shortly after the deploy that introduced it.
 
 A flip reaches school pages within about five minutes and place pages within
 the hour. Next's ISR does the propagating — it revalidates a route at the