fix(memory): repair signed-package service restart on Windows and macOS

[Memtensor-AI]

Bug

After installing the signed 1.1.2 package, restarting the Memory service fails. Windows reports access denied from schtasks, while macOS reports a memory layer network error.

Root cause

The packaged Desktop startup path still asked the Memory installer to register an operating-system service. On Windows, a non-elevated signed package could not reliably overwrite an existing scheduled task. On macOS, launchd KeepAlive could race with restart and health checks, bringing the old process back and causing port contention.

Fix

• Skip OS service registration and installer health checks for packaged Desktop startup.
• Let Desktop directly own the bundled Memory child process.
• Add runtime-pointer loading, SQLite-lock-aware waiting, protocol-compatible health waiting, graceful shutdown, and legacy-service takeover.
• Preserve standalone OS service registration for the regular Memory CLI.
• Add regression coverage that starts the materialized bundled runtime as a Desktop child.

Validation

• Project Harness Full evidence passed.
• Root lint and typecheck passed.
• Desktop, Memory, and App Agent test suites passed.
• Memory-layer smoke tests passed 3/3.

Fix commit: 080c4ce