Use the standard server-job path for Memory

[hamzamerzic]

Why

This is the Memory companion to the platform cleanup that removes the server-job authority split. It deliberately reverses the manifest declaration added in #22 because the platform no longer exposes a separate scoped executor.

What changes

• remove permissions.job_authority from Memory's manifest;
• keep shared_memory: write, summary-level chat access, the schedule, and install-time initialization unchanged;
• keep liveness tied to the reviewed fetch.sh schedule while accepting both current schema 3 receipts and the cleanup's schema 4 receipts during rollout;
• remove obsolete “scoped” wording from wrapper and preflight diagnostics;
• bump Memory to 2.3.1.

Memory's model invocation remains deliberately text-only and receives no tools, filesystem handle, shell, or owner token. Graph validation, atomic Git publication, recovery history, provider choice, and owner data are unchanged.

Release order

Merge this change before the companion platform cleanup. An older platform already treats an omitted authority declaration as the ordinary server-job process path, so Memory-first is safe. The platform can then reject the retired field without making new installs or updates fail.

Verification

• 46 JavaScript tests passed;
• every offline-harness phase passed;
• all 106 Python tests passed;
• the candidate platform validator accepts the manifest;
• shell/Python syntax and git diff --check pass.