docs: formalize v1.2 requirements and roadmap

12 requirements across 3 phases:
- Phase 10: Modularization, update all, callback limits (7 reqs)
- Phase 11: Unraid sync, env audit, tech debt (4 reqs)
- Phase 12: Documentation overhaul (1 req)

Removed WEB-01 (webhook fix) - already resolved.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

.planning/PROJECT.md

@@ -35,9 +35,11 @@ When you get a container update notification or notice a service is down, you ca
 **Milestone v1.2: Modularization & Polish**
 
 - [ ] Workflow modularization (break main workflow into sub-workflows)
-- [ ] Environment variable audit (verify TELEGRAM_USERID/BOT_TOKEN necessity)
+- [ ] Update all containers via text command and inline keyboard
+- [ ] Fix callback data limits (batch selection >2 containers, long names)
 - [ ] Unraid update sync (clear "update available" when bot updates container)
-- [ ] Telegram webhook fix (bot responds when workflow is published)
+- [ ] Environment variable audit (verify TELEGRAM_USERID/BOT_TOKEN necessity)
+- [ ] Documentation update (proxy architecture, new features)
 
 ### Out of Scope
 
@@ -93,14 +95,15 @@ When you get a container update notification or notice a service is down, you ca
 
 ## Current Milestone: v1.2 Modularization & Polish
 
-**Goal:** Complete remaining v1.1 scope — modularize workflow for maintainability, fix webhook, audit environment, sync Unraid badges.
+**Goal:** Modularize workflow for maintainability, add "update all" functionality, fix callback limits, and polish remaining issues.
 
 **Target features:**
-- Workflow modularization (carried from Phase 9.1)
-- Webhook fix (WEB-01)
-- Environment audit (ENV-01, ENV-02)
+- Workflow modularization into sub-workflows
+- "Update all" command (text and inline keyboard)
+- Callback data limit fix (batch selection, long names)
 - Unraid badge sync (UNR-01)
-- Documentation overhaul
+- Environment audit (ENV-01, ENV-02)
+- Documentation overhaul (proxy architecture)
 
 ---
 *Last updated: 2026-02-04 after v1.1 milestone*