chore(release): normalize v1.1.8 generated version metadata

[syzsunshine219]

Run 35828663453 failed at Verify repository version metadata on the old PR #529 merge target 8d39dc6672f348d098c660ba09b69e593e9ca013 (release branch head ad55d9d284dd7064e9d9a5bf6c2dc45e24e355b2). The generator compares exact file contents, and three derived files each had an extra trailing blank line.

Run npm run version:sync to normalize only App/memmy-agent/package.json, App/shell/desktop/package.json, and App/backend/src/project-version.ts. No version values, lockfiles, business logic, workflow, Harness Control, or tags are changed.

Validation:

• npm run version:check: failed before sync with precisely these three staleFiles; passed after sync.
• npm run test:release-workflow: 30 passed, 5 skipped across 3 files.
• npm run test:packaging-guards: 44 passed across 6 files.
• git diff --check: passed; PR diff is three blank-line deletions.
• Local test dependencies were restored with npm ci --ignore-scripts --no-audit --no-fund and npm rebuild electron --workspace @memmy/desktop after initial missing Vitest/YAML/Electron environment failures.
• This checkout has no Project Harness binding; Doctor reports that gap. No Harness Full gate is claimed.

After a maintainer merges this PR, start a NEW GitHub Draft Release v2 workflow_dispatch on main with version=1.1.8, preflight_level=full, and create_draft=true. Leave target_sha empty so the workflow resolves the new main SHA. Do not rerun run 35828663453, which retains its old merge target. Merging, tagging, and publishing are outside this PR task.