docs: withdraw the OpenClaw integration claims

The docs described a "drop-in" OpenClaw memory backend enabled with
`memory.backend = "clawhdf5"`. Checked against OpenClaw's source and
docs (v2026.2.26 through v2026.9.6): that config was never valid —
v2026.2-v2026.7 accepted only "builtin"/"qmd" and rejected unknown
keys, so a Gateway given it refuses to start, and v2026.8.1 (OpenClaw
2.0) removed the key. No plugin was ever built (no manifest, no
registration, no tools), nothing was tested against OpenClaw, the
linked github.com/redclawsystems/openclaw is a 404, and
@redclaw/clawhdf5 was never published.

Decision (2026-09-25): not pursuing an OpenClaw plugin for now; ZeroClaw
is the integration target.

- Remove openclaw-integration.md, openclaw-config.md and
  migration-guide.md; add docs/openclaw.md: the status, what a memory
  plugin needs against v2026.9.6 (plugins.slots.memory, manifest with
  kind "memory", registerMemoryCapability / MemorySearchManager,
  prebuilt native packages), and what this repo has as building blocks.
- README, QUICKSTART, USE_CASES, ROADMAP (Track 7 withdrawn), CLAUDE.md
  and the `openclaw` module docs describe ClawhdfBackend as what it is:
  a Markdown-oriented library backend, not an OpenClaw plugin. The
  QUICKSTART example is corrected (the old one called a three-argument
  create that does not exist) and states its limits.
- packages/clawhdf5-node: marked unpublished and broken, "private": true
  so it cannot be published by accident; its bugs (snake_case vs
  camelCase fields, wrong addon path, no way to store an embedding,
  wrong WAL name) are recorded in docs/known-issues.md.
- Two broken rustdoc links fixed along the way.

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

packages/clawhdf5-node/README.md

@@ -5,20 +5,20 @@ HDF5-backed agent memory system with hippocampal consolidation.
 
 Built with [napi-rs](https://napi.rs).
 
+> **Status: unpublished and known to be broken.** This package is not on npm,
+> no binaries are built, nothing in CI builds or tests it, and the wrapper
+> reads field names the native layer does not produce. It is not an OpenClaw
+> plugin. See [known issues](../../docs/known-issues.md) and
+> [docs/openclaw.md](../../docs/openclaw.md) before using it.
+
 ## Installation
 
+Not published. Building from source needs `@napi-rs/cli`:
+
 ```bash
-npm install @redclaw/clawhdf5
+npm install && npm run build
 ```
 
-Pre-built binaries are published for:
-
-| Platform | Architecture |
-|----------|-------------|
-| Linux (glibc) | x64, aarch64 |
-| macOS | x64, aarch64 (Apple Silicon) |
-| Windows | x64 |
-
 ## Quick start
 
 ```ts

packages/clawhdf5-node/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@redclaw/clawhdf5",
   "version": "2.7.0",
-  "description": "Node.js bindings for clawhdf5 — HDF5-backed agent memory with hippocampal consolidation",
+  "description": "Node.js bindings for clawhdf5 \u2014 HDF5-backed agent memory with hippocampal consolidation",
   "main": "index.js",
   "types": "index.d.ts",
   "license": "MIT",
@@ -14,8 +14,7 @@
     "memory",
     "hdf5",
     "vector-search",
-    "embedding",
-    "openclaw"
+    "embedding"
   ],
   "napi": {
     "name": "clawhdf5",
@@ -51,5 +50,6 @@
   },
   "engines": {
     "node": ">= 16"
-  }
+  },
+  "private": true
 }