Distillation

Date: Aug 29, 2026

• 🟡 (12:34) User provided src/commands/workspace.ts: yargs command workspace <command> (“Manage release workspaces”) requires a subcommand via yargs.demandCommand().command(list) and has a no-op handler; it imports ./workspace_cmds/list.
• 🟡 (12:34) User provided src/commands/workspace_cmds/list.ts: workspace list (“List defined release workspaces as a JSON array”) calls console.log(formatJson(getWorkspaceNames())).
• 🔴 (12:34) User stated that minimal-version compatibility logic relaxes only the current Craft-version side, never the configured minVersion side.
• 🟡 (12:35) User provided src/schemas/project_config.ts: WorkspaceSchema represents named independently-versioned release units, inherits optional releaseUnitFields from top-level config, permits partial github overrides but rejects github.projectPath; WorkspaceNameSchema accepts only /^[A-Za-z0-9_.-]+$/ and rejects "__proto__" to prevent prototype mutation. CraftProjectConfigSchema.workspaces is z.record(WorkspaceNameSchema, WorkspaceSchema).optional(), requires a selected workspace when nonempty, remains backward-compatible when absent, and rejects top-level github.projectPath when workspaces exist.
• 🟡 (12:35) User provided src/index.ts: CLI imports/registers workspace, declares global string --workspace with CRAFT_WORKSPACE documentation, and calls setActiveWorkspace(extractWorkspaceSelection(argv)) before yargs parsing because command builders can access/validate config before middleware. CLI precedence is delegated to extractWorkspaceSelection; middleware remains setGlobals.
• 🔴 (12:35) User stated that a following option such as --workspace --dry-run must never be mistaken for a workspace name.
• 🟡 (12:35) User provided src/utils/helpers.ts: extractWorkspaceSelection(argv, env) uses node:util parseArgs with options: { workspace: { type: 'string' } }, allowPositionals: true, strict: false, and tokens: true; supports --workspace foo and --workspace=foo; last occurrence controls selection; a bare/empty final workspace option clears an earlier CLI value and falls back to env.CRAFT_WORKSPACE; inline option-looking values such as --workspace=-foo are valid, while separated --workspace --foo is invalid.
• 🟡 (12:35) User provided src/__tests__/action.test.ts: action tests verify Craft Prepare and Read Craft Targets pass option-looking workspace input inline as --workspace=--config-from=untrusted; both steps receive ${{ inputs.workspace }} and Validate workspace receives ${{ inputs.path }}. Validation is the first action step and rejects control/tab, Unicode RTL-format (\u202e), line-separator (\u2028), paragraph-separator (\u2029), and non-ASCII (cli-é) workspace values before git/Craft side effects, including UTF-8 locale; accepts '' and cli-v2; rejects simultaneous workspace cli plus path packages/cli, and rejects cli/v2. Publish issue titles are publish: getsentry/toolkit@1.2.3 without workspace and publish: getsentry/toolkit/cli@1.2.3 with workspace cli.
• 🟡 (12:35) User provided src/utils/publishState.ts: publish-resume state was moved from repository-local .craft-publish-<version>.json to $XDG_STATE_HOME/craft/ or fallback $HOME/.local/state/craft/ to prevent committed repository files/earlier CI steps from pre-populating completed targets. getPublishStateFilename() uses sanitized owner/repo, 12-character SHA-1 cwd hash, sanitized version, and optional losslessly Base64url-encoded workspace-<name>- prefix; without GitHub config it uses a 16-character SHA-256 cwd hash. getPublishStatePath() joins this filename under getCraftStateDir(), isolating same-repository/same-version workspace publish state.
• 🟡 (12:35) User referenced script path /home/byk/Code/getsentry/publish-workspace-acceptance/scripts/generate-publish-issue-title-parser.js.