ci: provable-chain pre-publish gate in release.yml - #326
Merged
Conversation
added 2 commits
July 30, 2026 14:31
Wires a cross-package regression gate into the release pipeline so a broken provable chain fails BEFORE publish, not after. - examples/integration-smoke/provable-chain.mjs: self-contained end-to-end smoke over the freshly-built workspace (no LLM, no network). A task output is verified by @wasmagent/compliance (backed by @wasmagent/core VerificationPipeline+DeterministicVerifier), the verdict becomes signed AEP evidence via @wasmagent/aep, and the signature is verified; includes a tamper-evidence check. Adds @wasmagent/aep + @wasmagent/compliance as workspace:* deps of the smoke package so bare imports resolve to local builds. - run-all.mjs: register provable-chain.mjs in ORDER (cheap, no-IO — runs early). - release.yml: run the gate after Build and before npm auth/publish. A break (a verified task can no longer become signed, verifiable evidence) fails the release. Verified on VPS: CI-equivalent (frozen install + build + gate from repo root) exits 0 on a healthy chain; an injected signature break exits 1. The trust-passport link is intentionally excluded (external dep, not a workspace package, so a wasmagent-js pre-publish gate cannot guard it). Complements the after-publish canary in agent-golden-path. No changeset needed (examples/ + CI only, no publishable package source).
telleroutlook
force-pushed
the
ci/provable-chain-gate
branch
from
July 30, 2026 06:32
b212c97 to
274615f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements the strong half of the cross-package regression gate (restructure plan §4-1): prove the provable chain holds on the freshly-built workspace before publishing to npm, not after.
What
examples/integration-smoke/provable-chain.mjs— a self-contained end-to-end smoke (no LLM, no network) over the local workspace builds:@wasmagent/compliance(backed by@wasmagent/coreVerificationPipeline+DeterministicVerifier);@wasmagent/aep;Adds
@wasmagent/aep+@wasmagent/complianceasworkspace:*deps of the smoke package so the bare imports resolve to local builds.run-all.mjs— registersprovable-chain.mjsinORDER(cheap/no-IO, runs early).release.yml— runs the gate afterBuildand before npm auth/changeset publish. A break (a verified task can no longer become signed, verifiable evidence) fails the release rather than shipping the break.Verification
Run on the workspace exactly as CI will (frozen install + build + gate command from repo root): exits 0 on a healthy chain; an injected signature break exits 1 (proving the gate is not a no-op).
check:changeset-required,check:branding,check:no-control-bytesall pass — no changeset required (examples/ + CI only, no publishable package source).Scope note
The trust-passport link (
@openagentaudit/passport) is intentionally excluded: it is an external published dependency, not a workspace package, so a wasmagent-js pre-publish gate cannot meaningfully guard it. This complements the after-publish canary already merged inagent-golden-path(which tests the latest published stack daily).