release: Memmy v1.1.0

[syzsunshine219]

Summary

• integrate the completed v1.1.0 product line after PRs fix: hot reload Composio MCP after backend startup #292 and fix(updater): preserve authoritative Windows data during upgrade #293
• synchronize all managed application, CLI, desktop, lockfile, and generated versions to 1.1.0
• add reviewed, source-backed release notes for Memmy v1.1.0
• restore two tests corrupted by branch integration and close inherited Frontend/Agent lint gaps
• integrate main PR fix(release): verify Multipart OSS assets with CRC64 #295 so Normal OSS assets verify with Content-MD5 and Multipart assets verify with streaming CRC-64/XZ

Verification

• Project Harness Full/T3 on 60cb7206: 12/12 required checks passed, verificationPassed=true, no failed evidence
• version sync/check and packaged runtime version guard passed
• release workflow and CRC tests: 27/27 passed
• packaging guards: 16/16 passed
• official Draft Release smoke preflight passed: https://github.com/MemTensor/memmy-agent/actions/runs/32732146139
• all four current v1.1.0 Multipart installers were fully downloaded and matched OSS CRC-64/XZ using the committed verifier
• release owner reports final package testing completed

Remaining review boundaries

Keep this PR in Draft until the release owner and independent maintainer complete the decisions below.

1. Confirm the final Windows validation record for cross-volume upgrade and force-kill recovery against the unchanged installer bytes originally built from e61049c3. The new 60cb7206 delta contains release workflow, verifier, tests, and test-command integration only; it does not change packaged runtime inputs.
2. Dependency audit reports 22 findings overall and 13 with --omit=dev, identical to v1.0.9 rather than newly introduced here. Electron 38.4.0 and agent runtime PostCSS require a maintainer fix or documented risk decision before Ready/merge; remaining unreachable or constrained paths must be reviewed.
3. Obtain an independent MemTensor maintainer approval submitted after the refreshed Project Harness handoff marker, then convert this PR from Draft to Ready.

After this canonical PR is merged, the trusted workflow will run full preflight and create a Draft Release only. Publishing remains a separate human action.

[syzsunshine219]

Project Harness review handoff marker. Only reviews submitted strictly after this GitHub timestamp qualify.

[syzsunshine219]

Project Harness review handoff marker. Only reviews submitted strictly after this GitHub timestamp qualify.