---
phase: 12-polish-audit
plan: 02
type: execute
wave: 1
depends_on: []
files_modified: []
autonomous: false

must_haves:
  truths:
    - "User can type 'update all' and see confirmation listing :latest containers"
    - "User can tap 'Update All :latest' button in container list keyboard and see confirmation"
    - "Confirming update-all triggers batch execution with progress updates"
    - "Final summary shows success/failure counts for updated containers"
  artifacts: []
  key_links:
    - from: "Keyword Router"
      to: "Get All Containers For Update All"
      via: "update all text command routing"
      pattern: "update all"
    - from: "Route Callback [updateallstart]"
      to: "Answer Update All Start"
      via: "uall:start callback routing"
      pattern: "updateallstart"
---

<objective>
Execute deferred Phase 11 UAT tests for Update All functionality (BATCH-04 text command, BATCH-05 inline keyboard button).

Purpose: Complete the two UAT tests deferred from Phase 11. Code is already deployed -- this is validation only.
Output: UAT results confirming Update All works end-to-end via both entry points.
</objective>

<execution_context>
@/home/luc/.claude/get-shit-done/workflows/execute-plan.md
@/home/luc/.claude/get-shit-done/templates/summary.md
</execution_context>

<context>
@.planning/PROJECT.md
@.planning/ROADMAP.md
@.planning/STATE.md
@.planning/phases/11-update-all-callback-limits/11-02-SUMMARY.md
@.planning/phases/11-update-all-callback-limits/11-VERIFICATION.md
</context>

<tasks>

<task type="checkpoint:human-verify" gate="blocking">
  <name>Task 1: UAT -- Update All via text command (BATCH-04)</name>
  <files>n8n-workflow.json</files>
  <action>
User verifies the Update All text command end-to-end. This was deployed in Phase 11 (Plan 11-02) but UAT was deferred. The Keyword Router matches "update all" and routes to Get All Containers For Update All, which filters :latest containers and shows a confirmation dialog. No code changes needed -- this is validation only.
  </action>
  <verify>
**Preconditions:**
- Workflow is active and deployed
- You have containers with :latest tag on your Unraid server

**Test Steps:**

1. Send "update all" to the bot via Telegram
2. **Expected:** Bot responds with a confirmation message listing all containers with :latest tag and their current status
3. Verify the container count in the confirmation matches your actual :latest container count
4. Tap the "Confirm" button
5. **Expected:** Progress message appears showing batch execution starting
6. Wait for execution to complete
7. **Expected:** Final summary message shows N succeeded, M failed (ideally 0 failed)
8. Send "/status" to verify containers show updated status

**Pass criteria:**
- Confirmation lists all :latest containers
- Progress updates appear during batch execution
- Summary shows accurate success/failure counts
- No error messages or timeouts
  </verify>
  <done>
User confirms "update all" text command triggers confirmation dialog, batch execution with progress, and summary. BATCH-04 UAT complete.
  </done>
</task>

<task type="checkpoint:human-verify" gate="blocking">
  <name>Task 2: UAT -- Update All via inline keyboard (BATCH-05)</name>
  <files>n8n-status.json, n8n-workflow.json</files>
  <action>
User verifies the Update All inline keyboard button end-to-end. This was deployed in Phase 11 (Plan 11-02). The container list keyboard in n8n-status.json includes a "Update All :latest" button with callback data `uall:start`. When tapped, Route Callback matches `updateallstart` and routes through Answer Update All Start to the same confirmation flow as the text command. No code changes needed -- this is validation only.
  </action>
  <verify>
**Preconditions:**
- Same as Task 1 (workflow active, :latest containers present)

**Test Steps:**

1. Send "/status" or "/list" to the bot to display the container list keyboard
2. Locate the "Update All :latest" button in the inline keyboard (below navigation, above Select Multiple)
3. Tap the "Update All :latest" button
4. **Expected:** Bot acknowledges with "Checking for updates..." callback answer
5. **Expected:** Confirmation message appears listing all :latest containers (same as text command flow)
6. Tap "Confirm" button
7. **Expected:** Same batch execution flow as Task 1 (progress, summary)
8. Send "/status" to verify containers show updated status

**Pass criteria:**
- "Update All :latest" button visible in container list keyboard
- Tapping button shows confirmation dialog with :latest containers
- Confirmation and batch execution work identically to text command
- No error messages or timeouts
  </verify>
  <done>
User confirms "Update All :latest" inline keyboard button triggers same confirmation and batch execution flow as text command. BATCH-05 UAT complete.
  </done>
</task>

</tasks>

<verification>
- BATCH-04 (Update All text command) passes end-to-end UAT
- BATCH-05 (Update All inline keyboard) passes end-to-end UAT
- Both entry points produce identical confirmation and execution flows
</verification>

<success_criteria>
- User successfully triggers Update All via "update all" text command with confirmation and batch execution
- User successfully triggers Update All via inline keyboard button with confirmation and batch execution
- Both Phase 11 deferred UAT tests completed with pass/fail determination
</success_criteria>

<output>
After completion, create `.planning/phases/12-polish-audit/12-02-SUMMARY.md`
</output>