chore: promote memory activation release to main

[LeXwDeX]

Closes #583
Closes #585

Why

Promote the accepted Memory activation repair from dev to main for GraphAgent 1.0.43. The first /memory on now completes activation after repairing a missing initialization stamp, including unavailable-model replacement.

What changed

• Repair the delivery context with official SpecGit bind from an ordinary branch checkout so GitHub CI can verify it; preserve the existing PR and all quality gates.
• Integrate dev commit b997acc, including the reviewed fix: complete memory activation after init self-heal #581 repair and regression tests from fix: complete memory activation after init self-heal #582.
• Update the release notes with actual accepted-candidate CI results and compiled debug CLI evidence.
• Preserve all policies and CI gates; no runtime changes beyond the accepted repair.

Evidence

• PR fix: complete memory activation after init self-heal #582 accepted by specgit finish exit 0 and merged to dev; fix: complete memory activation after init self-heal #581 is closed.
• Candidate 3b0d9da: 4574 opencode tests passed (23 existing skips, 1 todo), 29 workspace typechecks passed, DAG coverage 820 passed, HttpAPI 3 x 230 passed, Linux/Windows E2E 21 passed each.
• Bun 1.3.14 memory/search/server-wiring suite: 116 passed. Debug binary first activation and restart status passed in isolated temporary storage.
• Independent Standards and Spec review found no implementation blockers; the release-note follow-up is addressed here.
• Both prerelease and stable release-note renders passed. Candidate build succeeded: https://github.com/LeXwDeX/OpenCode-GraphAgent/actions/runs/34295529961
• Downloaded candidate archives: all four SHA256SUMS entries match. macOS actual-artifact installation acceptance: 6 passed, 0 failed. Packaged binary 1.0.43-dev.1 passed first /memory on, restarted status, off, and restarted off-state in new isolated storage.
• Main promotion requires its own current-head checks and SpecGit acceptance before merge. Stable release asset verification follows publication.

Checklist

• Accepted repair integrated into dev
• Release notes include actual CI evidence
• Runtime patch independently reviewed
• Release-note rendering validated