release-docs

# zuvo:release-docs Sync documentation with a release. Only updates docs whose source files actually changed. ## Mandatory File Loading Read these files before proceeding: ``` CORE FILES LOADED: 1. ../../shared/includes/env-compat.md — READ 2. ../../shared/includes/run-logger.md — READ 3. ../../shared/includes/retrospective.md — READ ``` ## Argument Parsing | Input | Effect | |-------|--------| | _(no flags)_ | Auto-detect range from `memory/last-ship.json` or git tags | | `<range>` | Explicit git range (e.g., `v1.1.0..v1.2.0`) | | `--dry-run` | Show proposed changes without writing | --- ## Phase 0: Determine Range and Suffix 1. If an explicit `<range>` argument was provided: use it. Skip remaining steps in this phase. 2. Else if `memory/last-ship.json` exists: read the `range` field (SHA-based, e.g., `"abc1234..def5678"`) and use it directly for `git diff`. Also read `previousTag` and `newTag` for display in the output block. If the artifact uses a legacy version-based range (e.g., `"v1.1.0..v1.2.0"`), fall back to it but log: "Warning: legacy version-based range — consider re-running zuvo:ship for SHA-based artifact." 3. Else: derive from git tags. - Run `git describe --tags --abbrev=0` to get the latest tag. - Run `git describe --tags --abbrev=0 <latest-tag>^` to get the previous tag. - Construct range as `<previous-tag>..<latest-tag>`. 4. If no range can be derived after the above steps: - Interactive environments: ask the user to prov...