Fix links and commands in the documentation that no longer work
Links that 404 and commands that error, fixed after each one is actually exercised.
The ticket
Fix broken links and non-working commands in the documentation.
Acceptance criteria
- Every link resolves
- Every command is run and its output matches what the documentation claims
- Commands that need credentials are marked as such rather than silently failing
- A link check runs on a schedule afterwards
What lands as proof
Evidence that each command was run, not just read, since a command that errors is worse than no command.
Why teams defer it
- Documentation is reviewed for prose and never executed.
- Commands rot as flags change, and the person following them assumes they made the mistake.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: fix broken links and non-working commands in the documentation. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means each link and each command exercised in the pull request, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.