Move the Dispatch-Refresh Note Out of the Docker Clause in branching-and-release-model #3588

The no-op publish bullet in .agents/skills/branching-and-release-model/SKILL.md attaches a GitHub Releases fact to the Docker exception:

Docker is the exception: it always re-pushes (a dispatch refreshes the release instead of skipping) to pick up upstream base-image refreshes.

Its source, references/release-publish-mechanics.md "No-op republish guarantee", says the dispatch refresh belongs to GitHub Releases. There the github-release job's release-exists check skips the create step on a scheduled or push publish, and a dispatch refreshes the release instead. The Docker sentence there says only that Docker always re-pushes to pick up upstream base-image refreshes.

A reader of the skill alone can take the parenthetical to describe Docker, or conclude that a GitHub Release is never refreshed. The fix moves the parenthetical out of the Docker sentence. It can go onto a GitHub Releases clause, or be dropped in favor of the pointer to the reference file. The text predates the sentence-length sweep, which left it unchanged in #3585.