TestBannerRendersAboveBoard renders the bare board twice in the package directory of the live checkout and requires the two renders to agree byte for byte; since the board gained its peers line it reads the sibling worktrees on disk, so a peer session creating or retiring a worktree between the two renders changes the live-peer count and fails the test (seen in a preflight: 30 live peers without the banner, 31 with it). The test is not hermetic: it should render in a directory with no peers.

TestBannerRendersAboveBoard renders the bare board twice in the package directory of the live checkout and requires the two renders to agree byte for byte; since the board gained its peers line it reads the sibling worktrees on disk, so a peer session creating or retiring a worktree between the two renders changes the live-peer count and fails the test (seen in a preflight: 30 live peers without the banner, 31 with it). The test is not hermetic: it should render in a directory with no peers.

Grounds

• pursued: the test passes whatever peer worktrees exist beside the checkout; a preflight failing it with differing live-peer counts in the two renders would show it wrong