Blinkling v3.2.6

Blinkling 3.2.6

A Mac without Node.js gets a working install, an honest Windows requirement, first-start windows you can move, and several fixes to the card, the answers and the click away.

• Start Claude Code with claude --dangerously-load-development-channels plugin:blinkling@blinkling, then type /blinkling:blinkling. The flag lets Blink's chat reach this session. Claude Code asks you to confirm it once. Without it Blink still works and answers from its own session.
• A Mac without Node.js now gets a working install. Every plugin command starts through bin/blinkling-run (a shell script, with a small blinkling-run.exe stub and a .cmd file for the Windows MCP server), which finds Node.js 22 or newer (PATH, Homebrew, Volta, asdf, mise, nvm, fnm) or fetches a private, SHA-256 checked copy into ~/.blinkling/runtime/node. Hooks exit quietly without Node.js and say so once. A test runs every hook command and the MCP handshake with a PATH that has no node.
• The README no longer says Node.js is not required on Windows. Windows needs Node.js 22 or newer from nodejs.org, while macOS and Linux fetch a private copy. The Windows MCP server starts through bin/blinkling-run.exe, a stub built in CI and checked by a test that spawns it without a shell. CI also installs the plugin into Claude Code 2.1.302 on Windows, where claude mcp list reports the server connected, and the same check passes on Linux with a PATH that has no Node.js.
• Every README and the install doc list Node.js 22 or newer as a Windows prerequisite before step 1, and the open command tells a Windows user whose MCP server is down to install it and run /mcp.
• A card, its tail and a dropped Blink are measured from Blink's real window frame, so they stay together where the frame starts below the display's corner.
• One question has one answer: the first reply is final. A later reply is told it came late and changes nothing.
• On macOS a click away from Blinkling is heard before Input Monitoring is allowed, by a second helper mode that only reads the mouse buttons and stops once the key tap is up.
• A click inside Settings or the welcome no longer closes the card, and the next click on the background still ends it.
• The translate demo is recorded with the app pinned to English, its answer text is kept with the recording, and a test reads that the answer is in the language its caption names.
• Desktop tests pass on Node 22 as well as 24, because a request that waits keeps the event loop alive. The conversation spec expects Haiku 5.5.
• What is and is not isolated between chats: a card follows its own session's chat and its history, but an answer to a capture, Auto explain or a dropped question comes from Blink's own shared session, whose model, effort and context every chat uses.
• Welcome, Settings and the macOS permission guide can be moved from anywhere that is not a control: the whole header and any empty area drag, while buttons, links, fields and code stay clickable and selectable. The window stays inside the work area, a double click on an empty area puts it back, and the place is kept. Acceptance tests drag all three with the real pointer.
• The nine READMEs are rewritten. They tell you to close the terminal and open a new one after installing anything, give the one command that starts Claude Code with Blink's channel and say what its flag does, and keep Node.js 22 or newer for Windows and the private copy for macOS and Linux.
• A chat test no longer fails now and then because a delayed save recreated its folder during cleanup.
• Nothing else changes from 3.2.5.