Skip to content

Carry v0.4.3 to main - #556

Merged
afflom merged 633 commits into
mainfrom
main-v0.4.3
Nov 16, 2026
Merged

afflom merged 633 commits into
mainfrom
main-v0.4.3

Conversation

@afflom

@afflom afflom commented Nov 15, 2026

Copy link
Copy Markdown
Member

Brings main to the v0.4.3 tag, fa27108, from release/v0.4. The head branch is pinned at the tag so later landings on the line don't reach main.

tag.yml could not open this PR itself, because the repo setting does not allow Actions to create pull requests. Evidence: ci 43744252595 passed on fa27108, and tag run 43744252639 succeeded.


Generated by Claude Code

humuhumu33 and others added 30 commits November 9, 2026 13:26
`parseGeneric` lexes with lexText and reads the tokens with an explicit stack of
frames, so it admits no recursion; the object's members are sorted when it
closes. `printGeneric` builds the document by the structural recursion the
standard library's writer uses and lays it out with renderDoc. The module is an
entrypoint and the roots are exported; the lock is this tree's, and the
regeneration replaces it.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
`SOURCE` was never used, and the lint of the first draft refused it as dead
code. It was the only error of that step, so the case compiles.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…o BS-24

BS-24 stacks on BS-23. The conflicts keep that tree with this member's own
edits applied over it: the SurfaceGeneric entrypoint and module, the register
at 482 IDs (SPEC.md, the README, the RP-07 check and its case), the
README's bootstrap row through BS-24, and the CHANGELOG entry. The lock
and CONFORMANCE.md are the tree's and are rewritten next.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… the merge

The bootstrap lock follows the SurfaceGeneric entrypoint, CONFORMANCE.md is
written from the model with the BS-24 row, and the three places that named
the standard library's Json reader `SL-12` name it `SL-13`, as #415 renamed
it (`SL-12` stays Host's reservation).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…'s vector

The first run of conformance_bs_24 (259 s, on BS-23, BS-22, BS-21 and SL-13):
the evaluator agrees with the oracle on 1,080 reads and 607 prints, and 31 of
the 32 plants were detected. Two faults. The printer's rank table spelt the
key `axioms` as `axoims` (0x61786f696d73), so a seeded object printed it
after an unranked key where the oracle prints it before; the literal is now
0x6178696f6d73. The plant `a tag need not be a name` named `a b`, two bare
words that never reach the test of bareness; it now names `a word of digits
and a letter` (`1a`), which the oracle refuses and the planted reader admits.
All 32 are detected, and the case stops at the stack-bound step until the
regeneration commits bootstrap/parse_generic. VERIFICATION.md says so in
place of "the case has not run".

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
SL-13: reading canonical JSON in the standard library (#276)
The one conflict is the CHANGELOG, where both entries stay, the
writer's first as the later landing.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The merge is clean, but both sides added one register row over 477, so
the count moves to 479 in SPEC.md, the README, the RP-07 check and its
case, and the RB-24 entry of the CHANGELOG, now the newest, states it.
The locks of the standard library, the bootstrap and compiler projects
and the two std models are rewritten: they follow the standard library's
new member and the compiler-semantics ID this member moves. CONFORMANCE.md
is written from the model.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…cs ID

`lexlean lock` on this tree writes the moved `compiler_semantics` digest
into each example's lock; nothing else in them changes.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
`cargo xtask check-production-export --write` at verify width 1 on BS-21
merged with SL-13 (release/v0.4 at 4dc5b80): the bootstrap export gains
the `parse_grammar` packages of the structural grammar and every package
records the standard library's new digest; the lock follows.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
`cargo xtask check-golden --write` on the regenerated export.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
`LEXLEAN_EXAMPLES_PART=without:uor-atlas cargo xtask verify-examples
--write` at width 1: 482 normalized records for bootstrap (attestation
e7c027e2422e88511a077ff190af086ce79c7bbfcf7c38a90a04a02aed2d322e); the
UOR Atlas example is skipped on this host, as before.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Written from the model at the regeneration; the merge had taken the
tree's copy, which predates the row.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…d BS-13 to BS-15

The committed export gains one package, so the committed manifests, packages,
programs and crates each grow by one and the corpora the cases draw from them
follow: 18 constants in seven cases, their §31 rows, register statements and
scenarios, and the §17.23 prose that repeats them. Measured under
LEXLEAN_COUNTS=fast with the count writer of #442 applied and then removed
again; the writer placed every number. BS-11, BS-12 and every mutant draw are
unchanged. VERIFICATION.md carries the landing's table.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The merge kept the standard-library row from before #415 claimed its
row; RP-11 reads the row from release/v0.4 again.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ing module

The fifth slice of the front end as source (#269), on BS-24: the row
(register 482 -> 483, the §31 table, the RP-07 check and its case), the
scenario, the §17.23 prose, the CHANGELOG entry, the README's claim, the CI
part, and the case, conformance_bs_27, which holds
SurfaceTooling.printToolingModule, parseToolingModule, and declarationSpans
to surface::tooling::{print_module, parse_module, declaration_spans} on
hand-built vectors that reach every error and the limit on nesting at both
depths, on the committed JSON files printed as modules and read and spanned
back, on the committed tooling modules, and on seeded edits, with 20
planted defects each named by its vector. VERIFICATION.md records the
first run: the evaluator agrees on 654 prints, 218 reads, and 229 spans,
rustc on 5,098 runs, and every plant is detected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bootstrap/src/SurfaceTooling.lex.tex over SurfaceGeneric: printToolingModule
removes the spec and prints with printGeneric; parseToolingModule reads one
object with parseGeneric and adds the implied spec in order of key;
declarationSpans walks the members with a state machine over the tokens,
reading a member with readFrom at depth 1 and an element of declarations at
depth 2. Lean verifies the module and each root is eligible with exactly its
declared effects, the printer's including recursion. The entrypoint, the
lock, the three export roots, and the project README follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The one conflict is the README's bootstrap row, where this member's row,
which claims BS-21 and the range through BS-21, is kept; the standard
library row is the line's, as BS-21 already had it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preserve actual281 contributor/history and actual4dc release ancestry.
Reconcile only demonstrated golden source/build envelopes and retain
reviewed export/verification products with additive scoped evidence.
Integrate the reviewed Atlas prerequisite scheduling from #444 and the
BS-07 host-preparation hoist from #448 into one release/v0.4 candidate.
Preserve complete host coverage, exact evidence custody, and failure
aggregation without increasing the host timeout.
Preserve the exact #394 source and generated products together with #450's
Atlas scheduling, BS-07 host preparation and Intel construction changes.
Retain both contributor histories and historical verification scopes.

No producer regeneration is needed: the only shared path is the additive
VERIFICATION record, and the CI changes do not alter compiler or project
identity inputs. Complete combined-head hosted acceptance remains required.
… of print_generic

`cargo xtask check-production-export --write` at verify width 1 (2,893 s) on
BS-24 over BS-23, BS-22, BS-21, and SL-13: the bootstrap export gains the
parse_generic and print_generic packages, every package records the merged
tree's digests, and the lock follows. conformance_bs_24 then passed whole
with LEXLEAN_MEASURE_STACK=all (1,894 s), which measured the row of
bootstrap/print_generic in tests/stack-bounds.json (PD-08).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`cargo xtask check-golden --write` on the regenerated export.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`LEXLEAN_EXAMPLES_PART=without:uor-atlas cargo xtask verify-examples
--write` at width 1 (8,074 s); the UOR Atlas example is skipped on this host,
as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…S-13 to BS-15

The committed export gains six packages (those of BS-21 to BS-24 on this
tree), so the committed manifests, packages, programs and crates each grow by
six and the corpora the cases draw from them follow: 20 constants in seven
cases, their §31 rows, register statements and scenarios, and the §17.23
prose that repeats them. Measured under LEXLEAN_COUNTS=fast with the count
writer of #442 applied and removed again; the writer placed every number.
BS-11, BS-12 and every mutant draw are unchanged. VERIFICATION.md carries
the landing's table.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…scans

BS-02: the lexer's scans run only in the branch that reads them (#373)
BS-22, BS-23, and BS-24 were regenerated together on a tree that holds
BS-21's source byte for byte, so this tree's export, build oracles, verify
records, lock, stack bounds and counts are a superset of BS-21's and are
kept; the rows, statements, scenarios and §17.23 prose carry the counts of
the six front-end packages. VERIFICATION.md keeps BS-21's count section, and
the section of BS-22 to BS-24 counts from BS-21's tree (300 -> 305). The
records of BS-21 to BS-24 now say each case passed whole on its regenerated
tree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude and others added 20 commits November 14, 2026 20:18
The register is 497 IDs (496 on the line + CL-25): §31's total, RP-07's
two checks and the README line follow; CONFORMANCE.md and ERRORS.md are
rewritten by validate-model --write. Cargo.toml and build.rs keep both
the WASI target dependencies and stack link argument and the line's
rustc-address build dependency and production-data feature.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…§9.4)

Intel macOS runs on the release line, not on each pull request (§8.3, §9.4)
Brings in #535 (Intel macOS on the line). The only conflict was the
Unreleased CHANGELOG list; both entries are kept, the Lean 4.32.2 pin
first. No file #535 touches names the Lean pin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Brings in #535 (Intel macOS on the line). The only conflict was the
Unreleased CHANGELOG list; both entries are kept. #535 adds no register
IDs, so the count stays 497.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…n with no hand step (§9.4)

A cut lands, tags, publishes and reaches main with no hand step
Keep #431's Json::from_serde for the snapshot value inside this PR's
deep-stack wrapper, place from_str_unbounded ahead of the duplicate-key
check's (#520) doc comment, and keep both CHANGELOG entries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…patch

Patch the single Lean pin to 4.32.2 for kernel soundness
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
AU-01: read the corpus one module at a time (bdd-verification OOM)
A newer push cancels the pull request's older run, and the Intel and
Windows aggregates, guarded by always(), still ran and failed their
'every lane succeeded' step, so every superseded head showed a red host
context. They now run on !cancelled(): still after a failed or cancelled
lane of a run that goes on, never in a run that was itself cancelled, which
leaves no evidence. RP-14's pins and plant follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3QVAsEzzaQPMzJnNz1
Keep both MAX_COMPILE_STACK_BYTES definitions from #503 (native and
WASI) at the crate visibility this PR needs for on_stack callers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…t (§9.4)

Cut the full gate's time without weakening it (§9.4)
SM-12: a semantic module nests to max_scope_depth, not 128 levels
cargo xtask bump-version 0.4.3: the workspace version, SPEC.md §2.3, RP-01, Cargo.lock, and the changelog's unreleased entries.
The write recipes of SPEC.md §9.2, run by regenerate.yml (https://github.com/UOR-Foundation/lexlean/actions/runs/43701488279),
rewrote 29 paths.

The counts writer reported:

    counts: no count moved
Release 0.4.3. Gate: ci 43709771141 (attempt 2, all jobs, four hosts) on 670310a.

afflom commented Nov 16, 2026

Copy link
Copy Markdown
Member Author

The aarch64 Linux job failed because its runner was lost (shutdown signal partway through cargo test). This is the known aarch64 memory blowup. #554 fixes it on release/v0.4, but this PR is pinned at the v0.4.3 tag, which is before that fix. The same tree already passed in full on ci 43709771141 and 43744252595. I'll re-run the job once this run finishes.


Generated by Claude Code

@afflom afflom left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delivery/evidence disposition at fa27108: current synthetic2c64d941 has ordered parents71defb4c+fa271 and tree0af41e38, equal to headfa271. Existing push run43744252595 attempt1 is bound by run metadata to fa271 and now has all72jobs/838steps successful. This is reusable technical evidence to retain; a blanket full-gate repeat is not needed merely because the same tree is proposed for main. Actual merged-tree equality remains required after any eventual landing, and no individual job checkout audit is claimed here.

Both additional runs43773562747(workflow_dispatch) and43773711832(PR) are on fa271 and already show failed ARM Linux jobs with cargo-test cancellation; remaining jobs are active/queued. Do not aggregate them into the successful attempt or infer an OOM cause from this metadata. The existing owner should disposition the current incident and input-bound evidence before another retry, preserving all failed/successful receipts. No retry or CI-control action is requested or performed by root.

The material #431/oldTC03 STOP conflict remains unresolved: #551 (comment). The standing user instruction is 'Keep #431 and old TC-03 stopped: no retry/rephrase/circumvention.' Shared account authorship, the external v0.4.3 tag, and technical gate success do not lift it. Existing release owner must resolve that instruction conflict before this lane can certify the carry to main. No stopped-work adoption, merge, rollback or tag deletion here.

Receipt /workspace/work/pr556-fa271-forward-stop-review-20261116.json; SHA25634c8e64e1a005ef2ea163606b60f6a6c132ce0c8a208a10179eea6420e3edad4. Annotated tagv0.4.3 resolves tofa271; no GitHub release publication observed.

@afflom
afflom merged commit a74b1f9 into main Nov 16, 2026
301 of 305 checks passed
@afflom
afflom deleted the main-v0.4.3 branch November 16, 2026 04:09

@afflom afflom left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New actual-main observation, separate from prior successful exact-tree evidence: ARM job 133092924431 in run 43802480909 attempt 1 logged a runner shutdown signal at 05:04:07Z and cancellation at 05:04:08Z. Earlier test groups completed, but the conformance suite was unfinished. The log establishes interruption, not its underlying cause; it does not establish OOM or a code assertion failure.

Actual main a74b1f9 still has the previously recorded fa271 tree. Preserve the failed job alongside the already completed 72-job/838-step exact-tree gate; do not aggregate them or repeat completed producer work. Actual repro has passed. The existing owner retains incident disposition. No retry, source repair or CI control is requested here, and #431/old TC-03 STOP remains unchanged.

New log retained once: /workspace/work/main-a74b-arm-job133092924431-20261116.log, SHA256 1c34f6bca231e9bc05d05a5825e11be707bb9e3469b878decaa338aca6e12abf. Receipt: /workspace/work/main-a74b-arm-incident-20261116.json.

This branch was successfully deployed

1 active deployment
crates.io — fa271080 Deployed Nov 16, 2026 by github-actions[bot] via publish the release #28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants