Merge branch 'feat/p1-plugin-filters' into feat/p1-proof

# Conflicts:
#	crates/clawhdf5/tests/h5py_chunked_read_tests.rs
#	docs/known-issues.md

docs/known-issues.md

@@ -139,7 +139,23 @@ fill-value item that did is fixed).
   - x87 long double and binary128 are refused.
   - N-Bit on 64-bit scale-offset data and some N-Bit parameter layouts fail.
 - **Filters:** blosc, blosc2, bitshuffle, bzip2, LZF and zfp are not
-  implemented.
+  implemented. **Fixed 2026-09-26** for LZF (default-on `lzf` feature),
+  bitshuffle, bzip2 and Blosc 1 (`bitshuffle`, `bzip2`, `blosc`, or
+  `plugin-filters` for all), read and write, pure Rust; h5ex_d_lzf,
+  h5ex_d_bshuf, h5ex_d_bzip2 and h5ex_d_blosc now read (conformance 573 of
+  697 ok). **Still open:** Blosc2 (32026 — hdf5plugin stores each chunk as a
+  Blosc2 super-chunk frame, and n-D chunks as B2ND arrays) and ZFP (32013);
+  both fail with an `UnsupportedFilter` error that names the filter, and
+  either can be plugged in with `filter_registry::register_filter` (32023,
+  Granular BitRound, too, since 2026-09-26 even with the `pcodec` feature).
+- **Wrong data: a chunk whose filters decode to fewer bytes than the chunk
+  read with zeros for the missing bytes** (any filter; found reviewing the plugin
+  filters). **Fixed 2026-09-26:** it is an error naming the chunk. A corrupt
+  chunk must never read as zeros. Unfiltered chunks are read at their stored
+  size and are not checked this way.
+- **Crash:** a hostile Blosc chunk (frame size below its header) panicked in
+  builds with overflow checks. **Fixed 2026-09-26**; the new decoders are
+  fuzzed in the unit tests.
 - ~~**Header checks:** on 12 CVE datasets libhdf5 rejects a corrupt header and
   we read data anyway. We need stricter header checks.~~ **Fixed
   2026-09-26** (counted again: 18 objects on the CVE corpus that libhdf5