foolish-bandit/gary: Explain This flow and UX polish -- closed without merging

foolish-bandit proposed a batch of frontend changes centered on a new `/explain` page, unified backend-unavailable messaging, an "Ask Gary" sidebar rename, and a font strategy swap from `next/font/google` to `@fontsource/inter`. The PR was closed without merging; none of it landed in Gary's main branch.

The proposed /explain surface takes a piece of legal text, optional context/goal/tone fields, assembles a structured prompt ("What it says, Why it matters, What could go wrong, Possible revision."), and hands off to useAssistantChat.handleNewChat. The backend-unavailable messaging was intended to standardise the error strings across draft, review, and explain -- replacing ambiguous "Could not start" copy with a single explicit message naming GaryOSS and the missing backend dependency.

Other changes in the proposal: the initial view expands from four to five action cards to include Explain This. Desktop sidebar persistence is fixed by routing open/closed state through a single variable. The login and signup pages pick up a visible banner when NEXT_PUBLIC_GARY_SKIP_AUTH is set, so the dev bypass stops being invisible to anyone running locally.

The font swap moves from next/font/google to @fontsource/inter, with CSS variables adjusted to keep the serif utility functional. foolish-bandit reported a clean local build and lint pass.

The substance here was largely superseded by a subsequent PR (#15) that landed a similar batch with shadcn/ui primitives added on top. The unmerged PR is most useful as a reference for the individual pieces -- the error message standardisation approach in particular is visible and unchanged between the two.