From c071b890ef3eedf128977d26685b16b8cebf155a Mon Sep 17 00:00:00 2001 From: Lucas Berger Date: Sun, 8 Feb 2026 19:35:46 -0500 Subject: [PATCH] docs: start milestone v1.3 Unraid Update Status Sync --- .planning/PROJECT.md | 18 +++++++++++++++--- .planning/STATE.md | 9 +++++---- 2 files changed, 20 insertions(+), 7 deletions(-) diff --git a/.planning/PROJECT.md b/.planning/PROJECT.md index 77a2fbf..f734b7f 100644 --- a/.planning/PROJECT.md +++ b/.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* diff --git a/.planning/STATE.md b/.planning/STATE.md index cfb9f6f..08087c1 100644 --- a/.planning/STATE.md +++ b/.planning/STATE.md @@ -2,16 +2,17 @@ ## Current Position -- **Milestone:** v1.2 SHIPPED -- **Status:** Milestone archived, tagged v1.2 -- **Last activity:** 2026-02-08 -- v1.2 milestone completed and archived +- **Milestone:** v1.3 Unraid Update Status Sync +- **Phase:** Not started (defining requirements) +- **Status:** Defining requirements +- **Last activity:** 2026-02-08 -- Milestone v1.3 started ## Project Reference See: .planning/PROJECT.md (updated 2026-02-08) **Core value:** When you get a container update notification or notice a service is down, you can immediately investigate and act from your phone. -**Current focus:** Planning next milestone +**Current focus:** v1.3 — Sync update status back to Unraid after bot-initiated updates ## Progress