24 August 2026 — Lacunari's CI runs on Postgres 14, 16 and 17, on macOS, Ubuntu and Linux Mint. Windows has never been in that matrix. Until recently, docs/STATUS.md listed "Windows, in any form" under a section called Not yet exercised, next to things like recovery from a database failover mid-claim and draining a single lane from more than one machine at once.
That line stopped being true a while ago, and leaving it up would have been the wrong kind of caution. A real development team has been running Lacunari on Windows on a live project for weeks: indexing, claiming tasks, working the board, the whole loop. We aren't naming the project. What matters for anyone deciding whether to trust this on their own Windows machines is the shape of the evidence, not whose it is.
What changed in STATUS.md
The Windows line moved out of Not yet exercised and into Verified, worded to say exactly what is and isn't known yet:
In real use on Windows, on a live project — not yet in CI, so treat it as proven-by-use rather than proven-by-suite until that gap is closed.
Those are two different kinds of confidence, and the doc now names which one this is. Proven-by-suite means the same 23 test suites that run on every commit also ran on this platform and passed. Proven-by-use means real commands, run by real people, against a real Postgres, for real weeks, with no regression test standing behind it if a future release breaks something a CI run would have caught first.
Why say it this way
docs/STATUS.md already lists its own bugs plainly: a keeper that mis-parsed every escalation because of a whitespace IFS, an audit log that attributed every entry to one role because of a SECURITY DEFINER trigger, a migration whose aborted transaction looked like a clean install and passed the suite anyway. Holding the Windows claim to that same standard, instead of rounding it up to "supported," follows the same instinct. Overclaiming here costs nothing today and costs somebody a debugging session later.
A Windows CI runner is the actual fix, and it hasn't shipped yet. Until it does, this is where the project stands: working, in production, not yet checked by the automation that checks everything else.