studio-engine 0.69.0 → 0.69.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 528dc35d5f8eb65f9c9be8b69d5541d9eaba24bb6e18ec1b2d144274c39f3b75
-  data.tar.gz: 92b56fbeda78e7404eaf3ea3832aaa4cc1faa43d88915be60bc4dc7cdc694a3e
+  metadata.gz: 44c016968027b022962e8b79363c104b263e3ab48b8b0d8553bb502d3dfdc42a
+  data.tar.gz: 5c06f265e369ac196c5a2a6ba23c93e060661cdb3cc7d5c4d5416e9c105f655f
 SHA512:
-  metadata.gz: 7d95ee9d3c5cf24d466feb69d52e90e763bc7985543740df1458d46dedca41def112f35ce2e3a6642b02ac37a195ac5efe2adec043ecad9516d3e03bd650c156
-  data.tar.gz: 4d2d7a231e57e84fb746d0b5db9c77f2780c03c1a7e817273a898bc4484be68d55765bcbc51ccd7e4fc784591bed4fadce17f6e28637ccdbbb713cb0ccf8070c
+  metadata.gz: 2dec7eba2710e3fc6cfc17c10df0b93f9f028d15953491e15997c14ccbcaebf2c5b03e09c6e729904a087ad16262940316390c537a4314d5f3d1c449d8032e79
+  data.tar.gz: 822ea41413bea1441fa4bbf76ae941653520dff81c690918568ee61de96e820fbbcec8bc860b5dc179f0fa4ef57c683d9905723bf8f7432cc2061eb40eab2fce

data/CHANGELOG.md

@@ -23,6 +23,10 @@ The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This pro
 
 ### Changed
 
+- **`Gemfile.lock` resolves solana-studio 0.5.7, and a gate now keeps it there.** The lock had sat on **0.5.3 for four patch releases** while BOTH consumers shipped 0.5.7 (turf-monster `~> 0.5.3`, mcritchie-studio `~> 0.5`). Nothing was red and nothing could have been: engine CI installs with `bundler-cache: true`, so it resolves from the lock and never fresh — the drift does not self-correct and never surfaces as flakiness. It matters because `test/views/style_web3_specimens_test.rb` exists to prove "the style guide renders the REAL gem cards" and reads them off whatever the LOCK resolved; four versions behind, that guard certifies a card no consumer receives. It still passes — only its MEANING changes. MEASURED on this span, the gem's whole `app/` tree was byte-identical 0.5.3 → 0.5.7 (only `CHANGELOG.md`, `README.md` and `version.rb` differ), so this instance cost nothing, which is exactly why it went four releases unnoticed.
+- **The constraint stays `>= 0.5.3`, deliberately.** 0.5.3 is a real FLOOR (0.5.2 shipped the credential partial without `solana_studio/modals/_wallet_connect`, which the web3 capability gate requires). Above it this engine claims no ceiling: it is the BASE half of the base/bolt-on split, and a pessimistic `~> 0.5.3` here would be NARROWER than mcritchie-studio's own `~> 0.5` — a dev-only dependency constraining a resolution it does not own. The defect was the LOCK, not the pin, so the fix is a gate rather than a tighter pin.
+- **`bin/gem-drift-check`** — fails when this engine's lock resolves a tracked gem OLDER than a consumer's, wired into `consumer-ci.yml` after the consumer bundle install. That lane is the only place two repos' lockfiles exist at once (engine at `studio/`, consumer beside it); `test/lib/consumer_ci_shard_contract_test.rb` records the same constraint for its own cross-repo contract. Direction is ONE-WAY on purpose: engine behind FAILS, engine level or ahead passes (the engine is the producer and may test an unreleased gem), and a consumer bundling no tracked gem is a SKIP, not a failure — `mcritchie_industries` is the base half working as designed. Stdlib-only, and it names its one-command remedy (`bundle update solana-studio`) in the failure.
+
 - **The auth modal's Solana button moved to solana-studio, behind a CREDENTIAL
   SLOT.** `style/modals/_auth` no longer draws the button; it renders whatever
   resolves at `solana_studio/auth/wallet_credential` and nothing when that path

data/Gemfile

@@ -52,6 +52,34 @@ end
 # The style guide self-gates on the partial RESOLVING (style/_modals.html.erb),
 # so an app without this gem renders /admin/style with the web3 cards badged
 # rather than raising a missing-template error.
+#
+# THE CONSTRAINT STAYS OPEN-ENDED, AND THAT IS A DECISION, NOT AN OVERSIGHT.
+# ">= 0.5.3" is a FLOOR: 0.5.2 shipped the credential partial without
+# solana_studio/modals/_wallet_connect, which the web3 capability gate requires,
+# so 0.5.3 is the first version that can draw the button at all. Above it this
+# engine deliberately claims no ceiling. It is the BASE half of the split; the
+# bolt-on is the consumer's choice, and an engine that pinned the bolt-on more
+# tightly than the app bolting it on would be dictating upward. Concretely: a
+# pessimistic "~> 0.5.3" here would be NARROWER than mcritchie-studio's own
+# "~> 0.5", so this dev-only dependency would start constraining a resolution it
+# does not own.
+#
+# WHAT ACTUALLY WENT WRONG, and it was the LOCK, not the constraint. The lock sat
+# on 0.5.3 while both consumers shipped 0.5.7 — four patch releases — and nothing
+# was red, because engine CI installs with `bundler-cache: true` and never
+# resolves fresh. Meanwhile test/views/style_web3_specimens_test.rb exists to
+# prove "the style guide renders the REAL gem cards" and reads them off whatever
+# the LOCK resolved. Behind, that guard certifies a card no consumer receives; it
+# still passes, and only its MEANING has changed. (Measured on this span: the
+# gem's whole app/ tree was byte-identical 0.5.3 -> 0.5.7, so this instance cost
+# nothing — which is precisely why it went four releases unnoticed.)
+#
+# SO THE FIX IS A GATE, NOT A PIN. bin/gem-drift-check fails when this engine's
+# lock TRAILS a consumer's, and consumer-ci.yml runs it — the only lane holding
+# two repos' lockfiles at once. Direction is one-way: engine behind fails, engine
+# ahead or level passes, a consumer bundling no solana-studio is a skip. Keeping
+# up is now enforced rather than remembered, which is what lets the floor stay a
+# floor. Guarded by test/lib/gem_drift_check_test.rb.
 group :development, :test do
   gem "solana-studio", ">= 0.5.3"
 end

data/app/views/studio/modals/blocks/_wallet_brand_sprite.html.erb

@@ -28,7 +28,8 @@
   whenever a brand is absent or unrecognised, instead of hiding the avatar and
   giving the surface two different shapes.
 
-  ONE CALLER DELIBERATELY DOES NOT: studio/modals/_wallet_connect paints a LETTER
+  ONE CALLER DELIBERATELY DOES NOT: solana-studio's
+  solana_studio/modals/_wallet_connect paints a LETTER
   TILE for a detected wallet whose brand it does not know, not se-wallet-default.
   A detected wallet always has a name (it registered through Wallet Standard to
   get there), and its initial identifies it where a generic mark would not. The

data/app/views/style/_modals.html.erb

@@ -182,8 +182,9 @@
         return { connecting: false, error: null, statusText: 'Connect Wallet',
                  walletAvailable: false, isMobile: false, connect: function () {} };
       };
-      // Connect stub for the promoted wallet picker (studio/modals/_wallet_connect,
-      // configured by style/modals/_wallet_connect). Performs NO connect: it
+      // Connect stub for the wallet picker (solana-studio
+      // solana_studio/modals/_wallet_connect, configured by
+      // style/modals/_wallet_connect). Performs NO connect: it
       // resolves success after a beat so the picker's connecting state is
       // visible and its onConnected hook can continue the demo walk.
       window.dsWalletConnectDemo = window.dsWalletConnectDemo || function () {
@@ -1169,9 +1170,9 @@
         (<code class="font-mono text-2xs">studio/modals/blocks/_wallet_brand_sprite</code>),
         so every app inherits them with no per-app icon files.
         The two <strong>Sign Wallet</strong> cards are a different kind of thing
-        from the rest of this section: they render
-        <code class="font-mono text-2xs">studio/modals/_web3_step_up</code> &mdash;
-        the <strong>REAL shared partial a host renders in production</strong>,
+        from the rest of this section: they render solana-studio's
+        <code class="font-mono text-2xs">solana_studio/modals/_web3_step_up</code>
+        &mdash; the <strong>REAL shared partial a host renders in production</strong>,
         not a style-guide copy of it &mdash; so what you review here is the
         shipped card, and it cannot drift from what users see. They also carry the
         <strong>standard web3 auth button</strong>: a wallet row (brand mark, the

data/app/views/style/modals/_wallet_connect_slot.html.erb

@@ -1,5 +1,6 @@
 <%#
-  The style guide's pre-connect slot for studio/modals/_wallet_connect — the
+  The style guide's pre-connect slot for solana-studio's
+  solana_studio/modals/_wallet_connect — the
   legal-age attestation, sitting exactly where turf-monster puts its own.
 
   A PARTIAL rather than a block because the picker takes its slot as a named

data/lib/studio/version.rb

@@ -1,3 +1,3 @@
 module Studio
-  VERSION = "0.69.0"
+  VERSION = "0.69.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: studio-engine
 version: !ruby/object:Gem::Version
-  version: 0.69.0
+  version: 0.69.2
 platform: ruby
 authors:
 - Alex McRitchie
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-02 00:00:00.000000000 Z
+date: 2026-09-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails