feat(account): accept a third gender value

Add "OTHER" to the accepted gender values (the column is a free String, so no
migration) and surface it in the account selector. This lets a non-binary or
trans user record their gender and opt into the cycle-tracking surface through
the per-user enable flag, rather than being gated out by a binary field.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

src/components/settings/account-section.tsx

@@ -448,6 +448,7 @@ export function AccountSection() {
                 <option value="">{t("settings.genderNone")}</option>
                 <option value="MALE">{t("settings.genderMale")}</option>
                 <option value="FEMALE">{t("settings.genderFemale")}</option>
+                <option value="OTHER">{t("settings.genderOther")}</option>
               </NativeSelect>
               <p className="text-muted-foreground text-xs">
                 {t("settings.genderHint")}

src/lib/validations/auth.ts

@@ -38,7 +38,7 @@ export const profileSchema = z.object({
   email: z.email("Invalid email address").nullable().optional(),
   heightCm: z.number().min(50).max(300).nullable().optional(),
   dateOfBirth: z.string().nullable().optional(), // ISO date string
-  gender: z.enum(["MALE", "FEMALE"]).nullable().optional(),
+  gender: z.enum(["MALE", "FEMALE", "OTHER"]).nullable().optional(),
   // v1.7.0 — optional patient-identity fields for the health-record
   // export cover + FHIR Patient resource. All optional, never required.
   fullName: z.string().trim().max(120).nullable().optional(),