Distillation

Date: Aug 28, 2026

• 🔴 (20:56) User stated that the CI poller always adds the ci-ready label.
• 🟡 (20:56) Workflow excerpt indicates .github/workflows/publish.yml has a waiting-for-ci job and a “Publish a new version” job; the latter is designed not to race with waiting-for-ci on the same event because the poller adds ci-ready.
• 🟡 (20:56) Workflow excerpt shows publish eligibility includes an open issue whose title starts with publish: ; it comments, “Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.”
• 🟡 (20:56) Workflow excerpt shows the publish job checks out the target repository with fetch-depth: 0, passes CRAFT_PUBLISH_REPO from parsed inputs, derives a published-target JSON payload using jq, derives a cwd_hash from container_cwd with sha1sum | cut -c1-12, and base64url-encodes CRAFT_PUBLISH_WORKSPACE when present.
• 🟡 (20:56) Workflow excerpt documents that Craft state must follow the issue checkout identity rather than a workspace checkout identity, and that separate tokens are needed for GHCR.io and GitHub API access.
• 🟡 (20:57) Assistant stated it is restructuring the controller workflow so compact suffixes are resolved only after checking out the CI revision; existing state and publish steps consume the title path too early, and the resolved location will become their only input.