AILang

Brummel/AILang

Fork 0

Commit Graph

Author	SHA1	Message	Date
Brummel	29625e7262	feat(cma): revive cross-model harness corpus to current language (refs #68 ) The cma authoring-form harness corpus had gone dead against the language as it evolved since May. The plan modelled it as merely schema-dead (missing param_modes/ret_mode); it was also drift-dead in the example BODIES. Fixed in place, with `ail check` + both test suites as the oracle: - Schema: param_modes/ret_mode completed on every fn type; existing borrow annotations preserved (data_with_match's borrow over List). - Symbol drift: `<`/`==` -> `lt`/`eq` (operator-routing); the removed `io/print_int` op -> print_str(int_to_str n) followed by a newline print, preserving the trailing newline the references' expected_stdout needs. - Ownership/ADT restructures: data_simple's reuse-as now wraps the source in a match arm (ctor must be statically visible); data_with_match's count_via_letrec + local go switched borrow->own (consume-while-borrowed under the tightened ownership analysis; head_or_zero still exercises borrow over the boxed List). - param_modes_all rewritten to own (Int) + borrow over a boxed ADT -- (borrow Int) is now a borrow-over-value error. - Two new author-facing examples (loop_sum: Loop/Recur; new_rawbuf: New) cover the Term variants that landed since May. - spec_completeness.rs: drop the deleted ParamMode::Implicit; cover Loop/Recur/New; allowlist the non-authorable Term::Intrinsic out. - spec.md section 4 rewritten to own/borrow (mandatory, no implicit) with the borrow-over-value rule; rendered/ regenerated. - mock_full_run fixture's t3 turn-2 program migrated so the harness score assertions hold; usage fields untouched. Both render/ and harness/ cargo test suites green in mock mode; no live IONOS call. Run the harness budget/reference tests with AIL_BIN pointing at target/debug/ail (ail is not on PATH in the test env).	2026-06-02 17:08:30 +02:00
Brummel	4fc65ccb99	iter schema-camelcase-fix.1 (DONE 4/4): paramTypes/retType → param-types/ret-type — closes #30 `Term::Lam`'s two camelCase JSON tags become kebab-case, matching the convention every other compound-key tag in the AST schema already follows. After this iter the canonical JSON has zero camelCase outliers. ## Schema swap (atomic, Task 2) - `crates/ailang-core/src/ast.rs:492,494` — two `#[serde(rename)]` strings: `"paramTypes" → "param-types"`, `"retType" → "ret-type"`. Rust field names unchanged. - `crates/ailang-core/src/workspace.rs:1925-1926` — in-source JSON literal in the `ct1_validator_walks_lam_embedded_types` test. - `design/contracts/data-model.md:142-147` — fenced JSON block in the canonical data-model contract. Honesty-Rule touch-point: the contract document must describe the actual present-state schema. - `examples/test_loop_binder_captured_by_lambda.ail.json` and `experiments/2026-05-12-cross-model-authoring/master/examples/fn_with_lambda.ail.json` — the two `.ail.json` fixtures whose canonical-JSON embeds the renamed tags. The five files moved together within one task because `Term::Lam` has no `#[serde(default)]` on `param_tys` / `ret_ty` — a renamed-away key is a hard deserialise error. Splitting the swap would have left the workspace untestable mid-step. ## RED → GREEN pin (Tasks 1, 2) `crates/ailang-core/tests/design_schema_drift.rs` gains `lam_serialises_with_kebab_keys`: pins that `serde_json::to_value(&Term::Lam{...})` emits `"param-types"` / `"ret-type"` AND does not emit the old camelCase keys. Companion: the existing `design_md_anchors_every_term_variant` test now also asserts the kebab anchors appear inside `data-model.md`'s `lam` fenced block. Both confirmed RED on entry, GREEN after Task 2. ## Rustdoc honesty pass (Task 3) Three pure-prose edits keep production rustdoc consistent with the new schema vocabulary: `crates/ailang-core/src/ast.rs:8` (the module-level rename enumeration), `crates/ailang-surface/src/parse.rs:81` (prose mention of `lam`'s carry), `crates/ailang-check/src/lib.rs:1707` (InstanceMethod routing helper rustdoc). No compile or test consequence — Honesty-Rule maintenance. ## Plan-pseudo-vs-reality finding: under-audited hash blast radius The brainstorm spec audited `crates/ailang-core/tests/hash_pin.rs` exhaustively (5 pinned modules, zero `(lam ...)` occurrences, "no hash refresh required"). It missed `crates/ailang-surface/tests/prelude_module_hash_pin.rs` — a separate hash-pin file in a different crate that pins `prelude.ail`, which contains 11 `(lam ...)` forms. The prelude module hash drifted (`6d0577ff0d4e50ac` → `562a03fc57e7e017`); the implementer refreshed it with a Honesty-Rule provenance comment matching the precedent set in commit `26fb345`. Form-A is unchanged — only the canonical-JSON byte stream differs, which is exactly what the rename targets. The spec-side learning is: schema-rename brainstorms must walk every test crate for hash-pin files, not just the home crate of the AST. ## Why this shape, and not the alternatives - `params-ty` / `ret-ty` (Rust-field-name vibe) — rejected. The AST JSON schema follows its own kebab/single-word convention, not Rust field names. The other multi-word tag (`reuse-as`) is kebab; abbreviating `params-ty` mixes singular+plural and has no precedent. - Inline typed params as a sub-tag (e.g. `params: [{name, type}, ...]`) — rejected. Stronger semantic locality, but it changes schema topology rather than tag spelling. Out of scope for a camelCase correction; would have re-pinned far more than this milestone. - Bundle with #27 (arith-rename) — rejected. #27 carries four open brainstorm questions (mod vs rem, neg vs sub 0, Num class, deprecation window) and is structurally a separate milestone. Each gets one re-pin wave with its own rationale; no churn saving from bundling. ## Honest call on the feature-acceptance gate Clause 1 (LLM author naturally uses the new form) is the weakest of the three. Direct empirical evidence is absent — the 2026-05-21 naming-A/B run measured a different axis. The argument is indirect: a future LLM author generalises from the rest of the schema ("compound keys are kebab"), and the two camelCase outliers are precisely the sites where that generalisation diverged from reality. Clause 2 (redundancy reduction) and Clause 3 (no semantic surface touched) are direct. ## Forbidden touches verified untouched `docs/plans/.md` historic plans (which embed old tag names in example JSON), `experiments/2026-05-12-cross-model-authoring/master/spec.md`, `experiments/.../rendered/.md`, and `experiments/.../runs/**` — all left as frozen historical artefacts per Honesty-Rule analogue (describe state at time of writing, not present state). Verified via `git diff --name-only HEAD` (Task 4 Step 4). ## Verification - `cargo test --workspace`: all test groups OK, 0 failed, 2 ignored (pre-existing). - `cargo test -p ailang-surface --test round_trip`: GREEN (Form-A unchanged invariant). - New schema-shape pin and the extended data-model anchor walk: GREEN after Task 2. - Negative grep across `crates/`, `examples/`, `design/`, `runtime/`: the only remaining `paramTypes` / `retType` occurrences in checked-in code are the load-bearing negative-assertion strings inside the new pin (intentional — they are what makes the pin RED-able on regression). - Stats: `bench/orchestrator-stats/2026-05-21-iter-schema-camelcase-fix.json` — 4/4 tasks DONE, no re-loops, no review-loops. closes #30	2026-05-21 12:57:06 +02:00
Brummel	a8c29d130b	iter cma.1: master mini-spec + render binary for cross-model authoring experiment New top-level experiments/2026-05-12-cross-model-authoring/ (out of root Cargo workspace; nested-crate standalone via empty [workspace] table per Cargo idiom). The renderer projects one canonical master/spec.md into two form-specific files (rendered/json.md and rendered/ailx.md) by walking three directive forms ({form-only: json}, {form-only: ailx}, {example: <id>}) and emitting per-example fenced blocks sourced from 13 curated .ail.json fixtures. Four test gates green (10/10 total): - splitter_unit (7) — directive parser, malformed inputs panic - spec_completeness (1) — AST-variant visitor lifted verbatim from schema_coverage.rs; 34/34 variants covered by the curated subset - example_roundtrip (1) — every fixture roundtrips through ailang_surface::{print, parse} to identical canonical bytes - token_balance (1) — form-only block totals balanced to 3.22% under tiktoken-rs::cl100k_base (gate is ±5%) Six of the 34 variants did not have a dedicated fixture topic in the plan and were absorbed into the closest existing fixture per the plan's Step 4.14 escape hatch (Let/Clone → fn_calls_prelude; LetRec → data_with_match; If → match_literal_pattern; ReuseAs → data_simple; Const → floats). Surfaced as a journal note, not a plan revision. Two ancillary additions vs. plan, both structural Cargo necessities, spec-compatible: render/Cargo.toml carries an empty [workspace] table so the nested crate refuses parent-workspace discovery, and render/.gitignore drops /target + Cargo.lock. Both surfaced inline in the per-iter journal's Concerns section. cma.2 (harness) and cma.3 (live IONOS run + DESIGN.md addendum + journal + roadmap edits) remain out of scope per the spec.	2026-05-12 11:43:10 +02:00

Author

SHA1

Message

Date

Brummel

29625e7262

feat(cma): revive cross-model harness corpus to current language (refs #68 )

The cma authoring-form harness corpus had gone dead against the language
as it evolved since May. The plan modelled it as merely schema-dead
(missing param_modes/ret_mode); it was also drift-dead in the example
BODIES. Fixed in place, with `ail check` + both test suites as the oracle:

- Schema: param_modes/ret_mode completed on every fn type; existing
  borrow annotations preserved (data_with_match's borrow over List).
- Symbol drift: `<`/`==` -> `lt`/`eq` (operator-routing); the removed
  `io/print_int` op -> print_str(int_to_str n) followed by a newline
  print, preserving the trailing newline the references' expected_stdout
  needs.
- Ownership/ADT restructures: data_simple's reuse-as now wraps the
  source in a match arm (ctor must be statically visible);
  data_with_match's count_via_letrec + local go switched borrow->own
  (consume-while-borrowed under the tightened ownership analysis;
  head_or_zero still exercises borrow over the boxed List).
- param_modes_all rewritten to own (Int) + borrow over a boxed ADT --
  (borrow Int) is now a borrow-over-value error.
- Two new author-facing examples (loop_sum: Loop/Recur; new_rawbuf: New)
  cover the Term variants that landed since May.
- spec_completeness.rs: drop the deleted ParamMode::Implicit; cover
  Loop/Recur/New; allowlist the non-authorable Term::Intrinsic out.
- spec.md section 4 rewritten to own/borrow (mandatory, no implicit)
  with the borrow-over-value rule; rendered/ regenerated.
- mock_full_run fixture's t3 turn-2 program migrated so the harness
  score assertions hold; usage fields untouched.

Both render/ and harness/ cargo test suites green in mock mode; no live
IONOS call. Run the harness budget/reference tests with AIL_BIN pointing
at target/debug/ail (ail is not on PATH in the test env).

2026-06-02 17:08:30 +02:00

Brummel

4fc65ccb99

iter schema-camelcase-fix.1 (DONE 4/4): paramTypes/retType → param-types/ret-type — closes #30

`Term::Lam`'s two camelCase JSON tags become kebab-case, matching
the convention every other compound-key tag in the AST schema
already follows. After this iter the canonical JSON has zero
camelCase outliers.

## Schema swap (atomic, Task 2)

- `crates/ailang-core/src/ast.rs:492,494` — two
  `#[serde(rename)]` strings: `"paramTypes" → "param-types"`,
  `"retType" → "ret-type"`. Rust field names unchanged.
- `crates/ailang-core/src/workspace.rs:1925-1926` — in-source
  JSON literal in the `ct1_validator_walks_lam_embedded_types`
  test.
- `design/contracts/data-model.md:142-147` — fenced JSON block
  in the canonical data-model contract. Honesty-Rule touch-point:
  the contract document must describe the actual present-state
  schema.
- `examples/test_loop_binder_captured_by_lambda.ail.json` and
  `experiments/2026-05-12-cross-model-authoring/master/examples/fn_with_lambda.ail.json`
  — the two `.ail.json` fixtures whose canonical-JSON embeds
  the renamed tags.

The five files moved together within one task because `Term::Lam`
has no `#[serde(default)]` on `param_tys` / `ret_ty` — a
renamed-away key is a hard deserialise error. Splitting the swap
would have left the workspace untestable mid-step.

## RED → GREEN pin (Tasks 1, 2)

`crates/ailang-core/tests/design_schema_drift.rs` gains
`lam_serialises_with_kebab_keys`: pins that `serde_json::to_value(&Term::Lam{...})`
emits `"param-types"` / `"ret-type"` AND does not emit the old
camelCase keys. Companion: the existing
`design_md_anchors_every_term_variant` test now also asserts the
kebab anchors appear inside `data-model.md`'s `lam` fenced block.
Both confirmed RED on entry, GREEN after Task 2.

## Rustdoc honesty pass (Task 3)

Three pure-prose edits keep production rustdoc consistent with
the new schema vocabulary: `crates/ailang-core/src/ast.rs:8` (the
module-level rename enumeration), `crates/ailang-surface/src/parse.rs:81`
(prose mention of `lam`'s carry), `crates/ailang-check/src/lib.rs:1707`
(InstanceMethod routing helper rustdoc). No compile or test
consequence — Honesty-Rule maintenance.

## Plan-pseudo-vs-reality finding: under-audited hash blast radius

The brainstorm spec audited `crates/ailang-core/tests/hash_pin.rs`
exhaustively (5 pinned modules, zero `(lam ...)` occurrences,
"no hash refresh required"). It missed
`crates/ailang-surface/tests/prelude_module_hash_pin.rs` — a
separate hash-pin file in a different crate that pins `prelude.ail`,
which contains 11 `(lam ...)` forms. The prelude module hash
drifted (`6d0577ff0d4e50ac` → `562a03fc57e7e017`); the implementer
refreshed it with a Honesty-Rule provenance comment matching the
precedent set in commit `26fb345`. Form-A is unchanged — only the
canonical-JSON byte stream differs, which is exactly what the
rename targets. The spec-side learning is: schema-rename
brainstorms must walk *every* test crate for hash-pin files, not
just the home crate of the AST.

## Why this shape, and not the alternatives

- *`params-ty` / `ret-ty` (Rust-field-name vibe)* — rejected. The
  AST JSON schema follows its own kebab/single-word convention,
  not Rust field names. The other multi-word tag (`reuse-as`) is
  kebab; abbreviating `params-ty` mixes singular+plural and has
  no precedent.
- *Inline typed params as a sub-tag* (e.g. `params: [{name, type}, ...]`)
  — rejected. Stronger semantic locality, but it changes schema
  topology rather than tag spelling. Out of scope for a camelCase
  correction; would have re-pinned far more than this milestone.
- *Bundle with #27 (arith-rename)* — rejected. #27 carries four
  open brainstorm questions (mod vs rem, neg vs sub 0, Num class,
  deprecation window) and is structurally a separate milestone.
  Each gets one re-pin wave with its own rationale; no churn
  saving from bundling.

## Honest call on the feature-acceptance gate

Clause 1 (LLM author naturally uses the new form) is the weakest
of the three. Direct empirical evidence is absent — the 2026-05-21
naming-A/B run measured a different axis. The argument is
indirect: a future LLM author generalises from the rest of the
schema ("compound keys are kebab"), and the two camelCase
outliers are precisely the sites where that generalisation
diverged from reality. Clause 2 (redundancy reduction) and
Clause 3 (no semantic surface touched) are direct.

## Forbidden touches verified untouched

`docs/plans/*.md` historic plans (which embed old tag names in
example JSON), `experiments/2026-05-12-cross-model-authoring/master/spec.md`,
`experiments/.../rendered/*.md`, and `experiments/.../runs/**` —
all left as frozen historical artefacts per Honesty-Rule
analogue (describe state at time of writing, not present state).
Verified via `git diff --name-only HEAD` (Task 4 Step 4).

## Verification

- `cargo test --workspace`: all test groups OK, 0 failed,
  2 ignored (pre-existing).
- `cargo test -p ailang-surface --test round_trip`: GREEN
  (Form-A unchanged invariant).
- New schema-shape pin and the extended data-model anchor walk:
  GREEN after Task 2.
- Negative grep across `crates/`, `examples/`, `design/`,
  `runtime/`: the only remaining `paramTypes` / `retType`
  occurrences in checked-in code are the load-bearing
  negative-assertion strings inside the new pin (intentional —
  they are what makes the pin RED-able on regression).
- Stats: `bench/orchestrator-stats/2026-05-21-iter-schema-camelcase-fix.json`
  — 4/4 tasks DONE, no re-loops, no review-loops.

closes #30

2026-05-21 12:57:06 +02:00

Brummel

a8c29d130b

iter cma.1: master mini-spec + render binary for cross-model authoring experiment

New top-level experiments/2026-05-12-cross-model-authoring/ (out of
root Cargo workspace; nested-crate standalone via empty [workspace]
table per Cargo idiom). The renderer projects one canonical
master/spec.md into two form-specific files (rendered/json.md and
rendered/ailx.md) by walking three directive forms ({form-only:
json}, {form-only: ailx}, {example: <id>}) and emitting per-example
fenced blocks sourced from 13 curated .ail.json fixtures.

Four test gates green (10/10 total):
- splitter_unit (7) — directive parser, malformed inputs panic
- spec_completeness (1) — AST-variant visitor lifted verbatim from
  schema_coverage.rs; 34/34 variants covered by the curated subset
- example_roundtrip (1) — every fixture roundtrips through
  ailang_surface::{print, parse} to identical canonical bytes
- token_balance (1) — form-only block totals balanced to 3.22% under
  tiktoken-rs::cl100k_base (gate is ±5%)

Six of the 34 variants did not have a dedicated fixture topic in the
plan and were absorbed into the closest existing fixture per the
plan's Step 4.14 escape hatch (Let/Clone → fn_calls_prelude; LetRec
→ data_with_match; If → match_literal_pattern; ReuseAs →
data_simple; Const → floats). Surfaced as a journal note, not a
plan revision.

Two ancillary additions vs. plan, both structural Cargo necessities,
spec-compatible: render/Cargo.toml carries an empty [workspace] table
so the nested crate refuses parent-workspace discovery, and
render/.gitignore drops /target + Cargo.lock. Both surfaced inline
in the per-iter journal's Concerns section.

cma.2 (harness) and cma.3 (live IONOS run + DESIGN.md addendum +
journal + roadmap edits) remain out of scope per the spec.

2026-05-12 11:43:10 +02:00

3 Commits