studio-engine 0.114.3.rc1 → 0.115.0.rc1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d5b753ca6d71e6be266c72e98b0d6c0bb9e6e642ee4812292f00b85e89212a2e
-  data.tar.gz: 146fe269e2670d0db81cc5e2b7cc7715582358da3da0202c0dcd3b0c49a73a68
+  metadata.gz: '0899e08c1d3bce3e63d3f1c6cef0fa178c47d30a80ccb5246e7155d12f46eec9'
+  data.tar.gz: 933f3be8adef99b85196b1e873859b665d676fcc9c26af6cfb15ab4e32460293
 SHA512:
-  metadata.gz: b620c0242040c2aa0850fbf1ba00bd55cdab9e5606df9b890ccd7124c739be97ed8c200ef79d076b68f82fd4bf0084daee270448d8349b9792e65e2552aa624e
-  data.tar.gz: 4c37aa5bdc67ac54448e5091fe0779c52a40267aa3f9ca924090399634f21aa1a577db5574e4ca64fb727fe4a67a2d95ad28afa8f8f304ff9ca345eaca4abf1a
+  metadata.gz: 59cb10068b65ceb8ef9f46cbaddaa6e998c3117a00bda165e2cbdc3ffaf8e43fa2bca65f0843d3e3740437e2ed3d0f7e4d034c2af41319884d2ec4bedb9f30b4
+  data.tar.gz: 1b9fafe6b140123496e4ce5fbcae20529adb6a3c358fd30fa5d027b9f7828c7a8f60e1480720a3931f2ae44ee84f43f3f2a9fa90687214768c5c908d36a59b0a

data/CHANGELOG.md

@@ -4,6 +4,41 @@ The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This pro
 
 ## Unreleased
 
+## 0.115.0 — 2026-10-26
+
+### Breaking
+
+- **The deprecated JS Tailwind preset `tailwind/studio.tailwind.config.js` is
+  deleted**, with its parity test (`test/integration/tailwind_preset_parity_test.rb`),
+  and the gemspec no longer packages a `tailwind/` directory. Every host in the
+  release relock set had already moved to the CSS-first entry (hub, Turf
+  Monster, Rantly, McRitchie Industries, Cyvasse, Moms App, Alex Build,
+  Commercial Welding), so none of them reads it. The one known
+  holdout is acquisition-studio, pinned to 0.24.0 and outside the relock set;
+  it migrates on its next bump.
+  **Upgrade note for a host still on `@config` + the preset** (its
+  `config/tailwind.config.js` `require`s
+  `${studioPath}/tailwind/studio.tailwind.config.js`): bumping past 0.114.3
+  fails its Tailwind build, because the file is gone. Switch to the CSS-first
+  entry in the same change as the bump:
+  1. Make `app/assets/tailwind/application.css` start with `@import
+     "tailwindcss";` and `@import "../builds/tailwind/studio_engine";`, and
+     delete its `@config` line (and any `studio_engine_motion` import).
+  2. Delete `config/tailwind.config.js` and
+     `lib/tasks/tailwindcss_engine_motion.rake`, moving only the host's own
+     theme extensions into an `@theme inline { ... }` block after the import.
+  3. Rebuild with `bin/rails tailwindcss:build` and check that the class set of
+     `app/assets/builds/tailwind.css` only grew.
+  The full recipe, with the safelist and `vendor/bundle` cases: README,
+  "Migrating a host from `@config`".
+
+### Changed
+
+- README lists every host, and `docs/NEW_APP_SETUP.md` section 16's apt
+  install sample carries the hardened pattern (apt retries and 30s fetch
+  timeouts, a bounded step, three attempts), so a new app's first CI does not
+  hang on a stalled mirror.
+
 ## 0.114.3 — 2026-10-26
 
 ## 0.114.2 — 2026-10-26

data/README.md

@@ -1,6 +1,6 @@
 # Studio Engine
 
-Shared Rails engine for McRitchie apps. Provides authentication, error handling, dynamic theming, and common concerns used by [McRitchie Studio](https://app.mcritchie.studio) and [Turf Monster](https://app.turfmonster.media).
+Shared Rails engine for McRitchie apps. Provides authentication, error handling, dynamic theming, and common concerns used by [McRitchie Studio](https://app.mcritchie.studio), [Turf Monster](https://app.turfmonster.media) and the other McRitchie hosts: Rantly, McRitchie Industries, Cyvasse, Moms App, Alex Build and Commercial Welding.
 
 > **Part of the McRitchie ecosystem** — see [`ECOSYSTEM.md`](https://github.com/McRitchie-Studio/mcritchie-studio/blob/main/docs/ECOSYSTEM.md) for the 5-repo map; [`house-burn-down.md`](https://github.com/McRitchie-Studio/mcritchie-studio/blob/main/docs/agents/system/house-burn-down.md) for fresh-Mac recovery.
 
@@ -24,8 +24,9 @@ rather than constraining the resolve — read the `Gemfile.lock` for what really
 resolved.
 
 > Published to RubyGems as of v0.4.0 (2026-05-17). New installs should use the
-> RubyGems form, which all three consumer Rails apps (`mcritchie-studio`,
-> `turf-monster`, `mcritchie-industries`) already use.
+> RubyGems form, which every consumer Rails app (`mcritchie-studio`,
+> `turf-monster`, `rantly`, `mcritchie-industries`, `cyvasse`, `moms-app`,
+> `alex-build`, `commercial-welding`) already uses.
 
 ## What It Provides
 
@@ -64,7 +65,7 @@ wire by hand:
 
 | What | Where it lives | What it replaced |
 |------|----------------|------------------|
-| The design tokens (surfaces, inks, the primary ladder, brand palettes, `text-2xs`/`text-3xs`, Montserrat) and the class-based `dark:` variant | `theme.css`, `@theme inline reference` | `tailwind/studio.tailwind.config.js` and the host's `@config` |
+| The design tokens (surfaces, inks, the primary ladder, brand palettes, `text-2xs`/`text-3xs`, Montserrat) and the class-based `dark:` variant | `theme.css`, `@theme inline reference` | the deleted JS preset `tailwind/studio.tailwind.config.js` and the host's `@config` |
 | The scan of every engine directory that emits a class (views, components, helpers, both JavaScript trees) | `host.css`, `@source` | the host's content glob over the gem's views, found with a bundler call from Node |
 | Every engine class, with no safelist | the scan above; no class is assembled at render time | the host's primary-colour safelist (about 240 classes) |
 | The motion, effect and leveling primitives (`.spinner`, `.hold-btn`, `.level-badge-*`, ...) | `engine-motion.css`, imported last by `host.css` | `lib/tasks/tailwindcss_engine_motion.rake` and its `studio_engine_motion` import |
@@ -81,14 +82,12 @@ by path, such as the hub's client kit (`ClientApps::StudioKit::Css`, held to
 
 ### Migrating a host from `@config`
 
-Hosts adopt on their own cards (hub, Turf Monster, Rolio, chain-ops, Rantly,
-McRitchie Industries, Cyvasse, Moms App). Until each one does, it keeps
-building unchanged: `tailwind/studio.tailwind.config.js` stays one release as a
-deprecated shim, and `test/integration/tailwind_preset_parity_test.rb` holds it
-to the same utilities as `theme.css`. A host that has bumped the gem but not
-yet migrated gets the motion layer twice (once through `host.css`, once
-through its own generated import). The duplicate is harmless and goes with
-step 3.
+Every host has migrated: hub, Turf Monster, Rantly, McRitchie Industries,
+Cyvasse, Moms App, Alex Build and Commercial Welding.
+The deprecated JS preset `tailwind/studio.tailwind.config.js` and its parity
+test are **deleted**, so a host still on `@config` that bumps the gem past
+0.114.3 fails at its own Tailwind build (`require` of a file the gem no longer
+ships). Run this recipe in the same change as that bump (CHANGELOG, Breaking).
 
 1. **Bump** `studio-engine` to the release that carries this section.
 2. **`application.css`**: delete the `@config` line. Keep `@import
@@ -124,11 +123,9 @@ step 3.
    engine now also scans its helpers and scripts). Spot-check one class from
    each column above: `.text-heading`, `.btn-primary`, `.spinner`.
 
-When every host has adopted, the shim and the parity test are deleted in one
-engine change. Before that, every reader of the preset has to move, not only
-the build: the hub's `app/services/client_apps/studio_kit/css.rb` reads it at
-runtime to build the client kit CSS, and a few host tests read its text
-(CHANGELOG, Deprecated).
+A migrating host also moves every other reader of the preset, not only the
+build: any production code or test that `require`s or reads the preset's text
+reads `theme.css` instead.
 
 ## Configuration
 
@@ -1057,7 +1054,8 @@ config.navbar_z_tier = true      # the live header at z-[var(--z-nav)], not z-50
   wins when both are set. Rules: `lib/studio/navbar_brand.rb`.
 - **The word classes live in the host's initializer**
   (`config/initializers/studio.rb`), which a host's Tailwind scan may not
-  read (a host still on `@config` lists only its `content:` globs). A utility
+  read (Tailwind's automatic detection and the engine's own `@source` lines
+  may both miss it). A utility
   named only there, `text-heading` say, compiles only if some view also uses
   it. Add the initializer to the scan (`@source "../../../config/initializers/studio.rb";`),
   or give the word a class the host's CSS defines (`tm-wordmark`). See

data/app/assets/tailwind/studio_engine/theme.css

@@ -1,7 +1,7 @@
 /*
   studio-engine THEME — the shared Tailwind v4 design tokens, CSS-first.
 
-  This file replaced tailwind/studio.tailwind.config.js (the JS preset every
+  This file replaced tailwind/studio.tailwind.config.js (since deleted; the JS preset every
   consumer spread through `@config`, after shelling out to bundler from Node to
   find the gem). engine.css imports it (and host.css imports engine.css), so a
   consumer gets these tokens from the same one line that brings the component

data/lib/studio/version.rb

@@ -1,3 +1,3 @@
 module Studio
-  VERSION = "0.114.3.rc1"
+  VERSION = "0.115.0.rc1"
 end

data/studio-engine.gemspec

@@ -30,7 +30,7 @@ Gem::Specification.new do |spec|
   # citation should resolve in the installed gem, not only on GitHub. The rest of
   # docs/ is the engine's own operating material. Guarded by
   # test/lib/gemspec_ships_footer_docs_test.rb.
-  spec.files = Dir["lib/**/*", "app/**/*", "config/**/*", "db/**/*", "tailwind/**/*", "Gemfile", "studio-engine.gemspec", "README.md", "CHANGELOG.md", "LICENSE",
+  spec.files = Dir["lib/**/*", "app/**/*", "config/**/*", "db/**/*", "Gemfile", "studio-engine.gemspec", "README.md", "CHANGELOG.md", "LICENSE",
                    "docs/SITE_FOOTER.md", "docs/BOOKING.md"] - ["config/e2e_lane.yml"]
   spec.require_paths = ["lib"]
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: studio-engine
 version: !ruby/object:Gem::Version
-  version: 0.114.3.rc1
+  version: 0.115.0.rc1
 platform: ruby
 authors:
 - Alex McRitchie
@@ -801,7 +801,6 @@ files:
 - lib/tasks/studio_knowledge.rake
 - lib/tasks/studio_trash.rake
 - studio-engine.gemspec
-- tailwind/studio.tailwind.config.js
 homepage: https://github.com/McRitchie-Studio/studio-engine
 licenses:
 - MIT

data/tailwind/studio.tailwind.config.js

@@ -1,141 +0,0 @@
-// DEPRECATED — kept for ONE release so consumers can adopt on their own cards.
-//
-// The engine's Tailwind layer is CSS-first: the tokens below now live in
-// app/assets/tailwind/studio_engine/theme.css (@theme), and every host gets
-// them, the engine's @source scan and the motion layer from its one
-// `@import "../builds/tailwind/studio_engine";` line. Nothing in the engine
-// reads this file any more. A host still on `@config` + this preset builds
-// exactly as before; test/integration/tailwind_preset_parity_test.rb holds it
-// to the same utilities as theme.css until it goes.
-//
-// Migration (README, "Tailwind"): drop the host's `@config` line,
-// config/tailwind.config.js, its safelist and lib/tasks/tailwindcss_engine_motion.rake.
-// This file is removed in the release after every consumer has adopted.
-//
-// Shared Tailwind config for all Studio apps
-// Apps spread from this in their own tailwind.config.js
-
-module.exports = {
-  darkMode: 'class',
-  theme: {
-    fontFamily: {
-      sans: ['Montserrat', 'system-ui', 'sans-serif'],
-      mono: ['ui-monospace', 'SFMono-Regular', 'monospace'],
-    },
-    extend: {
-      // Sub-xs type scale for dense UI (badges, meta rows, tick labels).
-      // Bare sizes (no line-height tuple) so text-2xs / text-3xs are drop-in
-      // replacements for the text-[11px] / text-[10px] arbitrary values that
-      // dominate the consumer apps.
-      fontSize: {
-        '2xs': '0.6875rem', // 11px
-        '3xs': '0.625rem',  // 10px
-      },
-      colors: {
-        // Theme-aware semantic tokens (reference CSS variables)
-        page:          'var(--color-page)',
-        surface:       'var(--color-surface)',
-        'surface-alt': 'var(--color-surface-alt)',
-        inset:         'var(--color-inset)',
-
-        // Dynamic primary palette (from theme role colors)
-        primary: {
-          DEFAULT: 'rgb(var(--color-primary-rgb) / <alpha-value>)',
-          50:  'rgb(var(--color-primary-50-rgb) / <alpha-value>)',
-          100: 'rgb(var(--color-primary-100-rgb) / <alpha-value>)',
-          200: 'rgb(var(--color-primary-200-rgb) / <alpha-value>)',
-          300: 'rgb(var(--color-primary-300-rgb) / <alpha-value>)',
-          400: 'rgb(var(--color-primary-400-rgb) / <alpha-value>)',
-          500: 'rgb(var(--color-primary-500-rgb) / <alpha-value>)',
-          600: 'rgb(var(--color-primary-600-rgb) / <alpha-value>)',
-          700: 'rgb(var(--color-primary-700-rgb) / <alpha-value>)',
-          800: 'rgb(var(--color-primary-800-rgb) / <alpha-value>)',
-          900: 'rgb(var(--color-primary-900-rgb) / <alpha-value>)',
-        },
-
-        mint: {
-          DEFAULT: '#06D6A0',
-          50: '#e6faf4',
-          100: '#b3f0de',
-          200: '#80e6c8',
-          300: '#4ddcb2',
-          400: '#1ad29c',
-          500: '#06D6A0',
-          600: '#05b888',
-          700: '#049a70',
-          800: '#037c58',
-          900: '#025e40',
-        },
-        navy: {
-          DEFAULT: '#1A1535',
-          50: '#e8e7ed',
-          100: '#b8b5c8',
-          200: '#8883a3',
-          300: '#58517e',
-          400: '#3a3359',
-          500: '#1A1535',
-          600: '#16122e',
-          700: '#120f27',
-          800: '#0e0c20',
-          900: '#0a0919',
-        },
-        violet: {
-          DEFAULT: '#8E82FE',
-          50: '#f0eeff',
-          100: '#EAE8FF',
-          200: '#b2aafe',
-          300: '#C5C0FE',
-          400: '#8E82FE',
-          500: '#8E82FE',
-          600: '#6558e5',
-          700: '#6558E0',
-          800: '#3b2cb3',
-          900: '#3D2FB5',
-        },
-        mist: '#F7F6FF',
-        lavender: '#E8E6F0',
-        slate: '#6B6580',
-        charcoal: '#2D2648',
-        midnight: '#120F28',
-        ember: '#FF8C69',
-        gold: '#FFD166',
-        magenta: '#F72585',
-      },
-      textColor: {
-        heading:   'var(--color-text)',
-        body:      'var(--color-text-body)',
-        secondary: 'var(--color-text-secondary)',
-        muted:     'var(--color-text-muted)',
-        // The status roles as TEXT. Separate from the success / warning /
-        // danger FILLS below on purpose: a fill can be vivid, but text must
-        // clear WCAG AA 4.5:1 on every surface, and none of the default role
-        // colours does that on BOTH themes (#EF4444, #FF7C47 and #4BAF50 all
-        // fail on the light surfaces). Each ink is derived per theme by
-        // ThemeResolver#contrast_ink. There is deliberately NO text-danger,
-        // text-warning or text-success: a bare role colour as text is the
-        // defect, so it stays uncompilable.
-        'danger-ink':  'var(--color-danger-ink)',
-        'warning-ink': 'var(--color-warning-ink)',
-        'success-ink': 'var(--color-success-ink)',
-        // The primary role as chip text, derived the same way. text-primary
-        // stays the brand colour for links, icons and large text.
-        'primary-ink': 'var(--color-primary-ink)',
-      },
-      // The status-role FILLS: badge tints, flash panels, borders. Registered
-      // for backgrounds and borders ONLY (not `colors`), so that registering
-      // them cannot also mint the text utilities the comment above rules out.
-      backgroundColor: {
-        success: 'var(--color-success)',
-        warning: 'var(--color-warning)',
-        danger:  'var(--color-danger)',
-      },
-      borderColor: {
-        subtle: 'var(--color-border)',
-        strong: 'var(--color-border-strong)',
-        success: 'var(--color-success)',
-        warning: 'var(--color-warning)',
-        danger:  'var(--color-danger)',
-      },
-    },
-  },
-}