trelix v2.7 to v2.9: The Release Where the Pipeline Itself Became the Product

Short summary

A detailed post-mortem of six releases (v2.7.1 through v2.9.0) of trelix, an AI retrieval tool, focusing on non-retrieval issues: a binary name collision in the release pipeline, a test suite never wired into CI, SQLite concurrency bugs including TOCTOU races and stdout write races, and silent foreign-key corruption during partial re-indexing. The author groups fixes by theme rather than changelog order, covering pipeline, concurrency, and deployment problems.

• •Six releases over two weeks fixing release pipeline, concurrency, and deployment issues — not retrieval logic
• •Key bugs: binary name collision in CI, untested MCP suite, TOCTOU race in sparse embedder, silent FK corruption on re-index
• •SQLite check_same_thread=False misunderstood as concurrency-safe; required proper locking and double-checked locking patterns

Generated with AI, which can make mistakes.