docs: withdraw the ZeroClaw integration claims

CLAUDE.md said ZeroClaw "imports this as a Cargo feature (clawhdf5
feature flag)" and uses clawhdf5 as its memory backend; the agent crate
called itself the "ZeroClaw agent memory HDF5 backend"; the migrator
claimed to read "the ZeroClaw layout". Checked on 2026-09-25 against
ZeroClaw v0.8.5 (its latest release), the osobh/zeroclaw fork (on
v0.8.5) and both histories back to February 2026:

- no `clawhdf5` feature, dependency or memory backend has ever existed
  in ZeroClaw; its backends are sqlite, lucid, postgres, qdrant,
  markdown and none, behind its own `Memory` trait;
- ZeroClaw's SQLite schema is a single `memories` table (id, key,
  content, category, embedding, created_at, updated_at); the
  migrator's memory_chunks/sessions/entities/relations layout never
  existed in ZeroClaw, so it cannot read a ZeroClaw database.

Decision: withdraw the claims (as with OpenClaw); clawhdf5 is a
standalone library with no framework integration. The migrator's
default layout is documented as its own. ZEROCLAW_VERSION keeps its name
and value (it is the persisted `edgehdf5_version` writer tag) with a
doc comment saying it is unrelated to ZeroClaw.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

docs/openclaw.md

@@ -9,9 +9,10 @@ keys, and since v2026.8.1 ("OpenClaw 2.0") the key no longer exists. A Gateway
 given that config refuses to start. No plugin was ever built or tested against
 OpenClaw, and the `@redclaw/clawhdf5` npm package was never published.
 
-As of 2026-09-25 we are not pursuing an OpenClaw plugin; the maintained
-integration target is ZeroClaw. This page records what a plugin would need,
-for when that changes.
+As of 2026-09-25 we are not pursuing an OpenClaw plugin, and clawhdf5 has no
+framework integration at all (ZeroClaw, also named as a consumer in older
+docs, does not use it either). This page records what an OpenClaw plugin would
+need, for when that changes.
 
 ## What OpenClaw expects today (v2026.9.6)