Skip to content

Forward-merge release/v0.4 (0a9891ea) into release/v0.5 - #541

Open
afflom wants to merge 29 commits into
release/v0.5from
forward/v04-to-v05-0a9891ea
Open

afflom wants to merge 29 commits into
release/v0.5from
forward/v04-to-v05-0a9891ea

Conversation

@afflom

@afflom afflom commented Nov 14, 2026

Copy link
Copy Markdown
Member

This forward-merges release/v0.4 into release/v0.5. AGENTS.md says forward merges land as a merge commit, so please merge this with Create a merge commit, not squash or rebase.

What the merge reconciles

  • Spec text: v0.4 has no spec/ directory, so its §9.4, §22.11 and VR-23 text is written into the modules of spec/src (Chapter09, Chapter22, IdsVR). The changed register statements were carried into their rows (NS-03). The generated projections (SPEC.md, model/ids.toml and the rest) are rebuilt by the official writers through regenerate/ on this head, not edited by hand.
  • verify: every part names its toolchain by address (UOR-native, piece 1) #498 without sha2: verify: every part names its toolchain by address (UOR-native, piece 1) #498's build script hashes the address of the rustc that built the crate. On this line it uses the certified Sha256 package, compiled by that rustc into a hasher in OUT_DIR. The shipped crate still declares no sha2 dependency (SL-05, R6).
  • New xtask option: cargo xtask spec port --merged <SPEC.md> --register <ids.toml> first carries the changed statements of a merged register into their rows of spec/src, then ports SPEC.md. It refuses a register that adds or removes IDs, because those rows are written by hand. This is the primitive the forward-merge automation will call.

Verification

Run locally before pushing:

  • cargo clippy --workspace --all-targets -D warnings passes.
  • cargo fmt --check is clean.
  • The xtask counts unit tests pass.
  • These conformance tests pass: SL-05, RP-14, RP-10, RP-06, RP-07.

Disk on the build host is tight, so the full suite is left to CI on this head.


Generated by Claude Code

afflom and others added 29 commits November 3, 2026 08:19
Assemble the same ordered evaluator and native corpora directly. Keep the
existing full accepted-package recipe assertions, bounded native inputs,
all plants, counts and exported-package checks. Add an old/new assembly
regression without changing compiler semantics or gate orchestration.

Refs #457
Retain accepted release/v0.4 source, products, corpus counts and gate plans
from c66f83d. Preserve the reviewed BS-15 assembler and regression. Keep the
accepted BS-21 verification history and distinguish historical/current
work-count deductions. Prior-tree qualification is historical evidence;
this combined candidate requires its own complete current-graph gate.

Refs #457
…al declarations)

One closed declaration that binds a foreign function to a stated contract: an opaque constant whose hidden value is a LexLean witness, and one generated contract axiom that every dependent theorem carries in its exact observed set and verify reports with its evidence. Options, a Lean 4.32.1 prototype with its output, an assessment of an Aeneas bridge, and the decisions left to the owners. Proposal only: nothing is implemented.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A shard writes toolchain.json (lexlean/verify-toolchain/1) beside its
output: the SHA-256 of the lean, lake and leanchecker its preflight
hashed, of the running lexlean, and the address of the rustc that
compiled it (its executable and rustc_driver library, hashed by the
build script). A part that reads another refuses it (LLI9001, naming the
part, the tool and both addresses) unless all five equal its own. A
process record names only lean or leanchecker, so a part that ran
another lake, lexlean or rustc was accepted before.

VR-23 plants another lake address in a shard's output and, on unix, runs
a join whose own lake differs from the pinned one by one byte; both are
refused. Published directories, attestations and expected/verify do not
change, and neither does the compiler-semantics ID.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The custody record becomes lexlean/ci-bootstrap-export/2. Beside what
`rustc -vV` and `lean --version` report, it names the SHA-256 of the
pinned toolchain's lake, lean and leanchecker and the address of the
rustc that compiled the exporting binary (SPEC.md §22.11). A leg whose
own executables differ refuses the export. A version banner is the same
for a rebuilt or patched binary; the bytes are not. RP-14 plants another
leanchecker and another rustc.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Json::parse refused {"a":1,"a":2} but accepted {"a":1,"a":2} and
returned {"a":2}, because check_duplicate_keys compared raw escaped key
bytes. Decode each key before inserting it into the per-object set, add
AR-11 assertions, and a CHANGELOG entry. Fixes #475.

Recreated from #473 (conflicted with release/v0.4; fork gets no CI).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Separate proof-axiom dependencies from executable external uses (call
inventory), complete the report-to-implementation binding, narrow the
opacity statement.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…, record D1

One reviewed documentation carrier, as requested on #492. D1 (SPEC.md
9.4 reuse of verification results) is decided: not adopted now.

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

test(bootstrap): avoid discarded BS-15 full-library runs
verify: every part names its toolchain by address (UOR-native, piece 1)
…ntracts

docs: proposals for external contracts and for reused verification results
The repository is now UOR-Foundation/lexlean. intel_host_tests.py compared
GITHUB_REPOSITORY with "UOR-Foundation/LexLean" exactly, so every Intel
test construction job refused its own run as a foreign repository. GitHub
names repositories case-insensitively; the check now does too, and any
other repository is still refused (a unit test covers both spellings and
two foreign names). The workflow if: guards already compare without case.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Running the helper scripts' unit tests left __pycache__/*.pyc beside them,
and the previous commit carried them. They are removed, and .gitignore
names Python bytecode so it cannot be committed again.

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

fix(canonical-json): compare duplicate keys after escape decoding
ci: Intel host tests accept the renamed repository spelling
…depth

fix(snapshot): preserve deep structured values during canonical serialization
Forward merge of release/v0.4 from 6a02d2c to 0a9891e: #431, #459,
#492, #498, #520 and #533. The §9.4, §22.11 and VR-23 text of v0.4 is
written into the modules of spec/ (NS-03); the projections are left to
the official writers (regenerate/).

#498's build-script address of the rustc that built the crate is hashed
with the certified Sha256 package, compiled by that rustc into a hasher
in OUT_DIR, so the shipped crate still declares no sha2 (SL-05, R6).

`cargo xtask spec port --register <ids.toml>` carries a merged
register's changed statements into their rows of spec/src before the
SPEC.md port, refusing added or removed IDs, for forward merges from a
line without spec/.

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

afflom commented Nov 14, 2026

Copy link
Copy Markdown
Member Author

Coordination hold: this forward merge explicitly carries #431. The standing maintenance instruction still keeps #431 and old TC-03 stopped, including no retry, rephrase or circumvention; its external v0.4 landing did not lift that restriction (hold6874415009). Please keep this forward adoption unaccepted until that conflict is explicitly resolved. No runtime/snapshot source review, test, retry or revert is requested here, and existing release history must be preserved.

Claude retains the forward-integration implementation. #405's actual6c368 landing and its final attempt are being checked separately; they do not automatically admit this new tree or root-reserved #316. Regeneration43644952249 is already active—do not launch a competing writer. Retain its exact scope/results and all existing frozen evidence; draft/readiness or a launched process is not final acceptance.

This branch has not been deployed

No deployments
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