four bespoke LOCK_EX flock loops remain (memory/writer.go, intent/create.go, spec/store.go, history/store.go) now that fsutil.WithFileLock is the canonical inter-process lock primitive; consolidate them onto it (one-canonical-primitive) — pre-existing, no defect, pure debt

four bespoke LOCK_EX flock loops remain (memory/writer.go, intent/create.go, spec/store.go, history/store.go) now that fsutil.WithFileLock is the canonical inter-process lock primitive; consolidate them onto it (one-canonical-primitive) — pre-existing, no defect, pure debt

Remedy grounds (2026-09-29)

• Confirmed at the base: five sites call syscall.Flock directly (decide.go:283, memory/writer.go:77, spec/store.go:326, intent/create.go:673, history/store.go:156), and history/store.go blocks without a timeout.
• The detector test keeps a sixth site from appearing. Rejected: forcing directory locks onto the lock-file primitive, which the deferral records WithFileLock cannot take.

Grounds

• pursued: we expect every inter-process lock in the tree to go through one of fsutil's two primitives, with each site's refusal and budget kept; a production flock outside internal/fsutil, or a site test that went red, would show it wrong