Distillation

Date: Aug 29, 2026

• 🔴 (13:19) User asserted that new Craft publish requests always include the checkout repository identity.
• 🔴 (13:19) User asserted that the controller never normalizes names; workspace names preserve exact spelling.
• 🟡 (13:19) docs/publish-issue-format.md defines canonical publish-title EBNF: title = "publish: ", [ "getsentry/" ], repository, [ path ], [ legacy-workspace ], "@", version; path consists of /-separated token segments; legacy-workspace = " [workspace: ", json-string, "] "; tokens allow ASCII letters, digits, ., _, and -; versions additionally allow +.
• 🟡 (13:19) New root-workspace release titles use a trailing path segment as the workspace name, e.g. publish: getsentry/sentry@21.3.1 and publish: getsentry/toolkit/cli@1.2.3; Craft rejects a workspace with a non-root checkout path.
• 🟡 (13:19) New-title workspace names must match ^[A-Za-z0-9_.-]+$. For an ambiguous one-segment suffix, the controller first checks out the exact CI-approved revision from the View check runs link, then reads exact workspace keys via craft workspace list when root .craft.yml exists; only an exact key match is a workspace, otherwise the suffix remains a checkout path.
• 🟡 (13:19) A missing root .craft.yml always selects checkout-path behavior; workspace-discovery errors when root configuration exists fail the release.
• 🟡 (13:19) Existing legacy JSON-qualified workspace titles remain parse-compatible but are never newly created by Craft, e.g. publish: getsentry/toolkit [workspace: "cli/v2"] @1.2.3 and publish: getsentry/toolkit [workspace: "cli [preview] \"next\""] @1.2.3; legacy workspace titles also require the repository root path.
• 🟡 (13:19) Legacy <json-string> must be one valid double-quoted JSON string decoding to a nonempty workspace name without Unicode Cc, Cf, Zl, or Zp characters. Legacy titles require one space after ] before @; unqualified titles have no space before @.
• 🟡 (13:19) Existing-issue parsing continues to accept an optional getsentry/ prefix; publish-title paths may not contain a .. segment.
• 🟡 (13:19) Publish-issue body fields are Requested by: @<actor>, optional Merge target: <branch-or-(default)>, Quick links for View changes and View check runs, acceptance guidance, and a ### Targets checklist. Merge target (default) selects the target repository’s default branch; explicit branches may contain letters, digits, _, ., /, and -.
• 🟡 (13:19) The workflow reads checked - [x] <target-id> entries in ### Targets; checked entries are preserved when Craft refreshes an existing request. On release failure, target checkboxes are updated from Craft’s secure publish-state file; checked targets are skipped on retry unless manually unchecked.
• 🟡 (13:19) In publish issues, requester, quick links, approval guidance, and optional changelog are informational; the accepted label starts publishing and dry-run requests dry-run mode.