TASK: Fix remaining tone persistence issue caused by Title Case default state values.
You must edit TWO files exactly as described. Do not change anything else.
────────────────────────────────────────────────────────────
FILE 1: app/settings/page.tsx
────────────────────────────────────────────────────────────
Problem:

• The initial React state for xPreferences.tone and linkedinPreferences.tone is still Title Case (e.g., "Professional").
• The dropdown option values are now lowercase ("professional", "casual", etc.).
• When <select value="Professional"> but no <option value="Professional"> exists, the dropdown looks blank/wrong until settings load, which feels like Save did not work.
  Required fix:

1. Find the initial state objects for:
   • const [xPreferences, setXPreferences] = useState(...)
   • const [linkedinPreferences, setLinkedInPreferences] = useState(...)
2. Change the default tone values from Title Case to lowercase:
   • Change tone: "Professional" → tone: "professional"
3. Do NOT change hashtags or platform names.
   Exact replacements you must make:

• In xPreferences initial state:
  replace: tone: 'Professional'
  with: tone: 'professional'
• In linkedinPreferences initial state:
  replace: tone: 'Professional'
  with: tone: 'professional'
  Make sure the final default is exactly 'professional' (all lowercase).
  ────────────────────────────────────────────────────────────
  FILE 2: components/settings/posting-preferences.tsx
  ────────────────────────────────────────────────────────────
  Problem:
• Even after fixing defaults, future refactors or bad data could still set preferences.tone to Title Case.
• Make the <select> defensive by always lowercasing the value prop.
  Required fix:

1. Locate the X tone <select> element (the one using xPreferences.tone).
2. Change the value prop to ALWAYS lowercase:
   replace:
   value={xPreferences.tone || 'professional'}
   with:
   value={(xPreferences.tone || 'professional').toLowerCase()}
3. Locate the LinkedIn tone <select> element (the one using linkedinPreferences.tone).
4. Change the value prop to ALWAYS lowercase:
   replace:
   value={linkedinPreferences.tone || 'professional'}
   with:
   value={(linkedinPreferences.tone || 'professional').toLowerCase()}
   Do NOT change:

• toneOptions array
• labels
• option value attributes
• onChange handlers
  Acceptance check after this task:
• Before settings load, the dropdown must still show “Professional” (label) by matching the lowercase value "professional".
• No blank/empty dropdown state should appear due to casing mismatch.

TASK: Fix Venice generator hashtags type mismatch and prompt formatting.
You must edit ONE file exactly as described. Do not change anything else.
────────────────────────────────────────────────────────────
FILE: lib/venice-generator.ts
────────────────────────────────────────────────────────────
Problem:

• The call site passes hashtags as an array: platformOptions.hashtags || []
• But the Venice generator currently defines hashtags as a string (hashtags?: string).
• This is a TypeScript mismatch and can break builds or produce wrong prompt formatting.
  Required fixes:

1. Update the function signature to accept hashtags as a string array:
   Find the parameter that currently looks like:
   hashtags?: string
   Replace it with:
   hashtags?: string[]
2. Fix the prompt interpolation to format hashtags nicely:
   Find the part of the prompt construction that currently includes something like:
   Suggested hashtags: ${hashtags}
   or a conditional like:
   ${hashtags ? Suggested hashtags: ${hashtags} : ''}
   Replace that logic with this exact behavior:
   • If hashtags is defined AND hashtags.length > 0:
     include: "Suggested hashtags: " + hashtags joined by ", "
     Example: Suggested hashtags: #AI, #Tech, #Startup
   • If hashtags is missing or empty:
     include nothing.
     Implement this exact expression (or equivalent) in the prompt:
     ${hashtags && hashtags.length ? Suggested hashtags: ${hashtags.join(', ')} : ''}
3. Do NOT remove or replace the existing Venice API call logic.
   • Keep the same request structure and parsing logic you already have.
   • Only adjust:
     • function signature type
     • prompt string assembly / interpolation
4. Make sure the return type stays consistent with the caller:
   The function must still return:
   { content: string; hashtags: string[] }
   If you currently return hashtags as a string, fix it so it returns an array of strings.
   Acceptance check after this task:

• TypeScript should no longer complain about passing string[] into the Venice generator.
• The Venice system/user prompt must contain a clean hashtags line when hashtags are provided.
• When hashtags are empty, the prompt must not contain “Suggested hashtags:” at all.