chisel-auth 0.2.2

[package]
name = "chisel-auth"
description = "Platform side of Chisel Docs: identity, assets, and the tamper-evident document audit trail: composed from the WyattAu kit estate"
# Literal, not workspace-inherited: tokenkit 0.4 to 1.0 is breaking for
# this crate's public API (ChiselClaims carries tokenkit::claims), while
# the sibling crates did not change. The next lockstep bump realigns it.
version = "0.2.2"
edition.workspace = true
license.workspace = true
repository.workspace = true
rust-version.workspace = true

[dependencies]
chisel-kernel.workspace = true
oauth-toolkit.workspace = true
tokenkit.workspace = true
webauthn-kit = { version = "0.4", features = ["serde"] }
chrono.workspace = true
serde.workspace = true
serde_json.workspace = true
thiserror.workspace = true

# Feature unification for the wasm32 web build: oauth-toolkit/tokenkit pull
# getrandom 0.3 transitively; getrandom 0.3 gates wasm32-unknown-unknown behind
# this feature, paired with the getrandom_backend cfg in .cargo/config.toml.
# Native targets never see it.
[target.wasm32-unknown-unknown.dependencies]
uuid = { version = "1", features = ["rng-getrandom"] }
getrandom = { version = "0.3", features = ["wasm_js"] }
# tamper-audit's own wasm32 table pulls getrandom 0.4 (uuid's rand backend);
# unify the feature so both majors compile on the web target.
getrandom_04 = { package = "getrandom", version = "0.4", features = ["wasm_js"] }

[dev-dependencies]
# Real-crypto ceremony fixtures mirror webauthn-kit's own vectors suite: an
# ES256 keypair (ring), CTAP2 CBOR attestation objects (ciborium), and the
# authData hash (sha2). Versions align with the kit's own graph so nothing
# new is compiled.
ciborium = "0.2"
ring = "0.17"
sha2 = "0.10"

[lints]
workspace = true