release: Memmy v1.1.1

[syzsunshine219]

Summary

• prepare the official release/v1.1.1 branch for review against main at the exact source HEAD 65060a181d12e23b2b87484d88818a8d07cf695f
• synchronize all managed application, Memory CLI, Agent, Desktop, lockfile, and generated versions to 1.1.1
• carry the complete upstream v1.1.1 change set without trimming its history
• fix the clean-runner Linux CLI workflow bootstrap and make the Memory CLI setup fixture independent of host OpenCode/XDG configuration
• keep this pull request in Draft until signed desktop artifacts and independent review are complete

Included changes

• add headless Goal CLI execution with multiline objectives, exact project binding, and terminal-session targeting
• add configurable Memory retrieval layers and the matching Memory configuration, setup, contract, and turn-capture coverage
• add the one-line Linux CLI installer, archive verification, and managed systemd gateway lifecycle
• preserve Unicode Windows update paths and keep Windows Memory refresh behavior available without unsupported drawer controls
• restore local embedding selection, synchronize account-mode model configuration, and prune stale model assignments after provider deletion
• synchronize version metadata to 1.1.1, add reviewed release notes, and align the registration-flow source assertion with the current onboarding call shape
• install the standalone Agent lockfile dependencies before Linux archive contract tests in commit e519dceca9438bf7cfd81294256331a3c37426f8
• isolate OPENCODE_CONFIG_DIR and XDG_CONFIG_HOME inside Memory CLI setup fixtures in commit 65060a181d12e23b2b87484d88818a8d07cf695f

Verification

• NODE_OPTIONS=--no-webstorage npm test passed on exact HEAD 65060a181d12e23b2b87484d88818a8d07cf695f
• Linux targeted tests passed locally: archive/package boundary 5/5, Agent gateway/terminal tests 41/41, Memory CLI setup 20/20
• release workflow and OSS CRC tests passed: 27/27
• packaging guards passed: 16/16
• the final revision 4 Project Harness Full run passed all 12 required evidence commands with no failed evidence
• the final Full run used VITEST_MAX_WORKERS=1 to serialize Vitest file workers after an existing 0.5-second exec-session readiness assertion showed load-sensitive timing failures; no test command, file, or gate was skipped or waived
• Linux CLI installer run 32961525754 completed with conclusion=success on the exact head SHA: build, archive contract tests, release-asset build, Actions artifact upload, x64 install-smoke, and arm64 install-smoke all passed

Project Harness Evidence

• Task / revision: feature-2026-08-26-7832ead1-066e57f6 / 4
• Risk / profile: T3 / full
• Gate: 12/12 passed, verificationPassed=true, deliveryReady=true, failedEvidence=[]
• Run: run-1787741885068-07918444-922d-4683-82d9-c1d917e81905
• Evidence fingerprint: a32cb89cb31118b40de56b73c4bcb0fec02c8cc2d727b76c9f0747b253d74d0f
• Manifest fingerprint: 527ade8b1d4a6f89087732f9afe34f72608b0a0bf2e87b0f7dd9a2a3f89ebe11
• Task scope fingerprint: 495be0dc28175fdcac1d66518a71c10d50e96b1204ff697cec8d4f11a07ff163
• Selection fingerprint: 88f9ac2d94d2f562b6bf8b30d0af5cd87c42d1e5c8b48483b125c0c81c578d7f
• Control fingerprint: d358dc596cfb78c31c9b16fa54cb9f26b09dc2bac02430798d58694c29945390
• Delivery fingerprint: 5c6ddffdfc68042e15d9ddd8f440d103957bf9762663b02f2ce40db6fbe82cab
• Base / head: b4c37f78557b1d9a2ed9addf148c53d406ce954a / 65060a181d12e23b2b87484d88818a8d07cf695f
• control_contract initially rejected an ignored .DS_Store in the Control inventory. The file was moved out without changing Control policy; Control inventory, self-test, and Doctor recovered, and the final control_contract passed.
• The installed Project Harness 0.3.7 task deliver command has no title/body/body-file parameters and uses fixed gh pr create --fill --draft arguments when creating a PR. This existing Draft PR's metadata was therefore corrected with gh pr edit; official task deliver then recovered the same PR and bound the current evidence to a new handoff marker.

Artifact and Release Boundaries

Provider history remains explicit:

1. Run 32953490709 failed because the clean runner installed only root workspaces; the standalone Agent build lacked its dedicated dependencies and TypeScript returned status 2. install-smoke and upload were skipped and the run produced no artifact.
2. Commit e519dceca9438bf7cfd81294256331a3c37426f8 added the independent Agent install. Run 32960128204 moved past that bootstrap but exposed a second non-hermetic test fixture: the runner's ambient XDG_CONFIG_HOME made the OpenCode fixture resolve outside the temporary test home. The build failed and downstream jobs were skipped.
3. Commit 65060a181d12e23b2b87484d88818a8d07cf695f isolated OPENCODE_CONFIG_DIR and XDG_CONFIG_HOME. Run 32961525754 then passed build plus x64/arm64 install-smoke. It produced the non-expired Actions artifact memmy-linux-cli-assets (artifact id 9604096365, 18,210,087 bytes) bound to the final head SHA.

The workflow's Release upload job is intentionally skipped for a pull-request event; therefore the successful run proves archive generation and cross-architecture installation, but it did not publish a Linux asset to a GitHub Release.

The four expected signed desktop v1.1.1 OSS objects are still missing and returned HTTP 404 during the final pre-handoff check:

• Memmy-1.1.1-win32-x64-cn-signed.exe
• Memmy-1.1.1-win32-x64-intl-signed.exe
• Memmy-1.1.1-darwin-arm64-cn-signed.dmg
• Memmy-1.1.1-darwin-arm64-intl-signed.dmg

No v1.1.1 tag or GitHub Release exists. No installer signing, notarization, OSS upload, Draft Release creation, or Publish action was performed here. Signed desktop artifact production and independent review remain release blockers.

Independent Review Boundary

Keep this pull request in Draft. All earlier handoff markers and approvals tied to them are superseded for review eligibility by the new revision 4 marker that Project Harness will post after this metadata refresh. A different eligible MemTensor maintainer must submit a provider-authenticated approval strictly after that revision 4 marker timestamp; the delivery author cannot approve their own work.

Merge, tag creation, Draft Release creation, and Publish remain separate trusted-provider or human actions and are not authorized by this handoff.

[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.

[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.