Remove example YAML files (users.yaml.example, workspaces.example.yaml)

[dcellison]

Parent: #196
Depends on: #193 (users.yaml.example), #195 (workspaces.example.yaml)

Problem

Both example files become redundant once their respective features are Telegram-native:

• users.yaml.example - the config wizard generates users.yaml directly (Replace ALLOWED_USER_IDS with users.yaml in config wizard #193), and the full schema is documented in the README Multi-User section
• workspaces.example.yaml - once workspace config is manageable via Telegram (Manage per-workspace config via Telegram commands #195), the example file's role as "the only way to configure per-workspace settings" disappears

Proposal

1. Delete users.yaml.example (can be done as part of Replace ALLOWED_USER_IDS with users.yaml in config wizard #193)
2. Delete workspaces.example.yaml (after Manage per-workspace config via Telegram commands #195 is merged and stable)
3. Update any references in README.md, CLAUDE.md, or code comments
4. Ensure the README documents both schemas as the single source of truth

Timing

• users.yaml.example: remove in Replace ALLOWED_USER_IDS with users.yaml in config wizard #193 (already in the spec)
• workspaces.example.yaml: remove after Manage per-workspace config via Telegram commands #195 ships and per-workspace config via Telegram is verified working

[dcellison]

Triage by Kai

Triage summary: Cleanup task to remove redundant example YAML files (users.yaml.example, workspaces.example.yaml) once their respective Telegram-native configuration features (#193, #195) are merged and stable. Also requires updating README.md and other references to ensure documentation serves as the single source of truth.

Priority: low
Labels applied: documentation
Related issues: #196, #193, #195