Workspace dependency audit (2026-05)
Workspace dependency audit (2026-05)
Section titled “Workspace dependency audit (2026-05)”Rolling closure from the workspace dependency audit v2 plan:
Completed in-tree
Section titled “Completed in-tree”regress: kept as a real dependency ofvox-research-events: typify-generatedschema_types.generated.rsreferences::regress::Regexfor pattern-backed string types (grep there before treating it as removable).- Workspace inheritance: external crates in high-churn manifests use
{ workspace = true }with versions centralized in rootCargo.toml. schemars0.8 vs 1:vox-scientia-jsonschema-codegendepends on workspace aliasschemars08(package = "schemars", version = "0.8") while the rest of the workspace stays onschemars1.x /typify0.6.x until a typify upgrade is scoped.- LSP stack: consolidated on
tower-lsp-server/ls-types(Uriinstead of legacyUrl). - Heavy retrieval:
vox-searchdefaults omit lexical/scrape; consumers opt in via features (tantivy-lexical,web-scrape). - Pins: workspace carries current lines for
thiserror2,wasmtime/wasmtime-wasi44,self_update0.44,tokio-tungstenite0.29, etc., per lockfile verification (cargo check --workspace).
Intentional duplicates / deferred
Section titled “Intentional duplicates / deferred”- Candle / QLoRA / zip: multiple
zipmajors remain via Candle vs other consumers; upgrade needs GPU CI and ADR 034. - Rand 0.8 vs 0.9: workspace uses
rand09alias where Oratio STT needs 0.9 APIs; broader unification waits on Wasmtime/Tantivy upstreams. syn1.x: remains viaabi_stable_derive(plugin ABI risk).- tiktoken-rs: not replaced by heuristics —
cl100k_baseis used for accurate budgeting (vox-orchestrator).
Local evidence artifacts
Section titled “Local evidence artifacts”Optional snapshots (gitignored): .tmp_audit/duplicates.after.txt, .tmp_audit/shear.after.json — regenerate with:
& "$env:USERPROFILE\.cargo\bin\cargo.exe" tree --workspace --duplicates --depth 0 > .tmp_audit/duplicates.after.txt& "$env:USERPROFILE\.cargo\bin\cargo.exe" shear --format json > .tmp_audit/shear.after.jsonPolicy
Section titled “Policy”See Dependency policy.