chore[claude]: update claude.md (#5318)

Signed-off-by: Joe Isaacs <[email protected]>

Author: joseph-isaacs

CLAUDE.md

@@ -4,9 +4,13 @@
 
 * project is a monorepo Rust workspace, java bindings in `/java`, python bindings in `/vortex-python`
 * run `cargo build -p` to build a specific crate
-* use `cargo clippy --all-targets --all-features` to make sure a project is free of lint issues. Please do this every time you reach a stopping point or think you've finished work.
-* run `cargo +nightly fmt --all` to format Rust source files. Please do this every time you reach a stopping point or think you've finished work.
-* you can try running `cargo fix --lib --allow-dirty --allow-staged && cargo clippy --fix --lib --allow-dirty --allow-staged` to automatically many fix minor errors.
+* use `cargo clippy --all-targets --all-features` to make sure a project is free of lint issues. Please do this every
+  time you reach a stopping point or think you've finished work.
+* run `cargo +nightly fmt --all` to format Rust source files. Please do this every time you reach a stopping point or
+  think you've finished work.
+* you can try running
+  `cargo fix --lib --allow-dirty --allow-staged && cargo clippy --fix --lib --allow-dirty --allow-staged` to
+  automatically many fix minor errors.
 
 ## Architecture
 
@@ -31,8 +35,10 @@
 * Use `vortex_err!` to create a `VortexError` with a format string and `vortex_bail!` to do the same but immediately
   return it as a `VortexResult<T>` to the surrounding context.
 * When writing tests, strongly consider using `rstest` cases to parameterize repetitive test logic.
-* If you want to create a large number of tests to an existing file module called `foo.rs`, and if you think doing so would
-  be too many to inline in a `tests` submodule within `foo.rs`, then first promote `foo` to a directory module. You can do
+* If you want to create a large number of tests to an existing file module called `foo.rs`, and if you think doing so
+  would
+  be too many to inline in a `tests` submodule within `foo.rs`, then first promote `foo` to a directory module. You can
+  do
   this by running `mkdir foo && mv foo.rs foo/mod.rs`. Then, you can create a test file `foo/tests.rs` that you include
   in `foo/mod.rs` with the appropriate test config flag.
 * If you encounter clippy errors in tests that should only pertain to production code (e.g., prohibiting panic/unwrap,
@@ -45,3 +51,7 @@
 ## Other
 
 * When summarizing your work, please produce summaries in valid Markdown that can be easily copied/pasted to Github.
+
+## Commits
+
+* All commits must be signed of by the committers in the form `Signed-off-by: "COMMITTER" <COMMITTER_EMAIL>`.