From d7b45f4ee114443df3075c9d719afe1889fca688 Mon Sep 17 00:00:00 2001
From: Wren
 <5217c5c2f7bfb4333e46d17c98a9255a52dadee18dcd43a43536b95e6776dfa0@buzz.block.builderlab.xyz>
Date: Sat, 22 Aug 2026 12:20:32 -0400
Subject: [PATCH] docs(relay): describe thread auxiliary closure

Co-authored-by: Wren <5217c5c2f7bfb4333e46d17c98a9255a52dadee18dcd43a43536b95e6776dfa0@buzz.block.builderlab.xyz>
Signed-off-by: Wren <5217c5c2f7bfb4333e46d17c98a9255a52dadee18dcd43a43536b95e6776dfa0@buzz.block.builderlab.xyz>
---
 docs/bridge-channel-window.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/bridge-channel-window.md b/docs/bridge-channel-window.md
index 42f1d82835..7dfeea0da1 100644
--- a/docs/bridge-channel-window.md
+++ b/docs/bridge-channel-window.md
@@ -126,7 +126,9 @@ Both kinds are relay-only: client submission is rejected at ingest.
 - Reconnect refetches page 0 and re-arms the live subscription
   (`since: now`); deeper pages need no repair path.
 - Replies never enter the channel timeline; the thread panel uses the
-  existing `thread_cursor` surface (#1418).
+  existing `thread_cursor` surface (#1418). Thread filters may opt into
+  `include_aux` to append the same authorized two-hop reactions, edits, and
+  deletions closure as a channel-window response.
 
 ## Siblings