Docs

docs/plans/feature-0-foundation.md

@@ -1,5 +1,7 @@
 # Feature 0: Foundation
 
+**Status:** ✅ **Completed**
+
 ## Context
 Before implementing any user-facing features, we need shared infrastructure: package structure, platform abstraction, config persistence, and logging. Every subsequent feature depends on this.
 

docs/plans/feature-1-system-tray.md

@@ -1,5 +1,7 @@
 # Feature 1: System Tray Icon
 
+**Status:** ✅ **Completed**
+
 ## Context
 The app lives primarily in the system tray. The window is secondary — it opens for configuration/status and closes back to tray. This is the shell that all UI features plug into.
 

docs/plans/feature-2-configuration.md

@@ -1,5 +1,7 @@
 # Feature 2: Configuration Screen
 
+**Status:** ✅ **Completed**
+
 ## Context
 The configuration screen is the primary setup interface. It appears automatically on first run (when config is incomplete) and is accessible anytime via the tray menu. All backup behavior depends on the values set here.
 

docs/plans/feature-3-backup.md

@@ -1,5 +1,7 @@
 # Feature 3: Backup
 
+**Status:** ✅ **Completed**
+
 ## Context
 This is the core functionality — automatically backing up WoW's WTF and Interface folders on a daily schedule. The backup runs in the background, respects configuration, and notifies the user of results.
 

docs/plans/feature-4-status.md

@@ -1,5 +1,7 @@
 # Feature 4: Status Screen
 
+**Status:** ✅ **Completed**
+
 ## Context
 The status screen is the default view when the user clicks the tray icon. It gives a quick overview of backup health and provides shortcuts to key actions.
 

docs/plans/feature-5-restore.md

@@ -1,5 +1,7 @@
 # Feature 5: Restore
 
+**Status:** 🚧 **Pending / Next Priority**
+
 ## Context
 Allows users to restore a previous backup, replacing their current WoW configuration. This is a destructive operation (overwrites current WTF/Interface folders), so it requires clear confirmation and progress feedback.