diff --git a/agentydragon/tasks/20-render-patch-content-in-chat-display.md b/agentydragon/tasks/20-render-patch-content-in-chat-display.md
index f35bf400b3..fd7a3ee730 100644
--- a/agentydragon/tasks/20-render-patch-content-in-chat-display.md
+++ b/agentydragon/tasks/20-render-patch-content-in-chat-display.md
@@ -21,6 +21,7 @@ goal: |
 - Configurable parameter (e.g. `patch_context_lines`) controls the number of context lines for collapsed hunks.
 - Preserve the user’s draft input when an approval dialog or patch diff appears; ensure the draft editor remains visible so users can continue editing while reviewing.
 - Provide end-to-end integration tests that simulate drafting long messages, triggering approval dialogs and overlays, and verify that all UI elements (draft editor, diffs, logs) render correctly without overlap or content loss.
+- Exhaustively test all dialog interaction flows (approve, deny, cancel) and overlay scenarios to confirm consistent behavior across combinations and prevent rendering artifacts.
 
 ## Implementation
 
@@ -30,6 +31,7 @@ goal: |
 - Track the current patch ID and render its full content; collapse previous patch bodies according to `patch_context_lines` setting.
 - Preserve and render the current draft buffer alongside the active patch diff, ensuring live edits remain visible during approval steps.
 - Add integration tests using the TUI test harness or end-to-end framework to simulate user input of long text, approval flows, overlay dialogs, and log output, asserting correct screen layout and content integrity.
+- Design a parameterized test matrix covering all dialog interaction flows (approve/deny/cancel) and overlay transitions to ensure exhaustive coverage and UI sanity.
 - Replace verbose event debug output with a single-line status message.
 
 ## Notes