covalent-bond: Skill for Claude Code

Testing Covalent Bond

npm test runs every test/*.test.js file as a separate process via test/run-all.js. A suite passes when its process exits 0; use plain assert and let a failed assertion crash the process. No test framework; keep it that way (small surface is a feature).

Ground rules

• Every bug fix and every new behavior ships with a test. Put it in the matching existing suite, or a new *.test.js; the runner picks it up automatically.
• The mitm suite is the security-model guardrail. It must stay green, and any change to the key schedule, handshake, or abort logic needs a case there (or a clearly linked one).
• Tests must run offline: no network, no wrangler, no deployed relay. Everything talks to the in-process mock relay.
• Tests may console.log freely (they are standalone processes, not loaded by the MCP server).

Using the mock relay

import { startMockRelay, stopMockRelay, resetMockRelay } from './mock-relay-server.js';

await startMockRelay(PORT);   // pick a UNIQUE port per suite (see below)
resetMockRelay();             // wipe sessions + rate limits between suites
// ... test ...
await stopMockRelay();

Port allocation: each suite binds its own port so suites can never collide: 8791 handshake, 8792 mcp-routing, 8793 payload-hardening, 8794 rate-limiting, 8795 hardening-regressions. A new suite takes the next free number. 8787 is reserved for npm run relay:dev.

The mock mirrors the production worker's API exactly (sequence numbers, create-clobber refusal, rate limits, payload caps, security headers, error codes). Protocol constants (TTL, caps, throttle, error codes) live once in relay/constants.js; the mock imports them and the Worker keeps mirrored copies that relay-parity.test.js verifies by reading worker.js. If you change the worker's behavior, change the mock in the same PR, keep the shared constants in sync, and cover the difference with a test.

Deterministic polling (never sleep)