Always verify workflow run results and identify the next manual step after triggering CI/CD

After triggering a GitHub Actions workflow (release, build, publish), check all job statuses to confirm success, then identify the specific next manual action. For Craft-based releases: find the publish issue URL from workflow logs, verify CI passes on the release/X.Y.Z branch, then add the accepted label to trigger npm publish. Track each job individually. The workflow run is a checkpoint — always ask 'what do I need to do next?' Also watch for deprecation warnings (e.g. app-id → client-id in actions/create-github-app-token@v3) and fix them in follow-up PRs.