Update Documentation from Changes

Update documentation from current behavior. Use checked-in source, tests, and accepted product scope as behavior authority.

Establish the range

For Docs / Author Post-Merge Catch-Up, inspect changes from the latest reachable semver tag through the exact pushed main commit. Do not advance either boundary while authoring. For a direct documentation task, use the commit range supplied by the user or current checkout context.

Release-entry completion belongs to nemoclaw-maintainer-evening, not this workflow.

For an existing managed draft, extend its staged changes after the workflow merges them with main. Preserve previous documentation changes unless current source and tests justify a revision or removal. The independent reviewer checks those revisions against the previous draft commit.