osobhandClaude Opus 5.5
b55b24b7ba
Every crate under crates/ now has a README (android, bench, cli, napi and wasm had none), each saying what the crate is, its main types and functions (names checked against the code), its cargo features with defaults and which ones build C (checked with `cargo tree`), and links to the top-level docs. Corrections to the old stubs: - clawhdf5-derive: the derive is `H5Type`, not `HDF5Type`, and it needs clawhdf5-format as a dependency. - clawhdf5-filters: deflate backends only, and no library crate depends on it; the filter pipeline and every other codec are in -format. - clawhdf5-gpu: vector distance compute, not I/O; not used by HDF5Memory::search. - clawhdf5-io: MpiVol is root-read + broadcast, not collective MPI-IO. - clawhdf5-ann: from_hdf5/search(q, k) did not exist; load_from_hdf5 and search(q, k, ef). - clawhdf5-accel: checksum::crc32_simd did not exist; the SSE4 and wasm backends are reported but run the scalar kernels. - clawhdf5-gpu: the old example called l2_distances, which does not exist (l2_search). - clawhdf5-agent: it described a "vector store" with "GPU acceleration"; it now covers HDF5Memory, search options, WAL, signing, the graph. - crates.io/docs.rs badges removed and `cargo install <crate>` replaced: nothing is published; depend on git. - fuzz: the opt-in CLAWHDF5_FUZZ_SECONDS smoke run in ci-test.sh. - tools: the FileEditor interop tests that live in this crate. - remote, py: license, other front ends, limits, File.mode/flush/chunks. The Rust examples of the facade, format, filters, accel, ann, derive and agent READMEs were compiled and run as tests (netcdf4, gpu and remote compiled only) in a scratch crate; the CLI example was run. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
clawhdf5-migrate
CLI tool to migrate a SQLite agent-memory database in the memory_chunks / sessions / entities / relations layout (table and
column names are configurable) to a
clawhdf5-agent store. This is not
ZeroClaw's schema — ZeroClaw keeps memories in a single memories table and
does not use clawhdf5.
The output is written through clawhdf5-agent's own API, so it opens with
HDF5Memory::open and is searchable immediately: memory records, sessions and
the knowledge graph (entities and relations) are carried over.
Installation
Not on crates.io yet; install from a checkout:
cargo install --path crates/clawhdf5-migrate
It builds C: rusqlite is built with its bundled feature, which compiles
SQLite (so no system libsqlite is needed, but a C compiler is).
Usage
clawhdf5-migrate --sqlite agent.db --hdf5 agent.h5 --agent-id my-agent
Embeddings are stored as float16 (the library default for new stores); pass
--f32 for full precision. Every embedding must have the same dimension
(the first row's, or --embedding-dim, which a source with no memory records
requires); rows are never truncated, and the whole source is checked before an
existing output store is replaced. --incremental adds only new rows to an
existing store of the same dimension and carries over changes to rows'
deleted flags, --skip-deleted leaves out tombstoned rows, and --dry-run
only counts.
See clawhdf5-migrate --help for every option.
License
MIT