fix(16): revise plans based on checker feedback

.planning/phases/16-api-migration/16-03-PLAN.md

@@ -13,6 +13,7 @@ must_haves:
     - "User sees 'already up to date' when no update is available"
     - "User sees error message when update fails (pull error, container not found)"
     - "Update success/failure messages sent via both text and inline keyboard response modes"
+    - "Unraid Docker tab shows no update badge after bot-initiated container update (badge cleared automatically by updateContainer mutation)"
   artifacts:
     - path: "n8n-update.json"
       provides: "Single container update via Unraid GraphQL updateContainer mutation"
@@ -202,6 +203,7 @@ n8n-update.json uses single updateContainer GraphQL mutation instead of 5-step D
 5. All 3 response paths work: success, no-update, error
 6. Format Result Code nodes reference correct upstream nodes
 7. Push to n8n with HTTP 200
+8. After a successful container update via bot, verify Unraid Docker tab shows no update badge for that container (badge cleared automatically by updateContainer mutation — requires Unraid 7.2+)
 </verification>
 
 <success_criteria>
@@ -211,6 +213,7 @@ n8n-update.json uses single updateContainer GraphQL mutation instead of 5-step D
 - Success/no-update/error messaging identical to user
 - Container ID Registry refreshed after successful update
 - Node count reduced by ~15 nodes
+- Unraid Docker tab update badge clears automatically after bot-initiated update (Unraid 7.2+ required)
 - Workflow valid and pushed to n8n
 </success_criteria>