Review documentation of Jujutsu changes

Review the Jujutsu changes for the target revision, and report documentation that no longer matches the code.

Follow the common review instructions: @../review-common.md

Scope

Documentation covers:

• AGENTS.md, README.md, and any other documentation file
• diagrams and schemas
• code comments and docstrings

Main goals

Find documentation that:

• contradicts the code: stale command, renamed item, removed option, changed default or behavior
• describes something the change deleted
• is missing for something the change introduced, and that a reader could not guess
• lists cases where a term covering them all would serve the reader as well, above all when the change grew it by appending its own case

Also report comments and docstrings that break the rules of the "Comment and docstring style" section of AGENTS.md.

Guidelines

• Quote both the code and the documentation that contradict each other
• Fix documentation that is out of sync, only delete it when what it describes is gone
• When documentation lists cases and the change adds one, reword it around a term that covers them all rather than append the new case; keep the list only where the reader needs each case named, such as a reference of options, and never trade precision the reader needs for a vaguer term
• Be sparing with new documentation, do not propose any for its own sake
• Stay on documentation: correctness, readability and test coverage are covered by other review domains

Severity

Anchor severity to what the documentation makes its reader do:

• critical — following it destroys state or costs work that cannot be recovered
• major — it contradicts the code and sends the reader down a path that does not exist
• minor — a style rule break, an enumeration a general term would replace, or documentation missing where the code already says it