doc-updatelisted

# Documentation Update - Treat documentation as a contract: verify commands, flags, paths, versions, examples, and behavior before writing them. - Use current repository evidence for local claims and current authoritative primary sources for platform or compatibility claims; date unstable claims. - Separate current behavior from proposals, limitations, and pending work. Never promote an assumption or unavailable check into fact. - Keep examples public and repository-relative; do not commit personal paths, credentials, private hosts, or machine-specific output. Finish when shown commands and links resolve, factual claims have applicable evidence, and generated or related docs agree.