From ff491e86dd20359f6a21d90f8d46b2500d6e3129 Mon Sep 17 00:00:00 2001 From: ue-toolchain Date: Tue, 1 Sep 2026 21:08:38 +0700 Subject: [PATCH] docs(adr-0001): remove premature reference to ADR-0002 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Убрана отсылка к 'ADR-0002-candidate' про удалённый транспорт, которая была вставлена для красоты аргумента, но не подкреплена реальным запросом. Заменено на честную формулировку: loopback-only — это ограничение v0.1, удалённый сценарий будет рассмотрен отдельным ADR при появлении конкретной потребности, а не упреждающе. Соответствует принципу YAGNI: ADR фиксируют принимаемые решения, а не гипотетические. --- .../architecture/decisions/0001-discovery-over-pid-file.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/architecture/decisions/0001-discovery-over-pid-file.md b/docs/architecture/decisions/0001-discovery-over-pid-file.md index 312c265..1279b7b 100644 --- a/docs/architecture/decisions/0001-discovery-over-pid-file.md +++ b/docs/architecture/decisions/0001-discovery-over-pid-file.md @@ -150,9 +150,10 @@ Good: Bad: -- **Loopback-only broadcast** is a deployment constraint. Running the editor on one - machine and the MCP client on another requires a different transport (out of scope - for v0.1, listed as ADR-0002-candidate). +- **Loopback-only broadcast** is a deployment constraint: editor and MCP client must + be on the same machine. Remote scenarios (editor on one host, agent on another) are + not addressed by this decision. If such a need arises, it will be handled by a + future ADR when there is a concrete request — not pre-empted now. - **Discovery adds latency** to first tool call (≤500ms once at startup, then cached). Negligible compared to the 60s timeouts it replaces. - **Two-editor scenario needs disambiguation** rules, which the user must configure