On 28 Oct 2026 the development machine's data volume fell to 658 MiB free of 926 GiB and a peer's verify failed with No space left on device. The Go build cache had grown to 177 GiB: every store worktree, race build and pinned-toolchain build adds entries, and Go trims only entries unused for five days, so days of many-worktree autonomous runs fill the disk, and every preflight on the machine then fails or writes truncated files with no gate naming the cause. Entries unused for two days (79 GiB) were deleted by hand.

Frontmatter

.abcd/work/issues/resolved/iss-2610281502581386-on-28-oct-2026-the-development-machine-s.md
open on GitHub ↗ · commit history ↗

mentions2

• iss-2610290717018523The load gate now refuses a test stage when the volume holding the Go build cache or the worktree store has less than its floor free (iss-2610281502581386), but nothing keeps the cache from growing back. Go trims only entries unused for five days, and every store worktree, race build and pinned-toolchain build adds entries, so a machine running many worktrees for days still fills its disk and then stands until a person trims the cache by hand; on 29 Oct 2026 the cache on the development machine had grown back to about 291 GiB. The first issue's remedy also asked the worktree store's reclaim to trim cache entries older than a day when it removes worktrees; that was left out of its fix because abcd deleting another tool's cache is a trust change that needs its own decision.
• spc-2611020732419632abcd's load gate waits for memory as it waits for load