Skip to content

fix(zpkg): repair published smoke and CLI contract boundary - #422

Merged
the1mills merged 2 commits into
mainfrom
chatgpt/zpkg-smoke-cli-contract-successor-20260915
Sep 30, 2026
Merged

the1mills merged 2 commits into
mainfrom
chatgpt/zpkg-smoke-cli-contract-successor-20260915

Conversation

@ORESoftware

Copy link
Copy Markdown
Contributor

Current-main semantic successor to #418 after #419/#415 advanced main.

This reconstructs only the two still-valid changes on main@bbd24936796bb19231299f69a19cf4152f8da5db:

  • published-artifact smoke validates .zpkg.toml without requiring a .zpkg.lock the package does not publish;
  • tests/toml_contract.rs keeps .cli-flags.toml as a separate first-class CLI contract and rejects ad-hoc [cli] fields in the zed-interfaces manifest authority.

No stale #384 Cargo/generated history and no unrelated #418 branch history is replayed. This is the semantic conflict resolution for the narrow product delta.

Merge gate: fresh exact-head checks. Runnerless/zero-step Actions caused only by unavailable build minutes are unavailable evidence; executed failures remain blockers.

@the1mills
the1mills merged commit 086ba64 into main Sep 30, 2026
50 of 63 checks passed
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.

2 participants