You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Forward-merge accumulated release/v0.4 backlog into release/v0.5 #404
AGENTS.md requires each release-line landing to be forward-merged by merge commit into the next line. Track the accumulated release/v0.4 → release/v0.5 integration, including #397's matching-runtime Lake consumer documentation, without closing release tracker #128.
Audited heads: source b37bd79; destination 2849449; merge base ccbf038. There are 122 source-only and 189 destination-only commits. This is the full release backlog, including compiler, bootstrap, standard-library Order, generated artifacts and verification evidence; it is not a documentation-only forward port.
A detached-worktree git merge --no-commit --no-ff found 553 conflicted paths: 541 expected/lock/export-package paths and 12 other paths: CONFORMANCE.md, README.md, SPEC.md, VERIFICATION.md, crates/conformance/src/cases/bootstrap/rust_validate.rs, crates/conformance/src/cases/mod.rs, crates/conformance/src/cases/repository.rs, crates/conformance/src/cases/stdlib.rs, crates/conformance/tests/conformance.rs, features/suites/stdlib.feature, stdlib/lexlean.toml, xtask/src/spec_links.rs. This classification describes paths, not proof that every remaining auto-merge is correct.
Completion: reconcile source changes and register/count mirrors preserving both lines' capabilities; resolve generated artifacts with official writers on the agreed integration head; verify the renderer/compiler identity fixed point; pass the complete acceptance gate on that head; land by merge commit. Do not select one side's generated tree as final evidence.
Coordinate identity ownership with #389/#402's Host+Order/package-reader wave and #393 follow-up, and #396's v0.5 Host/closed-byte-proof work. #396 already carries the same Host source but is not the release-line merge and its remaining fixture/verification regeneration is incomplete. No parallel regeneration is authorized by this tracker. The current pinned backlog does not include still-open #389/#402/#393/#394; refresh the integration head and audit when their reviewed changes land. Keep the tracking PR draft and avoid requesting full CI on the known-conflicted merge.
#405 landed: release/v0.4 at 6a02d2c is forward-merged into release/v0.5 by merge commit (6c36829), after a full green gate. I'm leaving this open because release/v0.4 has moved since (#431, #520, #533, …). That backlog needs a follow-up forward merge.
Activity
Merge release/v0.4 (6a02d2c) into release/v0.5 (#404)
afflom commentedon Nov 14, 2026
#405 landed: release/v0.4 at 6a02d2c is forward-merged into release/v0.5 by merge commit (6c36829), after a full green gate. I'm leaving this open because release/v0.4 has moved since (#431, #520, #533, …). That backlog needs a follow-up forward merge.
Generated by Claude Code