AGENTS.md points to github.com/PSModule/memory, which doesn't exist

[MariusStorhaug]

Problem

This repo's root AGENTS.md instructs agents to clone https://github.com/PSModule/memory alongside PSModule/docs and to "commit your memories here for work inside the PSModule organization":

2. Clone the ecosystem locally:
   1. <https://github.com/PSModule/docs> — requires PRs to be updated.
   2. <https://github.com/PSModule/memory> — work directly towards main.
      - Simple clone, only main.
...
3. Read the `.msx/PSModule/memory` - start with the index to get an overview of what is here. Use this while working - commit your memories here for work inside the PSModule organization.

Verified live just now: github.com/PSModule/memory returns 404 (checked via authenticated gh api repos/PSModule/memory, gh search repos memory --owner PSModule, and an unauthenticated fetch of the URL). The PSModule org has 94 repositories; none is named memory — the only near-match is the unrelated MemoryMappedFile module.

Impact

Any agent following these AGENTS.md instructions literally cannot install the ecosystem as documented, and has no repo to persist cross-session research/findings to, as the doc directs. This came up concretely in a recent session: research findings about PSModule/docs routing had no PSModule/memory to be committed to.

Options to resolve

1. Create the PSModule/memory repository (with at least a minimal index page) so the instructions become accurate.
2. Or remove/rewrite the memory-repo steps in AGENTS.md if this was aspirational/deprecated and there's no current plan to stand it up.

Either way, the doc shouldn't point agents at a resource that doesn't exist — this is currently misleading onboarding guidance for both humans and agents.