fix: keep release verification in release job

[intel352]

Summary

• Move runtime capability verification out of the registry notification job
• Run verification in the release job where wfctl and dist/artifacts.json exist
• Keep the registry dispatch job focused on dispatching after release success

Verification

• ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "workflow yaml ok"'\n- git diff --check

[Copilot]

Pull request overview

This PR moves the runtime capability verification step into the release job so it runs where wfctl and dist/artifacts.json are available, and keeps the registry notification job focused solely on dispatching after a successful release.

Changes:

• Relocated the “Verify capabilities (runtime truth-check)” step from notify-workflow-registry into release.
• Simplified notify-workflow-registry to only trigger the downstream repository-dispatch event after release completes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.