Distillation

Date: Aug 29, 2026

• 🟡 (00:06) Project task status: high-priority “Fix reviewed Craft workspace-key and locale validation blockers” completed; high-priority “Run Craft verification and adversarial review” in progress; high-priority “Implement Publish compact-title checkout resolution” in progress; high-priority “Add compact-title cross-repository regression coverage” pending; high-priority “Verify, push, and monitor linked PRs” pending; low-priority “Document workspace migration” pending.
• 🟡 (00:07) Assistant stated it had added the release-revision extractor and would wire it into the Publish workflow so it checks out the ci-ready revision before resolving a compact title, creating state, or starting Craft.
• 🔴 (00:08) User stated the CI poller always adds ci-ready.
• 🟡 (00:08) .github/workflows/publish.yml comments describe a waiting-for-ci flow that adds ci-pending and removes ci-failed when retrying; the publish job is named Publish a new version and is intended not to conflict with waiting-for-ci on the same event because the poller adds ci-ready.
• 🟡 (00:10) src/modules/publish-location.js exports resolvePublishLocation({ path, workspace, workspaceNames }): an explicit workspace returns { path, workspace }; otherwise it validates every discovered name with isWorkspaceName(), converts a single-segment ./<name> path into { path: ".", workspace: <name> } when <name> is in workspaceNames, and otherwise returns { path }.
• 🟡 (00:10) src/modules/publish-location.js rejects invalid workspace-discovery entries with Craft workspace discovery returned an invalid workspace list.; isWorkspaceName(name) requires a string other than __proto__ matching /^[A-Za-z0-9_.-]+$/.
• 🟡 (00:12) src/publish/resolve-location.js reads PUBLISH_ARGS as JSON and CRAFT_WORKSPACE_NAMES as JSON defaulting to "[]"; it rejects a non-array CRAFT_WORKSPACE_NAMES value with Craft workspace discovery returned an invalid workspace list., calls resolvePublishLocation({ path: input.path, workspace: input.workspace, workspaceNames }), and writes the result through core.setOutput("result", ...).
• 🟡 (00:15) craft-workspace-action-propagation/.github/workflows/image.yml runs on pull_request and pushes to master, release/**, and test-me-*; its image job runs on ubuntu-latest with contents: read and packages: write.
• 🟡 (00:15) image.yml checks out via actions/checkout@v6; builds ghcr.io/getsentry/craft-builder:latest with docker buildx build --target builder, optionally using --cache-from after docker pull -q; then builds ghcr.io/getsentry/craft:latest with SOURCE_COMMIT=$GITHUB_SHA and BUILDKIT_INLINE_CACHE=1.
• 🟡 (00:15) image.yml logs into ghcr.io as ${{ github.actor }} using ${{ secrets.GITHUB_TOKEN }} only when the event is not pull_request; it then pushes ghcr.io/getsentry/craft-builder:latest, tags ghcr.io/getsentry/craft:latest as ghcr.io/getsentry/craft:${GITHUB_SHA}, and pushes both the versioned tag and latest.
• 🟡 (00:15) Assistant identified that the old Publish workflow branches from a mutable default/allowlisted target branch and creates state before checkout. It stated the replacement sequence: parse title syntax; extract the poller-approved SHA; check out that SHA; discover workspace keys; resolve the suffix; then create state and publish from the resolved location.