rust-dependencieslisted

# Rust Dependencies **Resolution.** Prefer a maintained crate that already solves the problem idiomatically over template-owned code, and prove the choice before declaring it. Explain what Cargo actually selects before changing its declarations. Honor supplied requirements and preserve settled choices outside the requested change; resolve only what the task leaves open. Before a new crate or a new general mechanism, survey the candidates against the actual requirement and record the comparison in the research synthesis for the current topic under specs: the latest version and release date from the registry, the maintenance signal from the repository, the exact behavior verified in source or in a scratch project outside the repository, known issues, and what the crate does not do. The Go template supplies the problem and its reasons, never the shape of the solution; when Rust solves it differently, record the deviation. Template-owned code exists only for a gap the synthesis names. Declare each version once in the workspace dependency table with default features disabled, enable features per crate, and keep every Cargo invocation locked so a lockfile change ships with the change that caused it. Inspect what actually resolved: the tree with duplicates shown for a second version of the same crate, and the feature-edge view for a feature another dependency turned on. A second OpenTelemetry minor or an unexpected exporter client feature silently sends telemetry to a no-op provi