Command	Purpose
`pnpm poc:qr`	QR login. Writes the token file.
`pnpm control:bridge`	Start the daemon. It listens on `http://127.0.0.1:8788/mcp`.
`pnpm control:mock`	Start the mock core. Test the daemon without Electron.
`pnpm test:trigger`	Inject a trigger event into the mock core.
`pnpm poc:dm`	Send one test DM to zzib.
`pnpm test:comm`	Run the unit tests for the pure logic.
`pnpm cdp:probe`	Check CDP access and event delivery.
`pnpm cdp:dispatch`	Run one CDP expression in the client.
`pnpm check`	Type check the daemon code.

Transport

The primary transport is the validated core bridge at vesktop-puppet.sock. The daemon sends validated actions and receives normalized events. See ../docs/core-bridge.md.

The CDP transport is a development fallback. It needs no Vesktop patch, and it has no core-side guardrails. Use it for debugging only.

Pacing

Every command gets a random delay of 500 to 2800 ms. One queue serializes the commands. The queue coalesces identical concurrent reads. State reads use the cache. DEBUG=1 logs each command and its delay.

Live test target

The only permitted live-send target is user zzib. See ../docs/testing.md for the full setup.

Verified

QR login works end-to-end. The token came from a phone scan.
The core bridge works live. get_state returned the real account and 7 guilds. send_dm reached zzib. A synthetic owner message reached the daemon log with the command parsed.
The mock path works. The daemon handles state, sends, commands, and the two log buckets.
Pacing stayed inside the 500 to 2800 ms window.

Findings

Official discord.js is bot-only. It fails at login with a user token. The popular selfbot fork is archived. Do not use either. The core is the real Vesktop client.
MCP SDK 1.30.0 Streamable HTTP works as used here.
CDP gives control and events with no Vesktop patch. Raw CDP has no guardrails. The validated core bridge is the target for this reason.
pnpm 11: this folder is its own workspace root. Build approvals live in pnpm-workspace.yaml (allowBuilds).