Distillation

Date: Sep 5, 2026

• 🔴 (01:25) User stated new Craft requests always include the checkout repository identity.
• 🔴 (01:25) User stated a missing root .craft.yml always means checkout-path behavior.
• 🔴 (01:25) User stated the controller never normalizes names.
• 🟡 (01:25) Publish workflow diff removes the requires_workspace_discovery Node invocation from .github/workflows/publish.yml around the publish job’s workspace-state setup; the surrounding script initializes workspace_names='[]' and creates "$state_dir" with mkdir -p "$state_dir". Full removed/added workflow logic was elided.
• 🟡 (01:25) Publish issue-format documentation changes: workspace releases now use the full concrete path as the title suffix, replacing the prior one-trailing-segment workspace-name convention for root-workspace releases.
• 🟡 (01:25) Publish issue-format documentation states repository identities follow the safe-token rule and cannot be ., .., __proto__, or begin with -.
• 🟡 (01:25) Publish issue-format documentation states versions must be valid Craft semantic versions and that build metadata, exemplified by 4.2.6+sentry1, is valid.
• 🟡 (01:25) Publish controller documentation states it resolves the complete title suffix only after checking out the exact CI-approved revision from the View check runs link.
• 🟡 (01:25) Publish controller documentation states that, if the exact CI-approved checkout contains root .craft.yml, craft workspace list supplies exact concrete workspace paths; a suffix exactly matching one path is a workspace, while every other suffix remains a checkout path.
• 🟡 (01:25) Publish controller documentation states discovery errors fail the release when root configuration exists.
• 🟡 (01:25) Documentation removes legacy JSON-qualified workspace-title compatibility details, including examples publish: getsentry/toolkit [workspace: "cli/v2"] @1.2.3 and publish: getsentry/toolkit [workspace: "cli [preview] \"next\""] @1.2.3; it also removes the former JSON-string character restrictions and spacing rules. Whether compatibility was removed from implementation is unverified because the diff content is elided.
• 🟡 (01:25) Test diff retains/updates keeps a non-workspace suffix as a checkout path, expecting { path: "./packages" }.
• 🟡 (01:25) Test diff adds or includes unsafe path input packages/../cli; full assertion and validation outcome are elided.
• 🟡 (01:25) In the monorepo state-filename alignment test, resolvePublishLocation() input changes from path: "./cli", workspaceNames: ["cli"] to path: "./packages/cli", workspaceNames: ["packages/cli"], then passes location.path to runSetTargets().
• 🟡 (01:25) The generated publish-issue-title parser output is modified extensively, including parser state/error-handling code; exact grammar and generated-parser parity remain unverified because the relevant diff is elided.