aontu 0.64.0 → 0.66.0

package/grammar/aontu.gbnf

@@ -1,9 +1,9 @@
 # Aontu — published grammar (GBNF), for constrained decoding.
 #
-# G7 phase 6, docs/capability-review/g7-machine-access.md. This
-# grammar covers the DOCUMENTED EMISSION SURFACE: what a model should
-# be allowed to write, which is a superset of JSON plus the operators,
-# constraints and marks the language's own canonical form emits.
+# This grammar covers the DOCUMENTED EMISSION SURFACE: what a model
+# should be allowed to write, which is a superset of JSON plus the
+# operators, constraints and marks the language's own canonical form
+# emits.
 #
 # It is CONSERVATIVE BY CONSTRUCTION: it may accept less than the
 # parser does, never more. Two deliberate exclusions:
@@ -21,19 +21,9 @@
 
 root ::= ws value ws
 
-# No pipe. `|>` was parse-time sugar (G8 phase 4); ADR-018 removed it,
-# `x |> f(a)` being written `f(x, a)`.
-#
-# That ADR says "the operator from both grammars", and both kept it
-# anyway — the engine, the suite, the error code and the docs were
-# done, these two files were not. Nothing caught it, and nothing here
-# could have: the parity discipline above runs one way, requiring every
-# canon output to PARSE, so a rule canon never emits is unreachable and
-# a test that only reads this file cannot tell a dead rule from a live
-# one. What it cost was the direction that matters to this file's
-# consumer — a decoder constrained by the old text could emit `|>` and
-# have the engine refuse it with `aontu/unexpected`. Fixed before the
-# next release, so no published grammar ever disagreed with its engine.
+# No pipe. `|>` is not in the language; `x |> f(a)` is written
+# `f(x, a)`. A decoder constrained by this file cannot emit a spelling
+# the engine refuses with `aontu/unexpected`.
 value ::= disjunct
 
 disjunct ::= conjunct ( ws "|" ws conjunct )*
@@ -108,7 +98,7 @@ ref ::= "$" ( "." segment )+ | ( "." segment )+
 # `a:6-2` as a parse error), so admitting it over-approximated.
 segment ::= ( [a-zA-Z0-9_] )+
 
-# The placeholder: a hole a call is filled through (G8 phase 3). BARE
+# The placeholder: a hole a call is filled through. BARE
 # only -- `"_"` is an ordinary string, and a longer bare word
 # containing it is ordinary text.
 place ::= "_"

package/grammar/aontu.lark

@@ -1,9 +1,8 @@
 // Aontu — published grammar (lark), for constrained decoding.
 //
-// G7 phase 6, docs/capability-review/g7-machine-access.md. The same
-// rules as grammar/aontu.gbnf, for the other consumer: keep the two in
-// step, and note that ts/test/grammar.test.ts checks that every rule
-// named there is named here.
+// The same rules as grammar/aontu.gbnf, for the other consumer: keep
+// the two in step, and note that ts/test/grammar.test.ts checks that
+// every rule named there is named here.
 //
 // The gbnf file is the one the parity test INTERPRETS against the
 // shared suite's canonical output; this file is its transcription, so
@@ -15,16 +14,9 @@
 
 root: value
 
-// No pipe. `|>` was parse-time sugar (G8 phase 4); ADR-018 removed it,
-// `x |> f(a)` being written `f(x, a)`.
-//
-// That ADR says "the operator from both grammars", and both kept it
-// anyway — the engine, the suite, the error code and the docs were
-// done, these two files were not. Nothing caught it: a rule nothing
-// derives never matches, so every canon still parsed and every test
-// stayed green while the grammars offered a spelling the parser
-// refuses with `aontu/unexpected`. Fixed before the next release, so
-// no published grammar ever disagreed with its engine.
+// No pipe. `|>` is not in the language; `x |> f(a)` is written
+// `f(x, a)`. The engine refuses the old spelling with
+// `aontu/unexpected`, and all three published grammars agree with it.
 value: disjunct
 
 disjunct: conjunct ("|" conjunct)*

package/grammar/aontu.tmLanguage.json

@@ -14,16 +14,14 @@
     "rejects AS THOUGH it were valid, which is why the builtin list below is",
     "the engine's own set and not a hand-picked sample of it.",
     "",
-    "THE BUILTIN LIST IS A COPY, AND A COPY DRIFTS. aontu.lark carried",
-    "`same` — never a builtin — and was missing `acyclic`, `inverse` and",
-    "`rel` for two releases, with every test green. So the same guard the",
+    "THE BUILTIN LIST IS A COPY, AND A COPY DRIFTS, so the same guard the",
     "other two grammars have covers this file: ts/test/grammar.test.ts,",
     "`the-textmate-grammar-names-exactly-the-engine-builtins`, asserts this",
     "list against BUILTIN_FUNCS in BOTH directions. Add a builtin to the",
     "engine without adding it here and that test fails.",
     "",
-    "No `|>`: ADR-018 removed the pipe from the language, and all three",
-    "published grammars now agree about that."
+    "No `|>`: the pipe is not in the language, and all three published",
+    "grammars agree about that."
   ],
   "name": "aontu",
   "displayName": "Aontu",
@@ -130,7 +128,7 @@
           "match": "\\b(true|false|null)\\b"
         },
         {
-          "comment": "`_` is a literal of the language as of G8 phase 3, not text.",
+          "comment": "`_` is a literal of the language, not text.",
           "name": "constant.language.placeholder.aontu",
           "match": "(?<![A-Za-z0-9_])_(?![A-Za-z0-9_])"
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aontu",
-  "version": "0.64.0",
+  "version": "0.66.0",
   "main": "dist/aontu.js",
   "type": "commonjs",
   "types": "dist/aontu.d.ts",
@@ -78,7 +78,8 @@
     "@tabnas/parser": "0.9.7",
     "@tabnas/path": "0.3.2",
     "@tabnas/toml": "0.5.7",
-    "@tabnas/yaml": "0.5.7"
+    "@tabnas/yaml": "0.5.7",
+    "jostraca": "0.38.0"
   },
   "devDependencies": {
     "@tabnas/railroad": "0.3.6",

package/skill/SKILL.md

@@ -32,9 +32,9 @@ The verbs, all of which answer as JSON with `--format json`:
 
 ```
 aontu vet schema.aon data.aon   # does this data satisfy that truth?
-aontu get $.a.b file.aon        # what does it say at a path?
-aontu why $.a.b file.aon        # why does that value hold?
-aontu set $.a.b=1 --entry file.aon --overlay over.aon
+aontu model get $.a.b file.aon        # what does it say at a path?
+aontu model why $.a.b file.aon        # why does that value hold?
+aontu model set $.a.b=1 --entry file.aon --overlay over.aon
 aontu allow --role dev roles.aon $.a.b   # may this role change that subtree?
 aontu hash file.aon             # a pin that survives reformatting
 ```

package/skill/error-codes.md

@@ -10,9 +10,9 @@ test suite holds to the engine in both implementations.
 | Class | Meaning | What to do |
 |-------|---------|------------|
 | `parse` | the text is not a document | fix the syntax at the site the frame points at |
-| `conflict` | two values cannot both hold | one of them is wrong: `aontu why <path>` names both and where they were written |
+| `conflict` | two values cannot both hold | one of them is wrong: `aontu model why <path>` names both and where they were written |
 | `incomplete` | nothing contradicts, but the value is not concrete | supply what is missing, or accept it with `--partial` |
-| `reference` | a path names nothing | check the spelling; `aontu get $ --keys` lists what is there |
+| `reference` | a path names nothing | check the spelling; `aontu model get $ --keys` lists what is there |
 | `compat` | a change breaks an earlier version | that is `aontu subsume` / `aontu breaking` talking: widen the change or version it |
 | `budget` | evaluation hit a deterministic limit | usually a cycle; simplify, or raise the budget deliberately |
 | `internal` | the engine surprised itself | a bug worth reporting |
@@ -37,14 +37,14 @@ offending values filled in, and for several codes it names the fix
 outright — `lossy_integer_literal` tells you to write the literal as
 `0d…`. It is absent for codes that have no hint text.
 
-For a conflict, `aontu why <path> mine.aon` lists every contribution
+For a conflict, `aontu model why <path> mine.aon` lists every contribution
 to that path with its role and source line, which turns "these
 disagree" into "these two lines disagree".
 
 Then fix it:
 
 ```
-aontu set '$.replicas=5' --entry schema.aon --overlay mine.aon --in-place
+aontu model set '$.replicas=5' --entry schema.aon --overlay mine.aon --in-place
 ```
 
 `--in-place` rewrites the pinned literal **where it was written**, so

package/skill/examples.md

@@ -59,7 +59,7 @@ services: {
 }
 ```
 
-The `&:` template meets EVERY key. `aontu why $.services.db.replicas`
+The `&:` template meets EVERY key. `aontu model why $.services.db.replicas`
 reports both contributions — the template's `*1|integer` and the
 literal `3` — with the line each was written on.
 
@@ -83,7 +83,7 @@ A port of `0` is now an error with a path, not a runtime surprise.
 service: { image: string, replicas: *1 | integer }
 
 # prod.aon
-@"base.aon"
+@"./base.aon"
 service: { image: "auth:v2.3", replicas: 5 }
 ```
 
@@ -91,9 +91,9 @@ Unification is order-independent: `base & prod` is `prod & base`. To
 change a value without editing the file, append to an overlay:
 
 ```
-aontu set '$.service.replicas=7' --entry prod.aon --overlay local.aon
+aontu model set '$.service.replicas=7' --entry prod.aon --overlay local.aon
 ```
 
 If the value is PINNED rather than open, that command refuses and
 names the pinning site — which is the honest answer, and where
-`aontu why` takes you next.
+`aontu model why` takes you next.

package/skill/grammar-card.md

@@ -54,6 +54,6 @@ ranges meet to their overlap.
 
 ## Files
 
-`@"other.aon"` includes another document — it unifies in, it does not
+`@"./other.aon"` includes another document — it unifies in, it does not
 concatenate. (A constrained decoder is not given this: generated
 documents describe values, they do not load files.)

package/skill/init/check.sh

@@ -16,10 +16,10 @@ cd "$(dirname "$0")"
 $AONTU vet --strict-coverage model.aon data.aon
 
 # 2. What does it say at a path?
-$AONTU get '$.entity.planet.table' data.aon
+$AONTU model get '$.entity.planet.table' data.aon
 
 # 3. Why does it say that? Every contribution, with the line it is on.
-$AONTU why '$.entity.planet.table' data.aon
+$AONTU model why '$.entity.planet.table' data.aon
 
 # 4. A pin for the truth: it survives reformatting and moves on any
 #    change of meaning.

package/skill/tasks.md

@@ -82,24 +82,29 @@ aontu trim --check model.aon     # entries whose removal changes nothing
 ## Generate code from a model, and hold it
 
 ```
-aontu get out gen.aon      # the component tree: files, and the lines in them
-aontu trace gen.aon        # what rule wrote each line
+aontu render gen.aon build          # write the files below build/
+aontu render --check gen.aon build  # write nothing; exit 1 when build/ has drifted
+aontu render gen/ build             # every generator directly in gen/, as one run
+aontu model get out gen.aon         # the component tree: files, and the lines in them
+aontu trace gen.aon                 # what rule wrote each line
 ```
 
 A generator answers a **component tree** -- `file(name, [lines])` and
-its neighbours -- which a generator runtime writes to disk. Hand the
-tree to one and compare with what is committed: the model is the truth,
-the code is the claim, and drift is a finding. `aontu trace` answers
-the other direction: for a line of the output, the model node and the
-rule behind it.
+its neighbours -- which `aontu render` hands to jostraca, the generator
+runtime, to write. A tree that is one file is written to the path
+itself, and a folder of generators is one run. `--check` compares with
+what is committed: the model is the
+truth, the code is the claim, and drift is a finding. `aontu trace`
+answers the other direction: for a line of the output, the model node
+and the rule behind it.
 
 ## Ask what a model says, and why
 
 ```
-aontu get  $.entity.planet.table model.aon
-aontu why  $.entity.planet.table model.aon
-aontu get  $.entity --keys       model.aon
-aontu get  $.entity --types      model.aon
+aontu model get  $.entity.planet.table model.aon
+aontu model why  $.entity.planet.table model.aon
+aontu model get  $.entity --keys       model.aon
+aontu model get  $.entity --types      model.aon
 ```
 
 `why` names **every** contribution to a value, with the file and line
@@ -109,7 +114,7 @@ what you expected, and the second thing to run when `vet` refuses.
 ## Change a value without editing the file
 
 ```
-aontu set '$.entity.planet.table=planet_v2' --entry model.aon --overlay local.aon
+aontu model set '$.entity.planet.table=planet_v2' --entry model.aon --overlay local.aon
 ```
 
 The change is checked before it is written; a change that contradicts

package/src/agentsmd.ts

@@ -80,16 +80,16 @@ export function agentsMd(
     '',
     '```',
     '# what does it say at a path?',
-    'aontu get ' + example + ' ' + name,
+    'aontu model get ' + example + ' ' + name,
     '',
     '# why does that value hold?',
-    'aontu why ' + example + ' ' + name,
+    'aontu model why ' + example + ' ' + name,
     '',
     '# does my document satisfy it?',
     'aontu vet ' + name + ' mine.aon',
     '',
     '# change it without editing it',
-    'aontu set ' + example + '=<value> --entry ' + name +
+    'aontu model set ' + example + '=<value> --entry ' + name +
     ' --overlay overlay.aon',
     '',
     '# the language itself, offline: the whole grammar on one page',

package/src/aontu.ts

@@ -35,7 +35,7 @@ import { format, unifiedDiff } from './format'
 export type { LintFinding, FormatReport, FormatOptions } from './format'
 
 
-const VERSION = '0.64.0'
+const VERSION = '0.66.0'
 
 
 function genQuiet(val: any, aontu: Aontu): any {