[Pepps233]

Summary

Local release acceptance now exercises all eleven reviewed npm packages outside the workspace and blocks npm publication until the retained tarballs pass native acceptance.

Accompanies cloud PR #152

Reasoning

Installing every package together and checking CLI output could hide missing dependencies or a broken hosted-server executable.

Separate consumers, exact tarball checksums, installed-file verification, and process-level checks make those failures release blockers.

The approved policy continues to defer standalone binaries.

Advertised npm targets are narrowed to Darwin/Linux arm64/x64 until Windows has equivalent terminal acceptance.

Changes

• Derive every consumer and its dependency closure from the public workspace inventory.
• Exercise declared exports and package operations, native helpers, clipboard loading, image WASM, HTML export, CLI interaction, and hosted-server startup/authentication/shutdown.
• Isolate homes, projects, configuration, package prefixes, and caches; prevent fallback to registry Diffex packages and clean test-owned state.
• Run native acceptance against identical retained tarballs in PR CI and before npm publication, including recovery runs.
• Retain package results, process evidence, source identity, checksums, and explicit limitations.

Testing

• npm run check passed.
• ./test.sh passed with isolated non-E2E configuration.
• node --test scripts/*.test.mjs passed: 214 tests.
• Actionlint passed for all three affected workflows.
• Darwin arm64 acceptance passed for all eleven packages through npm and Bun, including CLI terminal prompt/reply and the packed server lifecycle.
• Clean Bun attempts exposed third-party registry integrity/resolution failures; fresh per-manager caches and bounded registry concurrency passed without weakening validation.
• Cloud quality and mirrored release-contract checks passed.

Committed candidate 7fc85b6c18d7c71662cab634c9be057ceac83d7f passed the frozen release artifact path, all 22 package operations, both server/terminal flows, final tarball checksum verification, and cleanup.
Local private inputs and evidence are retained in /private/tmp/diffex verified artifact candidate and /private/tmp/diffex verified artifact evidence.
The first native run reproduced missing system search helpers on all four runners.
Follow-up commit d33b3b584 provisions and executes fd and ripgrep, records their versions, and retains failed terminal evidence.
Its local acceptance passed all 22 operations and both process flows with cleanup.
Native CI retains the same evidence schema and exact checked tarballs in the corrected artifact acceptance workflow.
That run passed on Darwin arm64/x64 and Linux arm64/x64 for merge candidate 499786aab1b6002bfc1428514d43d3b4c4369237, incorporating head d33b3b584.
All four downloaded evidence records agree on the eleven tarballs and source identity, contain 88 passing package results in total, and confirm every server/terminal flow and cleanup.
The documented checksum command also rejected a deliberately modified copy of a final tarball with exit code 1; the original archive was preserved and the test copy removed.

No live provider test environment is available, as specified by the owner.
Real login/inference and public-artifact lifecycle acceptance remain pending.
No packages, releases, deployments, or production discovery records were published.