[RajGahoi]

Context

Addresses #74 by adding documentation on why semicolon-separated UTF-8 CSV exports open into a single column when regional settings use a comma list separator (such as English Windows), and providing exact steps to import the data correctly in Microsoft Excel and LibreOffice Calc.

What changed

1. docs/troubleshooting.md:
   • Added a ## Reports section before ## Licences.
   • Added an entry for "A CSV export opens in a single column" explaining the Turkish Windows semicolon (;) delimiter and UTF-8 BOM.
   • Documented exact step-by-step instructions for:
     • Microsoft Excel: Using Data → From Text/CSV with 65001: Unicode (UTF-8) and semicolon delimiter (and alternative via Data → Text to Columns).
     • LibreOffice Calc: Using the Text Import dialog with semicolon separator and UTF-8 charset.
2. docs/faq.md:
   • Linked the FAQ answer "Can I export data to a spreadsheet?" directly to [Troubleshooting: Reports](troubleshooting.md#reports).
3. CHANGELOG.md:
   • Added documentation entry under [Unreleased] -> Added.

Verification

• Verified Markdown links and anchor targets resolve cleanly (troubleshooting.md#reports).
• Verified steps match Excel and LibreOffice Calc CSV import workflows.
• Zero trailing whitespace or lint issues.

Closes #74