chore(spec): refresh Brale OpenAPI contract

[github-actions]

Brale's upstream OpenAPI bytes changed. This PR updates the vendored
document and its SHA-256/fetch-date pin. A semantic contract change
also proposes a CLI version and changelog entry from trusted main.
Documentation-only or formatting-only updates keep the version unchanged.
Contract changes conservatively propose a minor release before 1.0,
and a major release from 1.0 onward; review the diff and adjust the
proposed version and release note when appropriate before merging.
A merged version change enters the draft-release build workflow.

Upstream SHA-256: fd1edeaad80666809e719034c20042c7ed26c3fb13e9c05828e27ed8367c0857

Compatibility job: success.
Container step: success.
The intended sequence is nub run check, nub run build, nub run knip,
and nub run jscpd, stopping at the first failure. Setup, download,
validation, or container startup failures mean checks are NOT RUN.
Later checks after a failure are NOT RUN. Inspect the run logs for the commands actually started and their results.

Preparation installs no project dependencies. Compatibility runs on a
separate runner in a credential-free, offline container. The publisher
validates the preparation artifact and reconstructs the pin, version,
and changelog from trusted source; compatibility code cannot replace
the proposed files. The artifact contains no package or changelog files.

Review the contract diff, then close and reopen this draft PR as a
maintainer to trigger pull-request CI under this repository's actor
policy. Confirm all seven required checks appear on the current PR
revision and pass before marking it ready, requesting approval, or
merging. Manual CI dispatch remains useful for diagnostics;
verify the required checks attached to this PR itself. Required human
review and branch protections still apply; this bot never approves or merges.

This branch belongs to the bot and may be replaced on the next run.
Make compatibility fixes on a separate branch.