Regenerate pnpm-lock.yaml for bumped internal dep minimums

The previous commit bumped @atomicmemory/sdk to ^1.0.2 and
@atomicmemory/mcp-server to ^0.1.2 across adapters, plugins, and
packages, but pnpm-lock.yaml still had the old specifiers, so
`pnpm install --frozen-lockfile` rejected the mismatch on CI.

Ran `pnpm install --lockfile-only` to update the specifier fields
under each workspace project's `dependencies` block in the
lockfile. No other dependency resolution changed; the `link:`
targets to the in-workspace packages are unchanged.

Author: ethanj