claude-release-watch — YAML shape fix

Third attempt to register the workflow's workflow_dispatch trigger. Earlier attempts (PR #1592 explicit form, PR #1593 rename) produced fresh workflow IDs but neither registered the friendly name:, indicating GHA's YAML parser is choking on file content — not on a metadata cache.

Diagnostic comparison

Working file (cc-support-window-bump.yml) registers as CC Support Window Bump. Broken file (claude-release-watch.yml) registers as the file path. Differences in the on: block:

BROKEN

name: claude-release-watch

on:
  schedule:
    - cron: '0 14 * * *'  # comment
  # 6 lines of comments
  # explaining cache-coherency
  workflow_dispatch: {}

WORKING (sibling)

name: CC Support Window Bump
on:
  push:
    branches: [main]
  workflow_dispatch:

The fix

name: Claude Release Watch
on:
  workflow_dispatch:
  schedule:
    - cron: '0 14 * * *'

name: Title Case to match the convention every other registered workflow in this repo uses.
No inline comment after the cron value.
No comment lines inside the on: mapping.
workflow_dispatch: listed first (cosmetic, but matches the sibling order).

What gets dropped

The 6 lines of explanatory comments about the cache-coherency hypothesis. They were never load-bearing — just commentary in the on: block. The broader fix history is in the playgrounds for PRs #1591, #1592, #1593, and this one — all under docs/fix--m130-*/.

Verification

This PR merges to main.
gh workflow list shows the workflow under the friendly name Claude Release Watch instead of the file path.
gh workflow run "Claude Release Watch" --repo yonatangross/orchestkit returns a run URL — no 422.
The dispatched run executes the LLM triage step (with CLAUDE_CODE_OAUTH_TOKEN already configured).

If this still doesn't register the friendly name, the next mitigation is to bisect: copy the working sibling's structure verbatim and gradually add elements until the parser breaks — that pinpoints the YAML token GHA is choking on.