docs: crate READMEs describe each crate as it is today

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]>

crates/clawhdf5-remote/README.md

@@ -114,3 +114,34 @@ let s = storage.stats(); // requests, bytes_fetched, hits, misses, cached_bytes,
 directory with range support (the server the tests use), and
 `cargo run -p clawhdf5-remote --example read_url -- URL [DATASET]` lists a
 file and prints what it cost.
+
+## Other front ends
+
+- `h5rs` (built with `--features remote`, or `remote-https`) takes URLs as
+  FILE arguments: [`clawhdf5-tools`](../clawhdf5-tools/README.md).
+- Python: `clawhdf5.File("http://…")` and `File.open_url(url, ...)` go
+  through this crate: [`clawhdf5-py`](../clawhdf5-py/README.md).
+- The browser does **not** use this crate (its cache fetches by blocking);
+  `clawhdf5-wasm`'s `openUrl` has its own restartable cache:
+  [`examples/wasm-viewer`](../../examples/wasm-viewer/README.md).
+
+## Limits
+
+Files a SWMR writer is still appending to cannot be followed remotely
+(the file is pinned at open, so growth is `RemoteError::FileChanged`); the
+block size is fixed rather than taken from a paged file's page size; the
+cloud backends are built and unit-tested but have not been run against a
+real bucket. The full list is under "Remote files (`clawhdf5-remote`)
+limits" in [`docs/known-issues.md`](../../docs/known-issues.md); the design
+is milestone M3 of [`docs/design/range-reads.md`](../../docs/design/range-reads.md).
+
+Not on crates.io yet; depend on it from git:
+
+```toml
+[dependencies]
+clawhdf5-remote = { git = "https://git.redclaw.dev/quantumclaw/clawhdf5" }
+```
+
+## License
+
+MIT