Distillation

Current State

• As of Aug 28, 2026, 09:36, active work is the approved redesign of the Craft Action ↔ Publish controller workspace request contract. The already-pushed JSON-qualified design remains in linked PRs but is expected to be superseded:
  • Publish/controller PR #9339: https://github.com/getsentry/publish/pull/9339, feat: accept workspace publish requests, OPEN, non-draft, branch feat/workspace-acceptance, base main.
    • Existing commits: 33de3f1 feat: accept workspace publish requests (Aug 26, 14:16) and b658ffa fix: validate publish workspace JSON (Aug 27, 09:16).
    • Head: b658ffa0299fedf78c9dd9a2121cd740691ca157; base: 83d210b29553ea6f4d97508821724a834c43856e.
  • Craft/action PR #872: https://github.com/getsentry/craft/pull/872, feat: propagate release workspaces, OPEN, draft, branch feat/workspace-action-propagation, base master.
    • Existing commit: 6dae341 feat: propagate release workspaces (Aug 26, 14:18).
    • Head: 6dae341f9bc1378abde7a9022108caded2d22226; base: 21270a1d12a60b461c51fba93bd076b90d9cf4af.
  • Publish must deploy before Craft #872 becomes ready/lands because Craft requests must be understood by Publish.
• Both PRs remain blocked only on required review as of Aug 27, 16:07–16:21:
  • Publish #9339: mergeStateStatus: BLOCKED, reviewDecision: REVIEW_REQUIRED. All listed CI/security checks green, including CodeQL Actions/JavaScript, dependency review, Secret Scan, unit tests, Warden runs, Cursor Bugbot, Seer review, Socket, Semgrep, and warden: security-review.
  • Craft #872: draft, mergeStateStatus: BLOCKED, reviewDecision: REVIEW_REQUIRED, no reviews/comments/threads. All listed CI/security checks green, including Node 22/24, build/docs, changelog preview, CodeQL, dependency review, license, lint fixes, image, Warden, Socket, Semgrep, and security review.
  • Publish’s sole bot review is a sentry COMMENTED review submitted Aug 26, 14:25:34 UTC on superseded 33de3f1; its sole report about invalid JSON \q was fixed in b658ffa and resolved. There are no new bot comments.
  • User directive since Aug 27, 09:23 remains: after every push/PR update, monitor bot reviews, review threads, issue comments, CI, and merge state before declaring readiness. Monitoring is ongoing/high priority.
• Current agreed implementation direction, refined through Aug 27, 19:11–Aug 28, 09:27:
  1. New workspace requests use a compact single trailing path segment in the title rather than the current JSON [workspace: "..."] annotation.
  2. Publish resolves that potentially ambiguous suffix only from the exact CI-approved release revision, after checkout—not from default-branch configuration, issue-body metadata, or title regex alone.
  3. Publish determines workspace meaning using exact raw workspace identifiers exposed by a new Craft discovery command (craft workspace list / craft workspaces --json was discussed; final command spelling must be settled before implementation). Names are never normalized.
  4. Workspace-first classifier: for a single trailing title segment, exact membership in the checked-out root configuration’s discovered workspace list means workspace; otherwise it is a checkout path. Per the user correction at Aug 27, 19:26, a missing root .craft.yml means checkout-path behavior; workspace classification does not use a path fallback for other invalid/ambiguous discovery failures without an explicit final contract decision.
  5. Craft must enforce the non-ambiguity boundary: workspace names become safe ASCII title tokens; action rejects a non-root path combined with workspace before any side effect; workspace configurations may not use github.projectPath.
  6. The same pinned revision must control compact classification, state-file path/CWD, CRAFT_WORKSPACE, and craft publish --rev; state filename parity remains mandatory.
  7. Field-less legacy issues must not be converted into a new request. Their legacy route/meaning must remain compatible.
• Important unresolved design tension:
  • The user stated at Aug 27, 10:57 that release configuration at release-cutting time may determine meaning because release branches are materialized and locked down.
  • An adversarial review at 14:31 initially judged the compact-title proposal DO-NOT-MERGE, identifying title collision, CI/revision binding, pre-checkout state setup, workspace grammar mismatch, and path/workspace mutual-exclusion gaps.
  • User rejected introducing versioned/authenticated request metadata in issue bodies at 14:59 (“I would really avoid this”).
  • The later accepted direction is to derive the exact checked revision from the existing CI/check-runs flow and classify against that checkout, with workspace-first behavior. Exact behavior for invalid root configuration/discovery versus path fallback still requires deliberate fail-closed implementation/tests.
• Current task plan as of Aug 28, 09:27:
  1. Completed: Define compact title and release-checkout resolution contract.
  2. In progress: Add Craft workspace discovery and compact-input/configuration safeguards.
  3. Pending: Resolve compact titles from CI-approved Publish checkout, then propagate resolved path/workspace to state and Craft.
  4. Pending: Add focused cross-repository compact-title regression coverage.
  5. Pending: Full verification, adversarial review, push PR updates, and monitor both PRs.
• Worktrees:
  • Craft: /home/byk/Code/getsentry/craft-workspace-action-propagation, branch feat/workspace-action-propagation, based on 21270a1; latest original feature head 6dae341. Confirmed Aug 28, 07:27.
  • Publish: /home/byk/Code/getsentry/publish-workspace-acceptance, branch feat/workspace-acceptance, based on 83d210b; feature head b658ffa.
  • Publish working tree has pre-existing local changes from parser research: modified package.json adds devDependency "peggy": "5.1.0" and untracked pnpm-lock.yaml, observed Aug 27, 23:02 through Aug 28, 01:38. Do not accidentally discard/commit the pnpm lockfile; Publish requires Yarn for any intended lockfile update. The Peggy package pin is not yet a complete parser implementation or committed contract change.
• getsentry/publish default branch is main, not master.
• Historical context remains:
  • Craft PR #848 (feat/workspaces-schema) was admin-squash-merged Aug 25, 10:04:15Z as 21270a1d12a60b461c51fba93bd076b90d9cf4af.
  • Craft PR #844 was closed as superseded 2026-08-25T10:05:27Z.
• User assertions/directives that remain enforced:
  • CI poller always adds ci-ready after checking CI; waiting-for-ci first removes it to ensure a fresh labeled event (repeated Aug 26–Aug 28, latest Aug 28, 09:04).
  • workflow_dispatch must always be allowed for manual recovery in ci-poller.yml (repeated Aug 27–Aug 28, latest Aug 28, 09:06).
  • Always throw for unexpected values; switch default must throw e.g. new Error(\Unknown status: '${status}'`)` (repeated Aug 27–Aug 28).
  • Never normalize workspace names before lookup (Aug 27, 14:31).
  • A separated option token such as --workspace --dry-run must never be interpreted as a workspace name (Aug 27, 21:19).
  • Current-version prerelease relaxation applies only to the current Craft version, never configured minVersion (Aug 27, 20:45; Aug 28, 07:35).
  • New Craft-created requests always include checkout repository identity (Aug 27, 11:31).
  • CDN consumers must pin a version, not “latest” (Aug 27, 10:06).
  • Peggy extra-options-file keys use long two-dash spelling without literal dashes; internally dashed options are camelCase (Aug 27, 10:06).
  • Peggy Unicode-mode matching never matches a lone surrogate (Aug 27, 10:06).
  • Use pnpm, never npm/yarn, for Craft; Publish’s repository-specific declared policy remains Yarn Classic, not npm.
• Note on container image: Publish currently invokes docker://getsentry/craft:latest in publish.yml:236; user’s CDN/version-pin directive may require later review of this use, but no change has yet been made.

Key Decisions

• Merged Craft workspace hardening (#848)
  • #848 was held DO-NOT-MERGE after prototype workspace-selection and cross-workspace resume-state collisions; state isolation was included rather than deferred.
  • Admin squash merge was used because GitHub prevented self-approval.
• Workspace configuration is fail-closed
  • Object.hasOwn(workspaces, workspaceName) is required before lookup, rejecting inherited constructor, toString, and __proto__ selectors while permitting explicitly configured own keys with those names.
  • Workspace selection must not interpret option-looking separate tokens as values; node:util.parseArgs accepts --workspace=-foo but not --workspace --dry-run.
• Original deployed/pushed workspace contract
  • Workspace is a cross-repository identity: selects Craft config/targets, distinguishes/reuses Publish issues, survives controller parsing, selects secure state, restores matching state, and sets CRAFT_WORKSPACE for central publish.
  • Existing no-workspace action/reusable-workflow behavior remains compatible.
  • Controller deployment must precede Action deployment.
• Secure state identity decision
  • Workspace config can partially override github.owner, repo, and/or projectPath, so resolved release GitHub identity can differ from action checkout/title identity.
  • CRAFT_PUBLISH_STATE_GITHUB_REPO=getsentry/<title-repo> is limited solely to Craft’s state filename identity through getPublishStateGitHubConfig; it does not alter actual target/release identity.
  • Publish must pass exact secure state-file path as CRAFT_STATE_FILE_PATH on cancellation/failure; no repository-file fallback is permitted.
• Workspace publish-state filenames
  • Active workspace is Base64URL-prefixed as workspace-${Buffer.from(workspace).toString("base64url")}-; no ordinary sanitization because it collapses distinct legal names.
  • Unscoped filenames are byte-compatible.
  • State uses XDG state only, outside the checkout, to prevent PR-controlled state prepopulation.
• Current pushed title grammar is superseded-in-planning, not yet removed
  • Legacy: publish: <repo><path>@<version>.
  • Scoped: publish: <repo><path> [workspace: <JSON-string>] @<version>.
  • JSON was originally selected for readable/lossless arbitrary workspace names; malformed JSON now produces controlled Invalid publish workspace JSON in title: '<title>'.
  • Existing parser accepts optional getsentry/ for legacy compatibility, but Action-created titles include checkout identity.
• Parser library decision: Peggy
  • Independent research completed Aug 27, 10:08–10:11. Select Peggy 5.1.0 rather than Nearley 2.20.1 or PEG.js 0.10.0:
    • Peggy latest npm release 5.1.0 was 2026-03-01, repository MIT, unarchived, default main, last pushed 2026-03-19.
    • Nearley 2.20.1 latest release was 2020-12-06, repository last pushed 2024-11-14.
    • PEG.js 0.10.0 latest release was 2016-08-19, repository last pushed 2021-11-08.
    • Peggy is maintained PEG.js successor, MIT-licensed, and supports build-time CommonJS parser generation with no production runtime parser dependency.
  • Intended implementation: grammar is canonical EBNF/PEG source; generate and commit CommonJS JavaScript parser; Peggy remains development-only. Documentation: https://peggyjs.org/documentation.html.
  • Earlier direct fetch attempts failed: https://pegjs.org/documentation transport error 10:08; Peggy GitHub metadata transport error 10:05.
• Compact title contract evolution
  • Initial approved concept at Aug 27, 09:52 was to reuse title path segment for safe workspace names, require workspace/github.projectPath mutual exclusivity, make EBNF canonical, and research parser choice.
  • Assistant correctly identified at 10:11 that directly reinterpreting publish: getsentry/toolkit/cli@1.2.3 would change legacy path semantics. A body Workspace: cli discriminator was rejected at 10:41 due to duplicate title identity/collision and fragility.
  • After user’s release-branch immutability assertion at 10:57, direction changed: use release-cutting configuration, not mutable default branch, to classify.
  • User rejected versioned/request metadata body identity at 14:59. Do not add an authenticated request marker/body identity field.
  • Final working direction: retain legacy title/body shapes, pin and check out the CI-approved release revision, then use root-level exact workspace discovery to classify a single trailing segment workspace-first. Action must prohibit workspace + non-root path; workspace config must prohibit github.projectPath.
  • The exact title grammar intended for new compact requests remains to be written in canonical EBNF and generated through Peggy; parser should be syntax-only, while workspace/path semantics live in a separate post-checkout resolver.
• CI/revision binding
  • The poller already obtains an issue check-runs SHA, resolves release branch head where possible, updates check-run link, checks statuses and paginated check runs, and labels ci-ready only after passing CI.
  • Compact resolution must consume the same exact revision approved by this flow; it must not parse/classify/create state prior to checkout or independently derive a different branch.
  • Publish should invoke Craft against that pinned revision with craft publish <version> --rev <revision> (or equivalent), so Craft’s own checkout, checked CI, artifacts, state CWD, and target execution align.
• Workspace discovery design
  • Existing src/utils/workspaces.ts is for npm/yarn/pnpm package workspaces and must not be conflated with named Craft release-unit workspaces.
  • New read-only Craft discovery command should report exact named keys from raw validated project configuration; no controller-side YAML heuristics or name normalization.
  • Candidate naming discussed: craft workspace list versus craft workspaces --json; choose one and test its JSON contract before Publish relies on it.
• Action security decisions
  • First composite step remains workspace validation before all side effects; rejects nonempty /[\p{Cc}\p{Cf}\p{Zl}\p{Zp}]/u.
  • Both Craft invocations use inline --workspace=$WORKSPACE, preventing option injection.
  • New required extension: validate path and workspace mutual exclusivity in that first pre-side-effect validation step.
• Deferred/unrelated
  • Cloudflare target and monorepo prefixed-tag design remain independent future PRs.
  • CalVer Publish-issue changelog mentions must render bold to prevent pings; committed CHANGELOG.md retains original mentions.
  • Other user branch facts remain: 3566840 fix: replace extract-zip with node-stream-zip to fix Node 24.16.0 hang; 8484cd8 security(commit-repo): replace execSync tar with node-tar.

Technical Changes

• Merged Craft #848 (feat/workspaces-schema)
  • 086a633 fix(config): address workspace review feedback, pushed Aug 25, 09:31.
  • ab63572 fix(publish): isolate workspace release state, pushed Aug 25, 09:44.
  • Squash merge: 21270a1d12a60b461c51fba93bd076b90d9cf4af.
  • Key files: src/config.ts, src/utils/helpers.ts, src/utils/publishState.ts, associated config/helper/publishState tests.
• Existing Craft Action propagation commit 6dae341
  • Files changed: .github/workflows/release.yml, action.yml, src/__tests__/action.test.ts, src/commands/__tests__/publish.test.ts, src/commands/publish.ts.
  • release.yml forwards optional workspace through workflow_dispatch and typed workflow_call; workflow_call also supports version, force, merge target, blocker label, publish repo, git identity, path default ., and config-from-merge-target.
  • action.yml:
    • Optional workspace; optional path default ..
    • First step Validate workspace, with WORKSPACE: ${{ inputs.workspace }}, rejects Cc, Cf, Zl, Zp.
    • Craft Prepare and Read Craft Targets each set WORKSPACE in their own env, run under ${{ inputs.path }}, and use inline --workspace=$WORKSPACE.
    • Request Publish currently uses JSON workspace title syntax: publish: ${GITHUB_REPOSITORY}${SUBDIRECTORY} [workspace: ${workspace_json}] @${RESOLVED_VERSION}.
    • It obtains RELEASE_BRANCH, RELEASE_SHA, RELEASE_PREVIOUS_TAG, but body currently only stores merge target, compare/check links, targets, and changelog—not dedicated release branch/SHA fields.
    • It exact-matches open issue title via gh issue list, preserves checked target Markdown entries, and reads/truncates changelog at MAX_CHANGELOG_CHARS=60000.
  • src/__tests__/action.test.ts executes actual named Bash snippets with fake craft/git, asserts first-step side-effect-free unsafe validation and exact inline option behavior.
• Existing Craft configuration behavior to alter
  • src/schemas/project_config.ts:
    • GitHubGlobalConfigSchema: required owner, repo; optional projectPath.
    • WorkspaceSchema currently uses GitHubGlobalConfigSchema.partial().optional() and CraftProjectConfigSchema.workspaces is z.record(z.string(), WorkspaceSchema).optional().
    • Thus workspace-level github.projectPath is currently allowed, including standalone partial config that inherits owner/repo when available.
  • src/config.ts:110-160: resolveWorkspaceConfig() shallow-merges base GitHub with partial workspace GitHub, including projectPath; removes incomplete merged GitHub to retain remote fallback.
  • Tests currently intentionally cover github.projectPath: "cli" workspace configurations in src/__tests__/config.test.ts and src/commands/__tests__/publish.test.ts; these expectations must be revised when forbidding workspace project paths.
  • setActiveWorkspace() clears config/global-GitHub caches. applyWorkspaceSelection() requires selection when nonempty workspaces exist and enforces WORKSPACES_MIN_VERSION = "2.29.0".
  • checkMinimalConfigVersion() correctly removes prerelease/build only from current build for prerelease relaxation; configured minVersion has only build metadata stripped.
• Existing Craft command surface
  • src/index.ts sets active workspace before yargs parse and registers prepare, publish, targets, config, artifacts, changelog.
  • src/commands/config.ts outputs resolved config plus getGlobalGitHubConfig().
  • src/commands/targets.ts lists configured, expanded target IDs; its tests offer a pattern for a new workspace-list command/test.
  • src/utils/workspaces.ts handles package-workspace discovery only, not named release units.
  • Proposed addition: a dedicated named-release-workspace discovery command with exact JSON list output sourced from raw validated config, including dynamic workspace maps.
• Existing Craft publish checkout/state mechanics
  • src/commands/publish.ts:
    • Loads workspace-resolved config before checkout.
    • Uses argv.rev by git name-rev --name-only --no-undefined <rev> then checkout; otherwise checks out ${config.releaseBranchPrefix || DEFAULT_RELEASE_BRANCH_NAME}/${newVersion}.
    • Resolves HEAD, checks CI/artifacts, expands selected workspace targets.
    • State path is getPublishStatePath(newVersion, getPublishStateGitHubConfig(...), process.cwd(), getActiveWorkspace()).
    • State override only governs filename identity; invalid CRAFT_PUBLISH_STATE_GITHUB_REPO throws ConfigurationError("CRAFT_PUBLISH_STATE_GITHUB_REPO must be a GitHub owner/repository pair.").
    • Never reads legacy repo-local .craft-publish-${version}.json.
• Existing Publish controller implementation
  • 33de3f1 changed .github/workflows/publish.yml, parser/workflow/update-issue tests, src/modules/details-from-context.js, src/modules/update-issue.js.
  • b658ffa changed .github/workflows/cocoapods-keepalive.yml, README.md, docs/publish-issue-format.md, parser and tests.
  • src/modules/details-from-context.js currently has regex:

    /^publish: (?:getsentry\/)?(?<repo>[A-Za-z0-9_.-]+)(?<path>\/[\w./-]+)?(?: \[workspace: (?<workspace>"(?:[^"\\]|\\.)*")\] )?@(?<version>[\w.+-]+)$/
    

    • Optional getsentry/; path [\w./-]+; JSON workspace annotation; version [\w.+-]+.
    • Rejects invalid title, bad JSON with controlled error, empty/control/format/line/paragraph separator workspace, and .. path segments.
    • Extracts merge target, dry-run, and checked target IDs.
  • Parser tests currently cover JSON workspace cli/v2, escaped quotes/brackets, safe Unicode, malformed \q, empty/control/bidi/line/paragraph values, legacy separator incompatibility, traversal, + versions, and absent issue payload. These must be migrated/extended for compact syntax and legacy compatibility.
  • docs/publish-issue-format.md is 81 lines documenting JSON workspace titles and will require rewrite to canonical EBNF/compact contract.
• Existing Publish workflow ordering that must change
  • .github/workflows/publish.yml currently:
    1. Runs inputs.js / detailsFromContext() before target checkout.
    2. Chooses default or allowlisted protected branch (publish.yml:145-184) rather than a general CI-approved release revision.
    3. Runs Set targets (publish.yml:186-234) using parser path/workspace.
    4. Docker-runs craft publish <version> under __repo__/${path} with CRAFT_WORKSPACE.
  • This ordering is unsafe for compact semantic resolution. It must be changed so checkout of the CI-approved pinned revision precedes suffix classification, state creation, cd, CRAFT_WORKSPACE, and Craft invocation.
  • Current allowlisted divergent branch cases: sentry-migr8/tmp-merge-target; sentry-javascript/v10, v9, v8, v7, master; sentry-python/alpha; sentry-wizard/1.x.
• CI poller facts relevant to implementation
  • .github/workflows/ci-poller.yml has cron */5 * * * *, manual workflow_dispatch with optional attempt default "0", ci-status-poller concurrency, 60 attempt cap, and processes up to 200 open issues with ci-pending and accepted.
  • It extracts SHA from issue’s check-runs link, obtains first check suite’s head_branch, resolves branch head where possible, updates link when branch SHA changes, checks commit statuses and paginated check runs.
  • success, neutral, skipped are passing check conclusions; all-zero status/check counts means not ready.
  • Passing CI removes ci-pending, adds ci-ready, comments success. Failure removes pending/accepted and adds ci-failed; retry requires re-adding accepted.
  • Any compact design must use this existing branch/SHA data rather than introduce body metadata.
• Secure workflow state restoration
  • Set targets writes only $GITHUB_WORKSPACE/.craft-state/craft/publish-state-${owner}-${repo}-${cwd_hash}-${workspace_prefix}${version}.json.
  • It canonicalizes path under /github/workspace/__repo__; escaping emits ::error::Publish path must remain inside the target checkout. and exits 1.
  • CWD SHA-1 / Base64URL parity fixtures:
    • root /github/workspace/__repo__ → c232c383e26f.
    • /github/workspace/__repo__/cli → 21cf7beaeda4.
    • Root expected filename: .craft-state/craft/publish-state-getsentry-sentry-c232c383e26f-21.3.1.json.
    • Workspace expected filename: .craft-state/craft/publish-state-getsentry-toolkit-21cf7beaeda4-workspace-Y2xp-1.2.3.json.
  • src/modules/__tests__/publish-workflow.js extracts/runs actual shell script bounded by Set targets and Docker action; update it for post-checkout compact resolution and exact parity.
• Verification history for current pushed implementation
  • Craft focused Aug 26, 13:35: 45 tests; full 13:49: 1,138 passed / 1 skipped / 1,139 total; build/Prettier passed.
  • Craft lint: 0 errors, 7 pre-existing warnings (publish.ts _abortError/_statusError/_diffError; git.ts _err).
  • Publish full after b658ffa Aug 27, 08:57: 26 tests passed; lint 09:07, Prettier/diff-check 09:21 passed.
  • Independent adversarial review ses_fc1a82a13ffeaFWq7hymm7uL2z returned MERGE Aug 26, 14:05 for the old JSON-title design.
  • Later compact-design adversarial review at Aug 27, 14:31 returned DO-NOT-MERGE; two later read-only background reviews at 16:21 and 16:33 returned no evidence and were explicitly not approval.
• Publish repository constraints
  • Node 24.0.0, CommonJS source, ESM Vitest tests, Yarn Classic 1.22.22 via Volta, never npm.
  • Commands: yarn install, yarn test, yarn test:watch, focused yarn test ..., yarn lint, yarn prettier.
  • Kebab-case file names; camelCase code; UPPER_SNAKE_CASE constants; double quotes/semicolons; descriptive guard-clause errors; test mocks before require.
  • package.json contains dependencies @actions/core, @actions/github, @sentry/node; dev dependencies include Vitest, ESLint, Prettier and currently local "peggy": "5.1.0".
• Craft package/runtime context
  • @sentry/craft version 2.31.0-dev.0, MIT, Node/TypeScript project; Docker builder/runtime is Node 24.18.0.
  • Craft uses pnpm install --frozen-lockfile; its Docker image copies built Craft to /usr/local/bin/craft.
• Administrative details retained
  • Four malformed reviewer replies caused by Markdown backticks were deleted; corrected replies and PR descriptions were posted Aug 26, 14:26–14:27.
  • Staging checks found absent .lore.md on Aug 26, 14:15 and Aug 27, 09:14, with no index change.
  • Dependabot reported two high-severity Craft-default-branch vulnerabilities on Aug 25, 09:31 and 09:44.

Session Timeline

• Aug 25, 2026, 09:31–20:59
  • Fixed and merged Craft workspace schema/state hardening as #848; mapped cross-repository workspace propagation; implemented original JSON-qualified title contract; security reviews drove secure XDG state, exact state file propagation, Unicode validation, inline argument safety, and checkout-state identity design.
• Aug 26, 2026, 12:19–14:28
  • Completed action/controller hardening, executable tests, workflow parity tests, full verification, and adversarial review MERGE.
  • Pushed Publish 33de3f1, Craft 6dae341; opened Publish #9339 and dependent draft Craft #872.
• Aug 27, 2026, 08:36–10:06
  • Fixed invalid workspace JSON escape handling in Publish b658ffa; added Publish issue-format documentation.
  • Confirmed linked PR CI green but review-blocked.
  • User approved redesign: path-like workspace notation, workspace/github.projectPath exclusivity, EBNF canonical documentation, and independent parser research.
• Aug 27, 2026, 10:08–10:11
  • Researched parser ecosystem; selected Peggy 5.1.0 as maintained PEG.js successor with build-time parser generation.
  • Identified direct path reinterpretation breaks legacy titles; initially proposed explicit [workspace: safe-name] marker.
• Aug 27, 2026, 10:40–12:18
  • Rejected controller-only inference/body marker alternatives due to title identity/reuse collisions.
  • User clarified release branches are materialized configuration authority; investigation showed Publish currently parses and creates state before default/allowlisted checkout, not a release branch.
  • Confirmed existing action carries release branch/SHA only in links/body, not a dedicated identity field; user later rejected adding such metadata.
• Aug 27, 2026, 13:11–16:37
  • First replacement adversarial compact-design review started 13:12, returned DO-NOT-MERGE 14:31 with CI binding, ordering, collision, grammar, and mutual-exclusion concerns.
  • User enforced: field-less legacy issue must never become a new request; never normalize names; do not add versioned body identity.
  • Empty follow-up reviews at 16:21 and 16:33 were rejected as insufficient evidence.
  • Mapped CI poller’s existing branch/SHA/check-runs mechanism as the intended pinned revision source.
• Aug 27, 2026, 19:11–23:59
  • User proposed workspace-first classification. Settled direction: exact root workspace membership at approved revision means workspace; otherwise path, with missing root .craft.yml path-only behavior per 19:26 correction.
  • Proposed dedicated Craft named-workspace listing command to support dynamic workspace maps.
  • Installed/staged Peggy locally in Publish at 22:53 using pnpm, producing modified package.json and untracked pnpm-lock.yaml; no parser/source contract implementation completed.
  • Began planning Craft invariant edits: safe workspace keys, forbid workspace github.projectPath, reject non-root action path plus workspace.
• Aug 28, 2026, 00:03–01:53
  • Continued detailed mapping of current parser, CI poller, state script, action test harness, Craft config schema, checkout mechanics, and command patterns.
  • Reaffirmed implementation ordering: one exact CI-approved revision must drive classification, state creation, and Craft --rev publishing.
• Aug 28, 2026, 07:21–09:36
  • User requested continuation at 07:21 and 09:02.
  • Confirmed implementation plan: Craft discovery/safeguards first, then Publish post-checkout compact resolution, cross-repository regressions, verification/review/push/monitoring.
  • Reconfirmed CI poller and Publish workflow gates, current default/allowlisted checkout behavior, current state mechanics, and existing action/schema facts.
  • No source implementation beyond the pre-existing local Peggy package pin is recorded through 09:36.