Distillation

Date: Sep 5, 2026

• 🔴 (01:09) User stated new Craft requests always include the checkout repository identity.
• 🔴 (01:09) User stated the controller never normalizes names.
• 🔴 (01:09) User stated a missing root .craft.yml always means checkout-path behavior.
• 🟡 (01:09) Publish workflow and documentation change workspace-release title suffixes from one trailing workspace-name segment to the workspace’s full concrete path; e.g., root workspace releases retain one trailing path segment, while nested workspaces use paths such as packages/cli.
• 🟡 (01:09) Publish-title resolution now occurs after checkout of the exact CI-approved revision linked by View check runs; with a root .craft.yml, craft workspace list supplies exact concrete workspace paths. A complete suffix matching one of those paths is a workspace; every other suffix remains a checkout path. Workspace-discovery errors when root configuration exists fail the release.
• 🟡 (01:09) Repository identities must follow the same safe-token rule and cannot be ., .., __proto__, or begin with -; Craft semantic versions must be valid, including build metadata such as 4.2.6+sentry1.
• 🟡 (01:09) src/publish/resolve-location.js tests were updated so a monorepo workspace release resolves path: "./packages/cli" against workspaceNames: ["packages/cli"], replacing the prior root-level ./cli / ["cli"] fixture; test coverage also includes invalid suffix example "packages/../cli".
• 🟡 (01:09) Publish changes modify .github/workflows/publish.yml, docs/publish-issue-format.md, src/modules/__tests__/ci-poller-input.js, src/modules/__tests__/details-from-context.js, src/modules/__tests__/publish-location.js, src/modules/__tests__/publish-workflow.js, src/modules/ci-poller-input.js, src/modules/details-from-context.js, src/modules/publish-issue-title.js, src/modules/publish-issue-title.peggy, src/modules/publish-location.js, and src/publish/resolve-location.js; the diff also includes untracked src/modules/publish-issue-validation.js.