[ORESoftware]

Superseded by #418.

The useful delta was rebuilt semantically on current main rather than replaying this stale branch ancestry. #418 retains only:

• the published-artifact smoke correction that validates .zpkg.toml without requiring an unpublished .zpkg.lock;
• the .zpkg.toml / .cli-flags.toml authority-boundary regression.

This stale branch is closed to avoid reintroducing superseded source/generated state.

[ORESoftware]

Semantic blocker: this branch makes the locked build green by downgrading the resolver-owned zed-lock entry from the later sharing-violation candidate 1a95bb87272ac7b08895cea1f61743cf40321213 back to 1db0da00d30fcf2e0762f50eedb1f88458020b52 and removes zed-lock's libc dependency. That discards the later ERROR_SHARING_VIOLATION normalization previously reviewed in #303. Current main's real regression is the opposite half of this mismatch: Cargo.lock retained 1a95bb87…, while Cargo.toml and several provenance assertions regressed to 1db0da00… during the Sep-12 fleet merge. Please preserve 1a95bb87… in Cargo.lock and repair Cargo.toml / graph / lock-source assertions forward to that revision instead. The rustfmt-only tests/toml_contract.rs changes are independently salvageable.

[ORESoftware]

Continuation-batch sequencing note: keep this locked-build repair as a prerequisite for broader zed-cli feature promotion. The canonical boundary should remain .zpkg.toml for package metadata and .cli-flags.toml for flags; do not reintroduce root [cli] metadata to make tests pass. Once exact-head locked builds are green, use that admitted base for #388 outage recovery and #399 packed local-lock consumer certification.