Distillation

Date: Aug 29, 2026

• 🟡 (01:45) Assistant identified a deployment prerequisite: the Publish controller needs a Craft image that already supports craft workspace list; it planned to verify an immutable published Craft image before pinning a tag, and stated that without one the compact workspace-title contract cannot safely be deployed.
• 🟢 (01:47) A file search returned No files found.
• 🟡 (01:49) GitHub Packages API request failed with HTTP 403 Forbidden: You need at least read:packages scope to get a package's versions. The token scopes shown were gist, read:org, repo, workflow, lacking read:packages; rate-limit state was 4999 remaining of 5000.
• 🟡 (01:51) Assistant concluded the available token could not verify Craft image tags through the Packages API because it lacked read:packages; it chose to check the registry manifest directly and reconcile the Publish workflow with current scripts before modifying checkout order.
• 🟡 (01:52) Working tree status showed modified package.json and src/modules/details-from-context.js; untracked pnpm-lock.yaml, scripts/, src/modules/__tests__/publish-location.js, src/modules/__tests__/release-revision.js, src/modules/publish-issue-title.js, src/modules/publish-issue-title.peggy, src/modules/publish-location.js, src/modules/release-revision.js, src/publish/resolve-location.js, and src/publish/resolve-release-revision.js.
• 🟡 (01:54) Direct registry lookup initially returned manifest unknown.
• 🟡 (02:12) A subsequent registry manifest response was schema version 2 with media type application/vnd.docker.distribution.manifest.v2+json, config digest sha256:abb53760ea136432ba8f0f3606418b64b5ee660c4689c5aff3e2b8478d85580b (size 18163), and 16 gzip rootfs layers, including largest layers sha256:014e164aff3c8afb9526c162f2687830985ba8c055679d71deb1c74c1fe0a9f7 (982498837 bytes) and sha256:6cb3bd517303b784076ac73500b6365e47d5df5b045651af243c4d625f17a069 (904429468 bytes).
• 🟡 (02:13) Assistant stated ghcr.io/getsentry/craft:2.31.0 is not yet published and therefore cannot currently be used for testing or production. It chose to keep the controller pinned to immutable tag 2.31.0, explicitly rejecting fallback to latest; Craft release/image publication is a deployment prerequisite.