PBVex operations

Application release automation should install the pbvex CLI with npm and keep its version aligned with the application's local dependency. The package has an exact dependency on @pbvex/server; pbvex serve and managed local pbvex dev select its bundled platform binary. The PBVex source monorepo itself continues to use pnpm workspaces for contributor checks.

Separate application deployment from binary operation. The PBVex binary embeds PocketBase and needs no Node.js or checkout at runtime; run one process for one data directory. Do not turn it into a multi-node/shared-data-directory deployment or add a Node sidecar requirement.

The six published packages move in lockstep: @pbvex/protocol, @pbvex/server, pbvex, @pbvex/client, @pbvex/react, and @pbvex/svelte. Release validation must build/stage every server binary before ordered publication. Standalone GitHub archives remain the Node-free distribution.