From c31f0aa94a0d076f253d68bf10932dafc8cab240 Mon Sep 17 00:00:00 2001 From: Aidan Pace Date: Mon, 25 May 2026 21:56:47 -0400 Subject: [PATCH] =?UTF-8?q?docs(contract):=20fix=20duplicate=20section=20?= =?UTF-8?q?=C2=A79=20(Invariants=20vs=20Adding=20a=20New=20Transport)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit TRANSPORT-CONTRACT.org had two top-level headings both numbered "9": "9. Invariants" and "9. Adding a New Transport". Cross-references to "§9" were ambiguous (surfaced during conformance review of the HTTP transport proposal, PR #5). Renumber the second to §10. No internal §-references needed updating (none existed); content unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/adr/TRANSPORT-CONTRACT.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/adr/TRANSPORT-CONTRACT.org b/docs/adr/TRANSPORT-CONTRACT.org index b76fe86..069ddf2 100644 --- a/docs/adr/TRANSPORT-CONTRACT.org +++ b/docs/adr/TRANSPORT-CONTRACT.org @@ -503,7 +503,7 @@ These hold for any future transport implementation: 10. *Config is re-read on every invocation.* There is no daemon-side config cache. Changing config.json takes effect on the next command. -* 9. Adding a New Transport +* 10. Adding a New Transport To add transport =foo=: