McRitchie Studio

Agent Context

From the 2026-06-24/25 enumeral gem-ship session retro. The library/gem seam bit us: mcritchie#157 bumped studio-engine ~>0.9 while 0.9.0 was NOT on RubyGems, so CI went fully red (frozen bundle can't resolve) -> Avi blocked it 'dependency' -> manual publish + relock. dor-check (the deterministic, no-judgment DoR gate) should catch this at SUBMIT. CLEANEST LOCAL CHECK (no network, fits dor-check's offline ethos): when the branch diff bumps a gem constraint in Gemfile (e.g. studio-engine ~>0.9), confirm Gemfile.lock actually resolves a version SATISFYING it; if the lock is behind (still 0.8.0), the new version almost certainly isn't published -> CI will fail 'bundle install --frozen'. Flag at the merge gate with the fix: publish the gem first, or hold the bump / use the git-source bridge. Optional enhancement: cross-check rubygems.org/api/v1/versions for a definitive published signal, but the Gemfile-vs-lock mismatch is sufficient + offline. Tests in test/lib/dor_check_test.rb (a fixture whose diff bumps a constraint past the lock -> gate fails with the gem-seam reason). Would have erased the whole red-CI -> block -> manual-publish detour.