From 538e0ce665ae2240d79d67f24a159021e92db178 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Fri, 18 Sep 2026 19:38:58 +0200 Subject: [PATCH] =?UTF-8?q?AGENTS.md=20=C2=A78=20admits=20a=20plainly=20na?= =?UTF-8?q?med=20new=20code=20in=200.x,=20=C2=A711=20names=20from=20the=20?= =?UTF-8?q?spec?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- AGENTS.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 4a010a5..bcae506 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -117,8 +117,9 @@ A message names the violation, not the rule alone — a rule by itself states a must invert before it reads as a failure — and where the flavour's claim refuses ordinary prose it names the escape that unclaims the form claimed: `\!adf:` for a directive, block line and inline alike, `\|` for every pipe row. -Adding, removing or renaming a code is breaking, so a milestone meeting a new failure cause -reuses a code where one fits; the list is complete at `0.1.0`. A code names the +Adding, removing or renaming a code is breaking, so a new cause takes an existing code whose +name reads true of it in both directions; where none does and a plain name exists, a new code — in +any 0.x minor, and after 1.0 only in a MAJOR (the maintainer, 2026-09-18). A code names the cause; where one cause recurs across node types, across one mark's attributes or across directions, one code covers them all and `path` and `message` say which — `unsupported-nesting-depth` is the 500-level guard whichever @@ -324,7 +325,9 @@ someone spells it or pins it. number is the markdown flavour's choice, not ADF's. - Explicit over implicit; descriptive names; no catch-all files (`utils`, `helpers`, `misc`); a file does not repeat its directory in its name — `adf/document.ts`, never - `adf/adf-document.ts`. + `adf/adf-document.ts`. A name is the noun `spec/flavour.md` or ADF's schema uses for the + thing; a directory follows a split the spec draws; a placement these rules leave open goes + beside its only reader, or in what both read where there are two (the maintainer, 2026-09-18). - Reuse before adding; the smallest sufficient diff is the benchmark; no speculative generality — a second consumer, or it goes.