refactor(memory): name the domain memory, not mem

[retr0h]

First of the renames from #566, following the rule merged as osapi-io/specs#242. Chosen first because it is the abbreviation case, with no tool name involved.

The URL segment, the SDK service and the generated types all say memory. The provider directory and its package said mem, so the domain carried two names and the cross-layer search that checks a domain reaches every layer missed one of them.

Not mechanical, because gopsutil is also called mem

19 + 2  import github.com/osapi-io/osapi/internal/provider/node/mem
 2 + 2  import github.com/shirou/gopsutil/v4/mem

Two files import both. They already alias gopsutil as sysMem, so a bare mem. always meant ours and nothing was ambiguous. Our package is renamed; gopsutil's references are untouched.

I did get this wrong once mid-change, rewriting mem.VirtualMemoryStat to memory.VirtualMemoryStat inside darwin.go and debian.go where it was gopsutil's. The build caught it.

What moved, and what deliberately did not

Renamed: the directory, the package declaration including package mem_test, the import paths including node/mem/mocks, and the identifiers memProvider and memMocks.

Kept: memFs is the in-memory filesystem used across the test suite. MemBytes and MemPercent belong to the process domain, where they are a process's resident memory. memInfo is a local holding a gopsutil value. None of them is this domain.

The CLI's MEM column header stays too; an abbreviation in a table of fixed-width columns is doing a different job.

Three stale doc comments turned up

internal/provider/node/host/debian.go   // Debian implements the Mem interface for Debian.
internal/provider/node/disk/debian.go   // Debian implements the Mem interface for Debian.
internal/provider/node/load/debian.go   // Debian implements the Mem interface for Debian.

Copied from this package and never corrected. They name their own interface now. That is the rename earning its keep: three providers claimed to implement an interface they have nothing to do with, and nothing would have found it.

Checks

go build ./internal/... ./cmd/... clean. internal/provider/node/memory and internal/agent/... pass.

Next

node/apt to node/package, then scheduled/cron to schedule and container/docker to container. Those two are restructures rather than renames, since the concept becomes the directory and the tool becomes an implementation file inside it, the way ntp already holds chrony.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c

[retr0h]

Closing unmerged.