[avrabe]

Summary

• meld 0.62.0's composite fails synth's VCR-VER-003 static-data validation; 0.59.0's does not (2x2 isolates meld) #479 (fix(#479): --pack-rebase leaves a 7-byte guard after each provider's data #506): --pack-rebase leaves a 7-byte guard after each provider's data. gale's composite then passes synth 0.78.0 and 0.85.0, where meld 0.63.0's correct composite was refused by VCR-VER-003.
• Element segments are not re-indexed after adapter wiring: a table entry for an adapted import bypasses the adapter #488 (fix(#488): element-segment items are re-resolved from the final function map #503): a function table entry for an adapted import no longer bypasses the adapter. Element items are resolved from the final function map.
• Fusing a wac-composed component in shared-memory mode: blocked by #461, plus internal and shim exports in the output #463 (feat(#463): --exports world limits the fused module's exports to the outer world #498): --exports world (opt-in) limits the fused module's exports to the outer world of its inputs, plus what the world and the remaining imports need.
• Tooling (Python tools: read rivet artifacts through rivet instead of PyYAML #500, chore(ci): release-readiness on rivet 0.40.0; hold compliance at 0.22.0 #502):
  • Python tools read rivet through its JSON output.
  • The release-readiness gate runs on rivet 0.40.0.
  • The compliance report stays on 0.22.0 until cited-source rejects a list of citations: an artifact that cites two sources cannot validate under 0.40 rivet#1106.

Release scope (rivet)

rivet release status v0.64.0 (rivet 0.40.0): 6 artifacts, all verified, cuttable.

Requirement	Verification	Issue
SR-100	SWV-112	#463
SR-101	SWV-113	#488
SR-102	SWV-114	#479

Test plan

• cargo fmt --all -- --check: exit 0
• cargo clippy --workspace --all-targets -- -D warnings: exit 0, with and without --all-features
• cargo test --workspace: exit 0, 993 passed, 0 failed
• cargo test --workspace --all-features: exit 0, 992 passed, 0 failed
• Built binary reports meld 0.64.0

After merge

1. Tag once the merged tree has passed every required check.
2. Create the release as a draft; the pipeline fills in the assets.
3. Verify the checksums and the cosign signature, each with a negative control.
4. Smoke-test the shipped binary on gale's composite with synth 0.78.0 and 0.85.0.
5. Publish, then confirm the assets gate.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WrmMqf1iuTS1UBEes5TmdC

[github-actions]

LS-N verification gate

✅ 59/59 approved LS entries verified

	count
Passed (≥1 test, all green)	59
Failed (≥1 test failure)	0
Missing (no ls_*_NN_* test found)	0

_{Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11 →
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.}

Failed LS entries

(none)

Missing regression tests

(none)

_{Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.}