@payysoon1Every task passed. The release didn't.
I build AIWorkHub, a VS Code extension and MCP server that runs AI coding agents as a task system. A manager model plans and reviews but doesn't write features. Workers write code in isolated worktrees, one card at a time. A card lands only when its declared tests and gates pass.
That process accepted 27 commits for the 0.12.95 release. Then I ran the full test suite on Linux, as I do before every tag.
25,326 tests passed. 55 did not.
18
failed because the release script tests an archive with no .git directory.
13
failed because of the test environment: no Node in that Linux install, or tests running as root.
4
failed the same way on the previous release tag.
20
traced back to four changes in this release.
Each of those four changes had passed its own validation. Three had only left something stale: a test fixture missing a newly imported module, a test that still expected a compiler to be refused, and a tool description over its published word limit.…
