Skip to content

docs: integration-smoke README reflects provable-chain pre-publish gate #329

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
telleroutlook merged 1 commit into from
Jul 30, 2026
Merged

docs: integration-smoke README reflects provable-chain pre-publish gate #329

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions examples/integration-smoke/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,13 @@
Local-only end-to-end smoke scripts that drive the public `@wasmagent/*`
package surface across `worker_threads`, real WASM isolates, and HTTP.

> **Not run in CI.** The suite spins up real isolates, real HTTP servers, and
> real cross-package wiring. Wall-clock ≈ 1–2 min. CI's fast feedback comes
> from `bun run test` (vitest, in-process) and `examples/benchmarks/run-all.mjs`
> (token-counter benchmarks). This directory is the **pre-merge / pre-release
> sanity gate** — run it by hand against a fresh build before tagging or
> publishing.
> **Mostly local-only — one exception runs in CI.** The suite spins up real
> isolates, real HTTP servers, and real cross-package wiring. Wall-clock ≈ 1–2 min,
> so CI's fast feedback comes from `bun run test` (vitest, in-process) and
> `examples/benchmarks/run-all.mjs` (token-counter benchmarks). Run the rest by
> hand against a fresh build before tagging. **Exception:** `provable-chain.mjs`
> (fast, deterministic, no isolates/HTTP) runs as a **pre-publish gate** in
> `.github/workflows/release.yml`, before `changeset publish`.

## Quick start

Expand Down Expand Up @@ -36,6 +37,7 @@ patterns where unit tests tend to skip a corner.

| Script | Strategic line | What it pins |
|---|---|---|
| `provable-chain.mjs` | provable chain (CI gate) | The core → compliance → AEP seam: a task output is verified by `@wasmagent/compliance` (backed by `@wasmagent/core` `VerificationPipeline`), the verdict becomes signed AEP evidence via `@wasmagent/aep`, the signature verifies, and a tampered record is rejected. **Runs as the pre-publish gate in `release.yml`.** |
| `a1-codemode.mjs` | S1 / A1 | Drive `createCodeModeServer` over JSON-RPC like a real MCP host. Verifies `tools/list` publishes exactly `docs_search + execute_code`, the in-sandbox `callTool` chain works, and only the script's return value crosses back. |
| `a2-aisdk-mastra.mjs` | S1 / A2 | Verify `@wasmagent/aisdk` (`sandboxedJsTool`) and `@wasmagent/mastra-sandbox` (`WasmAgentMastraSandbox`) actually work end-to-end against the structurally-typed shapes those upstream SDKs expose. No `ai` / `@mastra/core` import — just the call shape. |
| `a4-studio-http.mjs` | S3 / A4 | Start the local Studio HTTP server (`WasmAgent devtools`), exercise `/api/rollup`, `/api/runs`, `/`. Asserts JSON shape and clean shutdown. |
Expand Down
Loading