doc: inform about the absence of strict hash verification and strict …

…object creation.

Those are present in `git2` and enabled by default, and `gitoxde` definitely
wants to do the same at some point.

crate-status.md

@@ -615,6 +615,8 @@ See its [README.md](https://github.com/Byron/gitoxide/blob/main/gix-lock/README.
 * [x] utilities for applications to make long running operations interruptible gracefully and to support timeouts in servers.
 * [x] handle `core.repositoryFormatVersion` and extensions
 * [x] support for unicode-precomposition of command-line arguments (needs explicit use in parent application)
+* [ ] strict object creation (validate objects referenced by newly created objects exist)
+* [ ] strict hash verification (validate that objects actually have the hashes they claim to have)
 * **Repository**  
     * [x] discovery
         * [x] option to not cross file systems (default)

gix/src/lib.rs

@@ -75,6 +75,11 @@
 //! * [`git2::build::CheckoutBuilder::disable_filters()](https://docs.rs/git2/*/git2/build/struct.CheckoutBuilder.html#method.disable_filters) ➡ ❌ *(filters are always applied during checkouts)*
 //! * [`git2::Repository::submodule_status()`](https://docs.rs/git2/*/git2/struct.Repository.html#method.submodule_status) ➡ [`Submodule::state()`] - status provides more information and conveniences though, and an actual worktree status isn't performed.
 //!
+//! #### Integrity checks
+//!
+//! `git2` by default performs integrity checks via [`strict_hash_verification()`](https://docs.rs/git2/latest/git2/opts/fn.strict_hash_verification.html) and
+//! [`strict_object_creation`](https://docs.rs/git2/latest/git2/opts/fn.strict_object_creation.html) which `gitoxide` *currently* **does not have**.
+//!
 //! ### Feature Flags
 #![cfg_attr(
     feature = "document-features",