Establish MCP — reaching the graph when the harness cannot

Every other skill in this delivery assumes the nks_* MCP tools are already in the session. This one exists for when they are not — or when they are there in name and fail in use. Its job ends where entry's begins: a session whose first nks_orient call answers.

The server is remote (streamable HTTP + OAuth); nothing of it installs on the user's machine. What installs is this delivery — and it carries its own transport for harnesses that need one: scripts/verstak-bridge.mjs, beside this file.

First: which case is this?

Work down the ladder; stop at the first row that fits. Native support is preferred when it works — the bridge is the fallback, and there are two distinct reasons to fall back: the harness cannot do https+OAuth MCP, or it can and the experience keeps failing the user anyway.