[operator] Treat Sparkle no-update cycles as successful

[r3dbars]

Summary

• handle Sparkle finish-cycle code 1001 as a no-update success instead of update_check_finished:error
• add a repo contract test so finish-cycle no-update errors stay ahead of the generic failure path

Verification

• TRANSCRIPTED_DISABLE_FILE_LOGGER=1 bash build.sh --no-open
• TRANSCRIPTED_DISABLE_FILE_LOGGER=1 bash run-tests.sh

[r3dbars]

verdict: no-findings-but-human

findings: none. The Sparkle 1001 finish-cycle path now returns through the no-update success path before generic failure tracking, with a contract test guarding that ordering.

actions: no fix pushed.
current_head_sha: a097d5e
fix_commit: none
checks: repo-hygiene pass; gh pr view; gh pr diff --patch; gh pr checks; git diff --check origin/main...origin/codex/operator-sparkle-no-update-cycle-20260530; Observability/Test docs reviewed.

manual_merge_handoff:
head_sha: a097d5e
verdict: no-findings-but-human
blockers: draft PR; human signoff for Sparkle/update telemetry behavior
checks: repo-hygiene pass; PR metadata/diff/checks reviewed; diff-check clean; Observability docs reviewed