Distillation

Date: Jul 21, 2026

• 🔴 (16:02) User stated working directory is /home/byk/Code/getsentry/craft on branch feat/prefixed-tags.
• 🔴 (16:02) User's goal: design native "workspaces" support for the getsentry/craft codebase — letting ONE repository release multiple independently-versioned products (examples: cli@1.2.3, mcp@2.0.0), ideally from a SINGLE top-level .craft.yml, with a product/workspace selector.
• 🔴 [rejected-approach] (16:02) User explicitly instructed: do NOT write code — only read/investigate actual source and report findings.
• 🟡 (16:02) User requested a precise, file:line-cited map of every place in craft that would need to become workspace-aware, covering 8 areas: (1) config schema & loading in src/config.ts and src/schemas/project_config.ts — shape of CraftProjectConfig/CraftProjectConfigSchema, targets/github/releaseBranchPrefix/changelog/versioning/minVersion fields, functions getConfiguration(), loadConfigurationFromString(), getConfigFileDir(), findConfigFile(), getGlobalGitHubConfig(), getGitTagPrefix(), getVersioningPolicy(), and whether existing sub-configs/matrices/.passthrough() extension points exist; (2) the prepare command flow in src/commands/prepare.ts — version computation (auto/calver/explicit), latest tag lookup, release branch creation via releaseBranchPrefix, changelog writing, commit/push, and every call site of getGitTagPrefix/getLatestTag/getVersioningPolicy/getGlobalGitHubConfig; (3) the publish command flow in src/commands/publish.ts — release branch discovery, version resolution, iteration over targets, publish_repo/publish-issue mechanism, target instantiation, and github target's tag/release creation (versionToTag, tagPrefix, isLatestRelease, make_latest); (4) publish_repo/publish issue mechanics — searches for publish_repo, publish, issue creation/accepted label, composite GitHub Action (action.yml/.github), and why a reviewer worried a per-.craft.yml-per-product model could break the publish repo with 2 .craft.yml files vs 1; (5) CLI entry & arg parsing in src/index.ts and yargs builders per command — how a new global --workspace <name> option/positional would be added and how env/config defaults layer; (6) version/tag utilities in src/utils/version.ts, src/utils/git.ts, src/utils/calver.ts, src/utils/changelog.ts, src/utils/autoVersion.ts — every function taking/deriving tagPrefix/latest tag/release branch and what's already prefix-aware after the feat/prefixed-tags work; (7) precedents for grouping — per-target overrides of global config, npm workspaces detection in npm target, an expandWorkspaceTargets function possibly in src/commands/targets.ts, and a full grep for workspace across the repo; (8) tests that would need to change and existing test patterns for config/prepare/publish.
• 🟡 (16:02) User requested deliverable structured as: (a) current single-product release data-flow end-to-end with file:line cites; (b) inventory of every touchpoint a workspace selector must thread through; (c) any existing workspace-named code; (d) exact publish_repo/publish-issue behavior and concrete risk with multiple .craft.yml files; (e) schema extension points.
• 🟢 (16:02) Assistant began responding, stating it will research the codebase systematically, starting by confirming the correct git branch and getting an overview.