rust-workspace-documentationlisted

## Outcome Produce a reviewed, evidence-backed documentation change that describes the repository as it currently behaves, preserves clear ownership between documents, and leaves validation claims traceable to commands that actually ran. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Work against the target repository's Rust toolchain, MSRV, edition, workspace layout, lockfile policy, and documented commands; Edition 2024 examples require Rust 1.85 or newer. Network access is optional: use current primary sources when allowed, otherwise identify which external guidance could not be refreshed. Native-client behavior is unverified until a dated report records the client version and exact source commit. ## Use this skill when - A Rust change alters commands, modules, crate ownership, workflows, configuration, examples, compatibility, or validation and several repository-owned Markdown surfaces may drift. - The task is to audit or refresh README files, architecture documents, contributor guides, operational runbooks, agent instructions, or an explicit documentation inventory as one pass. - A branch or worktree needs a no-op documentation audit whose result must be supported by source and diff evidence. ## Do not use this skill when - The requested output is exclusively public API documentation, `//!`/`///` comments, or doctests; use `rustdoc-maintenance`. - The user asks for a localized copyedit and does not need repository-wide reconciliation.