Show what each setting option looks like before you switch it

[guilhermelippert]

Problem

Some settings are hard to understand from their one-line description, especially for people who are not deeply technical. When I turned on settings like these, I couldn't tell right away what had changed:

• Project grouping: "Combine matching repositories across environments." What counts as matching, and what does the sidebar look like on vs. off?
• Submodules: "Recursive", "Top level only", and "Skip" assume you already know how git worktree add treats submodules.
• Proactive panels: from the description it's hard to picture what opens on its own and when.

Today the only way to learn is to flip the setting, then go hunting for the difference.

Proposal

Add a small ⓘ next to the setting title. It opens a card showing each option side by side as a tiny schematic of the UI in that state, with a short caption, and marks the option that is currently active.

Before: Project Grouping

After: Project Grouping

After: Proactive Pannels

Gif:

How the prototype works:

• It's opt-in per row: SettingsRow takes an optional help node. Rows without it are unchanged.
• The schematics are plain JSX with theme tokens (no images or new dependencies), so they follow light and dark themes. There's no custom animation.
• It uses the existing Popover with openOnHover: it opens on hover, click, tap, and Enter/Space, so touch devices work too.
• The "current" marker reads the real setting value. When the value is mixed across environments or unset, nothing is marked.

Working prototype: https://github.com/guilhermelippert/t3code/tree/feat/settings-help

Scope questions

1. Is this direction something you'd want? If so, which settings should get it? I started with these three because their effect is the least visible from the description. More can follow one at a time if the pattern holds up.
2. Hover vs. click: Add a possibility to disable Hover Cards / Popovers #24373 asks for a way to turn off hover cards. Would you rather this open only on click/tap?
3. The native mobile app is out of scope here. This only covers web and desktop settings.

If the direction and scope get approval, I'll open a focused PR that links this discussion and includes before/after evidence.