docs(12): plan phase with Unraid badge research and UAT
Research found Unraid badge issue is architectural (bot bypasses Unraid's XML template system). Updated plans to document limitation with workaround instead of attempting programmatic fix. Plan 01 covers docs/env/debt, Plan 02 covers deferred Update All UAT. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -139,7 +139,7 @@ Plans:
|
||||
- [ ] 12-02-PLAN.md — Deferred UAT: Update All text command (BATCH-04) and inline keyboard (BATCH-05)
|
||||
|
||||
**Success Criteria:**
|
||||
1. After bot successfully updates a container, Unraid UI no longer shows "update available" for that container
|
||||
1. Unraid update badge behavior documented as known limitation with workaround (bot bypasses Unraid template system)
|
||||
2. Documentation clarifies whether TELEGRAM_USERID env var is required or can be hardcoded
|
||||
3. Documentation clarifies whether TELEGRAM_BOT_TOKEN env var is required or if n8n credential suffices
|
||||
4. Image pull command has single --max-time flag (600s)
|
||||
|
||||
Reference in New Issue
Block a user