docs: start milestone v1.3 Unraid Update Status Sync

.planning/PROJECT.md

@@ -46,7 +46,10 @@ When you get a container update notification or notice a service is down, you ca
 
 ### Active
 
-(No active requirements — define in next milestone)
+**v1.3: Unraid Update Status Sync**
+- [ ] After bot updates a container, Unraid recognizes it as current (no stale badges)
+- [ ] No false-positive Unraid Telegram notifications for containers already updated via bot
+- [ ] No manual Unraid login required to clear update status after bot updates
 
 ### Out of Scope
 
@@ -112,7 +115,16 @@ When you get a container update notification or notice a service is down, you ca
 | Action-based sub-workflow routing | Sub-workflow returns action field, main routes to Telegram handlers | ✓ Good |
 | Correlation IDs without persistent logging | Timestamp+random string traces requests; ring buffer non-viable on n8n | ✓ Good |
 | Infrastructure container exclusion | Exclude n8n and socket-proxy from "update all" to prevent self-destruction | ✓ Good |
-| Document Unraid badge as limitation | Unraid API integration adds complexity for cosmetic issue | ✓ Good |
+| Document Unraid badge as limitation | Unraid API integration adds complexity for cosmetic issue | ⚠️ Revisit |
+
+## Current Milestone: v1.3 Unraid Update Status Sync
+
+**Goal:** After the bot updates a container, Unraid recognizes it's current — no stale badges, no false-positive notifications.
+
+**Target features:**
+- Sync update status back to Unraid after bot-initiated container updates
+- Eliminate false-positive Unraid Telegram notifications for already-updated containers
+- (Nice-to-have) Use Unraid's update detection data in the bot's update flow
 
 ---
-*Last updated: 2026-02-08 after v1.2 milestone*
+*Last updated: 2026-02-08 after v1.3 milestone started*