AtMem 2.2.6 — maintenance and stable release handling

AtMem and the OpenClaw bridge use version 2.2.6; the companion remains atmem-atbot 0.1.0a6. This is the stable release of the 2.2.6 beta series.

User-visible changes

This maintenance release consolidates the existing 2.2.6 beta capabilities: governed retrieval, native and delegated context delivery, framework adapters, task state and responsive execution evidence. It does not deliver the proposed 2.3 investigation preview or the later enterprise roadmap.

Release validation now rejects mismatched Python/bridge versions and tag names. Stable packages use npm's latest channel and a non-prerelease GitHub release; alpha, beta and release candidates retain their respective preview channels. Publishing also waits for the installed companion-wheel gate.

Delegated host compatibility fixes and remaining gates

Spec 003 T049–T053 now passes its user-authorized latest-release Mem0 acceptance scope. The bridge binds isolated local identity to exact agent/workspace/session scope and verifies a private, unrouted CLI process when origin metadata is absent. The default owner gate still refuses missing ownership; requireOwner: false alone is no longer an identity bypass. Existing users must configure the explicit isolated mapping or restore the default gate.

Read/exec terminal results now reach Black Box through the real host event stream when typed completion hooks are absent. Correlation checks run, session, invocation and tool; digest-only observations survive registry reloads in a bounded cache. Missing/conflicting results remain incomplete_evidence. Observed tool errors are reported as errors, and normal completion hooks are deduplicated.

Real Mem0 with dummy data passed inject/withhold, exact receipt/context digests, one/zero deliveries, default-owner refusal, tool success/error closure and missing result checks on OpenClaw 2026.9.2 and 2026.9.3 with Claude CLI 2.1.236. Identity role-play also passed before-provider-access refusal checks. See the evidence journal.

Storizon beta10 HMAC/v2 results remain operator-reported; its private endpoint was not available. Live shared-channel authentication remains unverified. Mem0 role-play does not establish that boundary or Storizon-specific receipt behavior. The shared HMAC profile and signed delegated v1 payload are unchanged. These are compatibility/evidence fixes, so little visual change from beta10 is expected.

Install and upgrade

python -m pip install --upgrade atmem==2.2.6
atmem control verify

For an existing OpenClaw integration, also run:

atmem openclaw upgrade
atmem control verify

Optional framework and semantic installs:

python -m pip install --upgrade 'atmem[pydantic-ai]==2.2.6'
python -m pip install --upgrade 'atmem[langgraph]==2.2.6'
python -m pip install --upgrade 'atmem[semantic]==2.2.6'
atmem dashboard daemon restart

Install only the extras you use. AtBot remains automatically pinned to atmem-atbot==0.1.0a6; the managed OpenClaw installer pins openclaw-memory-atmem@2.2.6. No companion version change is required.

Migration and opt-in behavior

Existing delegatedContext.requireOwner: false configurations now fail closed unless a complete isolated local mapping and required host metadata are present. Restore the default owner gate or follow the local identity migration. The latest-release local Mem0 fixture verifies this stricter boundary. A later Storizon rerun is retained as attributed partner evidence; its private harness and fixture state were not independently reproduced by the AtMem maintainer.

No new canonical storage migration is introduced relative to beta 11. Existing memory, task state, evidence, authority settings and delegated payload formats are preserved; the identity checks above are intentionally stricter. No provider, task authority or hosted service is silently enabled. Back up persisted state before upgrading.

When upgrading earlier versions, the beta-11 semantic epoch and authenticated delegation requirements still apply: incomplete semantic profiles may need an exact-revision rebuild, and unauthenticated delegated registrations remain blocked. See the migration instructions. Do not bypass these checks to complete an upgrade.

Compatibility and limitations

• Supported Python matrix: 3.10–3.13; local validation is not a substitute for the full CI matrix.
• Native memory and Pydantic AI, LangChain/LangGraph, MCP and OpenClaw surfaces remain part of the same host-neutral product. A passing adapter test does not prove every framework version or deployment configuration works.
• No new shared-space permissions, durable enterprise credential authority, provider onboarding wizard or fleet administration is included.
• Evidence reports observed boundaries; missing final text or an unknown tool outcome is not proof of agent failure or successful remediation.
• Stable versioning does not certify the future enterprise roadmap as complete.