v0.6.27 — install-path repair

If you installed v0.6.26 and every command came back with Not connected to Vodou, this release is the fix — and it was our bug, not anything you did.

What went wrong

The published source tree was missing its .env.example, and the installer created your .env from that file without saying anything when it wasn't there. One missing file, two symptoms that looked unrelated:

• no account keys → the account gate refused every command (Not connected to Vodou)
• no path to the memory engine's native library → semantic search crashed with an ONNX error that read like a completely separate bug

Every one of our publish gates passed. They all ask whether something forbidden got in; none asked whether something required had fallen out.

Fixed

• A fresh install starts. .env.example is published again, and the installer now writes a working .env either way — telling you plainly if it had to fall back, so a packaging mistake can never be silent again.
• Every bundled app gets set up, not just the ten on a stale hardcoded list. The Kanban board's connector shipped without its dependencies and failed on first use, while the install cheerfully reported "0 need attention".
• Windows had the same hole for a different reason — its installer never created a .env at all.
• A mismatched memory library is replaced, not trusted. The installer checked only that the file existed, not that it could run on your processor.

Also

Release packaging now verifies required files are actually present in what ships, not only that forbidden ones are absent. Recorded test fixtures are no longer published — one captured a real session and carried personal details with it.

Install

curl -fsSL https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.sh | bash

macOS (Apple Silicon + Intel), Linux (x64 + arm64), Windows (x64).

Known issues

The Windows package is unsigned, so SmartScreen will warn on first run.

Alpha.