Memory changes

0.3.0-rc.3 — BrightOps naming and session preferences, 2026-09-09

Use Memory product names. Local session preferences remain available without optional cloud recall; app-specific corrections preserve history, and the CLI can read preferences when an MCP connection is closed.

0.3.0-alpha.2 — @wf scope

Use @wf/agent-memory. Replace imports and dependencies on @workforce-sdk/agent-memory; YAML and application data stay unchanged. Retain the previous exact archives and lockfile for rollback.

0.3.0-alpha.2 — private preview

Canonical WF package and shared current-only MCP runtime. Every configurable public engine takes a YAML path. This preview retains authenticated identity isolation, atomic notes, durable preference retry receipts, crash-released writer locks, bounded backups, and validated knowledge graphs from the newer Memory implementation. Tencent cannot be enabled; old cloud cleanup evidence is retained.

Preferences now write schema 2 and projections use a checksummed version-2 checkpoint. Stop writers, back up data, and rebuild legacy split projections before use. Do not downgrade in place; see Storage upgrade. Cancellation reaches async tools, suppresses late responses, and drains admitted disk writes before releasing their writer lock.

0.3.0-rc.2 — 2026-09-09

• Optional stable Tencent 2.0.1 uses WF-maintained source repair and strict YAML. The installed CLI pins archive and dependency integrity and ignores unrelated machine configuration.
• Per-user provider stores erase derived copies after draining extraction. Durable recovery journals and receipts cover crashes and lost responses.
• Windows long paths, restart reconciliation, local availability during outages, and preservation of other users are included.
• Earlier provider copies remain marked for cleanup; host backups and model logs retain their separate retention obligations.

See setup and storage guidance and the provider YAML.

0.3.0-rc.1 — 2026-09-09

Published release candidate; live licensed installation verified on 2026-09-09. That artifact remains @brightops/agent-memory and is separate from the new WF preview.

• Authenticated user/project isolation, durable notes, preference corrections, event retries, graph validation and namespace backup/restore are included.
• Windows storage locks support long customer directory paths.
• Installed-package tests cover process kill/reopen, backup/restore, isolation and current-only MCP on Windows x64, macOS arm64 and Linux x64.
• Commercial licensing includes embedded applications, AI/CI use, and continued reinstall/rebuild rights for versions acquired while paid.
• Registry tokens stay outside dependency URLs and lockfiles. Published archives are immutable; a paid version's pinned dependencies remain available after ordinary cancellation.
• Tencent cannot be enabled. Local memory works without it. Older cloud copies require a separate provider cleanup and are reported as cleanup-required.

Stop all writers and back up before upgrading older stores. Schema-1 preferences become schema 2 on change; legacy split projection checkpoints require a rebuild from the retained event log. This release does not silently discard corrupt files or reconstruct evidence already discarded by older versions.

See the guide and compatibility.