docs(docsite): correct the backdropGlow comment's causal chain

[imdreamrunner]

Follow-up to #5415 (issue #5392). Comment only — no behavior change, no CSS change.

Why

The backdropGlow comment added in #5415 states the wrong cause:

a fixed glow below 1024px reached past the footer into the bottom-overscroll gap, which blocked pull-to-refresh from ever registering a release

The glow never blocked pull-to-refresh. overscroll-behavior-y: none in globals.css did — the glow is the reason that rule was written. That direction matters: the rule suppressed the whole page's overscroll to hide one bleeding layer, and bounding the layer is precisely what let the rule retreat to desktop widths.

As written, the comment tells the next person the glow is the thing that breaks pull-to-refresh, which would send them to the wrong file. It is the durable record of this decision, so it is worth being right.

What

- for the whole page — a fixed glow below 1024px reached past the
- footer into the bottom-overscroll gap, which blocked pull-to-refresh
- from ever registering a release (#5392).
+ for the whole page — a fixed glow below 1024px reached past the footer
+ into the bottom-overscroll gap. That exposure is what the app-global
+ `overscroll-behavior-y: none` in globals.css was suppressing, at the
+ cost of pull-to-refresh on every route on mobile; bounding the glow
+ here is what lets that rule scope to desktop widths (#5392).

Risk

None. Five comment lines in one file.

Testing

prettier --check and eslint --no-cache clean on the changed file; check:changesets passes (no changeset — docsite app code, not a published package, and no consumer-visible change).

Opened as a draft since it is cosmetic — happy to close it if you would rather leave the comment as-is.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
astryx	Ready	Preview	Aug 25, 2026 2:04am