112 Commits

Author	SHA1	Message	Date
Brummel	a378dad0aa	docs(design): ratify the check→codegen boundary (mir.5, typed-MIR close) ... mir.5 is the typed-MIR milestone's closing iteration. Its CODE half had already converged before the iteration began, so mir.5 ships no code — it ratifies into the design/ ledger the boundary the code already holds. Verified at iteration entry (empirically, not from the spec sketch): - all four named re-derivers grep-clean in codegen: synth_with_extras, synth_arg_type, type_home_module, the second infer_module_with_cross; - lower_workspace takes &MirWorkspace (codegen consumes MIR); - MTerm::New is unreachable!() — raw-buf.4 desugars Term::New to (app T.new …) before codegen, so there is no element-type re-derivation left to relocate; - #51 / #53 (the element-type / new-T codegen crashes) are closed; their residue was fixed by ee4107c / 420f75f plus the New-desugar, not by a separate raw-buf patch track. Ledger work (the mir.5 deliverable): - NEW design/contracts/0018-check-codegen-boundary.md: the invariant "codegen re-derives nothing; MIR is total over what check proved; a codegen arm that recomputes a fact instead of reading MIR is drift." Ratifier: lower_to_mir_ty.rs::callee_classification_builtin_and_static. - 0013-typeclasses invariant 2 retracted: codegen no longer re-resolves cross-module names via an import_map fallback; lower_to_mir::classify_callee resolves the reference once into Callee::Static and codegen consumes it. - 0003-pipeline.md: the "lower to MIR" line names the real stage (elaborate_workspace → MirWorkspace → lower_workspace) and a new paragraph states the boundary, cross-referencing 0018. - INDEX.md: boundary contract row added; qualified-xref re-pointed at lower_to_mir + 0018. - codegen_import_map_fallback_pin.rs doc-comment made honest — it pins the post-mono AST precondition classify_callee relies on, not a codegen-side resolution that no longer exists. Assertions unchanged; the test stays green. - spec 0060 gains a mir.5 refinement note recording the early code convergence. Acceptance criteria 1-7 of docs/specs/0060-typed-mir.md are all met. Full workspace suite green (exit 0, 0 failed, 2 ignored); 708 passed carried from mir.4 (no test added or removed). Not done here (deliberately): the milestone #7 (raw-buf) subsumption note is an external Gitea tracker write; the /boss auto-mode classifier declined it as an unauthorised external write and it is surfaced to the user rather than worked around. The end-to-end milestone fieldtest remains the deliberate manual close-gate before the tracker milestone is marked done. refs #51 #53	2026-06-01 01:34:37 +02:00
Brummel	c5fd16a4eb	feat(codegen): StrRep loop-carried Str ⇒ Heap, close the #49 recur leak ... mir.4 closes bug #49 (a heap-Str loop binder replaced across `recur` leaks every superseded slab; the loop result leaks too) structurally, by making every Str a loop binder holds OR a loop returns an owned heap slab — then deleting the `!is_str` carve-out from BOTH codegen gates that carried it. The leg-by-leg `!is_str` patches are gone. Mechanism (the milestone thesis: representation in MIR, codegen reads it). lower_to_mir sets rep = StrRep::Heap on every Str literal in a loop-carried position; codegen's MTerm::Str arm promotes a Heap literal via ailang_str_clone (a fresh ailang_rc_alloc slab, rc_header refcount 1). Three promotion positions, all in the Loop/Recur lowering: 1. binder seed inits (is_str_ty on the binder type); 2. recur args at Str-binder positions (read off the innermost loop_stack frame); 3. exit-arm tail result literals (promote_tail_str_literals walks the loop body's tail positions when the loop returns Str). With every loop-carried Str now owned-heap, both gates lose !is_str: the recur superseded-value dec (lib.rs) frees each intermediate slab; the loop-result trackability gate (drop.rs:493) lets the caller's scope-close free the final slab. Why both gates, and the planning-time error this corrects. The original plan/spec scoped the deletion to the recur dec gate only, reasoning the #49 loop result is "consumed by print". The implement-orchestrator landed that scope (Tasks 1-2) clean and correctly BLOCKED: it took #49 from live=3 to live=1, the residual being the loop RESULT. I verified the diagnosis empirically: - print BORROWS its arg (prelude: `(let s (show x) (do io/print_str s))`, the eob.1 heap-Str discipline), so `(print s)` does not free the loop result; the caller's let-binder does, via drop.rs:493. "consumed by print" != "freed by print" — that was the error. - Deleting drop.rs:493's !is_str takes #49 and the recur-literal fixture to live=0. - Deleting drop.rs:493 WITHOUT exit-arm promotion SIGSEGVs (exit 139) on a loop returning a static Str literal — hence the third promotion position and the static-exit witness. The agent surfaced a real spec defect via an empirical BLOCK rather than guessing; I corrected the spec refinement note (both gates, three positions) and completed the loop-result leg inline, the context already loaded from verifying the BLOCK (CLAUDE.md "already loaded context" carve-out). drop.rs:493's Str carve-out is now sound to delete. Boundary (asserted ill-typed, not constructible): a borrowed static-Str Var seeded/recur'd into a consumed Str loop binder — rejected upstream by uniqueness (a consumed binder position is owned). Verification (orchestrator-run): all four leak fixtures reach live=0 under AILANG_RC_STATS — #49 (xyyy), recur-literal (reset), static-exit (result), and the f488d31 boxed-ADT guard (2, no regression). The #49 #[ignore] is lifted. Full workspace: 708 passed / 0 failed / 2 ignored (mir.3b baseline 702/0/3; +6 passed, -1 ignored = #49 lifted; the 2 remaining ignores are doctests). ir_snapshot: no drift (the Heap promotion does not reach non-loop-carried literals — the non_loop_str_literal_stays_static pin confirms at the unit level). Neither CLAUDE.md lockstep pair touches Str representation. New witness fixtures: examples/loop_str_recur_literal_no_leak_pin.ail (recur-arg leg) and examples/loop_str_static_exit_no_leak_pin.ail (loop-result leg / static-exit soundness). New pins: lower_to_mir_ty exit-arm producer pin + the flipped seed/recur-arg pins; two runtime leak pins alongside the lifted #49. closes #49	2026-06-01 00:54:44 +02:00
Brummel	eba1be8d9d	feat(codegen): fill MArg.mode for App args, read the anon-temp drop gate off it, delete module_def_ail_types (mir.3b) ... Second of two iterations delivering spec 0060's mir.3 row (plan docs/plans/0118-mir.3b-marg-mode-and-table-delete.md). lower_to_mir's Term::App arm fills each MArg.mode from the resolved callee's param_modes (the sig = synth_pure(callee) it already holds); codegen's emit_call anon-temp borrow-slot drop gate reads arg.mode instead of re-looking-up the callee's param_modes from the module_def_ail_types table; and — since that gate was the table's only reader — the module_def_ail_types field plus all its construction and threading are deleted. Two refinements to the spec's mir.3b sketch, settled in planning from a focused recon and recorded in spec 0060: 1. module_def_ail_types is deleted in mir.3b, not mir.5. A grep proved self.module_def_ail_types had exactly ONE reader (the anon-temp gate); the own-param drop reads param_modes from the def's own f.ty, not this table. Once the gate moves onto MArg.mode the table is dead, so it is removed now rather than carried as dead code to mir.5. The mir.5 row's "last re-derivation residue" shrinks to the element-type / Term::New (New.elem) work. 2. MArg.mode is filled for App args only; MTerm::Let.mode is not filled. Only App args have a real per-arg mode source (the callee Type::Fn.param_modes). Do args (EffectOpSig has no param modes), Ctor args (no per-field mode), and Recur args (loop binders carry no mode) stay Mode::Owned. Let.mode has no source (ast::Term::Let has no mode field) and no consumer (the let-drop gate reads consume, not Let.mode), so it stays Owned — filling it would invent a value nobody reads. Safety property held: MArg.mode is filled from the same callee fn-type the gate read from the table, so the drop fires identically. For (app RawBuf.get (app RawBuf.set …) 0), RawBuf.get's param 0 is borrow, so args[0].mode = Borrow — exactly the value module_def_ail_types yielded. Confirmed by the anon-temp witness staying green. ParamMode -> Mode conversion: Borrow -> Mode::Borrow; Own and Implicit (the Implicit ≡ Own contract) -> Mode::Owned. The own-param drop keeps reading ParamMode off f.ty (Type/ParamMode imports retained, live readers at lib.rs:1356/1507). Also retires three now-stale doc comments that named the deleted module_def_ail_types field (ailang-check/src/lib.rs, uniqueness.rs, and the codegen_import_map_fallback_pin test doc) — a direct consequence of the deletion, reworded to the current architecture. Verification (orchestrator, post-implement inspect): diff matches the plan (App-arg m_args built before m_callee consumes sig — the benign borrow-order deviation the plan's note flagged); module_def_ail_types grep-clean across all of crates/; cargo build --workspace clean (no unused/dead_code); cargo test --workspace 702 passed / 0 failed / 3 ignored (+1 = the new producer pin app_arg_carries_callee_borrow_mode; no #[ignore] added). The anon-temp drop-correctness witness raw_buf_owned_drop_balances_rc_stats stays live=0, now driven by MArg.mode; the other RC-stats leak pins green; #49 stays #[ignore] (mir.4); #51/#53 build guards green. mir.3 is now complete (3a relocated consume_count + deleted the second uniqueness run; 3b filled the mode annotation + deleted module_def_ail_types). Remaining: mir.4 (#49 StrRep RED->GREEN), mir.5 (element-type/Term::New + ledger).	2026-05-31 20:10:25 +02:00
Brummel	c5eca7e91d	bench: re-ratify compile_check baseline (closes #45) ... Re-baseline bench/baseline_compile.json, last ratified 2026-05-15 (20add51, mut.4-tidy). check_ms shifted +35..47% uniformly across all 12 fixtures (~1.8-3.3ms -> ~2.4-4.7ms); build_O0_ms rose ~10% (90->100ms) but stayed inside its 20% tolerance and so never tripped. RATIFY, not a regression. The decisive signal is that the check_ms drift is *uniform* across every fixture regardless of complexity (hello +35%, nested_pat +35%). Fixture-independent drift means the cost lives in shared per-invocation work, not in any fixture-specific checker path. Two concrete shared-cost growths fully account for it: - examples/prelude.ail grew 116 -> 153 lines (+32%); every `ail check` parses and typechecks the full prelude. - the kernel_stub module is now injected alongside prelude on every check (landed in raw-buf prep.3, 9339279, #33) — a whole extra module parsed + typechecked per invocation. Both are real modules added by wanted features, not a quadratic blow-up. There is no fixable type-checker regression hiding here; the +0.8ms is the parse+typecheck cost of more shared source. The throughput baseline (bench/baseline.json) was already re-ratified 2026-05-28 (de4399d); this brings the compile baseline back in sync. Corrects the record: the #44 cycle-close audit body (7321826) wrongly attributed the compile_check exit-1 to transient machine load. main is sacrosanct so 7321826 cannot be amended; #45 and this commit are the forward correction. Verified: compile_check.py -n5 -> 24 metrics, 0 regressed, 24 stable.	2026-05-30 15:31:04 +02:00
Brummel	de4399df37	audit + close: kernel-extension-mechanics — latency-arm restoration + p99 jitter-metric removal (ratify) ... Audit Step 2 (regression scripts) blocked at exit 2 on bench/check.py — the latency arms produced lines=0 because their fixtures rely on `(app print N)` to deliver one newline per sample, but the io/print_str byte-faithful change (commit 26fb345, closes #29) stopped trailing newlines from appearing in the polymorphic print path. Pre-existing infrastructure failure, NOT iter-caused; fix is one \n insertion per print site in both bench_latency_*.ail fixtures, behaviour-preserving for any other consumer. With infra unblocked, bench/check.py reported exit 1 on latency.explicit_at_rc.p99_us (+42% then +65% across two back-to-back runs) and the cognate p99_over_median. Median +1.3%, implicit-arm-control all green. Dispatched bencher for hypothesis-driven characterisation; the report (6 back-to-back invocations, recorded per-invocation p99 + within-invocation [lo, hi] spread) is unambiguous: - explicit-arm p99_us cv = 18.6% across invocations - explicit-arm median_us cv = 0.37% (steady-state allocator signal) - implicit-arm p99_us cv = 2.9% (the control — no co-firing) - 4 of 6 invocations would trip the 25% gate even though the underlying mean (~329 µs) is closer to baseline (259.9 µs) than to the worst observed (418 µs) Structurally identical to the 2026-05-20 recalibration that removed max_us and p99_9_us (iter bench-harness-recalibration.1, Gitea #15 / #16) — see docs/specs/0047-bench-harness-recalibration.md. The 2026-05-20 gamble was that p99 was still allocator-attributable on a quiet developer machine; that gamble has now failed on the explicit arm. Ratify path: removed latency.explicit_at_rc.p99_us and latency.explicit_at_rc.p99_over_median from baseline.json. The explicit arm gates only on median_us going forward — the only metric whose cv (0.37%) actually reflects allocator behaviour rather than OS jitter. The implicit-arm p99 + p99_over_median stay — they are stable (cv 2.9%) and provide the contrast that lets future audits distinguish a real allocator regression from machine-state jitter. This is a ratify, not an intentional baseline movement caused by prep.3: the kernel-extension-mechanics work touches schema + checker + workspace-load — no codegen-runtime change that could plausibly affect RC tail latency. The decision is forward-looking metric removal (per honesty-rule: a regression gate that fires 4 of 6 times on byte-identical code is not a gate, it is a random-event generator). Bench results post-ratify: exit 0 across all three scripts (bench/check.py 34 metrics 0 regressed; bench/compile_check.py 24 metrics 0 regressed; bench/cross_lang.py 25 metrics 0 regressed). Architect drift items (8 enumerated) will be addressed in a separate consolidated tidy iteration; this commit only closes the bench gate.	2026-05-28 19:00:12 +02:00
Brummel	078c39a76a	iter prep.2-term-new-construct (DONE 4/4): Term::New AST + Form-A surface + checker + drift — closes #32 ... Second iteration of the kernel-extension-mechanics milestone. Ships the `new` Form-A keyword + `Term::New { type_name, args: Vec<NewArg> }` AST variant + `NewArg::Type|Value` enum end-to-end through schema / surface / checker, with two new diagnostics (`NewTypeNotConstructible`, `NewArgKindMismatch`), a new arm in prep.1's workspace-wide normalisation pre-pass `qualify_workspace_term` that rewrites bare `Term::New.type_name` to qualified form (symmetric to the existing `Term::Ctor` arm), and the data-model.md + form_a.md anchor additions. Codegen out of scope per spec; codegen sites get `CodegenError::Internal` arms naming the raw-buf milestone as the carrier. Verification: - `cargo test --workspace`: 654 tests passing, 0 failed. - 3 new in-source checker tests pin the elaboration paths: `new_resolves_via_type_scope` (the spec's worked Counter example checks cleanly), `new_type_not_constructible` (missing `new` def in home module fires the new diagnostic), `new_arg_kind_mismatch_value_where_type` (kind-mismatch detection). - 2 new schema-drift pins (`term_new_round_trips`, `term_new_type_arg_round_trips`) ratify the JSON byte shape: `{"t": "new", "type": "<TypeName>", "args": [{"kind": "type"|"value", "value": ...}]}`. - 1 new surface round-trip pin exercises mixed-kind args through Form-A → JSON → Form-A. - 44+ exhaustive Term-match sites across 24 files extended with `Term::New` arms — workspace-wide cargo build clean. Concerns documented inline: - `crates/ailang-core/tests/schema_coverage.rs` deliberately does NOT register `VariantTag::TermNew` in the `EXPECTED_VARIANTS` set. The coverage test asserts every declared variant is observed in the .ail fixture corpus; no .ail fixture in the current tree emits `"t": "new"` (codegen-runnable Term::New programs require the raw-buf milestone's plugin registry). Registering would fail the coverage check. The `visit_term` arm IS extended (compile-forced); only the enum registration is deferred. Inline rationale in the source. Future milestone that ships a Term::New fixture extends both sides. - `crates/ailang-surface/src/print.rs` `write_term` Term::New arm was added in Task 1 (not Task 2 as planned), because without it ailang-core's tests fail to compile (the surface crate is in the dependency graph of ailang-core's test binaries). Task 2's round-trip pin verified the arm's correctness. - Task 3 (synth elaboration) needed one implementer re-loop: the first attempt over-qualified within-module type-references via `qualify_local_types` on `new`'s signature when the home module was the calling module itself. Fixed by skipping qualification when `home_module == env.current_module`. Architectural composition with prep.1: `Term::New` joins `Term::Ctor` as a `type_name`-bearing site that goes through `qualify_workspace_term`'s bare→qualified rewrite before the checker sees it. The checker's `synth` arm for `Term::New` therefore receives an already-qualified `type_name` (or a local bare name for same-module construction). Milestone status: kernel-extension-mechanics (Gitea #6) advances 2/3 iters. Next: prep.3 (kernel-tier modules + param-in), issue #33.	2026-05-28 15:31:13 +02:00
Brummel	b586999e81	iter prep.1-type-scoped-namespacing (DONE 5/5): TypeDef-first resolution + workspace pre-pass — closes #31 ... First iteration of the kernel-extension-mechanics milestone. Ships the type-scoped `<TypeName>.<member>` resolution path as the canonical form for type-associated operations, narrows the `BareCrossModuleTypeRef` / `BadCrossModuleTypeRef` diagnostics from "bare = strictly local" to "bare = in-scope by any path", migrates 12 std-library example fixtures, and introduces a workspace-wide normalisation pre-pass `prepare_workspace_for_check` shared between `check_workspace` and `monomorphise_workspace`. Architectural discovery during implementation: the plan covered the `Term::Var` dot-qualified resolver layer plus the workspace validator's bare-name acceptance, but the migration of bare-form fixtures exposed five sites where bare vs. qualified type-names needed symmetric treatment — `Term::Ctor` resolution, `Type::Con` well-formedness, mono's poly-free-fn name/constraint-count enumeration, codegen's `lookup_ctor_by_type` bare-name path, and the upstream desugar-then-qualify composition. Rather than scattering TypeDef-first ladders across each site, the implementer centralised the work into one pre-pass that walks every consumer module's `Type::Con.name` and `Term::Ctor.type_name`, rewriting bare cross-module references to their qualified `<home>.<Type>` form. This is symmetric to the pre-existing `qualify_local_types` (owner-side); the new pre-pass is the consumer-side mirror. Downstream passes see qualified Types regardless of authoring form. The TypeDef-first ladder still lives in `synth`'s `Term::Var` arm because `<TypeName>.<member>` is term-position-only — `Maybe.from_maybe` is a Var, not a Type expression, and the pre-pass does not rewrite Var names. Alternatives considered: (a) Add TypeDef-first ladder at every resolution site separately (the plan's implicit assumption). Rejected: O(N) extension sites, each carrying the same workspace-walking logic; the pre-pass version is O(1) — one pass, every downstream consumer benefits. (b) BLOCKED + spec re-brainstorm. Rejected: the architecture extension is consistent with prep.1's thesis (bare type-name resolves to the workspace-wide TypeDef) and forward-compatible with prep.2 (Term::New.type_name falls under the same rewrite) and prep.3 (kernel-tier TypeDefs enter the workspace map automatically). No design regression to bounce back over. Spec updated to document the realisation mechanism honestly: the "Realisation mechanism — workspace pre-pass" subsection clarifies that the resolver-level semantics described in "Implementation shape" are the user-facing contract, and the actual code path is the pre-pass. Verification: - `cargo test --workspace`: ALL GREEN. 87 e2e + every crate's unit + integration tests pass with no regressions. - Three NEW in-source tests pin Task 1's resolver paths: `type_scoped_member_resolves`, `type_scoped_member_not_found`, `type_scoped_receiver_not_a_type`. - One NEW workspace test pins the narrowed validator: `ct1_validator_accepts_bare_with_explicit_import`. - One renamed-and-flipped existing test: `ct1_validator_rejects_bare_xmod_with_import_candidate` → `ct1_validator_accepts_bare_xmod_with_import_candidate` (the bare-with-import path is now ACCEPTED). - One NEW companion test for the workspace-wide ctor lookup: `ct2_term_ctor_bare_cross_module_via_workspace_resolves`. - Two pre-existing tests' assertions updated for the new error wording: `ct1_check_cli::check_human_mode_emits_actionable_message_to_stderr` and `crates/ailang-check/tests/workspace.rs::unknown_module_prefix_is_reported`. - 12 migrated `.ail` fixtures verified via the existing e2e suite (each fixture is the test runner's target for an existing `build_and_run` assertion). - Negative fixture `ct_2_bare_cross_module.ail` semantically preserved: dropped its `(import std_maybe)` so bare `Maybe` is out-of-scope under the narrowed rule and still fires `BareCrossModuleTypeRef`. Concerns: - The pre-pass introduces a new architectural layer (consumer-side qualification) that the spec did not originally anticipate. Spec amendment in this commit documents the layer. Future iterations reference `prepare_workspace_for_check` as established infrastructure. - `examples/test_ct1_bare_xmod_rejected.ail.json` switched its offending name from bare `Ordering` (which under the prep.1 semantics may now resolve via implicit prelude) to a still- unresolvable `Mystery_Type`. The CLI test's intent (assert that a human-mode `ail check` exits non-zero on a still-RED case) is preserved. Milestone status: kernel-extension-mechanics (Gitea #6) advances 1/3 iters. Next: prep.2 (`Term::New` construct) issue #32.	2026-05-28 14:43:03 +02:00
Brummel	832375f2ac	convention: counter-prefix file naming across docs/specs/, docs/plans/, design/contracts/, design/models/ ... All 176 files in the four accumulating directories now use a zero-padded 4-digit counter prefix that reflects creation order (`NNNN-slug.md`). The counter is assigned per directory in strict git-log creation order; ties broken alphabetically by original name. The old `YYYY-MM-DD-` prefix on docs/specs/ and docs/plans/ files is dropped — the date is recoverable from git log and the counter carries the ordering. A file's counter is stable for the life of the file: never reassigned, never reused, never compacted. Deleted files retire their counter; subsequent files do not fill the gap. This is the property that lets cross-references stay literal — refs use the full filename including the counter (`design/contracts/0007-honesty-rule.md`) so they grep cleanly and resolve directly without a glob step. 313 cross-references updated across .md/.rs/.toml/.c/.json files (test pins, include_str! paths, design-INDEX entries, baseline notes, runtime C comments, inter-contract markdown links incl. bare basename and `../models/foo.md` forms). CLAUDE.md gets a new "File-naming convention" section spelling out the rule and rationale. skills/brainstorm/SKILL.md and skills/planner/SKILL.md updated so new spec/plan creation produces counter-prefixed names from the start. The full test suite (cargo test --workspace) passes.	2026-05-28 13:31:31 +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	26fb3459d8	GREEN: io/print_str byte-faithful via @fputs(@stdout) — closes #29 ... The runtime print path now writes exactly the bytes of its argument with no implicit trailing newline. `io/print_str` is byte-faithful; authors who want a newline emit `(do io/print_str "\n")` themselves. ## Codegen `crates/ailang-codegen/src/lib.rs`: - Module preamble: `@puts(ptr)` → `@fputs(ptr, ptr)` plus `@stdout = external global ptr` (libc's `FILE *stdout`). - Effect-op lowering for `io/print_str`: emit `getelementptr +8` then `load ptr, ptr @stdout` then `call/tail call i32 @fputs(ptr bytes, ptr fp)`. Identical bytes-pointer GEP, distinct sink. - The pinned IR-shape test renames from `print_str_calls_puts_with_bytes_pointer` to `print_str_calls_fputs_with_bytes_pointer_and_stdout` and now asserts: bytes-GEP present, stdout-load present, both module- preamble declarations present, and no `@puts(` call anywhere in the emitted IR. ## Why this shape, and not the alternatives - *Rename `io/print_str` to `io/println_str` (issue #29 option 2)* — kept the auto-newline, just relabelled it. AILang's design bias is explicit-over-implicit (CLAUDE.md: implicit conversions cut). Auto-newline is a hidden runtime augmentation; the rename would have preserved it. Rejected. - *Append `\n` inside the polymorphic `print` (Show-mediated) function in `examples/prelude.ail`* — would have been a one-line fix. Rejected: `print` is the Show-mediated formatter, not a newline emitter; baking a newline into it would have re-imposed the same implicit-augmentation problem one layer up, breaking callers that legitimately want pure-bytes output. ## Fixture / test sweep 30 `.ail` fixtures whose owning tests asserted line-separated stdout now emit explicit `(do io/print_str "\n")` after each print. Tests that asserted on multi-line stdout (`show_print_e2e`, `floats_e2e`, `str_concat_e2e`, `eq_ord_e2e`, several `print_*` smoke tests) had their fixtures sweetened the same way; assertions themselves remain the canonical observable output. Fixtures that never relied on the newline (no test ever read the absence of one) were left untouched. ## Migrated metadata - `crates/ailang-core/tests/hash_pin.rs`: the `ordering_match::main` canonical hash is refreshed (`b65a7f834703ffb4` → `8ed47b4062ce00f5`). The comment now names both successive corpus migrations honestly: the per-type-print-retirement (which moved `(do io/print_int x)` to `(app print x)`) AND this fputs swap (which wrapped that with `(seq ... (do io/print_str "\n"))`). - `design/contracts/str-abi.md`: the consumer-ABI table now lists `@fputs` as the print sink. A prose paragraph documents the byte-faithful semantics and references this issue. - `examples/ordering_match.prose.txt`: regenerated from the updated `ordering_match.ail`. - `crates/ail/tests/snapshots/{hello,sum,max3,list,ws_main}.ll`: IR snapshots regenerated via `UPDATE_SNAPSHOTS=1`. - Stale `@puts` comments in `runtime/str.c`, `crates/ail/tests/{e2e,show_print_e2e,print_no_leak_pin}.rs` replaced with `@fputs`. ## Verification - `cargo test -p ail --test print_str_no_auto_newline_e2e` — both RED tests from commit c8ecfa3 now pass. - `cargo test --workspace` — 90 test groups GREEN, 0 failures. - `cargo build --workspace` — GREEN. - No new clippy lints (24 warnings pre-existing in `crates/ailang-core/src/lib.rs:129`). - Stats: `bench/orchestrator-stats/2026-05-21-iter-bugfix-print- str-fputs.json` — 1/1 tasks, 0 re-loops, 0 review loops. ## Empirical evidence cited Caught in the 2026-05-21 Qwen3-Coder naming-A/B run (`experiments/2026-05-21-naming-ab/runs/r1/`): every cohort wrote `(do io/print_str "...\n")` with explicit `\n` and got doubled newlines, failing the `t3_main_prints` stdout match across all three cohorts. The empirical LLM-natural form already assumes the new (post-this-commit) semantics — confirming the feature-acceptance test in CLAUDE.md. closes #29	2026-05-21 12:22:45 +02:00
Brummel	5170b6abd1	iter operator-routing-eq-ord.1 (DONE 13/13): drop comparator builtins, route through Eq/Ord ... Closes Gitea #1. Realises the "P2 follow-up" called out in examples/prelude.ail:9 — removes the surface comparator names `==` / `!=` / `<` / `<=` / `>` / `>=` from the language entirely, routes the LLM-author's `(app eq …)` / `(app compare …)` / `(app ne|lt|le|gt|ge …)` through prelude.Eq / prelude.Ord class- dispatch, ships six named Float-comparison fns (`float_eq`/`float_ne`/`float_lt`/`float_le`/`float_gt`/`float_ge`) so Float keeps comparability without an Eq/Ord instance, and emits primitive instance bodies with `alwaysinline` so the -O0 IR shape stays at one instruction per comparison. Plan-task journal (13 tasks, single atomic iter per Approach A): Task 1 — Bootstrap: 4 new fixtures (eq_user_adt_smoke.ail, eq_float_must_fail.ail, float_compare_smoke.ail, operator_unbound_check.ail) + 5 new E2E/pin tests as RED starting state. All 5 confirmed RED at start: north-star fixed `NoInstance Eq Unit` (preserved by Unit-eq opening line intentionally added in plan-self-review); float_compare unknown `float_eq`; operator-name typechecked (== still polymorphic); must-fail diagnostic lacked `float_eq`; alwaysinline absent from IR. Task 2 — Codegen alwaysinline + intercept arms: introduced `intercept_emit_wants_alwaysinline` allowlist + appended ` alwaysinline` between `)` and `{` of the `define` line in `emit_fn`; added 9 new intercept arms to `try_emit_primitive_instance_body` — `eq__Int`/`eq__Bool`/ `eq__Unit` + the six `float_*` arms. Task 3 — Prelude reshape: `instance Eq Unit` added; Eq Int/Bool bodies become placeholder-`false` (intercept overrides); six `float_*` free fns added; line-9 P2-follow-up comment removed. Lockstep hash re-pins: prelude_module_hash_pin (3abe0d3fa3c11c99 → new), mono_hash_stability six body-hash literals (eq__Int/Bool/Str + compare__Int/Bool/Str all shifted because placeholder body changes the canonical hash). IR-snapshot regen (hello/list/max3/sum/ws_main) rolled forward into this task at orchestrator's pragmatic call — prelude shift forces the snapshots immediately. Task 4 — Fixture migration: 58 .ail fixtures rewritten (`(app == …)` → `(app eq …)`, etc.; Float-typed operand sites to `(app float_eq …)` / `(app float_lt …)`). eq_ord_user_adt.ail:21 inner `==` → `eq` migration with lockstep eq_ord_e2e.rs:134 body-hash re-pin (3c4cf040cb4e8bb2 → new). Two prose snapshots accepted; deps test + 5 hash_pin literals updated as cascading consequences. Task 5 — Test-scaffold migration: all 8 in-source `#[cfg(test)] mod tests` AST-literal sites threaded (desugar.rs:2414, check/lib.rs:5656/6092/6220, codegen/lib.rs sites). 7 obsolete in-source tests deleted (5 eq_typechecks + 2 lower_eq ADT/Fn rejection — coverage moves to E2E eq_user_adt_smoke + eq_float_must_fail). 2 additional letrec tests deleted (single-module check env can't resolve eq/ge without prelude auto-import; covered by workspace E2E). Task 6 — Lit-pattern desugar: build_eq emits `Term::Var { name: "eq" }` instead of `"=="` at desugar.rs:1109; doc-comment rewritten to describe class-dispatch. Task 7 — Dead-machinery deletion sweep (compile-gated): typchecker builtins (install + list comparator entries deleted); codegen builtin_binop_typed (10 comparator arms deleted from synth.rs, table reduced to arithmetic core); lower_eq fn entirely deleted; `==` short-circuit in lower_app deleted; `is_static_callee` `==` clause deleted; `is_arithmetic_or_comparison_op` renamed to `is_arithmetic_op` + caller-update at codegen/lib.rs:2152 + :2529. Dead `poly_a_a_to_bool` helpers also removed. Workspace build green after compile gate — every caller of the deleted surface was migrated by Tasks 4-6. Task 8 — Float-aware NoInstance diagnostic: check/lib.rs:856-880 addendum extended to name `float_eq` / `float_lt` as the explicit alternative for Eq/Ord at Float; eq_float_noinstance.rs:32-44 assertion extended. Task 9 — IR snapshot regen: subsumed by Task 3 (prelude shift forced immediate snapshot regen; deferring to Task 9 would have left the workspace red between tasks). Task 10 — Prose-projection cleanup: 6 comparator arms deleted from binop_info; 3 in-source mod-tests updated/deleted (comparator-infix rendering would be dishonest now that the operators are no longer language identifiers). Task 11 — Contract updates: 5 design files rewritten to the class-dispatch present — float-semantics.md (arithmetic guarantees retained on +/-/*/; comparison guarantees transferred from ==/!=/< to float_eq/float_ne/float_lt/etc.); prelude-classes.md (Eq Unit added to instance list; new paragraph on six float_* fns; Float-no-Eq/Ord clause gains `→ use float_eq` cross-reference); str-abi.md (clause "REMAIN primitive operators" rewritten to describe class-method dispatch); scope-boundaries.md (multiple operator-name and Pattern::Lit-desugar clauses rewritten); authoring-surface.md (==, <= dropped from operator-example list). Task 12 — Initial acceptance gate: workspace 638/0 GREEN; bench/compile_check + cross_lang 0 regressed; bench/check.py flagged 4 regressions on bench_closure_chain (+29% bump_s, +47% rc_s, +29% bump_rss_kb, +48% rc_rss_kb). Orchestrator initially classified as DONE-with-concerns; Boss reclassified as PARTIAL-via-acceptance-#8-fail after independent re-run, extended iter scope to Task 13. Task 13 — Direct icmp intercept arms (Boss-extension): try_emit_primitive_instance_body gains direct-icmp arms for lt__Int / le__Int / gt__Int / ge__Int / ne__Int, bypassing the compare__Int → Ordering → match indirection that allocated one Ordering ctor per call in tight loops. Each new arm inherits `alwaysinline` via the existing allowlist (extended accordingly). New IR pin test `ord_int_intercept_ir_pin.rs` + smoke fixture `ord_int_intercept_smoke.ail` ratify the optimization — opt -O2 -S confirms zero `call @ail_prelude_lt__Int` in optimized IR; the icmp folds directly at every use site. Bool variants (lt__Bool/etc.) deliberately NOT added — no bench/example calls Ord at Bool; spec-extension permits skipping if unreachable at bench level. Family can be extended symmetrically when first Bool-ordered perf workload appears. Bench-gate post-Task-13: bench_closure_chain bump_s -6.05%, rc_s -2.67%, bump_rss_kb -0.77%, rc_rss_kb +0.46% — all four previously-regressed metrics back inside tolerance. Full bench corpus: 36 metrics, 0 regressed, 0 improved beyond tolerance, 36 stable. bench/check.py exit 0 ✓; bench/compile_check.py exit 0 ✓; bench/cross_lang.py exit 0 ✓. Workspace: 640 passed, 0 failed across all binaries (delta vs. milestone start: +5 new E2E/pin tests added in Task 1 + 1 IR pin added in Task 13 − 9 in-source mod tests deleted as obsolete net ≈ −3). The eq_user_adt_smoke fixture's Unit-opening line was the deliberate RED-first device added in planner self-review so the north-star wouldn't accidentally GREEN at start (user-ADT-Eq on Point with hand-written instance was already operable today; the milestone's actual delivery is operator-name death + Eq Unit + Float-named-fns + cleanup of the two-pathy primitive comparator machinery). Net delta: 96 files changed, 1760 insertions, 1101 deletions; 12 net-new files (6 new fixtures, 5 new E2E/pin tests, 1 stats file). main passes-test-count: 640 (was 633 pre-iter, accounting for the deletions). Spec-vs-acceptance addendum: spec §Testing strategy anticipated the bench-gate-regression case with two recovery paths (`alwaysinline` investigation or "spec needs revisiting toward α"). Task 13 is the third path — direct intercept arms for `lt`/etc. that bypass the compare→match path entirely. The spec's contingency clause was thus generous enough to absorb Task 13 without spec revision, but a future iter that hits a class-method primitive where the body shape introduces a similar codegen cost (Ordering allocation, RC tax, deferred-init) should expect a parallel extension. The pattern is "primitive instance whose canonical body indirects through other class methods that allocate" → add a direct-emit intercept arm + alwaysinline + IR-shape pin. Concerns absorbed: - Codegen lower_app / resolve_top_level_fn gained a prelude-fallback lookup so bare monomorphic prelude fns (`float_eq` etc.) resolve from non-prelude modules without explicit `prelude.float_eq` qualifier. Mirrors the typechecker's implicit prelude import — not in plan but necessary infra for the named-fn surface to be callable. - Recon's "≈10 fixtures" estimate was 6× too low — 58 actual. Mechanical migration; no design impact. - Recon caught 4 in-source AST-literal sites the spec missed (lib.rs:5656 `>=` site + three codegen/lib.rs sites); Task 5 covered all. - Recon caught 2 contract files outside the spec's update set that directly contradicted the milestone (str-abi.md + scope-boundaries.md "REMAIN primitive operators" / "Pattern::Lit desugar to ==" clauses); Task 11 covered all 5. Stats file: `bench/orchestrator-stats/2026-05-21-iter-operator-routing-eq-ord.1.json`. closes #1	2026-05-21 01:16:21 +02:00
Brummel	14a91f0ae5	iter boehm-retirement.1 (DONE 10/10): retire the transitional Boehm GC backend ... Closes Gitea #4. Removes the Boehm-Demers-Weiser conservative GC backend wholesale across six layers in one atomic iteration. After this iter, `AllocStrategy` has two variants (`Rc`, `Bump`), `--alloc=gc` is rejected at CLI parse with `unknown --alloc value`, the libgc link arm is gone, and the design ledger describes RC (canonical) + bump (raw-alloc bench-floor) as the only allocators. Layer-by-layer summary: CLI surface — `crates/ail/src/main.rs`: `parse_alloc_strategy` arm `"gc" => Ok(AllocStrategy::Gc)` removed; error wording updated to `(expected `rc` or `bump`)`; clap-derive `value_parser = ["gc","bump","rc"]` allowlist on BOTH `Build` and `Run` subcommands DROPPED so that `parse_alloc_strategy` remains the sole gatekeeper for the unknown-value diagnostic (otherwise clap shadows the runtime diagnostic with `invalid value 'gc' for '--alloc'`, which would miss the milestone-pin's stderr substring check). The `default_value = "rc"` stays. Codegen — `crates/ailang-codegen/src/lib.rs`: `AllocStrategy::Gc` variant + `Default` derive removed (no caller of `AllocStrategy::default()` existed in the workspace, so the trait derivation was dead). `fn_name` (spec called it `runtime_alloc_fn` loosely; actual identifier is `fn_name`) drops the `Gc => "GC_malloc"` arm. `lower_workspace` and `lower_workspace_staticlib` defaults flip from `Gc` to `Rc`. In-source negative-complement codegen test (mod tests, lib.rs:3571ff) retargets from `AllocStrategy::Gc` to `AllocStrategy::Bump` (bump also doesn't emit per-type drop fns; the test's semantic "no drop fns under non-RC" is preserved). Link branch — `crates/ail/src/main.rs:2389ff`: The `match strategy { AllocStrategy::Gc => { ... cmd.arg("-lgc"); ... } }` arm and its libgc-link block are entirely gone. The surviving match exhausts on `Bump` and `Rc` (Rust's exhaustiveness check confirms; no `error[E0004]`). Staticlib-guard diagnostic rewritten to drop the "shared Boehm collector" phrasing while preserving the prefix `staticlib (swarm) artefact is RC-only` verbatim (the surviving `staticlib_bump_is_rejected` test depends on that substring). Test suite — 3 pure-differential e2e tests deleted (`gc_handles_recursive_list_construction`, `alloc_rc_produces_same_stdout_as_gc`, `alloc_rc_matches_gc_on_std_list_demo`); 9 RC-feature tests stripped of their `stdout_gc` build call and differential `assert_eq!(stdout_gc, stdout_rc, ...)` (absolute `assert_eq!(stdout_rc.trim(), "<n>")` pin retained as correctness oracle); `staticlib_gc_is_rejected` deleted; new milestone-pin `crates/ail/tests/boehm_retirement_pin.rs` asserts `ail build --alloc=gc` exits ≠ 0 with stderr containing `unknown --alloc value` and `\`gc\``; `examples/gc_stress.ail` fixture deleted (no remaining references). Implementer expansion (not in plan): `iter17a_local_box_alloca` (in `e2e.rs`) carried an IR-shape assertion against `@GC_malloc`-absence as the witness for non-escaping allocation. After the Task-2 codegen default flip, the witness shifts to `@ailang_rc_alloc`-absence in escape-targeted positions; assertion + doc-comment updated. Property protected ("no heap allocation in non-escaping contexts") is unchanged; only the named allocator shifts. Bench harness — `bench/run.sh` 9→6 column compaction (workload + bump(s) + rc(s) + rc/bump + bump RSS + rc RSS); gc-arm `bench_latency_implicit_gc` build call + harness invocation dropped from latency block; header comment reframed from "GC-overhead bench harness" to "RC-overhead bench harness"; "Decision 10's Boehm-retirement target (1.3x)" rewording to "RC-overhead-vs-bump bench-health regression gate". `bench/check.py:62` header-sentinel changes from `"gc(s)" in line` to `"bump(s)" in line`; column-count check at `:72` flips from `!= 9` to `!= 6`; per-workload field set drops `gc_s`/`gc_over_bump`/`gc_rss_kb`; `ARM_LABEL_TO_KEY` drops the `"implicit @ gc": "implicit_at_gc"` entry. `bench/baseline.json` regenerated via `--update-baseline`. Implementer note (planner-defect): `write_new_baseline` iterated over the *existing* baseline's metric list when emitting the regenerated file, so even after parser-level `gc_*` removal, the fallback emitted them back into the JSON. Scrubbed post-update; the cleaner fix (have `write_new_baseline` emit only keys present in `parsed_throughput[workload]`) is a follow-up if the script becomes load-bearing for further allocator changes. Design ledger — `design/models/rc-uniqueness.md` excises the `## Dual allocator — RC canonical, Boehm parity oracle` section and the `Boehm-Demers-Weiser conservative GC` choice block + rationale + trade-offs; the per-fn-alloca section generalises Boehm-specific language to allocator-agnostic; the memory-model section's `## Choice.` paragraph reframes the 1.3× target from "Boehm-retirement gate" to "bench-health regression gate". `design/models/pipeline.md` drops the `--alloc=gc → links libgc` arm of the pipeline diagram and replaces it with `--alloc=bump → links bump-floor`; the accompanying prose rewrites accordingly. `design/contracts/scope-boundaries.md` rewrites the "Memory management via Boehm conservative GC" bullet to describe RC + per-fn-arena present-tense; the dead reference to `examples/gc_stress.ail.json` (file never existed; the fixture only ever had a `.ail` form, deleted by this iter) is dropped along with the `examples/std_list_stress.ail.json` reference whose purpose was Boehm-only soak testing. `:67`'s `@printf` / `@GC_malloc` parenthetical updated. `design/contracts/memory-model.md:232` drops the "leaks like the pre-Boehm era" phrase; the RC inc/dec instrumentation is wired up, so the "until then" conditional that referenced pre-Boehm is closed. `design/contracts/embedding-abi.md:42-44` rewrites the staticlib-guard prose to drop the `--alloc=gc` clause (gc is now a CLI-parser-level unknown-value, not a staticlib-guard rejection) and reframe the swarm-safety justification around `--alloc=bump` (leak-only bench instrument) rather than the historical Boehm collector. Honesty pin — `crates/ailang-core/tests/docs_honesty_pin.rs` inverts the polarity: the present-tense Boehm-anchor assertion on `pipeline.md` (`:116-117`) is deleted, and four absence-pins are added to `design_md_has_no_wunschdenken` against the Boehm-zombie strings `transitional Boehm`, `parity oracle`, `GC_malloc`, `libgc`. The `design_corpus()` already includes `rc-uniqueness.md` so no path-list change was needed for the new pins to scan. `crates/ailang-core/tests/design_index_pin.rs:166` drops the `"pre-Boehm"` token from the protected-exception comment list (the phrase no longer appears in `memory-model.md` after this iter, so the exception is dead). Runtime docs — `runtime/bump.c`, `runtime/rc.c`, `runtime/str.c` header comments scrubbed of Boehm/`GC_malloc`/`libgc` references. `bump.c`'s function signature description still documents `void *bump_malloc(size_t)` as the bench-floor allocator interface, but no longer cross-references libgc. Example fixtures — `examples/bench_latency_implicit.ail`, `bench_latency_explicit.ail`, `escape_local_demo.ail`, `reuse_as_demo.ail`, `rc_pin_recurse_implicit.ail` doc-comment headers scrubbed of `--alloc=gc` / Boehm references. The `.ail` surface (AST) is untouched in every case; round-trip invariant holds (`cargo test -p ailang-surface --test round_trip` green). Skill / agent prompts — `skills/audit/agents/ailang-bencher.md` rewritten to use an RC-vs-bump worked example pattern for the hypothesis-driven bench tutorial, replacing the recurring "RC vs Boehm under heap pressure" example. `skills/implement/agents/ailang-implementer.md` Decision-10 / Boehm references replaced with present-tense RC-commitment framing. IR snapshots — the 5 checked-in snapshots (`crates/ail/tests/snapshots/{hello,list,max3,sum,ws_main}.ll`) regenerated via `UPDATE_SNAPSHOTS=1 cargo test -p ail --test ir_snapshot`. Each previously contained `declare ptr @GC_malloc(i64)` and (for `list.ll`) a `call ptr @GC_malloc(...)` invocation; post-flip the snapshots contain `declare ptr @ailang_rc_alloc(i64)` plus the rc inc/dec runtime declarations. Spec-vs-acceptance addendum (caught at orchestrator end-report, absorbed here rather than in a follow-up spec edit): spec §6 acceptance criteria said "Boehm-grep returns matches ONLY in docs_honesty_pin.rs". The plan itself prescribed historical Boehm references in 3 additional files: (a) the new milestone-pin `boehm_retirement_pin.rs` (must literally invoke `--alloc=gc` to assert its rejection), (b) `embed_staticlib_alloc_guard.rs` file doc-comment historical note ("`--alloc=gc` no longer exists as a CLI value"), (c) `embedding-abi.md:44-45` contract historical clause ("see the Boehm-retirement iter"). All three are prescribed; the spec's grep wording was too narrow. The four absence-pins in `docs_honesty_pin.rs` catch the actual zombies (Boehm-narrative re-emerging in the design ledger), which is the substantive intent the spec was aiming at — the four extra documented-by-design exceptions are the cost of having an explicit milestone-pin and contract-level historical anchors. Net delta: - 32 files modified, 2 new (boehm_retirement_pin.rs + stats), 1 deleted (gc_stress.ail); - workspace tests: every binary `0 failed`. Pass-count delta: -3 net (4 e2e tests deleted, 1 new milestone-pin test added); - boehm-grep state: hits only in the four by-design exceptions documented above; - `bench/check.py` exit 0 against regenerated baseline; - CLI must-fail fixture: `ail build --alloc=gc examples/hello.ail` exits non-zero with stderr containing `unknown --alloc value` and `\`gc\``; - design ledger present-tense honest (Boehm-narrative gone from `rc-uniqueness.md` + `pipeline.md`; the few historical references in `embedding-abi.md` / `boehm_retirement_pin.rs` / `embed_staticlib_alloc_guard.rs` are explicit milestone-pins or contract anchors, not silent ledger residue). Bench measurement variance noted: closure-chain and hof-pipeline are ±1-5% jittery between runs; one regeneration flagged 2 metrics as `regressed` before a second run returned 0. The captured baseline is within self-comparison range. Existing per-metric tolerances absorb the jitter. Stats file: `bench/orchestrator-stats/2026-05-20-iter-boehm-retirement.1.json`. closes #4	2026-05-20 20:51:53 +02:00
Brummel	7a42989b34	iter nullary-app.1 (DONE 5/5): accept (app f) as canonical zero-arg call ... Resolves Gitea #12 — the design fork from the 2026-05-20 /boss session, surfaced independently by two prior fieldtests (mut-local F3 + loop-recur `run_forever`). Mechanics, layer by layer: Parser — `crates/ailang-surface/src/parse.rs:1322-1331` drops the 4-line `expected at least one argument` guard in `parse_app_body`. Grammar comments at file top change `term+` to `term*` on both `app-term` and `tail-app-term`; doc comment on `parse_app_body` changes `1+ args` to `0+ args`. Inline comment cites #12 and notes which layers below already accept empty args. Serde — `crates/ailang-core/src/ast.rs:419-425` annotates `Term::App.args` with `#[serde(default)]`, mirroring `Term::Ctor.args`'s *actual* attrs verbatim (no `skip_serializing_if`). Write behaviour unchanged — canonical JSON still emits `"args":[]` for nullary calls; only read behaviour gains tolerance for the `args` key being absent. Verified hash-impact-free at plan time: `grep -rn '"args":\[\]' examples/*.ail.json` returns zero matches, so no existing fixture's canonical bytes shift. Doc-honesty — `design/contracts/data-model.md`: (a) the `app` jsonc shape gains an explicit "args may be empty / read-tolerant" note; (b) the existing `ctor` comment claiming "args omitted when empty" was factually false (Ctor.args has no `skip_serializing_if`; a serde probe at plan time confirmed writes always emit `"args":[]`). Rewritten to describe the actual write/read asymmetry, with a cross-reference to the new `app` note. E2E pin — `crates/ail/tests/nullary_app_e2e.rs` + `examples/nullary_app_smoke.ail`. Defines `greet : fn() -> Unit !IO` and calls it as `(app greet)`; asserts stdout `"hello\n"`. RED→GREEN pin for the parser change AND the milestone-protecting E2E for nullary call surface going forward. Fixture literal is `"hello"` (no `\n`) because `io/print_str` lowers via `puts` which appends a newline — the plan body had a `"hello\n"` literal which would have yielded `"hello\n\n"`; the implementer caught and aligned to the canonical pattern in `examples/hello.ail` while writing the fixture, fix scoped to that single file. Layers below parser untouched: typechecker's arity check at `crates/ailang-check/src/lib.rs:3300` is `args.len() != params.len()` which is `0 != 0 → false` for nullary; codegen's `args.iter().zip(sig.params.iter())` at `crates/ailang-codegen/src/lib.rs:2410` is an empty loop; LLVM `call @ail_<mod>_<name>()` with empty arglist is valid; surface printer's arg-emit loop at `crates/ailang-surface/src/print.rs:430-434` writes nothing for empty args, producing exactly `(app f)`. Verification: full workspace `cargo test --workspace --quiet` green (0 failed across all crates); drift pins `design_index_pin 5/5` + `design_schema_drift 8/8`; round-trip `2/2`; new `nullary_app_e2e 1/1`. Stats file: `bench/orchestrator-stats/2026-05-20-iter-nullary-app.1.json`. closes #12	2026-05-20 18:57:14 +02:00
Brummel	13946219f5	fix(runtime): mirror surface .0-fallback in ailang_float_to_str ... `runtime/str.c::ailang_float_to_str` now applies the `.0`-fallback already enforced by the surface printer's `write_float_lit` (crates/ailang-surface/src/print.rs lines 624-637): after the existing `%g` snprintf, if `x` is finite and the rendered buffer contains neither `.` nor `e`/`E`, append `.0` so a whole-valued Float renders with Float-shaped text. The `isfinite(x)` fence keeps `nan`/`inf`/`-inf` from matching the predicate and turning into `nan.0`/`inf.0`. The 64-byte stack buffer's truncation guard is extended by 2 bytes for the fallback path so the defensive `abort()` discipline holds. The alternative (document `%g`-without-fallback in the design/ ledger as a deliberate human-friendly contract) was rejected: the language's stated ethos is machine-readability and round-trip identity; the surface printer is the reference, runtime drift from it is a defect not a feature. Golden updates flow from the contract change. Three fixtures encoded the old Int-shaped output for Float values: - `crates/ail/tests/floats_e2e.rs`: `"4\n42\n-1.5\n"` → `"4.0\n42.0\n-1.5\n"` (1.5+2.5=4.0, int_to_float(42)=42.0). - `crates/ail/tests/e2e.rs::mut_sum_floats_prints_55`: `"55"` → `"55.0"`. The accompanying doc comment used to canonicalise the bug ("`%g` strips the trailing `.0` — so the canonical stdout for Float 55.0 is `55`"); rewritten to reflect the new contract. - `examples/mut_sum_floats.ail` docstring: same correction. Two doc comments are updated where the post-fix contract differs from the old text but the fixture golden does not change: - `examples/float_to_str_smoke.ail` docstring (3.5 still renders as `3.5` because `.` is already present — the fallback does not fire). - `crates/ail/tests/e2e.rs::float_to_str_smoke` doc comment (same observation, made explicit so the trip-wire's intent is clear). Verified: `cargo test -p ail --test print_float_whole_e2e` green (was RED at f19b0dd); `cargo test --workspace` 0 failed across all crates and integration suites. closes #7	2026-05-20 18:24:57 +02:00
Brummel	a355fd861e	fix(drift): scope anchor-presence check to jsonc fenced blocks ... Adds `anchor_in_jsonc_block(md, anchor) -> bool` to `design_schema_drift.rs` — a line-walking helper that toggles on ``` / ~~~ fence markers (any info-string: jsonc, json, or unspecified — all count) and returns true only if the anchor appears inside fenced content. Re-routes the seven `DATA_MODEL.contains(anchor)` assertion sites in the file (Term, Pattern, Type, Literal, Def, ParamMode, nested struct keys) onto it. The carrier from `debug` named six sites; in the implement phase the orchestrator flagged a seventh — `design_md_anchors_nested_ struct_keys` — that exhibited the identical scope-widening bug and was structurally identical to the named six. Routing it uniformly is the cohesive shape of the fix; leaving it as `.contains()` would have preserved a known false-positive surface inside the same file the fix targets. The "minimal fix, no surrounding cleanup" constraint blocks opportunistic refactor, not the uniform application of the named one-line substitution. Verified: 8/8 in `design_schema_drift` green (was 7 + 1 compile- blocking RED at c8c30d5); full ailang-core suite green; full workspace `cargo test` green, no regressions. Mirrors the inverse `strip_fences` pattern in `crates/ailang-core/tests/design_index_pin.rs`. closes #10	2026-05-20 18:15:44 +02:00
Brummel	21cfccf846	iter bench-harness-recalibration.1 (DONE 4/4): drop 6 latency entries + recapture baselines ... One-artefact iter on `bench/baseline.json`. Closes Gitea #15 + #16 as documented in the spec commit `a97aaeb`. Changes: - `note` field rewritten forward-looking: drops the retired-JOURNAL workflow reference (Journal system deleted in 54f0ced) and the now-moot `*.max_us` tolerance convention (the metric being described is being removed in the same edit). Points readers at `docs/specs/2026-05-20-bench-harness-recalibration.md` + closed issues #15 / #16 for rationale. - 6 latency entries removed (`max_us` + `p99_9_us` × 3 arms: `implicit_at_gc`, `explicit_at_rc`, `implicit_at_rc`). After the edit, `bench/check.py` gates only on `median_us` / `p99_us` / `p99_over_median` across the three latency arms. - All remaining baselines (48 throughput + 9 latency = 57 metrics) regenerated by `bench/check.py --update-baseline` on HEAD `ddb50c3` from a fresh `bench/run.sh -n 5`. `captured` field bumped 2026-05-09 → 2026-05-20. Per-metric `tolerance_pct` and `version` preserved verbatim by `write_new_baseline` (`bench/check.py:249-284`). Verification: - Acceptance §1 (same-HEAD replay): `bench/check.py` exit 0, summary `57 metrics; 0 regressed, 0 improved, 57 stable` on first try (no single-run noise mitigation triggered). - Acceptance §2 (synthetic injection): halving `throughput.bench_list_sum.bump_s.baseline` 0.053 → 0.026 fires REGRESSION row `+99.57% > 10.0%` with exit 1; restoration via `jq` returns the value to 0.053 and the next `bench/check.py` exits 0 (with 2 `improvement` rows on `latency.explicit_at_rc.p99_us` / `p99_over_median` at ≈-33% — improvements never gate; this is exactly the tail-distribution jitter that motivated dropping `max_us` / `p99_9_us`). Diff shape: - `bench/baseline.json` shows +230 / -67 lines. Most of the line- count growth is the `json.dumps(indent=2)` pretty-print emitted by `--update-baseline` (`bench/check.py:283`) replacing the previous hand-formatted compact entries (each metric was one line; now each is six). No behavioural delta — the file is semantically identical to a hand-edited version of the same changes. Future `--update-baseline` runs will keep this expanded format. - `bench/orchestrator-stats/2026-05-20-iter-bench-harness-recalibration.1.json` is the iter-stats artefact: outcome DONE, 0 re-loops across all 4 tasks, the four bench-result fields documenting the acceptance outcomes. Stats files are committed per `skills/implement/SKILL.md` Step 3. No code change to `bench/check.py` / `bench/run.sh` / `bench/latency_harness.py`. No Rust crate touched. `cargo test` not exercised by this iter — the harness IS the test surface and its replay+injection ARE the acceptance checks. Follow-up noted (not addressed here): - `skills/implement/agents/ailang-implement-orchestrator.md` references a Phase-4 per-iter journal write; the `docs/journals/` directory was retired in 54f0ced. The orchestrator handled the mismatch by skipping the phase; the agent prompt itself is stale and should be edited in a follow-up tidy iter. closes #15 closes #16	2026-05-20 16:15:13 +02:00
Brummel	93887aa03b	workflow: replace docs/roadmap.md with Gitea issue backlog ... The forward queue moves out of the in-tree markdown file and into Gitea issues at http://192.168.178.103:3000/Brummel/AILang/issues. Labels: kind:{milestone,feature,todo,idea} + prio:{p1,p2,p3} + state:in-progress. Big chunks live as Gitea milestones (containers) with full prose in the description; smaller items are standalone issues. Browse-and-filter scales constant against growing item count; the previous markdown file was 1059 lines, of which ~850 were already-closed-entry verlauf (the same failure class the JOURNAL cut removed). Sync-drift Code<>Tracker mitigation: Soft-convention `closes #N` / `refs #N` in commit bodies — Gitea auto-closes the issue on push. Captured in user-level CLAUDE.md (~/.claude/CLAUDE.md, not in this commit) as the durable rule; no hook enforcement. In-repo changes: - docs/roadmap.md deleted. - CLAUDE.md (project): Code-layout drops roadmap; /boss gating retargeted; Roles section rewritten with a new "Gitea issues" bullet (URL + tea-CLI snippet) and the closes-#N trailer note. - skills/boss/SKILL.md: 10 sites retargeted, plus Step 1 now prescribes `tea issues ls --labels prio:p1` as the queue read. - skills/brainstorm/SKILL.md: Step 7.5 no-override BLOCK now files a Gitea issue via `tea issues create` instead of appending a roadmap entry; spec deletion stays. - skills/audit/SKILL.md + ailang-architect.md: deferral requirement and debt-heuristic retargeted; forward-intent belongs in the Gitea backlog. - skills/fieldtest/SKILL.md, skills/docwriter/SKILL.md + ailang-docwriter.md: roadmap → backlog. - design/contracts/honesty-rule.md: forward intent lives in the Gitea backlog (pinned phrases unchanged). - design/INDEX.md: Docs bullet drops roadmap, adds the backlog URL. - crates/ailang-core/tests/docs_honesty_pin.rs: two assert messages retargeted (assertion bodies unchanged). - bench/architect_sweeps.sh: Sweep-4 TABU extended with `docs/roadmap\.md` so the deleted path cannot quietly regrow as a cross-reference in design/contracts/. Verification: - cargo build --workspace clean. - cargo test --workspace: 647 passed, 0 failed, 2 ignored. - bench/architect_sweeps.sh exit 0 (all five sweeps clean, incl. new TABU). - grep over the live tree (excluding docs/specs/, docs/plans/) shows zero residual docs/roadmap.md refs. Not touched: ~55 historical files under docs/specs/ and docs/plans/ that mention docs/roadmap.md. Snapshot-character, analogous to the JOURNAL-cut precedent — historical specs are not mass-edited just because a live file was retired; their mentions were correct at write time.	2026-05-20 14:48:27 +02:00
Brummel	99df14c792	workflow: scrub residual JOURNAL/journal refs missed in the first sweep ... A re-grep found 15 live references (excluding docs/specs/ and docs/plans/, which stay historical) the previous two commits missed — all in source comments, doctests, bench helpers, and one agent file. Per-file: - crates/ail/src/main.rs: typeclass-coherence diagnostic comment pointed at "the JOURNAL queue's wording" — points at design/contracts/typeclasses.md alone. - crates/ailang-prose/src/lib.rs: `//!` header referred to docs/JOURNAL.md "Pinned: human-readable prose surface" — retargeted to design/contracts/authoring-surface.md. - crates/ailang-check/src/lib.rs: bugfix tag + "see iter method-dispatch-refactor journal" prose collapsed to a clean rationale paragraph; the canonical shape is stated inline. - crates/ailang-surface/tests/prelude_decouple_carve_out_pin.rs: "(d) record the rationale in a per-iter journal" → "(d) record the rationale in the commit body". - crates/ailang-surface/tests/prelude_module_hash_pin.rs: header collapsed (pd.2/pd.3 milestone narrative dropped — the test's purpose is self-evident from its body); both "per-iter journal" drift-instructions point at the commit body. - runtime/rc.c: "bench numbers in JOURNAL 18f.2" → "original profiling bench numbers". - bench/run.sh: two "JOURNAL entry" comments → "commit body". - bench/architect_sweeps.sh: header rewritten (cross-ref to the design-md-consolidation milestone commits, not a JOURNAL entry). Sweep-4 extended with two new anti-regrowth phrases ("see the per-iter journal", "in a per-iter journal") so journal prose can't grow back into design/contracts/ silently. - skills/audit/agents/ailang-architect.md: "unlike a journal it lives on main" → "since it lives on main". - ail-embed/src/bin/timeshard_runner.rs: "records it in the close-out journal" → "prints it to stderr". - ail-embed/tests/timeshard.rs: two "journal-only friction timing" → "stderr-only friction timing". Verification (after the edit): - `grep -rin '\bjournal\b'` against live tree returns exactly two hits: the Sweep-4 regex itself (intentional — TABU phrases that prevent regrowth) and the PHRASES array in design_index_pin.rs (intentional — the same regrowth guard at test level). Both are load-bearing negative assertions. - `bash bench/architect_sweeps.sh` exits 0 ("All five sweeps clean") — no design/-side regrowth. - `cargo build --workspace` green; `cargo test --workspace` green.	2026-05-20 11:32:37 +02:00
Brummel	8ad91e7f24	iter design-ledger-formal-links.1 (DONE 5/5): clause-5 hard gate + 7 prose-ref conversions + 2 disposition-(b) homeless removals + honesty-rule positive-half (whole milestone in one iter) ... Positive-half completion of the DESIGN.md -> design/ split: design/ body cross-references are now formal, file-relative Markdown links into the durable tier (design/ or source), and a new in-tree hard gate (design_index_pin.rs clause-5, design_body_links_are_durable_and_resolve) walks every design/contracts/*.md + design/models/*.md, strips fenced code (strip_fences toggles on ```/~~~ lines so a ]( inside a fence is not treated as a link), extracts every ](path), and asserts the target resolves file-relative to a real file under design/-or-crates/-or- runtime/; never docs/, never an in-file #anchor. RED-first via identity-stubbed strip_fences (four embedded synthetic vectors -- first one FAILS); replacing the stub with the real toggle-on-fence impl turns the test GREEN. clause-5 composes with clause-3 into the complete invariant the milestone establishes: every contract cross-reference is EITHER a resolving durable file-link OR clause-3-forbidden decision-record prose. Conversions (recon-and-corpus-verified closed set): Task 2 (7 prose refs, 8 link tokens): float-semantics.md:69 Prelude classes -> [..](typeclasses.md) float-semantics.md:100 bare-path -> [Str ABI](str-abi.md) embedding-abi.md:45 "Frozen value layout" -> [..](frozen-value-layout.md) (drop stale "below") memory-model.md:44 Data model -> [..](data-model.md) memory-model.md:105-106 Method dispatch -> [..](typeclasses.md) (drop stale "below"; the target heading lives in typeclasses.md:227, not in this file) scope-boundaries.md:48 Str ABI -> [..](str-abi.md) scope-boundaries.md:88 mixed split: ailang-core::desugar -> source link + Pipeline -> ../models/pipeline.md (drop stale "above") Task 3 (2 disposition-(b) homeless removals): pipeline.md:60-61 (see docs/PROSE_ROUNDTRIP.md) pointer removed, CLI prose preserved authoring-surface.md:178-181 cross-tier pointer clause removed, ail merge-prose sentence preserved Task 4: honesty-rule.md positive-half paragraph inserted between L14 and the existing L15-blank-L16; both docs_honesty_pin.rs-pinned phrases byte-identical at L14/L19 (now shifted to L19 -> L25 by the +6 lines). Out of scope, preserved (asserted independently): every intra-file "above/below"; embedding-abi.md:51 "frozen value layout below specifies" (no quoted title, no (see) form); data-model.md 38/66/79/206/226 (in-fence ```jsonc schema annotations -- the inline analog of the nominal-mention carve-out). INDEX.md and the decision-records journal byte-unchanged; clauses 1-4 of design_index_pin.rs source byte-unchanged (the only `-` lines in the diff are the two-line //! header rewrite Task 1 Step 5 itself delivers). Boss-verified independently (not on agent report alone): cargo test --workspace 647 passed / 0 failed (+1 vs pre-milestone 646: the new clause-5) cargo test --test design_index_pin 5 / 5 passed cargo test --test docs_honesty_pin 5 / 5 passed (additive paragraph is pin-safe) grep ](.../docs/.../) under design/ zero grep ](#) under design/ zero ](-link count under design/ 8 (closed convert-set) git diff --quiet design/INDEX.md ok git diff --quiet decision-records ok embedding-abi.md:48 pinned phrase byte-identical One Concerns item: Task-5 Step-7's plan-predicted "`-` line count = 1" was actually 2 because Task 1 Step 5 rewrote the //! header 5 -> 8 lines (removing the original L4 + L5, not just L5). Planner self- review-item-8 miss on my part -- a verification-arithmetic error in the plan, NOT an implementation defect. The substantive assertion (clauses 1-4 source byte-unchanged) is fully satisfied; the implementer correctly flagged it and proceeded. The plan stands as written; the assertion's `1` should have been `2`. Lesson noted for future header-rewrite tasks. Spec: docs/specs/2026-05-19-design-ledger-formal-links.md (grounding-check PASS x3 across two corpus-grounded amendments -- clause-6 + cross-ref definition; clause-5 fence-skip + closed convert-set enumeration). Next: mandatory milestone-close audit (no fieldtest -- zero authoring-surface change, reasoned exclusion).	2026-05-19 23:31:30 +02:00
Brummel	f683f1aec8	iter design-md-rolesplit.tidy (DONE 7/7): resolve milestone-close audit drift ... Gate-first TDD: widened design_index_pin.rs clause-3 to a hand-rolled FAITHFUL Sweep-1 superset (case-sensitive digit-anchored line anchors + Sweep-1's ^[^/]* path-excluded date + the audit-named decision-record phrases, case-insensitive); no regex dep; the blanket iter-detector rejected as unworkable. Sentence-level strip of faithfully-migrated history/decision-record prose out of 5 contract files (the audit's 3 spot-checked + roundtrip-invariant.md + data-model.md the exhaustive scan found) into the decision-record journal, each replaced by its present-tense contract equivalent; float-semantics.md stale 'see Str ABI below' -> str-abi.md; architect_sweeps honesty sweeps re-scoped to design/contracts only (models/ is the narrative tier) + ailang-architect.md lockstep. Invariant: clause-3 GREEN => Sweep-1 clean in contracts/. The prior dispatch correctly BLOCKED on a real plan defect (iso_date lacked Sweep-1's path-exclusion, over-firing on legit docs/specs/2026-.. citations); per the two+-defects-in-one-iteration discipline the audit Resolution mechanism+scope were corrected upstream in lockstep (f2cdd67) before re-dispatch, not patched a third time. Boss-verified independently: cargo test --workspace 646/0, design_index_pin 4/4 (clause-3 RED->GREEN), architect_sweeps.sh exit 0 'All five sweeps clean' (acceptance criterion 9 met), acceptance grep CLEAN, 3 docs_honesty_pin pinned runs each exactly 1 contiguous match. Zero spec/quality re-loops. FINAL design-md-rolesplit iteration — milestone functionally complete, audited, drift-resolved, hard gate enforces the honesty spirit.	2026-05-19 13:44:37 +02:00
Brummel	176821c2e7	iter design-md-rolesplit.1 (DONE 9/9): DESIGN.md -> design/ ledger role-split ... The 3020-line docs/DESIGN.md is replaced by the design/ ledger: design/INDEX.md (sole addressable spine, typed Contracts+Models tables, polymorphic links — prose file OR authoritative source //!), 14 design/contracts/*.md test-linked invariants + 3 source-link-only contracts (mangling/env-construction/qualified-xref, no prose file — code is SoT), 5 design/models/*.md whitepapers, and docs/journals/2026-05-19-design-decision-records.md (the relitigation-guard archive — every why/rejected/does-not-do/rollback/ empirical ### moved out at ###-granularity). Clean cut: git rm docs/DESIGN.md, no stub. RED-first crates/ailang-core/tests/design_index_pin.rs — the 4-clause anti-regrowth spine (DESIGN.md-gone / every-INDEX-link-resolves / every-contract-names-a-resolvable-ratifier / contracts-carry-no-decision-record-prose) — demonstrably RED before, GREEN after. Build-atomic by task ordering: design_schema_drift.rs's include_str! (the only compile-time consumer) retargeted to design/contracts/data-model.md BEFORE the deletion; its ## Data model/## Pipeline slicer dropped (a simplification the split enables). 2 NoInstance diagnostics + 2 lockstep E2Es retargeted to design/contracts/{float-semantics,typeclasses}.md. ~12 agent reading lists + 5 SKILL bodies + CLAUDE.md + skills/README.md + ~25 code/C/.ail/spec comment xrefs retargeted; OQ7 dangling 'Iter 13b' cite deleted (no forward target — a pointer would be fiction). honesty-rule.md rewritten so the rule names the new home (rationale->journals), resolving the recon-found internal contradiction; the two docs_honesty_pin.rs:70,72 pinned phrases kept verbatim+contiguous. Boss-verified independently: cargo test --workspace 646 passed / 0 failed; design_index_pin 4/4; acceptance grep CLEAN of live DESIGN.md refs (residuals = only the spec-mandated clause-4 deletion-enforcer). 2 DONE_WITH_CONCERNS routed to the mandatory milestone-close audit: (a) str-abi.md:23 '(iter str-concat, 2026-05-13)' provenance stamp trips advisory architect_sweeps Sweep-1 — Boss-confirmed byte-identical to DESIGN.md@deeffb1:2062-2065, a faithfully-migrated PRE-EXISTING anchor (regexes verbatim, only path retargeted), NOT split-introduced — RATIFY-or-tidy at audit; (b) a now stale-direction intra-prose 'see Str ABI below' cross-ref in float-semantics.md — audit-adjudication candidate. Plan defect noted: Task 9 Step 4's verbatim acceptance grep used a ^./ anchor not matching the system's grep -rIn output; substance re-verified CLEAN. Spec grounding-check PASS x2. Journals INDEX + decision-records pointer appended (Boss-only).	2026-05-19 13:04:22 +02:00
Brummel	70f2a318e0	iter embedding-abi-m5.tidy (DONE 3/3): milestone-close doc-honesty drift — pin-safe, doc/comment-only ... Resolves the M5 milestone-close audit DRIFT (audit journal 28ab56a). Single cohesive commit, M2.tidy a80d495 / M3.tidy 63d7d60 precedent (pins are the coverage, no RED, no audit/fieldtest gate). - docs/DESIGN.md edit-1 §"Free (host side)": dropped the retired-M4 forward-reference ("an additive M4 concern, not a contradiction of this freeze"; M4 retired 2026-05-18) -> present-tense current fact (a boxed-field record is not an M3 embedding type, export-gate-rejected; the freeze covers exactly the all-scalar single-ctor record). - docs/DESIGN.md edit-2 §"Embedding ABI": reconciled the now- inaccurate "(no shared mutable runtime state - ... data-race-free, sanitiser-verified)" blanket with the real post-7bfa11e state: the per-allocation hot path (per-ctx counters + per-object refcount header) is non-atomic by design and never shared (Ctx:!Send, single-thread-per-ctx); the one shared datum is the atomic-relaxed global RC-stats fallback counter; "data-race-free, sanitiser-verified" retained (still true). - runtime/rc.c:88 comment-only: stale "two unconditional ++ operations" -> accurate "one counter bump per alloc/free ... relaxed atomic add on the global null-ctx fallback, a plain ++ on the per-ctx path" (consistent with the adjacent already- correct :93-106 atomic block + :45-55 Threading header). Boss-verified independently: all pins green (design_schema_drift 8/0, docs_honesty_pin 5/0, effect_doc_honesty_pin 4/0, embed_record_layout_pin 1/0) = mechanical proof no pinned/hashed byte moved; the adjacent separately-pinned bare-scalar sentence is byte-identical (shifted 2299->2305 by net-added lines; substring pin, passes); rc.c strictly comment-only (filter empty); cargo build --workspace Finished; git scope = only docs/DESIGN.md + runtime/rc.c + journal/stats. Clears the M5-audit doc-honesty debt; no new debt. FINAL M5 iteration. The M1-M5 Embedding ABI arc is functionally complete, audited, ratified, and doc-honest. Includes the per-iter journal, stats, and INDEX line.	2026-05-19 03:07:40 +02:00
Brummel	28ab56af7e	audit embedding-abi-m5: milestone close — RATIFY gc_rss trio (evidenced) + DRIFT (one doc-honesty tidy); P2 bench noise causally exonerated, baseline pristine for it ... Architect: Invariant 1 PASS (zero data-server in any compiler crate/runtime; ail-embed its own workspace root); M3 frozen-layout SSOT unmoved (the lone rc.c change 7bfa11e touched only the global stats counters); rc.c header-comment honesty accurate. Drift = [medium] DESIGN.md:2358-2360 stale "additive M4 concern" (PRE- EXISTING — M4 retired; correctly scoped out of every M5 iter) + [medium] DESIGN.md §"Embedding ABI" silent-drift (it asserts "no shared mutable runtime state … data-race-free" but the now-atomic global RC-stats fallback IS shared mutable state under concurrency; M5 is AILang's first concurrent consumer) + [low] rc.c:88 "two unconditional ++" imprecise → one doc-honesty tidy iteration (embedding-abi-m5.tidy), same honesty axis, not split. Bencher refuted my pre-audit "gc_rss allocator-orthogonal → environmental" hypothesis WITH EVIDENCE: the 3x *.gc_rss_kb +32% are genuine, deterministic, M5-attributable — 7bfa11e's atomic split a branch in ailang_rc_alloc (reached by GC programs via str.c int->str at print), spilling %r14/%rbx; a stale interior list pointer in the new spill slot is conservatively retained by Boehm, pinning a ~32 MB dead spine (collection #12 freed PRE 32 MB vs HEAD 32 B); bisects exactly on the commit, IR byte-identical, ail sha256-identical; RC/bump RSS dead-stable. bump_s + max_us are pre-existing tracked-P2 noise (bump RC-orthogonal; max_us 1-sample tail-jitter, PRE often worse, +65->+104% swing between runs) — NOT M5. RATIFY the gc_rss trio. Language reason (not effort): Decision 9 — Boehm is explicitly transitional; AILang's committed model is RC + uniqueness. The measurable cost of the correct, necessary, user-approved swarm-safety fix is exclusively a Boehm conservative-stack-scan false-retention artifact on the transitional allocator (codegen-layout-fragile; no memory actually leaked; RC/bump RSS dead-stable). Chasing it with an out-of-scope codegen change invests in the path being migrated away from; the committed RC path is unaffected. Selective baseline re-anchor: bench/baseline.json lines 14/44/64 ONLY -> 137448/137768/137636 (bencher-confirmed steady-state); every other metric byte-pristine (a wholesale --update-baseline would absorb the P2 noise and break the established-envelope discipline). Re-run confirms the 3 now ok at +-0.3%. bump_s x2 + max_us x2: NO-ratify, causally exonerated, baseline left pristine — identical disposition to the M2/M3/prelude-decouple milestone closes. Friction-harvest recorded (P2 flat-array-decision input): host-per-tick-FFI ~= ~206 ns/tick at real EURUSD volume. Ratify discipline: updated baseline JSON + this paired JOURNAL ratify entry committed together (bench/baseline.json + the audit journal + INDEX line). M5 closes after the doc-honesty tidy lands and is Boss-verified.	2026-05-19 02:56:43 +02:00
Brummel	0900f3f413	iter embedding-abi-m5.3 (DONE 3/3): time-shard boundary-invisibility proof + friction harvest ... Final functional M5 iteration (spec ae905de, plan 67027ab; on green m5.1 204c171 + m5.2 b724cd1 whose leak-proof resolved via dbd76e5). Proves the chunk/window-boundary-invisibility claim the M4 retirement rests on: - adapter::fold_window — purely additive windowed sibling of fold_symbol (same MidPriceStream+Kernel path; stream_tick_windowed). fold_symbol/MidPriceStream/Kernel byte-untouched. - chrono as a DEV-dep only — the time-shard test derives (y,m)->Unix-ms bounds (data-server's own precedent) and passes raw ms to the bin; the bin is date-math-free; Invariant 1 unaffected. - new single-responsibility [[bin]] timeshard_runner — one thread per disjoint window, each owning its Kernel (Ctx:!Send => compile-time per-thread-ctx). - tests/timeshard.rs — spec §3 strength-ordered: (a) per-shard (acc,n) BIT-EXACT vs single-thread host fold of that exact window in stream order (THE boundary-invisibility proof); (b) Σ partials bit-exact by construction; (c) whole-window within REL_TOL=1e-6 only (cross-shard f64 reassociation is host arithmetic, never a kernel property — bit-exact there would be the bug; tolerance derived from the recursive-summation error bound). Plus the now-deterministic leak-Σ + a journal-only friction timing capture (no bench gate, no timing assertion). Concrete pin: EURUSD 2017-03/04/05 (recon-verified present, contiguous, no gaps; data-server has no month-listing API). RED was a genuine deterministic compile failure (declared-but-absent bin source; Cargo missing-source error vs the plan's predicted env! error — same cause, no false-green; benign plan-text imprecision in Concerns). Boss-verified independently: timeshard determinism 5/5 (no jitter); full ail-embed suite 0 failed AND 0 ignored across all binaries (m5.2 symbol_fan_swarm_leak_free stays un-ignored & green — the saga's resolution intact); isolated embed_rc_global_stats_race still green; AILang workspace data-server count 0; compiler-surface diff empty (zero diff to crates/ailang-*, crates/ail/, runtime/, examples/*.ail, root Cargo.toml, DESIGN.md). Friction-harvest deliverable (P2 flat-array-decision input): host-per-tick-FFI ~= 658 ms / 3,192,562 ticks ~= ~206 ns/tick at real EURUSD volume. M5 functional work complete; milestone closes next via the mandatory audit (which also handles the pre-existing DESIGN.md:2358-2360 "additive M4 concern" drift, out of m5.3 scope). Includes the per-iter journal, stats, and the INDEX.md line.	2026-05-19 02:40:16 +02:00
Brummel	dbd76e5503	fix(ail-embed): GREEN — build.rs tracks runtime/ as rerun-if-changed; M5 swarm leak-proof armed & deterministic ... bugfix-swarm-rc-alloc-undercount, GREEN stage. RED is the separate audit-trail commit 483117d. Root cause of the m5.2-resume-attempt residual: ail-embed/build.rs declared cargo:rerun-if-changed only for the kernel .ail + build.rs itself — NOT the runtime/ C sources ail build --emit=staticlib compiles into libailang_rt.a. Cargo never re-ran build.rs after the atomic-counter fix 7bfa11e, so ail-embed kept linking a stale pre-7bfa11e non-atomic libailang_rt.a; the swarm's concurrent TLS-NULL host allocs raced the stale non-atomic g_rc_alloc_count++ (frees-stable/allocs-jitter). NOT a second runtime bug and NOT test-methodology unsoundness — runtime/rc.c at HEAD is correct; the isolated crates/ail RED was green only because it rebuilds the staticlib fresh per run. Fix (ail-embed/build.rs, +7 lines): directory-level cargo:rerun-if-changed=<repo>/runtime (Cargo recurses mtimes under the dir). Preferred over a per-file list — the implementer inspected crates/ail build_staticlib (libailang_rt.a = ar(rc.o, str.o), both under runtime/) and chose the directory mechanism so any future runtime source cannot silently re-introduce the same staleness. Existing kernel/build.rs/AIL_BIN rerun-if-changed lines kept. Cohesive consequence (in-scope): symbol_fan_swarm_leak_free un-#[ignore]d — the test BODY is byte-for-byte unchanged (it was quarantined, never weakened); the module-doc + fn-doc breadcrumbs rewritten to the resolved build-dep-staleness rationale. It is now the integration-level acceptance of both 7bfa11e and this fix. Boss also removed a pre-existing unused `DataFormat` import in swarm.rs inline (trivial; the file is committed this iter regardless; warning-clean after). Boss-verified independently: RED rt_archive_freshness -> GREEN; swarm determinism 5/5 (symbol_fan_swarm_leak_free + symbol_fan_swarm_bit_exact GREEN every run, 0 ignored, jitter gone, Sallocs==Sfrees==12000003); isolated embed_rc_global_stats_race still GREEN (untouched, runtime untouched); Invariant 1 data-server count 0; scope = ail-embed/build.rs + ail-embed/tests/swarm.rs + journal + stats only. The M5 swarm leak-proof bounce-back is fully resolved end-to-end. M5 stays open [~]; m5.3 (time-shard + friction-harvest + close-out) remains. Includes the per-iter journal, stats, and INDEX.md line.	2026-05-19 02:21:47 +02:00
Brummel	7bfa11e838	fix(rc): GREEN — atomic global g_rc_* stats fallback counters (swarm-safe) ... bugfix-rc-global-stats-race, GREEN stage. RED is the separate audit-trail commit 427b687. g_rc_alloc_count / g_rc_free_count (runtime/rc.c:90-91) were plain static uint64_t; the __ail_tls_ctx == NULL fallback at rc.c:161 (alloc) and rc.c:212 (dec-to-zero) did a non-atomic ++. A multi-threaded host using the global fallback path (no ailang_ctx_new) raced the read-modify-write and lost increments, so the AILANG_RC_STATS atexit Σ under-counted non-deterministically. Not a memory bug — Ctx:!Send keeps every box on one thread; only the global statistics Σ was wrong (the M5 iter-2 symbol-fan leak-proof finding, b724cd1; user-approved Option A bounce-back resolution). Fix (runtime/rc.c only, 37+/14-): the two globals are now _Atomic uint64_t; atomic_fetch_add_explicit(.., memory_order_relaxed) at the two null-ctx fallback ++ sites; atomic_load_explicit(.., relaxed) snapshot in ailang_rc_stats_atexit (its sole reader). Relaxed is correct and sufficient — pure statistics, no happens-before obligation, atexit reader runs after all worker threads joined. Per-ctx counters and the per-object refcount header stay non-atomic BY DESIGN (single-thread-per-ctx; boxes never cross threads) — out of scope, untouched. Frozen value layout / ABI offsets / host-free rule untouched. The genuinely-still- single-threaded drop-worklist doc note was correctly left unchanged (false correction refused); the two stale atomicity doc blocks corrected for honesty. Boss-verified independently: RED -> GREEN deterministically 3/3 (jitter gone, allocs==frees==16_000_000); full cargo test -p ail green (every binary 0 failed — per-ctx tsan harnesses + embed e2e unaffected; rc.c links into every ail binary, strong regression gate); scope = runtime/rc.c + journal + stats only; RED files unchanged. Unblocks resuming the M5 leak-proof. Includes the per-iter journal, stats, and the INDEX.md line.	2026-05-19 01:57:06 +02:00
Brummel	b724cd17a1	iter embedding-abi-m5.2 (PARTIAL 2/3): data-server adapter + symbol-fan swarm; leak-proof surfaced a non-atomic global g_rc_* stats race ... M5 iteration 2 (spec ae905de, plan 9cc9d9c). Tasks 1+2 clean and committable; Task 3 BLOCKED on a real finding → M5 bounce-back. Shipped: - data-server promoted [dev-dependencies] -> [dependencies] (Invariant-1 sanctioned: ail-embed is the sole meeting point; the AILang workspace graph still has data-server count 0; zero compiler-surface diff — not even root Cargo.toml this iter). - additive `adapter` module (ail-embed/src/adapter.rs): tick_to_px, MidPriceStream (lazy Iterator<f64> over SymbolChunkIter), fold_symbol; RED-first (E0432 -> GREEN). m5.1 core untouched except `pub mod adapter;`. - swarm_runner [[bin]]: one thread per symbol, each owning its Kernel. The clean compile IS the compile-time per-thread-ctx proof (Ctx: !Send => a shared-ctx swarm is E0277). - tests/swarm.rs: real-data symbol-fan E2E. `symbol_fan_swarm_bit_exact` is GREEN and live — per-symbol kernel (acc,n) bit-exact vs an independent same-order host reference (EURUSD/GER40/XAUUSD, ~4s). The Task 3 finding (Boss independently confirmed by reading runtime/rc.c): the global Σallocs==Σfrees leak measurement is an INSTRUMENTATION race, not a memory bug. No box crosses a thread (Ctx: !Send), the real refcount/free is correct (bit-exact GREEN every run); only the global g_rc_* stat counters (rc.c:90-91, 161,212) are non-atomic BY rc.c's own documented single-threaded design, losing ++s when 3 worker threads hit the null-__ail_tls_ctx host-side path. M5 is AILang's first concurrent consumer; rc.c's header (rc.c:44-49) explicitly defers exactly this atomic-vs-non- atomic decision to "when it acquires concurrency primitives". The leak assertion was Boss-split into `symbol_fan_swarm_leak_free` (#[ignore], body preserved VERBATIM — quarantined not weakened; un-ignore = the runtime fix's acceptance criterion) so main stays green and the finding is pinned as a regression marker. The earlier plan/journal claim that embed_swarm_tsan.rs covers this path was wrong and is corrected on the record (that test uses the scalar kernel — zero box allocs — so it never exercised the host-side global-counter path). Escalated as an M5 bounce-back: resolution touches M3-frozen runtime/ and re-frames M5's "zero runtime change" commitment; multiple substantive options, not unilaterally Boss's to pick in frozen-runtime territory. Boss recommendation on the record = Option A (make only the global-fallback g_rc_* counters atomic, as a standalone RED-first runtime micro-iteration; M5 framing amended). Time-shard + friction-harvest remain m5.3. Includes the per-iter journal (with Boss disposition), stats, and the INDEX.md line.	2026-05-19 01:37:50 +02:00
Brummel	204c171e60	iter embedding-abi-m5.1 (DONE 3/3): lean ail-embed core + build.rs + hermetic smoke ... M5 iteration 1 (spec ae905de, plan 22f02aa). Stands up the workspace-excluded `ail-embed` crate: - zero-dependency embedding core (`ail-embed/src/lib.rs`): extern "C" to the M3-frozen ABI + frozen-layout State/Tick box helpers + a Kernel price fold; the Rust port of the audited crates/ail/tests/embed/tick_roundtrip.c. Raw pointers never escape the type. - build.rs (no in-repo precedent): AIL_BIN env override else nested `cargo build -p ail` against the parent workspace (separate target dir → no cargo-lock deadlock), `ail build --emit=staticlib`, link directives. - hermetic data-server smoke (ail-embed/tests/smoke.rs): synthetic Pepperstone-format ZIP fixture via data-server's own public RawTickRecord type → real DataServer → Kernel, bit-exact vs a same-order host reference fold; runs with no /mnt. - `ail-embed` is its own cargo workspace root (empty [workspace] table); data-server is a dev-dependency only. Root Cargo.toml gains only a 4-line non-membership comment. Invariant 1 Boss-verified independently: full+no-deps cargo metadata on the AILang workspace shows data-server count 0; git status path filter empty (zero diff to crates/ailang-*, crates/ail/, runtime/, examples/*.ail); src/lib.rs zero code-level data_server; AILang cargo build --workspace still clean. ail-embed suite 2/2 green (kernel_run_sums_prices unit RED-first + hermetic_smoke integration), verified by me, not just the agent report. Two toolchain-forced corrections to the plan's verbatim ail-embed/Cargo.toml (added empty [workspace] table; sibling dev-dep path ../libs -> ../../libs, manifest-relative) — confined to the plan-created manifest, no acceptance gate altered, 0 review re-loops. Journal Concerns records the planner-recon implication for the next workspace-excluded-nested-crate plan. Adapter API + thread-swarm deferred to M5 iter 2+ per spec/plan. Includes the per-iter journal, stats, and the INDEX.md line.	2026-05-19 01:12:19 +02:00
Brummel	208d7095bc	fix(check): GREEN — over-strict-mode recognises ctor-rebuild-from-primitive-fields as a consume ... Drives the RED test from a11cb7c to GREEN. Bug-fix iter bugfix-over-strict-mode-ctor-rebuild-consume (debug -> implement mini). Check-only lint-precision fix; zero codegen / runtime / ABI / schema / DESIGN.md change. The [over-strict-mode] lint's consume-detection (any_sub_binder_consumed_for / pattern_has_consumed_heap_binder, crates/ailang-check/src/linearity.rs) only recognised a consume of an (own (con T)) param when a heap-typed pattern-binder was moved out of `match p`. When p was destructured into purely primitive fields fed into a Term::Ctor rebuilding p's own ctor, that genuine dismantle+rebuild consume was invisible, so the lint spuriously advised "(borrow ...) would suffice". An LLM author "fixing" that by flipping an export own->borrow would silently invert the ABI ownership contract — why a low-severity advisory FP got a real RED-first fix. Fix: a second recognition path in any_sub_binder_consumed_for — a `match p` arm destructuring binders out of p's ctor that references any of them (primitive or not) inside a Term::Ctor's args in the arm body genuinely consumes p. Two pure helpers: ctor_uses_any_binder (finds a fresh-allocation Term::Ctor reachable in the arm body) + term_mentions_any_binder (deep free-var scan, so binder flow through an intervening expr like (+ acc px) is recognised, not only a bare Var arg). Conservative toward NOT suppressing: a ctor ignoring p's payload still warns (negative-control verified). Over-strict-only — by-name-shadowing imprecision is extra-silence, never under-strict (Known debt in the journal + the fn doc). The two stale doc comments that mis-attributed this FP to a nested `match` corrected for doc-honesty (debugger concern #2 — same code region, in-scope). Boss-verified independently: RED test now GREEN; full cargo test -p ailang-check 108/0 lib + every binary 0-failed with NO existing test modified; ail check examples/embed_backtest_step_tick.ail no longer warns over-strict on st/tick (exit 0); embed_backtest_step_tick_borrow.ail + M3 embed_backtest_step_record.ail still clean; embed_tick_e2e + bench posture untouched. +166/-20 in crates/ailang-check/src/linearity.rs only. Journal + stats + INDEX line in this commit.	2026-05-18 23:50:13 +02:00
Brummel	63d7d60dd1	iter embedding-abi-m3.tidy (DONE 3/3): close M3 audit [medium]+[low] doc-honesty drift, pin-safe ... [medium] DESIGN.md §"Embedding ABI": surgically replaced ONLY the contradicted M1-era parenthetical (asserted the export boundary is scalar-only — false post-M3, a single-ctor record is an accepted export type) with the present-tense truth pointing at the frozen-layout SSOT + the own/borrow mode contract. The parenthetical shared physical line :2300 with the docs_honesty_pin:135 pinned bare-scalar sentence; the edit kept every pinned word (planner Step-5 item-6 pin-safety, the M2.tidy precedent — docs_honesty_pin stayed 5/5 green, RED-restore path never triggered). [low] codegen forwarder-body comment honesty fix (comment-only; the IR byte-pins assert generated code not comments — byte-identical before/after). Boss-verified: both stale fragments grep-absent; 4 standing pins green at the recon baseline; workspace 639/77 byte-unchanged; diff exactly 2 files. No behaviour change; the pins are the coverage (M2.tidy precedent, no audit/fieldtest gate). bench already carry-on/NO-ratify at the M3 audit (causally exonerated). One non-gating planner-quality grep defect recorded in the journal Concerns (orchestrator handled it correctly, no code bent).	2026-05-18 21:50:15 +02:00
Brummel	4ea8bc5faf	iter embedding-abi-m3.1 (DONE 6-7): freeze the value layout — DESIGN.md frozen-layout SSOT + lockstep pointers + enforceable byte-pin ... Tasks 6-7 of the Boss-repaired split dispatch (Tasks 1-5 committed d5c565d). Task 6: DESIGN.md §"Embedding ABI" gains the `### Frozen value layout (M3 — one-way commitment)` SSOT subsection; both "provisional until M3" sentences rewritten to one-way-freeze wording (docs_honesty_pin-safe — the pinned "written **bare**" sentence stayed byte-verbatim, :2297->:2299 content-asserted); // FROZEN ABI lockstep pointers at runtime/rc.c + match_lower.rs lower_ctor + drop.rs; 3 plan-named stale rustdocs fixed + the Boss-caught stale // gate-comment block (check/lib.rs:1917-1922, M1/scalar-only -> M1/M2/M3/C-ABI-permitted-incl-record); byte-pin enforceability demonstrated (RED on a local offset perturbation, GREEN on git-checkout restore — the only legitimate git op, working-tree only). Task 7: milestone-close verification gate. Boss-verified independently (agent report = intent, not outcome): workspace 639 passed / 0 failed; embed_record_e2e 2/2 (own+borrow, global leak-freedom model); byte-pin 1/1; gate 10/10; forwarder 3/3; docs_honesty_pin 5/5 pin-safe; design_schema_drift + embed_export_hash_stable + embed_e2e + M2 swarm regression-green-unmodified. INDEX.md line added (deferred from the PARTIAL — one line per iter, final title). Milestone-close audit next (architect Invariant 1 + bench trio, spec Testing items 8/9 — audit-owned, not the implement run's job).	2026-05-18 21:29:50 +02:00
Brummel	d5c565d48d	iter embedding-abi-m3.1 (PARTIAL 5/7 + Boss spec-defect repair): single-ctor scalar record crosses the C ABI, ownership follows declared mode ... Tasks 1-5 GREEN. T1 baseline pins (re-point annotation + @ailang_rc_alloc heap-box byte-pin: size=8+n*8, tag@0, fields@8/16). T2 export gate widened (is_c_scalar -> two-level is_c_abi_type: single-ctor all-Int/Float record; multi-ctor/Str/List/nested still RED; gate suite 10/10; M1 adt-ret must-fail re-pointed to multi-ctor+Str Reading). T3 codegen forwarder widened (llvm_scalar record Type::Con -> ptr; M2 forwarder body byte-unchanged; 3/3 staticlib pins). T4/T5 E2E record round-trip own+borrow, global leak-freedom. Boss spec-consistency repair (M2.1-precedent class): orchestrator correctly BLOCKED Task 5 on a genuine spec defect -- the single-ctx-readback allocs==frees proof model is unsatisfiable for borrow (and only coincidentally passes for own) because M2's TLS-ctx is bound only during the synchronous forwarder call, so host-side decs land on g_rc_*, not ctx. Boss-verified globally leak-free + value-correct both modes. Spec + plan + harness amended to the stronger global model (sum all ailang_rc_stats: lines; the M2-TLS cross-attribution documented as correct behaviour). No fresh grounding-check (removes an over-strong measurement assumption). Tasks 6 (DESIGN.md frozen-layout SSOT + lockstep pointers + freeze wording + enforceability demo) and 7 (workspace-green gate) re-dispatched on the amended plan. Bench/architect milestone-close is audit-owned. iter embedding-abi-m3.1 (PARTIAL); INDEX.md line deferred to the DONE commit	2026-05-18 21:16:41 +02:00
Brummel	a80d495ab3	iter embedding-abi-m2.tidy: '## Embedding ABI (M1)' -> '## Embedding ABI' lockstep rename (M2 audit doc-honesty fix) ... Resolves the M2 milestone-close audit's only actionable drift item (architect [medium] DESIGN.md:2266 stale (M1) header vs its now-M2 present-tense body + coupled [low] :2354 xref). Current-state-mirror: the section describes the current embedding ABI (M1+M2), so the milestone tag is internal history, not current state. 5 live-coupling sites renamed in lockstep, 3 files: - docs/DESIGN.md:2266 header '## Embedding ABI (M1)' -> '## Embedding ABI' - docs/DESIGN.md:2354 schema-block xref 'see §"Embedding ABI"' - docs_honesty_pin.rs:134 test comment + :136 assert-message - crates/ailang-core/specs/form_a.md:89 live forward-xref (Boss-added 5th site: plan-recon-undercount countermeasure surfaced a live dangling-xref the architect's 3-site scope missed; folded in on the merits — a half-rename contradicts the tidy's own thesis) docs_honesty_pin.rs:135 asserted substring (the rename-immune DESIGN.md body sentence) byte-verbatim untouched. Committed append-only history NOT falsified (Boss-verified diff = 3 content files + journal + stats only). Pins green before AND after (docs_honesty_pin 5/0, design_schema_drift 8/0). Zero language/checker/codegen/schema change.	2026-05-18 17:52:10 +02:00
Brummel	fbeeadeba5	iter embedding-abi-m2.1 (DONE 5-9): swarm-safe ctx ABI complete + sanitiser-verified ... Completes Embedding ABI — M2.1 (Tasks 1-4 committed c9a84b3 as the known-good subset; this commit lands Tasks 5-9 from the re-dispatch against the Boss-corrected plan). - T5: swarm.c per-thread-ctx scalar-swarm capability demo (no SHARED_CTX) + rc_accounting_shared_ctx_is_flagged_by_tsan added to the item-1 harness driver (de-globalisation negative-control teeth, where a shared ctx genuinely races on ctx->alloc_count). - T6: M1 host.c migrated to the ctx ABI; embed_e2e green (s==25 through the ctx-threaded forwarder). - T7: DESIGN.md current-state update (provisional-until-M3 narrowed to the value/record layout; Decision-10 per-thread-ctx note); docs_honesty-pinned sentence + (con Int) snippet preserved verbatim. - T8: regression gate — workspace green; null-ctx fallback byte-behaviour preserved. - T9: bench-trio — compile_check/cross_lang clean; check.py tracked-P2 noise only, causally exonerated (zero codegen/runtime diff vs HEAD), NO baseline ratified. Boss-verified directly (not on report trust): docs_honesty_pin 5/0, design_schema_drift 8/0, embed_export_hash_stable 1/0, embed_export_gate 6/0, embed_e2e 1/0, embed_staticlib_alloc_guard 2/0, print_no_leak_pin 1/0 + e2e rc_stats 4/0; the tsan coherent-stop proven by hand — per-ctx clean (exit 0, 0 warnings), shared-ctx a real ThreadSanitizer data race at rc.c:157/:208 (exit 66). Known debt (journal + roadmap): DESIGN.md '## Embedding ABI (M1)' header still says (M1) while the body mirrors M2 — out of Task 7's scope-limited regions by design; post-audit doc-honesty tidy. Milestone-close audit next.	2026-05-18 17:31:50 +02:00
Brummel	c9a84b33b3	iter embedding-abi-m2.1 (PARTIAL 4/9 + Boss spec-defect repair): ctx ABI + de-globalisation ... Tasks 1-4 land fully review-green and are the cohesive shippable subset (the per-thread embedding ABI, fully wired + proven): - T1: FIXED-FIRST alloc-guard baseline pin (RED captured -> GREEN at T4). - T2: runtime/rc.c gains ailang_ctx_t {alloc_count,free_count} + ailang_ctx_new/_free + __thread __ail_tls_ctx; the two increment sites become 'if (_ctx) _ctx->... else g_rc_...'. g_rc_* statics + ailang_rc_stats_atexit + the constructor RETAINED VERBATIM as the null-ctx (single-threaded executable) fallback. rc_accounting_tsan.c + driver: per-ctx 8x200000 tsan-clean (de-globalisation positive proof). - T3: codegen Target::StaticLib forwarder gains a leading 'ptr %ctx' + one '@__ail_tls_ctx = external thread_local global ptr' decl + TLS save/store/restore around the BYTE-UNCHANGED internal call; _adapter/_clos + internal arg vector untouched (M1 decision held); doc-comment provisionality narrowed to the value/record layout. - T4: build_staticlib rejects --alloc != rc (RC-only swarm artefact). Boss adjudication of the orchestrator's Task-5 BLOCKED (spec-defect, correctly surfaced not hacked): swarm.c's -DSHARED_CTX negative control is structurally impossible — examples/embed_backtest_step.ail is a non-allocating scalar kernel that never writes a ctx field, and __ail_tls_ctx is __thread, so a shared-ctx scalar swarm has no shared-memory write to race on (the spec's OWN item-1 honesty point). The de-globalisation teeth belong to the item-1 rc_accounting harness (shared ctx genuinely races on ctx->alloc_count; orchestrator independently confirmed tsan exit 66). Spec amended in lockstep (Goal coherent-stop, must-fail-axis item 2, Testing item 3, Acceptance) so item 3's negative control is item-1's by the de-globalisation-proof / capability-demo split; plan Task 5 restructured (swarm.c per-ctx capability demo only; negative-control standing test relocated into the item-1 harness driver) + Task 3's plan-transcription error (@ail_backtest_step -> @ail_embed_backtest_step_step) corrected. This is a Boss consistency-repair of an internally-contradictory clause whose intent is already correctly realised in the same spec — not a redesign; no brainstorm bounce. Task-5 working files discarded (corrected plan reproduces them; a structurally-RED test must not enter main). INDEX.md + final journal land at iter completion (re-dispatch [5,9]).	2026-05-18 17:16:40 +02:00
Brummel	bcfe554686	iter emit-ir-staticlib: ail emit-ir --emit=staticlib (M1 fieldtest spec_gap#2) ... Restores the Decision-5 IR-readability affordance for main-free kernels: ail emit-ir gains --emit=staticlib, symmetric with ail build, reusing the M1-audited Target::StaticLib path via a new one-line lower_workspace_staticlib convenience. Zero-export guard byte-identical to build_staticlib's. DESIGN.md widened (not narrowed) + a pre-existing M1 synopsis omission corrected. 3 new E2E tests; no fixture minted, no doc pin (E2E is the coverage). Plan 03493c9.	2026-05-18 16:08:33 +02:00
Brummel	7d7f04e1a4	iter form-a-scalar-param-mode-carveout: scalar-param mode carve-out (docs-honesty tidy) ... Resolves the M1-fieldtest [friction] + [spec_gap]#1 shared root: form_a.md stated an unconditional 'every (fn ...) param needs an (own/borrow) mode' rule in 4 places, contradicting shipped checker behaviour (scalars take and require bare (con Int); a mode on a scalar trips body-pointing use-after-consume/consume-while-borrowed). All 4 sites rewritten symmetric to the existing return-type carve-out; DESIGN.md gains the bare-scalar export-param rule + a corpus-grounded Form-A snippet; RED-first anti-regrowth pin via FORM_A_SPEC + norm(). Zero language/checker/codegen change. Plan 4c266a6.	2026-05-18 15:51:34 +02:00
Brummel	e406d07d81	iter embedding-abi-m1.1 (DONE 7/7): Embedding-ABI M1 — scalar AILang fn callable from C/Rust ... Tasks 4-7 on the Boss-Repaired plan, completing the M1 iteration: - Task 4: check-side export-signature gate — CheckError variants ExportNonScalarSignature / ExportHasEffects (codes export-non-scalar-signature / export-has-effects), code() arms, check_fn gate (params->ret->effects, first-violation-wins, unconditional on f.export.is_some()). The clause-3 discriminator in code: effectful/non-scalar exports fail to typecheck. 6/6. - Task 5: codegen Target::StaticLib — Target enum, threaded param, @main/MissingEntryMain gated behind Target::Executable, one external @<sym> forwarder per export to @ail_<module>_<fn> (fn_scalar_sig/llvm_scalar). In-source missing_entry_main_is_error byte-unchanged. Lowering pin 2/2. - Task 6: CLI ail build --emit=staticlib — clap field, Cmd::Build branch, build_staticlib (verbatim build_to prefix + has_export guard + two-archive clang -c/ar rcs tail) + run_cmd. CLI pin 2/2. - Task 7: C-host E2E coherent-stop proof (cc links libembed_backtest_step.a + libailang_rt.a, backtest_step(0,3)=9 / (9,4)=25, s==25, exit 0) + DESIGN.md §"Embedding ABI (M1)" (scalar C ABI, provisional until M3). E2E pin 1/1. Independent Boss verification: E2E 1/1, gate 6/6, full workspace 0 failures, roundtrip_cli + design_schema_drift + spec_drift green, Invariant 1 holds (no new dep in core/codegen/runtime). 3 behaviour- neutral plan pseudo-vs-reality concerns in the journal. Default-exe codegen/runtime path byte-unchanged (check.py firing = tracked-P2 known-noise, audit-adjudicated). INDEX line added. Completes the M1 iteration (impl). Milestone-close audit + fieldtest (surface-touching) are the next pipeline steps.	2026-05-18 14:50:27 +02:00
Brummel	818177d835	iter embedding-abi-m1.1 (PARTIAL 3/7): schema + surface + baseline prerequisites; plan Repair ... Tasks 1-3 of docs/plans/embedding-abi-m1.1.md, a verified known-good subset (cargo build --workspace exit 0; full workspace green; the roundtrip_cli all-examples gate green): - Task 1: CLI build-path MissingEntryMain baseline pin (examples/embed_noentry_baseline.ail + embed_missing_main_baseline.rs; triple-assertion, layered on the green codegen-unit pin lib.rs:3314). - Task 2: additive FnDef.export: Option<String> (serde default + skip_serializing_if, modelled on FnDef.doc); compile-driven thread of export: None across ~85 FnDef/AstFnDef literals / 18 files incl. all in-source #[cfg(test)] mod tests + drift/hash/spec-drift literals + the codegen lib.rs:3320 in-source pin; hash-stability golden pin; DESIGN.md fn-JSON "export" line. DONE_WITH_CONCERNS (plan symbol content_hash_fn -> def_hash per hash_pin.rs, plan- pseudo-vs-reality class, plan corrected). - Task 3: Form-A (export "<sym>") modifier — parse_export + parse_fn thread + write_fn_def emission + form_a.md grammar; byte-identical round-trip. Task 4 BLOCKED (Boss plan-defect: fixtures declared module != file stem; AILang's loader hard-enforces module==stem at workspace.rs:438, so ail check panicked on load before the gate). Boss resolution (Option 2, overriding the orchestrator's Option 1, rationale in the journal + plan Design-decision 6): keep descriptive embed_* filenames, rename fixture MODULES to their stems — the C symbol backtest_step stays via (export ...), demonstrating spec Decision 2's mangling- decoupling rather than violating it; archive becomes libembed_backtest_step.a, internal symbol @ail_embed_backtest_step_step, host.c unchanged. Plan fixed (Design-decision 6 + Task-4 module==stem + Task-5/6/7 dependent strings + the no-*. Float-head + content_hash_fn concerns folded). Headline fixture corrected; blocked-Task-4 WIP discarded (recreated by the [4,7] re-dispatch from the fixed plan). PARTIAL commit (not the iter's final commit): the implement Repair path mandates committing the known-good subset so the [4,7] re-dispatch starts from a clean tree that includes Tasks 1-3 (Tasks 4-7 structurally depend on the schema field + surface). INDEX line added when the full iter lands post-re-dispatch.	2026-05-18 14:32:39 +02:00
Brummel	7580d434f0	iter docs-honesty-lint.1: canonical docs present-tense-honest + wrap-robust pin + Sweep 5 ... Strips Wunschdenken (forward intent stated as fact) and non-citation post-mortem / doc-archaeology from docs/DESIGN.md (14 corrections incl. 1 Step-14 procedural-catch-all site the spec's illustrative regex would have missed) + docs/PROSE_ROUNDTRIP.md; genuine forward intent (LLM tool-use / MCP / LSP) relocated to roadmap P3. Codifies the tense+modality discriminator as a present-tense DESIGN.md meta- subsection. Guards two ways: wrap-robust enumerated absent/present pin (crates/ailang-core/tests/docs_honesty_pin.rs, norm() whitespace- collapse helper — structurally discharges the recurring grep/contains line-wrap failure family) + wrap-robust advisory Sweep 5 in architect_sweeps.sh (contiguous-fragment regex) with full sweep-count lockstep + new ailang-architect.md "DESIGN.md honesty drift" bullet. KEEPs preserved (Diverge-reserved, regions-rejected, self-labelled tiebreaker). No language/checker/codegen/runtime change — sole crates/ change is the additive pin; ail check/run/build byte-unchanged. Workspace 609/0 (delta +4 pin), sentinel trio green, build clean.	2026-05-18 12:30:03 +02:00
Brummel	07f080256c	iter remove-mut-var-assign.1: atomic removal of mut/var/assign ... mut/var/assign removed from AILang entirely and atomically. Deleted: Term::Mut/Term::Assign/struct MutVar; the three Form-A keywords + parse_mut/parse_assign + grammar EBNF; the 4 mut CheckError variants; the mut_scope_stack synth threading (param dropped from synth + every internal/external/test caller); the two lower_term arms; and every exhaustive no-_ Term::Mut/Term::Assign match arm across 17 source files — cut in lockstep with DESIGN.md, fixtures, the drift trio, carve-out and roadmap so the schema is honest at every commit. No catch-all wildcard introduced (verified). loop/recur + let/if are the surviving forms. The shared codegen alloca machinery survives (loop reuses it): mut_var_allocas renamed binder_allocas (representation-only, loop codegen byte-identical) and the shared Term::Lam escape guard simplified to !loop_stack.is_empty() with the loop half (LoopBinderCapturedByLambda) byte-equivalent. Feature-acceptance applied inverted: the removed feature fails clause 2 (redundant) and clause 3 (IS the iterated-mutable-state bug class). Behaviour preservation is executable: mut_counter/mut_sum_floats still print 55 after the faithful let/if rewrite. The removal is made executable by the new mut_removed_pin.rs (4 must-fail pins). Independent verification: cargo test --workspace 605/0, zero residual mut symbols in any crate source, loop/recur non-regression all green (55 / 500000500000 / infinite-compiles / the lambda_capturing_loop_binder pin), roundtrip_cli PASS. One DONE_WITH_CONCERNS: a 4th recurrence of the recon-undercount class (in-source mod tests + a drift-pin fn + 5 orphaned mut .ail.json carve-outs + a non-enumerated E0599); all resolved within implementer remit, no behaviour change. Milestone-close audit then fieldtest remain. spec docs/specs/2026-05-18-remove-mut-var-assign.md (grounding PASS) plan docs/plans/remove-mut-var-assign.1.md	2026-05-18 11:06:17 +02:00
Brummel	c9355d7d58	iter prose-loop-binders.1: Form-B loop binders as parenthesised init-list ... The Term::Loop arm of write_term rendered binders as bare `name = init;` statements inside the `loop { … }` body block, which reads as C/Rust re-init-every-iteration semantics — a projection lying about a body the prose surface exists to let the reader trust. Rewrite to a parenthesised init-list on the keyword line, `loop(acc = 0, i = 1) { … }`, positionally isomorphic to the unchanged Term::Recur arm. Projection-only: loop/recur AST, Form-A, JSON-AST, typecheck, codegen, and the Form-A↔JSON round-trip invariant untouched. RED-first via two new committed examples/*.prose.txt byte-equality snapshots + two snapshot_loop_* tests; full ailang-prose suite 10/0; both ail-prose CLI byte-matches green. Single-iteration milestone, brainstorm→plan→implement. Spec: docs/specs/2026-05-18-prose-loop-binders.md Plan: docs/plans/prose-loop-binders.1.md	2026-05-18 01:04:19 +02:00
Brummel	2ee97943bd	iter loop-recur.tidy GREEN: reject lambda-captures-loop-binder at check + milestone-close audit resolution ... GREEN side of the RED audit-trail commit 39380d3. The loop/recur milestone-close audit found a [high] correctness defect — a lambda capturing a loop binder passed `ail check` then panicked unreachable!() at codegen (crates/ailang-codegen/src/lambda.rs:102) on type-correct input. Fixed symmetrically to mut.4-tidy: new CheckError::LoopBinderCapturedByLambda (code loop-binder-captured-by-lambda, bracket-free F2 Display), the Term::Lam escape guard gained a parallel loop_stack pass. Minimal mechanism: loop_stack element Vec<Type> -> Vec<(String,Type)> so the already-threaded per-loop frame carries binder names; recur still reads .1 by position (Boss-call-2 positional invariant preserved verbatim — the name is a second field for the escape guard only, a consumer iter-2 did not anticipate). Codegen byte-unchanged (typecheck-only fix). carve_out 17->18 + ct1-F2 + DESIGN.md note lockstep. Folded in (Boss-side, audit resolution): the two [medium] doc-honesty edits the audit surfaced (mut_var_allocas rustdoc now states its mut-var+loop-binder dual use; Term::Loop doc-comment now describes the real shipped state, not iter-1's stale "per-binder phi" forward-look) + a [low] P2 roadmap todo (plan-recon undercount countermeasure, pairs with planner Step-5 items 7+8). Bench gate: all 3 scripts exit 0, 25 metrics 0 regressed — pristine, carry-on (no baseline/ratify). cargo test --workspace 619 -> 622 / 0 red (Boss-reran independently, hash_pin 11/0). The loop/recur milestone is audit-clean; fieldtest is the only remaining step before close.	2026-05-18 00:21:06 +02:00
Brummel	edd2558d35	iter loop-recur.3: codegen — real LLVM-IR lowering + run-to-value E2E (milestone terminal) ... Third and terminal iteration of the standalone loop/recur milestone (plan eae73bf). Replaces the iter-1 lower_term CodegenError::Internal stub for Term::Loop/Term::Recur with real LLVM-IR lowering: loop binders as entry-block allocas (mut.3 pending_entry_allocas, reusing mut_var_allocas so the existing Term::Var load path is byte-unchanged), a fresh loop-header block, recur stores + back-edge br, a loop_frames stack saved/restored at the lambda boundary. clang -O2 mem2reg promotes the allocas to phi. Four Boss design calls implemented verbatim and journalled (alloca-not-hand-phi; mut_var_allocas reuse; emergent loop-exit via the if/match join; single block_terminated field + parallel SET site). Diff confirmed surgical: codegen/lib.rs 3 hunks (field + init + stub->2-arms), lambda.rs 2 hunks (save+restore); zero edits to any existing block_terminated SET/READ site, tail-app lowering, or verify_tail_positions (Boss call 4, the spec-pinned invariant). Three new .ail fixtures: sum_to->55, deep-n 1e6->500000500000 (clause-2 correctness made executable), infinite-loop build-only. Codegen-only: no schema/typecheck change; hash pins + drift trio stay green untouched. One DONE_WITH_CONCERNS (T3): the plan's `cargo test ... tail` filter resolved to no tests; ran via real names + the full 619/0 which subsumes it (feedback_plan_pseudo_vs_reality class, no behaviour change). Boss systemic fix folded in: planner SKILL.md Step-5 gains item 8 (verification-command filter strings must resolve) — the second planner-meta-gap this milestone surfaced. cargo test --workspace 616 -> 619 / 0 red (Boss-reran independently); the 3 loop/recur e2e explicitly green. All three components shipped: the loop/recur milestone is structurally complete. Milestone-close audit + fieldtest is the next step.	2026-05-17 23:57:46 +02:00
Brummel	1566ce0b29	iter loop-recur.2: typecheck semantics — binder typing, recur checks, verify_loop_body ... Second of three iterations of the standalone loop/recur milestone (plan 5ac57fe). Replaces the iter-1 synth CheckError::Internal stub for Term::Loop/Term::Recur with real binder typing + positional recur arity/type checking via a new loop_stack: &mut Vec<Vec<Type>> frame threaded as mut.2's mut_scope_stack, a new private verify_loop_body tail-position pass (sibling of the byte-frozen verify_tail_positions — 0 deletions there), and the four Recur* diagnostics firing point-exactly on four negative fixtures. The iter-1 loop_sum_to.ail fixture now also typechecks clean; an infinite loop typechecks (no termination claim). NO codegen (the iter-1 lower_term stub stays — iter 3); NO Diverge/guardedness (spec boundary). Three Boss design calls implemented verbatim and journalled: RecurTypeMismatch is an Assign-style structural pre-check (not a unify-propagate); loop_stack is positional Vec<Type> (binder names via ordinary locals); diagnostic-code precedence is by pass ordering (no explicit logic). Two DONE_WITH_CONCERNS, both journalled: a plan-ordering defect (Task 2's compile gate forced the check_fn threading the plan deferred to Task 4 — resolved byte-identically, only resequenced) and the recurring mut.2-class recon-undercount of cross-module synth callers (resolved via the plan's compile-sweep oracle). Boss systemic fix folded in: planner SKILL.md Step-5 gains item 7 (compile-gate vs. deferred-caller ordering) so the plan-ordering defect class is scrubbed at plan time. cargo test --workspace 608 -> 616 / 0 red (Boss-reran independently).	2026-05-17 23:33:43 +02:00
Brummel	a179ec30a0	iter loop-recur.1: additive Term::Loop / Term::Recur / LoopBinder foundation ... First of three iterations of the standalone loop/recur milestone (spec 97c1ed1). loop/recur become real parseable / printable / round-trippable / hash-stable strictly-additive AST nodes across every no-wildcard exhaustive Term match in all six crates, plus parse/print, prose arms, DESIGN.md + form_a.md schema blocks, drift/coverage/hash anchors, and the spec's worked sum_to program as a green round-trip fixture. NO typecheck semantics and NO real codegen this iter by design: synth and lower_term are stubbed CheckError::Internal / CodegenError::Internal exactly as mut.1 (real typecheck = iter 2, real loop-header/phi/back-edge = iter 3). Two binding Boss design calls recorded in the plan header and the journal: (1) verify_tail_positions "byte-unchanged" = its tail-app verification role is unchanged, not its source — it is an exhaustive no-wildcard match so two descent-only arms are mandatory; acceptance evidence is the tail-app non-regression test. (2) codegen is in iter-1 scope as stubs/pass-throughs because the workspace must compile for cargo test --workspace. Three plan-pseudo-vs-reality substitutions (serde Type::Con literal, bare Int -> (con Int), unqualified LoopBinder) and one recon-undercount integration-test site, all intent-preserving and journalled. Boss forward-fix folded in: the committed specs themselves wrote bare Int in the loop-binder snippets (parses as Type::Var) — corrected the three headline snippets to (con Int) for doc-honesty (no design/schema change). cargo test --workspace 600 -> 608 / 0 red (Boss-reran independently); iter13a + new loop_recur hash pins green.	2026-05-17 23:00:15 +02:00
Brummel	a29700cc9e	iter effect-doc-honesty: make the effect-system documentation true ... Standalone documentation-honesty tidy (no language/checker/codegen change; `ail check`/`run` byte-unchanged by construction). Corrects three false effect-system claims the effect-subsystem recon surfaced, plus two satellite mentions, guarded by a new doc-presence pin: - DESIGN.md Decision 3: removed the "row-polymorphic (`![IO | r]`)" claim (no EffectRow / row variable exists in any crate — effect sets are a flat, unordered, closed set unified by set-equality); reconciled "`IO` and `Diverge` are wired up" to IO-only + `Diverge` reserved/unimplemented (zero code in any crate), modelled on Decision 4's reserved-refinements precedent. - DESIGN.md "What is not (yet) supported": "IO and Diverge ops" bullet -> IO-only + Diverge-reserved. - ast.rs Term::Do doc-comment: "resolved against the effect-handler table at link time" -> the real mechanism (typecheck lookup in Env::effect_ops + literal lower_effect_op codegen match; no handler table, no link-time resolution). - form_a.md:226 + rule 3, and main.rs merge-prose CONTRACT example: Diverge mentions reconciled in lockstep. - new crates/ailang-core/tests/effect_doc_honesty_pin.rs: 4 tests, fiction-absent + corrected-anchor-present, single-line wrap-robust substrings. cargo test --workspace 600 -> 604 (4 new pin tests, 0 regressions); design_schema_drift / spec_drift / schema_coverage stay green, empirically confirming none scans the effect-prose region.	2026-05-16 13:25:49 +02:00
Brummel	37ac704bf3	iter revert: back out the Iteration-discipline milestone (it.1 + it.2) ... One forward iteration; main never rewound. 1ff7e81 (the pre-9973546 commit) is the per-region byte oracle — every reverted source/test file is byte-identical to it; crates/ailang-check/src/lib.rs fully so. Root cause being corrected: the Iteration-discipline milestone was an over-escalation of fieldtest finding F1 (a [friction] item whose own minimal recommendation was a DESIGN.md note). Its totality dichotomy made the maximally-LLM-natural build(d:Int)=Node(1,build(d-1), build(d-1)) inexpressible (it.3 BLOCKED); the only in-thesis escape (A1/it.2b) conceded the language's first documented-unenforced totality precondition — a purity-pillar dilution the user rejected in favour of a full revert + rebuild. Removed: Term::Loop/Term::Recur/LoopBinder; the verify_structural_ recursion guardedness pass + term_contains_loop + Diverge-injection + the transitively-it.2 module_fns plumbing; the five Recur*/ NonStructuralRecursion CheckError variants (+ code() + the 3 dedicated ctx() arms); the it.1 codegen loop-header/phi/back-edge + parallel block_terminated setter; all Loop/Recur walker arms; 16 it.1/it.2 fixtures; 2 pin files; bench/it3-oracle/. Restored: 2 RC fixtures to 1ff7e81 content. Surgically kept (not in 1ff7e81, landed with the milestone but independently sound): feature-acceptance clause 3 in DESIGN.md and skills/brainstorm/SKILL.md, with its worked example de-claimed from "shipped" to hypothetical-illustration form; the F3 P2 todo. bench/orchestrator-stats/2026-05-15-iter-it.{1,2,3}.json kept as historical record (like journals/plans). Sole net addition: an honest F1/F4 documented-idiom note in DESIGN.md (the tail-recursive accumulator fallback; examples/mut_counter.ail), guarded by a doc-presence test — "a documentation note is not a reshape", asserts nothing at the typecheck level. Roadmap: the Iteration-discipline block + blocking-fork section removed; the genuine total-Int-recursion ambition preserved as a deferred P2 milestone sequenced behind a future Nat/refinement-types milestone (not abandoned — correctly sequenced after the type machinery it needs). 2026-05-15-iteration-discipline.md carries a superseded header; it.1/it.2/it.3 journals + plans stay as history. Correctness gate PRISTINE: 164 surviving 1ff7e81-era fixtures ail check/ail run byte-identical to pre-milestone behaviour (verified against a 1ff7e81 worktree reference compiler, zero drift); cargo test --workspace 600/0; zero residual it.1/it.2 production surface. Spec docs/specs/2026-05-16-iteration-discipline-revert.md (b3853bf), plan docs/plans/2026-05-16-iter-revert.md (abf0013).	2026-05-16 01:28:47 +02:00
Brummel	305ffd1367	iter it.3 BLOCKED: surfaced fundamental milestone-design fork (bounce-back) ... it.3 Task 1 (non-destructive oracle + spec-delegated class-(b) sweep) ran complete; zero production code changed. The mandated sweep surfaced that 6 corpus fixtures contain build(d:Int)=if d==0 then Leaf else Node(1,build(d-1),build(d-1)) — a terminating, maximally-LLM-natural, non-structural non-tail BRANCHING recursion the milestone's totality dichotomy makes inexpressible (not ADT-structural; not recur-able — branching is not a single tail back-edge). The milestone as-specified would fail its own feature-acceptance criterion. Orchestrator correctly bounced rather than patch a 4th time (spec_over_plan_patches). Records the blocked attempt + the reusable bench/it3-oracle/ (40-fixture behavioural oracle, valid for the post-decision re-dispatch). main forward-only; nothing reverted. Resolution (it.2b + a user purity-pillar decision) tracked in the roadmap.	2026-05-15 16:06:42 +02:00
Brummel	a4be1e58a3	iter it.2: structural-guardedness checker + first real Diverge effect ... Iteration-discipline milestone, 2 of 3. Strictly additive (nothing tail-related removed; that is it.3). New whole-body pass verify_structural_recursion sibling of verify_tail_positions (DD-1): smaller-set algorithm with implicit candidate inference + unconstrained accumulators (DD-2, foldl=structural), self/mutual via inline ADT-family union-find (DD-3), it.2-only tail==false grandfather. CheckError::NonStructuralRecursion. term_contains_loop (stops at Term::Lam, DD-4) injects Diverge so existing UndeclaredEffect enforces it, no new variant; lam-arrow + LetRec sub-effect sites wired. DESIGN.md Decision 3 synced. Four it.1 loop fixtures gained !Diverge. Two spec-premise boundary defects surfaced + resolved within the additive invariant (corpus clean, check not weakened), recorded as corrected it.3 corpus-migration scope: (1) the "21 tail-app fixtures" grandfather premise under-counts the corpus — no-ADT-candidate counter recursions have no structural position to verify, deferred to it.3; (2) two RC-regression fixtures joined the spec's transitional tail-app grandfather as the other 20 do (RC==GC guards verified still green). cargo test --workspace 622/0; 9 acceptance pins non-vacuous. Spec fda9b78, plan bc9f512.	2026-05-15 15:29:43 +02:00