meta: create project roadmap (v2.0 vision)

[chernistry]

Summary

Create a public project roadmap (docs/ROADMAP.md) that outlines the vision for RightLayout v2.0 and beyond. This gives the community direction, helps potential contributors find meaningful work, and signals that the project has long-term ambitions.

Why This Matters

• Contributors want to work on something with a future -- a roadmap signals commitment
• Users want to know if their desired feature is planned
• Prevents duplicate feature requests by showing what is already planned
• "Vote with thumbs up" on roadmap items = free prioritization data
• Makes the project look mature and well-maintained

Proposed Roadmap Structure

docs/ROADMAP.md

# RightLayout Roadmap

This document outlines the planned direction for RightLayout.
Vote on items with a thumbs-up reaction to help us prioritize.

## Phase 1: Language Expansion (Current)

Goal: Support the 10 most-requested languages.

- [x] English <-> Russian
- [x] English <-> Hebrew
- [ ] English <-> Arabic
- [ ] English <-> Ukrainian
- [ ] English <-> German (QWERTZ)
- [ ] English <-> French (AZERTY)
- [ ] English <-> Spanish
- [ ] English <-> Polish
- [ ] English <-> Turkish
- [ ] English <-> Japanese (Romaji)

## Phase 2: Power User Features

Goal: Make RightLayout indispensable for daily use.

- [ ] Correction undo with Cmd+Z
- [ ] Statistics dashboard
- [ ] Privacy mode for password fields
- [ ] Dvorak/Colemak support
- [ ] Per-app language preferences
- [ ] Custom dictionary / exclusion list
- [ ] Correction sound feedback

## Phase 3: Platform Expansion

Goal: Bring RightLayout beyond macOS.

- [ ] Linux support -- X11/Wayland input monitoring
  - Feasibility: Medium. Linux has IBus/Fcitx frameworks.
  - Challenge: No unified accessibility API like macOS.

- [ ] iOS keyboard extension -- Auto-correct at the keyboard level
  - Feasibility: High. iOS custom keyboards are well-documented.
  - Challenge: App Store review, keyboard extension sandbox limitations.

- [ ] Browser extension -- Chrome/Firefox extension for web-only use
  - Feasibility: High. Content scripts can monitor and modify text fields.
  - Challenge: Will not work in all web apps (Canvas-based editors).
  - Advantage: Cross-platform (works on Windows/Linux via browser).

- [ ] Windows support -- Native Windows app
  - Feasibility: Medium. Windows has SetWindowsHookEx for keyboard hooks.
  - Challenge: Completely different codebase (C++/Rust, not Swift).

## Phase 4: Intelligence

Goal: Make detection smarter and more context-aware.

- [ ] Context-aware detection -- Use surrounding text to improve accuracy
- [ ] User learning -- Adapt to individual typing patterns over time
- [ ] Multi-word detection -- Detect wrong layout mid-sentence, not just per-word
- [ ] Code-aware mode -- Do not correct in code editors (or be smarter about it)
- [ ] URL/email detection -- Never correct URLs, email addresses, or file paths

## Non-Goals

Things we intentionally will NOT do:
- Spell checking (use macOS built-in or Grammarly)
- Grammar correction (different problem domain)
- Keystroke logging or analytics without explicit opt-in
- Paid/premium features (RightLayout is free and open source)

Issue Cross-References

Replace placeholders with actual issue numbers from the issues we have created.

Acceptance Criteria

• docs/ROADMAP.md created with all phases
• Issue numbers linked where applicable
• "Vote with thumbs up" instruction included
• Non-goals section included (sets expectations)
• Contributing section points to existing contributing guide
• Written in clear, non-marketing language
• Feasibility assessments are honest (not hype)

Maintenance

The roadmap should be updated:

• When a roadmap item is completed (check it off)
• When priorities change based on community feedback
• At each major release (add new phase or revise existing ones)