rustdoc-maintenancelisted

## Outcome Deliver accurate, navigable public API documentation whose examples exercise the supported API, whose safety and failure contracts match the code, and whose verification evidence is reported without suppressing warnings or fabricating unavailable runs. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Use the target repository's Rust toolchain, MSRV, edition, enabled targets, features, and rustdoc lint policy; Edition 2024 examples require Rust 1.85 or newer. Network access is optional for checking current rustdoc guidance. If unavailable, rely on the installed toolchain and report the freshness limitation. Native-client compatibility remains unverified until a dated report records the client version and exact source commit. ## Use this skill when - Public `//!` crate/module documentation, `///` item documentation, intra-doc links, or examples drift after an API or behavior change. - A library needs a coordinated public-surface audit across one or more crates. - Doctests, rustdoc lints, feature-gated docs, or `# Errors`, `# Panics`, or `# Safety` contracts need focused review. - A no-op rustdoc audit must prove the public documentation still matches current code. ## Do not use this skill when - The deliverable is README, architecture, contributor, operations, or agent-facing Markdown; use `rust-workspace-documentation`. - The task is a private implementation comment or a narrow prose correction with no public contract implications. -