Merge branch 'feat/p3-python-remote-edit' into feat/p3-wasm-swmr-python

# Conflicts:
#	CHANGELOG.md
#	docs/design/range-reads.md
#	docs/known-issues.md

docs/design/range-reads.md

@@ -12,6 +12,10 @@ done on branch `feat/p3-m5-swmr-reader`, with its own design in
 [`swmr.md`](swmr.md) (see the M5 status below). M4 (wasm) is
 next. Every count in §1–§2 was
 
+object stores) and URLs in `h5rs` (see the M3 status below); the Python
+bindings followed on branch `feat/p3-python-remote-edit` (2026-09-27),
+which completes M3. M4 (wasm) is next. Every count in §1–§2 was
+
 change. Progress: M1, first part (the `Storage` trait and the metadata
 parsers listed in `CHANGELOG.md` under "Range reads, milestone M1") is done;
 group B-tree v2 lookups, dense groups and the facade are not converted yet.
@@ -477,7 +481,7 @@ fast path within benchmark noise.
   a request counter exposed for tests and users.
 - Python bindings: `clawhdf5.File("s3://…")` / `https://` through it.
 - *Status 2026-09-26:* done on branch `feat/p3-m3-remote`, except the
-  Python bindings, with these choices:
+  Python bindings (done 2026-09-27, below), with these choices:
   - A new crate, `clawhdf5-remote`, instead of a `remote` feature of
     `clawhdf5-io`: `open_url` returns a `clawhdf5::File`, and `clawhdf5-io`
     sits below the facade.
@@ -514,6 +518,17 @@ fast path within benchmark noise.
     same work without a cache: 141 936 requests. Per file: A lists in 2
     requests (§2 predicted 2 blocks of 1 MiB), B in 1, C in 7 (its whole
     6.4 MB: 35 001 object headers spread over the file).
+- *Status 2026-09-27, Python bindings:* done on branch
+  `feat/p3-python-remote-edit`. `clawhdf5.File(url)` and
+  `File.open_url(url, **options)` (cache and HTTP options) go through
+  `clawhdf5_remote::storage_for_url`; the default wheel is plain HTTP (no
+  C), `https`/`s3`/`gcs`/`azure` are build features. The bindings' own
+  parsing (path lookups, headers, attributes, listings, the global heap)
+  moved from `File::as_bytes` to `File::storage()` and the `*_in`
+  functions, and every file access, metadata included, runs with the GIL
+  released. Checked by running the whole read-vs-h5py suite over an
+  in-process range server (1 MiB and 1 KiB blocks) and by request counts
+  in `crates/clawhdf5-py/tests/test_remote.py`.
 
 **M4 — wasm lazy loading (1–2 weeks).**
 - `clawhdf5-wasm`: `openUrl(url) -> Promise<H5File>` backed by `fetch` with a