v0.3.1

[eareimu]

h3x v0.3.1

This is a release-engineering patch release that makes the published h3x
manifest converge on crates.io for released cross-repository dependencies.

Why this release exists

v0.3.0 is already published, but its released Cargo.toml still referenced
upstream genmeta crates through GitHub git sources:

• dhttp-identity through the dhttp repository
• dquic through the dquic repository

That can work for some development flows, but it is not a stable release
convergence surface for downstream crates. Cargo treats different source
identities separately, so a downstream graph that mixes git-based genmeta
dependencies with crates.io-based genmeta dependencies can resolve duplicate
instances of the same crate family.

v0.3.1 exists to remove that ambiguity from the released h3x manifest and
make crates.io the stable source of truth for already-published upstream
dependencies.

What changed

This release intentionally makes a minimal manifest-only change:

• bumped h3x from 0.3.0 to 0.3.1
• replaced the released git dependency on dhttp-identity with the published
  crates.io dependency dhttp-identity = "0.1.0"
• replaced the released git dependency on dquic with the published
  crates.io dependency dquic = { version = "0.5.1", optional = true }
• removed all remaining git = ... dependency entries from the released
  Cargo.toml

No protocol implementation, feature topology, or intended public API behavior
change is introduced by this patch release.

Dependency-source convergence

After this release, downstream repositories that depend on published h3x
should consume:

• h3x from crates.io
• released upstream genmeta crates from crates.io
• not reintroduce released git dependency edges where a published crates.io
  version already exists

This release is specifically intended to support release-wave convergence across
the wider genmeta dependency graph.

Verification

Release-readiness verification was run against the registry-only manifest state:

• cargo check --locked
• cargo test --all-features --all-targets
• cargo clippy --all-targets --all-features -- -D warnings
• cargo publish --dry-run --locked

Verification was performed from outside the reimu root patch context so the
result reflects published dependency resolution rather than local sibling
overrides.

Upgrade notes

• downstream repositories should update to h3x 0.3.1 if they need a released
  manifest without git dependency edges
• no code-level migration is expected beyond normal version bump adoption
• this release should be preferred over v0.3.0 for downstream release work

Full changelog: v0.3.0...v0.3.1