From 67552d56cce45a4fedffa544f9f6e3bbcc418fcd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=EA=B9=80=EC=A4=80=ED=98=B8?=
 <101695482+chordpli@users.noreply.github.com>
Date: Wed, 4 Nov 2026 20:03:56 +0900
Subject: [PATCH] docs(limits): say setup forwards the selected MCP response
 budget (#8342)

The design guide said the setup allowlist does not copy
REA_MCP_MAX_RESPONSE_BYTES, but SELECTED_REGISTRATION_SETTINGS includes
it and setup forwards an explicit selection, as the client guide states.

Fixes #7420
---
 docs/design/limits-and-recovery.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/design/limits-and-recovery.md b/docs/design/limits-and-recovery.md
index 9eccda38fb..c6ea9dde98 100644
--- a/docs/design/limits-and-recovery.md
+++ b/docs/design/limits-and-recovery.md
@@ -121,9 +121,9 @@ launch environment affects the next REA process.
 is the byte-budget shape: a decimal safe integer with a 10 MiB floor
 (`MINIMUM_RESPONSE_BYTES`), the same shared schema, and no silent fallback. A
 change needs a REA restart and a matching client receive buffer. It does not
-raise REA's reserved string limit or Node's string ceiling. The setup
-allowlist does not copy this setting. A new headroom setting should, following
-the regex deadline.
+raise REA's reserved string limit or Node's string ceiling. Like the regex
+deadline, it is in `SELECTED_REGISTRATION_SETTINGS`, so setup forwards an
+explicit selection into the client registration.
 
 A per-call budget can have a runtime default without having an environment
 setting. JavaScript `max_heap_mb`