studio-engine 0.61.1 → 0.61.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '0082dfd62bcd08f1a3a540bc351c6171c27a563d85aa50d7492c1f0bb1f0271a'
-  data.tar.gz: 920156a74de7a1bbc1953a29ef01cac6b79c7d5aaad81a9f223d64d72924702d
+  metadata.gz: e8e859fc4ea59dafad01b2aef524f8ff75bb2b5040bc05611ac17eec335c5c0a
+  data.tar.gz: ca4d9a0ed867017686c50d329190ef26d7488ea28349fa65996bd8b859ff4eee
 SHA512:
-  metadata.gz: ff49493b81e76496c8977d2403d1b3855e8146db9f4c452a0f81707bf2aebca3c8607202d90e3c91c91c5e8e56b152b5113750b3c051dbf83c5e9340484406ea
-  data.tar.gz: 525b285e971042834e9761b78cd359b7fc24a431bdf6e06ba6a1082fd80603ae1b7f7e1f8fbb68d69d22a174da53c429a6da505b4c534066df03b76bf7d3fbc3
+  metadata.gz: 805ad1e2f8d05504bb4ca7e782ab27fab96589dbe3acd5714502c24b0803de69631241a1a3374da1d7f92a762b1c21f6eb4122ba7c6cdafc3231844f2f03b479
+  data.tar.gz: 5cc030a1e38828fc0db6212f8686f6438253f00adf8a84dfa26faad576bf86fdda137b2d806e79d78a241b2b21ac706c39de6f99b694eedccfa034ec37669012

data/CHANGELOG.md

@@ -233,6 +233,31 @@ The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This pro
 
 ### Fixed
 
+- **The age gate's back link now returns the date the person already entered.**
+  `blocks/_age_gate`'s "Update your Birthday" swapped back to `blocks/_birthday`
+  with an EMPTY props object, discarding the `dobYear`/`dobMonth`/`dobDay` parts
+  the birthday factory had just handed across the store — and the factory started
+  its three fields at `""` and never read them anyway. So the correction path came
+  back BLANK: a mistyped year cost all three picks, on a card whose own header
+  comment promised "a correction, not a restart".
+
+  Both sides of the seam moved. `back()` forwards the three date parts — and only
+  those three, deliberately: `minAge`, `state` and `message` describe the refusal,
+  and `validates` is load-bearing by its ABSENCE (the style guide specimen reads an
+  absent prop as validating, and a forwarded stale one would let the refusal pick
+  the next card's mode). `window.birthdayModal` gained an `init` that re-picks the
+  three selects from the props of the modal entry it mounted in, clamping a day
+  that the restored month cannot hold.
+
+  **The gate is not weakened.** Restoring the date restores the DATE and never the
+  verdict: the card comes back submittable and the app's endpoint re-decides on the
+  next submit exactly as it did on the first. `e2e/birthday_gate.spec.js` asserts a
+  restored under-age date is refused again.
+
+  **No consumer action.** A host that renders `blocks/_age_gate` and
+  `studio/_birthday_assets` gets this by upgrading; nothing in the call signature
+  changed and no host wiring moves.
+
 - **The Geo signpost now reaches every app whose admin chrome the engine owns.**
   The row added last release went into `components/_admin_dropdown` alone, on the
   premise that the shared dropdown reaches every app from one change. It does

data/app/views/studio/_birthday_assets.html.erb

@@ -29,6 +29,13 @@
   age-gate card instead. `_finish` is unchanged: the success path still flips
   session.ageVerified and dispatches `age-verified`, which is the hook consuming
   apps already listen on, so nothing downstream had to change.
+
+  AND THE HANDOFF RETURNS (2026-08-26). `_reject` sends dobYear/dobMonth/dobDay
+  across the store; the gate card's back() hands the same three parts back; and
+  `init` re-picks the three selects from them, so the correction the gate card
+  offers costs one scroll rather than all three fields. The date is restored,
+  never the VERDICT: the card comes back submittable and the app's endpoint
+  re-decides on the next submit exactly as it did on the first.
 %>
 <script>
   (function () {
@@ -89,6 +96,56 @@
           if (this.day && parseInt(this.day, 10) > this.dayOptions.length) this.day = "";
           this.error = "";
         },
+        // THE RETURN TRIP. _reject writes dobYear/dobMonth/dobDay onto the store
+        // on the way out to the age-gate card, and that card's back() hands the
+        // same three parts straight back — so a card mounted from a return trip
+        // finds the person's date on its own modal entry and re-picks the three
+        // selects. Without this the factory started at "" whatever it was handed,
+        // and a mistyped year cost all three fields (fixed 2026-08-26).
+        //
+        // Read off the STORE rather than taken as an opt: that is where this
+        // factory already meets the store (_reject writes to the same object
+        // through the same guard), the ERB locals in blocks/_birthday are
+        // server-side and cannot carry a client value anyway, and it means a
+        // consuming app that renders the card needs no change at all.
+        //
+        // STRINGS, because that is what the selects produce: the options render
+        // :value="m.n" — a number stringified by the DOM — and x-model writes
+        // that string back. Seeding a Number would leave the field holding a type
+        // the person's own pick never produces.
+        _returnedDob() {
+          var props;
+          try {
+            var entry = Alpine.store(this.store).current();
+            props = (entry && entry.props) || {};
+          } catch (e) {
+            return null;
+          }
+          var y = parseInt(props.dobYear, 10),
+              m = parseInt(props.dobMonth, 10),
+              d = parseInt(props.dobDay, 10);
+          if (!y || !m || !d) return null;
+          return { year: String(y), month: String(m), day: String(d) };
+        },
+        // Alpine calls init() on the data object at MOUNT, synchronously, inside
+        // the x-data directive and before it walks the three <select>s below
+        // (Alpine 3.16.1 as vendored: `a.init && T(t, a.init)`). So this is the
+        // fields' initial state rather than a later mutation of them, and x-model
+        // paints the selects from it. Measured in chromium: all three hold the
+        // restored values on the FIRST frame the card exists, six runs out of six
+        // — no deferral needed, and e2e/birthday_gate.spec.js is what watches it.
+        init() {
+          var dob = this._returnedDob();
+          if (!dob) return;
+          this.year = dob.year;
+          this.month = dob.month;
+          // Day LAST, and clamped: dayOptions is only the restored month's list
+          // once month and year are set, and an impossible pair from a hand-built
+          // props bag (Feb 30) must land empty rather than leave the select
+          // holding a value its own options do not contain — which would read as
+          // complete and submit a date nobody picked.
+          this.day = parseInt(dob.day, 10) <= this.dayOptions.length ? dob.day : "";
+        },
         // Success path: flip a session flag if present, close via the app's store,
         // and let the app resume its own flow (the entry gate listens for this).
         _finish() {

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

@@ -16,7 +16,14 @@
     the back link — the thing they might NEED. A wrong birthday is an ordinary
                  typo (a mis-picked year is one scroll away), and a gate with no
                  way back turns a typo into a locked door. swap()s back to the
-                 birthday card, so this is a correction, not a restart.
+                 birthday card CARRYING THE DATE, so a mistyped year costs one
+                 scroll and not all three fields. That is what makes this a
+                 correction rather than a restart: back() forwards the dobYear /
+                 dobMonth / dobDay parts _reject handed across the store on the
+                 way in, and the birthday factory seeds its three selects from
+                 them. Until 2026-08-26 it swapped with an EMPTY props object and
+                 the card came back blank, which is the restart this paragraph
+                 disclaimed.
 
   DELIBERATELY NOT DISMISSIBLE-BY-DEFAULT-ONLY: the host still decides via
   props.dismissible at open() time, exactly like every other card. What this
@@ -146,7 +153,26 @@
        // sibling cards that poll: modals/_web3_step_up, blocks/_cta_redirect,
        // blocks/_seeds_bar.
        destroy() { this.stop(); },
-       back() { $store.<%= modal_store %>.swap('<%= j birthday_modal_id.to_s %>', {}); }
+       // THE DATE RIDES BACK. _reject put these three parts on the store on the
+       // way here so this card could say WHEN; handing them back is what makes
+       // the return trip a correction instead of a blank form. This swapped with
+       // an empty object until 2026-08-26, and a mistyped year cost all three
+       // picks.
+       //
+       // THE THREE PARTS ONLY, deliberately not the whole props bag. minAge,
+       // state and message describe the REFUSAL: message would land as an error
+       // line on a card nobody has submitted yet, and `validates` is load-bearing
+       // by its ABSENCE — the style guide specimen reads an absent prop as
+       // validating, so forwarding a stale one would let this card pick the next
+       // card's mode (style/modals/_birthday.html.erb).
+       back() {
+         var p = this.props;
+         $store.<%= modal_store %>.swap('<%= j birthday_modal_id.to_s %>', {
+           dobYear: p.dobYear || null,
+           dobMonth: p.dobMonth || null,
+           dobDay: p.dobDay || null
+         });
+       }
      }"
      <% if countdown %>x-init="start()"<% end %>
      class="relative">
@@ -211,7 +237,9 @@
 
   <% if birthday_modal_id.present? %>
     <%# The correction path. A mis-picked year is one scroll away from a right
-        one, and without this the typo is indistinguishable from the verdict. %>
+        one, and without this the typo is indistinguishable from the verdict.
+        back() carries the date across, so what comes back is the same three
+        picks with the wrong one still selected. %>
     <button type="button" @click="back()"
             class="block mx-auto mt-3 text-sm text-secondary hover:text-heading transition underline-offset-2 hover:underline">
       <%= back_label %>

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

@@ -23,11 +23,17 @@
 
     Why absent is not "no bar": the only card that can REACH the age gate is the
     validating one — the no-bar card carries no min_age, so the factory's _reject
-    never fires. So every arrival with no props is a return trip from the gate,
-    and `back()` swaps with EMPTY props by design (blocks/_age_gate.html.erb).
-    Reading undefined as falsy sent that return trip to the NO-BAR card, where
-    resubmitting the SAME under-age date was accepted — the guide demonstrating an
-    age gate being bypassed. Caught in review, 2026-08-25.
+    never fires. So every arrival with no `validates` is a return trip from the
+    gate, and `back()` never sends one: it forwards the dobYear/dobMonth/dobDay
+    parts and NOTHING ELSE, deliberately, so the refusal cannot pick this
+    specimen's mode (blocks/_age_gate.html.erb). Reading undefined as falsy sent
+    that return trip to the NO-BAR card, where resubmitting the SAME under-age
+    date was accepted — the guide demonstrating an age gate being bypassed.
+    Caught in review, 2026-08-25.
+
+    So the default is still load-bearing, and it is load-bearing in the same way
+    after the gate started carrying the date back (2026-08-26): the props bag on
+    a return trip is no longer empty, but `validates` is still absent from it.
 
     The engine primitive is right and is NOT changed: in a real host the mode
     comes from ERB locals, not from a prop, so this is a two-mode SPECIMEN's

data/lib/studio/version.rb

@@ -1,3 +1,3 @@
 module Studio
-  VERSION = "0.61.1"
+  VERSION = "0.61.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: studio-engine
 version: !ruby/object:Gem::Version
-  version: 0.61.1
+  version: 0.61.2
 platform: ruby
 authors:
 - Alex McRitchie