Tests and Electron fixtures

Choose checks that exercise the changed behavior. Root commands run from the directory containing the workspace package.json.

Core checks

pnpm check
pnpm build
pnpm test:architecture
pnpm test:docs

pnpm check runs formatting, lint, TypeScript checks, unit tests, Rust formatting, Clippy, and Rust tests. The production build is needed before the acceptance scripts and before documentation examples can use built SDK declarations.

Controlled Electron acceptance

pnpm test:integration
pnpm test:injector-integration
pnpm test:external-plugin
pnpm test:virus-check

On Linux without a graphical session, prefix each acceptance command with xvfb-run -a as CI does.

Suite	Evidence
integration	Injection, sandbox startup, plugin cleanup and pristine archive restoration
injector-integration	Preview/commit agreement, runtime launch, no-op reinjection and stale refusal
external-plugin	Starter packaged outside the workspace, ZIP import, both UI modes and restart persistence
virus-check	File-context interaction and browser-open behavior using the controlled fixture

Fixtures generate test installations; automated acceptance must not target a real Fluxer installation, send real messages, or open real third-party reports.

Documentation

Install docs dependencies separately, run pnpm –dir docs build, then pnpm –dir docs check:links. The root pnpm test:docs compiles examples and the starter against the public API.

For a version-only change, verify matching package/native/runtime labels, lockfile consistency, builds, and affected tests. Do not change schemaVersion or apiVersion without an actual protocol change.