docs(adr-0001): remove premature reference to ADR-0002
Убрана отсылка к 'ADR-0002-candidate' про удалённый транспорт, которая была вставлена для красоты аргумента, но не подкреплена реальным запросом. Заменено на честную формулировку: loopback-only — это ограничение v0.1, удалённый сценарий будет рассмотрен отдельным ADR при появлении конкретной потребности, а не упреждающе. Соответствует принципу YAGNI: ADR фиксируют принимаемые решения, а не гипотетические.
This commit is contained in:
@@ -150,9 +150,10 @@ Good:
|
|||||||
|
|
||||||
Bad:
|
Bad:
|
||||||
|
|
||||||
- **Loopback-only broadcast** is a deployment constraint. Running the editor on one
|
- **Loopback-only broadcast** is a deployment constraint: editor and MCP client must
|
||||||
machine and the MCP client on another requires a different transport (out of scope
|
be on the same machine. Remote scenarios (editor on one host, agent on another) are
|
||||||
for v0.1, listed as ADR-0002-candidate).
|
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).
|
- **Discovery adds latency** to first tool call (≤500ms once at startup, then cached).
|
||||||
Negligible compared to the 60s timeouts it replaces.
|
Negligible compared to the 60s timeouts it replaces.
|
||||||
- **Two-editor scenario needs disambiguation** rules, which the user must configure
|
- **Two-editor scenario needs disambiguation** rules, which the user must configure
|
||||||
|
|||||||
Reference in New Issue
Block a user