Closes#1477
## Why
With agent memory off, `codenomad_memory` was still registered for every
session (subagents included), so every request carried a tool that could
only fail with "Memory is disabled".
## What changes
- The backend writes `server.memoryEnabled` into its memory presence
leases (`{"version":1,"memory":true}` or empty) at startup and on each
server config change (`opencode/memory/preference.ts`), the same
lease-request mechanism as the Design agent.
- The plugin registers its tool transform only while a live lease
requests memory, rereads the request at each presence interval and calls
`ctx.tool.reload()` only on a change. Running sessions gain or lose the
tool within seconds, with no restart.
- The prompt hook stays registered, so disabling memory still clears
stale `codenomad.memory` instructions; execution still rejects disabled
use. Runtimes without `ctx.tool.reload` keep the tool registered.
- The lease request format is shared with Design
(`opencode/lease-request.ts`) and produces identical output.
## Validation
- Server typecheck, `test:help`, and unit tests for the memory plugin,
the preference sync, Design activation and the memory service (37 pass).
- `scripts/test-memory-tool-native.mjs` against a private OpenCode 2.2.7
daemon: the tool is absent while memory is disabled, appears when
enabled, disappears on disable and comes back on re-enable.
- Help updated in all ten locales.