Phase 4: Cleanup and documentation

[poodle64]

Overview

Remove deprecated WebView code after stabilisation period and update documentation.

Tasks

• Remove src/routes/(indicator)/recording-indicator/ directory
• Remove indicator_window_ready() Tauri command
• Remove recording-audio-level event handling
• Remove native-indicator feature flag (now default)
• Update README with new architecture
• Update architecture docs
• Add performance comparison notes (before/after metrics)
• Update troubleshooting guide

Acceptance Criteria

• No WebView indicator code remains
• Documentation reflects new architecture
• Migration guide exists for any breaking changes
• Performance improvements documented

Dependencies

• Requires Phase 3: Integrate with audio pipeline and replace WebView #26 (Phase 3) to be completed
• Requires stabilisation period (at least 1 release with both implementations)

Estimated Effort

Small (2-4 hours)

Milestone

Native Rendering for Recording Indicator

References

• Architecture doc: docs/architecture/native-indicator-renderer.md

[poodle64]

Status Update

Phase 3 has just been completed, but this phase requires at least 1 release with stabilisation before proceeding.

Already Completed in Phase 3

• indicator_window_ready command removed
• recording-audio-level event emission replaced with direct native calls
• Feature flag native-indicator added and enabled by default
• WebView fallback remains functional when feature disabled

Remaining Tasks After Stabilisation

• Remove src/routes/(indicator)/recording-indicator/ directory
• Remove feature flag (make native-only)
• Remove WebView fallback code
• Update documentation
• Add performance comparison metrics

Recommendation

Do NOT proceed with Phase 4 until:

1. At least one release has shipped with native-indicator enabled by default
2. User feedback confirms stability
3. No critical issues reported

The dual implementation provides safety during the transition period.

Timeline Suggestion

• Now (2026.2.x): Ship with native-indicator as default, WebView as fallback
• Monitor: Collect feedback for 1-2 releases
• Later (2026.4.x+): Execute Phase 4 cleanup after confidence established

This follows the migration strategy outlined in IMPLEMENTATION_PLAN.md.