Distillation

Date: Aug 27, 2026

• 🔴 (15:43) User asserted that workflow_dispatch must always be allowed for manual recovery.
• 🟡 (15:43) .github/workflows/publish.yml defines a cron schedule */5 * * * * (every 5 minutes) and an input with default value "0".
• 🟡 (15:43) .github/workflows/publish.yml contains a check-ci job with configured concurrency.
• 🟡 (15:43) The workflow’s CI-check logic uses RELEASE_TOKEN: ${{ steps.release-token.outputs.token }} and defines a gh_api_release() shell function that returns the underlying API-command exit code.
• 🟡 (15:43) CI poller logic lists open issues, parses titles in the form "publish: owner/repo[/path]@version", obtains repository commit/status information, and uses the commit-check link format https://github.com/{owner}/{repo}/commit/{SHA}/checks/.
• 🟡 (15:43) CI poller logic treats "success", "neutral", and "skipped" check conclusions as passing; comments state all-zero counts mean CI has not started yet.
• 🟡 (15:43) CI poller logic adds the ci-ready label when status is acceptable; a failure path removes ci-pending and a later path removes accepted.
• 🟡 (15:43) The workflow has a Check for remaining pending issues step that writes count=${count} to $GITHUB_OUTPUT.
• 🟡 (15:43) The workflow has a Get poller app token step using ${{ secrets.CI_POLLER_APP_PRIVATE_KEY }}.
• 🟡 (15:43) CI polling is capped at 60 attempts (approximately 30 minutes); workflow comments state this cap applies when CI has not passed by then.