McRitchie Studio

Agent Context

From conductor retro 2026-06-25; this bug just cost a manual gem save on studio-engine 0.11.0. bin/release gem_version_local(repo) (~bin/release:162) reads the gem version from the LOCAL checkout's version_file. During ship, that read happens BEFORE the ship ff's the local checkout to the new release SHA — so it reads the STALE pre-ff version (0.10.0), the publish-skip check sees 0.10.0 'already live', and it SKIPS publishing the actually-bumped version (0.11.0) whose gemspec is on the release SHA (1671e54). Net: rel-20260625-344494 shipped but studio-engine 0.11.0 never published (had to gem-push manually). The dry-run even labels it '0.10.0' (the tell). FIX: read the gem version from the RELEASE SHA / member_plan (e.g. git show <release-ref>:<version_file>, or use member_plan's version), independent of local ff order, so the publish-skip check + the published artifact use the version that will actually build (0.11.0). Fix the dry-run label too. Test: unit on the version resolver (reads release-SHA version, not pre-ff local); integration that a bumped gem PUBLISHES (not skips) via the existing release_cli_test stub seam — and keep it CI-portable (no on-disk sibling dependency; see the #191/#181 lesson).