Discourse Pr

PR Description Rules

Immediately after the commit message, output a Markdown PR description using exactly this format:

Previously, [brief description of the old state or issue].

In this update, [brief description of the change].

Keep both sections extremely brief — ideally one sentence each.

Constraints

• Never use lowercase "conventional commit" prefixes (e.g., fix:, feat:).

Example Output

UX: Improve `UserSelector` contrast for dark mode

**Previously**, the text in the `UserSelector` component was difficult to read on dark backgrounds due to low contrast.

**In this update**, updated the text color to use the `--primary-medium` CSS variable.

Steps

1. Determine the diff: run git diff main...HEAD (or fall back to session changes).
2. Read through the changed files to understand the purpose of the changes.
3. Pick the single most appropriate prefix based on the nature of the change.
4. Write the commit message subject line.
5. Write the two-sentence PR description.
6. Output both together, ready to copy.