RubyGems - plutonium - Versions diffs - 0.59.0 → 0.60.1 - Mend

plutonium 0.59.0 → 0.60.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (42) hide show

checksums.yaml +4 -4
data/.claude/skills/plutonium-auth/SKILL.md +8 -2
data/.claude/skills/plutonium-ui/SKILL.md +12 -0
data/CHANGELOG.md +15 -0
data/app/assets/plutonium.css +1 -1
data/docs/reference/auth/accounts.md +7 -0
data/docs/reference/configuration.md +1 -1
data/docs/reference/resource/definition.md +129 -0
data/docs/reference/ui/forms.md +51 -21
data/docs/reference/ui/layouts.md +37 -1
data/docs/superpowers/plans/2026-06-14-form-sectioning.md +926 -0
data/docs/superpowers/plans/2026-06-14-form-sectioning.md.tasks.json +40 -0
data/docs/superpowers/plans/2026-06-14-railless-portal.md +761 -0
data/docs/superpowers/plans/2026-06-14-railless-portal.md.tasks.json +51 -0
data/docs/superpowers/specs/2026-06-14-form-sectioning-design.md +247 -0
data/docs/superpowers/specs/2026-06-14-railless-portal-design.md +275 -0
data/gemfiles/rails_7.gemfile.lock +1 -1
data/gemfiles/rails_8.0.gemfile.lock +1 -1
data/gemfiles/rails_8.1.gemfile.lock +1 -1
data/lib/generators/pu/core/install/templates/config/initializers/plutonium.rb +1 -0
data/lib/generators/pu/rodauth/admin_generator.rb +5 -2
data/lib/generators/pu/rodauth/migration_generator.rb +1 -1
data/lib/generators/pu/rodauth/templates/app/interactions/resend_admin_interaction.rb.tt +18 -0
data/lib/generators/pu/rodauth/views_generator.rb +1 -1
data/lib/plutonium/auth/rodauth.rb +2 -1
data/lib/plutonium/configuration.rb +2 -1
data/lib/plutonium/core/controller.rb +19 -0
data/lib/plutonium/definition/base.rb +1 -0
data/lib/plutonium/definition/form_layout.rb +143 -0
data/lib/plutonium/interaction/base.rb +1 -0
data/lib/plutonium/package/engine.rb +17 -7
data/lib/plutonium/ui/form/components/section.rb +58 -0
data/lib/plutonium/ui/form/components/sticky_footer.rb +1 -1
data/lib/plutonium/ui/form/resource.rb +85 -7
data/lib/plutonium/ui/layout/base.rb +5 -0
data/lib/plutonium/ui/layout/resource_layout.rb +22 -6
data/lib/plutonium/ui/layout/topbar.rb +1 -1
data/lib/plutonium/version.rb +1 -1
data/package.json +1 -1
data/src/css/components.css +9 -0
data/src/css/slim_select.css +11 -2
metadata +11 -2

data/docs/superpowers/plans/2026-06-14-railless-portal.md.tasks.json ADDED Viewed

@@ -0,0 +1,51 @@
+{
+  "planPath": "docs/superpowers/plans/2026-06-14-railless-portal.md",
+  "tasks": [
+    {
+      "id": 1,
+      "subject": "Task 1: Controller rail DSL + rail? resolution",
+      "status": "completed",
+      "description": "**Goal:** Add inherited `rail` class DSL and `rail?` predicate to `Plutonium::Core::Controller`, defaulting from `config.shell`.\n\n**Files:** Modify lib/plutonium/core/controller.rb; create test/plutonium/core/controller_rail_test.rb\n\n```json:metadata\n{\"files\": [\"lib/plutonium/core/controller.rb\", \"test/plutonium/core/controller_rail_test.rb\"], \"verifyCommand\": \"bundle exec appraisal rails-8.1 ruby -Itest test/plutonium/core/controller_rail_test.rb\", \"acceptanceCriteria\": [\"rail? resolves shell default\", \"rail DSL overrides + inherits\", \"rail? public helper\"], \"requiresUserVerification\": false}\n```"
+    },
+    {
+      "id": 2,
+      "subject": "Task 2: Gate ResourceLayout rendering on rail?",
+      "status": "completed",
+      "blockedBy": [1],
+      "description": "**Goal:** ResourceLayout delegates rail? to controller; skips sidebar partial, initial pin script, and main rail offset when rail-less; emits pu-no-rail on <html>.\n\n**Files:** Modify lib/plutonium/ui/layout/resource_layout.rb; create test/plutonium/ui/layout/resource_layout_rail_test.rb\n\n```json:metadata\n{\"files\": [\"lib/plutonium/ui/layout/resource_layout.rb\", \"test/plutonium/ui/layout/resource_layout_rail_test.rb\"], \"verifyCommand\": \"bundle exec appraisal rails-8.1 ruby -Itest test/plutonium/ui/layout/resource_layout_rail_test.rb\", \"acceptanceCriteria\": [\"rail? delegates\", \"sidebar/pin gated\", \"main_attributes branches\", \"pu-no-rail emitted\"], \"requiresUserVerification\": false}\n```"
+    },
+    {
+      "id": 3,
+      "subject": "Task 3: Stable hooks + pu-no-rail CSS + asset build",
+      "status": "completed",
+      "description": "**Goal:** Add pu-topbar/pu-sticky-footer classes; CSS cancels lg:left-14 under html.pu-no-rail; rebuild assets via yarn build.\n\n**Files:** Modify topbar.rb, sticky_footer.rb, src/css/components.css; regenerate app/assets/plutonium.css + .min.js; modify topbar_test.rb, sticky_footer_test.rb\n\n```json:metadata\n{\"files\": [\"lib/plutonium/ui/layout/topbar.rb\", \"lib/plutonium/ui/form/components/sticky_footer.rb\", \"src/css/components.css\", \"app/assets/plutonium.css\", \"app/assets/plutonium.min.js\", \"test/plutonium/ui/layout/topbar_test.rb\", \"test/plutonium/ui/form/components/sticky_footer_test.rb\"], \"verifyCommand\": \"bundle exec appraisal rails-8.1 ruby -Itest test/plutonium/ui/layout/topbar_test.rb test/plutonium/ui/form/components/sticky_footer_test.rb\", \"acceptanceCriteria\": [\"hook classes added\", \"CSS cancel rule\", \"assets rebuilt\"], \"requiresUserVerification\": false}\n```"
+    },
+    {
+      "id": 4,
+      "subject": "Task 4: Integration test for plain vs modern shell",
+      "status": "completed",
+      "blockedBy": [1, 2, 3],
+      "description": "**Goal:** End-to-end: plain shell omits icon-rail + pin script, has pu-no-rail; modern unchanged.\n\n**Files:** create test/integration/plain_shell_rendering_test.rb\n\n```json:metadata\n{\"files\": [\"test/integration/plain_shell_rendering_test.rb\"], \"verifyCommand\": \"bundle exec appraisal rails-8.1 ruby -Itest test/integration/plain_shell_rendering_test.rb\", \"acceptanceCriteria\": [\"plain rail-less e2e\", \"modern unchanged\", \"shell restored\"], \"requiresUserVerification\": false}\n```"
+    },
+    {
+      "id": 5,
+      "subject": "Task 5: Named current_<account> Rodauth accessor",
+      "status": "completed",
+      "description": "**Goal:** Rodauth(name) exposes current_<name> aliased to current_user, both helper methods.\n\n**Files:** Modify lib/plutonium/auth/rodauth.rb; modify test/plutonium/auth/rodauth_test.rb\n\n```json:metadata\n{\"files\": [\"lib/plutonium/auth/rodauth.rb\", \"test/plutonium/auth/rodauth_test.rb\"], \"verifyCommand\": \"bundle exec appraisal rails-8.1 ruby -Itest test/plutonium/auth/rodauth_test.rb\", \"acceptanceCriteria\": [\"named accessor helper\", \"same account\", \"user name no-op safe\"], \"requiresUserVerification\": false}\n```"
+    },
+    {
+      "id": 6,
+      "subject": "Task 6: Docs + config comments",
+      "status": "completed",
+      "blockedBy": [1, 2, 3, 5],
+      "description": "**Goal:** Document :plain shell, rail DSL, named accessor; comment shell config sites.\n\n**Files:** Modify lib/plutonium/configuration.rb, lib/generators/pu/core/install/templates/config/initializers/plutonium.rb, docs/, .claude/skills/\n\n```json:metadata\n{\"files\": [\"lib/plutonium/configuration.rb\", \"lib/generators/pu/core/install/templates/config/initializers/plutonium.rb\", \"docs\", \".claude/skills\"], \"verifyCommand\": \"yarn docs:build\", \"acceptanceCriteria\": [\"config doc\", \"initializer comment\", \"docs+skills updated\"], \"requiresUserVerification\": false}\n```"
+    },
+    {
+      "id": 7,
+      "subject": "Task 7: Fix final-review findings (pu-no-rail Turbo nav + plain offset)",
+      "status": "completed",
+      "description": "**Goal:** From the final holistic review: (1) the turbo:before-render listener in base.rb now toggles pu-no-rail (inverse of hasRail, gated to non-classic shells) so the class stays consistent across Turbo navigations; (2) main_attributes keys the modern-family offset off rail? so :plain+rail true gets lg:pl-20. Commit f60bb5cd.\n\n**Files:** lib/plutonium/ui/layout/base.rb, lib/plutonium/ui/layout/resource_layout.rb, test/plutonium/ui/layout/resource_layout_rail_test.rb, test/integration/plain_shell_rendering_test.rb\n\n```json:metadata\n{\"files\": [\"lib/plutonium/ui/layout/base.rb\", \"lib/plutonium/ui/layout/resource_layout.rb\", \"test/plutonium/ui/layout/resource_layout_rail_test.rb\", \"test/integration/plain_shell_rendering_test.rb\"], \"verifyCommand\": \"bundle exec appraisal rails-8.1 rake test\", \"acceptanceCriteria\": [\"listener toggles pu-no-rail (non-classic)\", \"plain+rail true gets lg:pl-20\"], \"requiresUserVerification\": false}\n```"
+    }
+  ],
+  "lastUpdated": "2026-06-15T00:00:00Z"
+}

data/docs/superpowers/specs/2026-06-14-form-sectioning-design.md ADDED Viewed

@@ -0,0 +1,247 @@
+# Form Sectioning — Design
+**Date:** 2026-06-14
+**Status:** Approved (pending spec review)
+## Problem
+Plutonium forms render every field in a single responsive grid
+(`Form::Resource#render_fields` walks a flat `resource_fields` list inside one
+`fields_wrapper`). There is no way to group fields under headings ("Personal
+details", "Address", …). We want a clean DSL for *sectioning* forms that works
+for both resource definitions and interactions, without disturbing per-field
+configuration.
+## Constraints discovered in the codebase
+- **Field config lives in the definition** (`input :x, ...` via
+  `DefineableProps`, stored as ordered hashes), but the **set and order of
+  fields actually rendered come from the policy** (`permitted_attributes_for(action)`,
+  via `submittable_attributes_for`). The form receives that flat list as
+  `resource_fields`.
+- **Interactions reuse the resource form.** `Form::Interaction < Form::Resource`
+  and only swaps in `resource_fields` (from `interaction.attribute_names`) and
+  `resource_definition` (the interaction instance). So sectioning added to
+  `Form::Resource#render_fields` is inherited by interactions for free.
+- The shared definition DSL is composed from `Plutonium::Definition::*` concern
+  modules. `StructuredInputs` is the precedent for a module mixed into **both**
+  `Definition::Base` and `Interaction::Base`.
+Therefore: sectioning is a **presentation concern declared in the definition**
+that must group a **policy-driven** field list — skipping fields the policy
+filtered out and hiding sections that end up empty.
+## DSL
+A new shared module `Plutonium::Definition::FormLayout` provides `form_layout`.
+```ruby
+form_layout do
+  section :identity, :name, :date_of_birth, :grade,
+    label: "Your identification", description: "Basic info"
+  section :address, :street, :city, :country,
+    collapsible: true, columns: 2,
+    condition: -> { object.requires_address? }
+  ungrouped label: "Other", collapsible: true
+end
+```
+### `section(key, *fields, **opts)`
+- `key` — Symbol, the section's identity. Heading defaults to `key.to_s.humanize`.
+  `:ungrouped` is **reserved** for the macro below — `section :ungrouped, …`
+  raises `ArgumentError`.
+- `*fields` — ordered field keys placed in this section.
+- `**opts`:
+  - `label:` — overrides the humanized heading.
+  - `description:` — optional help line under the heading.
+  - `collapsible:` — Boolean (default `false`). Renders as a native
+    `<details>/<summary>` disclosure (no JS).
+  - `collapsed:` — Boolean (default `false`). Initial state when collapsible;
+    `false` ⇒ the `<details>` is `open`.
+  - `columns:` — Integer overriding the section's grid column count. Default
+    inherits the form's responsive grid.
+  - `condition:` — lambda evaluated in the **form instance context** (same
+    semantics as `input ..., condition:`; `object` and helpers available). A
+    falsey result renders nothing for the section.
+### `ungrouped(**opts)`
+- Configures the implicit bucket that auto-collects every permitted field not
+  claimed by a `section`. Takes **no field list**.
+- Accepts the same options as `section` (`label:`, `description:`,
+  `collapsible:`, `collapsed:`, `columns:`, `condition:`).
+- **Position:** where the macro is called sets where leftovers render. If the
+  macro is omitted, leftovers render **last** (appended after all declared
+  sections), with **no heading**. _(Amended — was "first"; see Amendments.)_
+- Calling `ungrouped` more than once in a single `form_layout` raises
+  `ArgumentError`.
+### Field configuration stays on `input`
+`form_layout`/`section` only reference field **keys** and carry **section-level**
+options. All per-field rendering config (`as:`, the field's own `label:`,
+`choices:`, per-field `condition:`, `pre_submit:`, blocks) remains on the `input`
+declaration. Layout never duplicates field config.
+### Inheritance / override
+- Re-declaring `form_layout` in a subclass **replaces** the parent layout as a
+  unit. Field-level `input` config continues to inherit normally.
+- The section registry is duplicated to subclasses on `inherited` (mirrors
+  `StructuredInputs`).
+### Backwards compatibility
+No `form_layout` declared ⇒ the current single-grid behavior is used unchanged.
+This is equivalent to one implicit, heading-less `ungrouped` region.
+## Rendering
+`Plutonium::Definition::FormLayout` exposes an ordered, frozen registry of
+section specs (and the `ungrouped` spec + its position) on definition and
+interaction instances.
+`Form::Resource#render_fields` becomes:
+1. **No layout** → existing path: one `fields_wrapper` over all `resource_fields`.
+2. **Layout present**:
+   - Assign each `section` its `fields ∩ resource_fields`, preserving the
+     section's declared field order.
+   - The `ungrouped` bucket gets `resource_fields` minus all claimed fields,
+     preserving `resource_fields` order.
+   - Build the ordered render list: sections in declared order with the
+     `ungrouped` bucket inserted at its declared position (default: **last**).
+   - For each entry: evaluate `condition` (skip if falsey); render a Section
+     component with its renderable fields. Empty sections are **not**
+     special-cased — they render with defaults (see Edge cases).
+Field rendering itself still goes through the existing `render_resource_field`,
+so all input types/components are unaffected.
+### Section component
+New `Plutonium::UI::Form::Components::Section` (Phlex). Responsibilities:
+- Wrapper + heading (`label`) + optional `description`.
+- When `collapsible`, wrap in native `<details>`/`<summary>` (`open` unless
+  `collapsed`), styled with Tailwind/`--pu-*` tokens.
+- A grid (`fields_wrapper`-style) whose column count comes from `columns:` when
+  given, else the existing responsive default
+  (`grid-cols-1 md:grid-cols-2 2xl:grid-cols-4`).
+- Yields to render the section's fields via `render_resource_field`.
+A small helper maps `columns:` → grid classes (e.g. `1 → "grid grid-cols-1 gap-6"`,
+`2 → "grid grid-cols-1 md:grid-cols-2 gap-6"`). Theme entries added for section
+heading/description/wrapper so they're themeable like the rest of the form.
+## Edge cases
+- **Field permitted but in no section** → falls into `ungrouped`.
+- **Section references a policy-filtered field** → that individual field is
+  skipped (no input is rendered for an unpermitted attribute).
+- **Empty section** (all fields filtered out, or none assigned) → **not
+  hidden**. It renders through the normal path with defaults (its default/declared
+  chrome). There is no automatic empty-hiding; to hide a section conditionally,
+  use `condition:`.
+- **Field key in a `section` not in the permitted set** (a typo, or filtered by
+  policy / per-action / scoping / nesting) → **silently skipped**, never an
+  error. _(Amended — originally raised; see Amendments.)_
+- **`condition` falsey** → section renders nothing; its fields do **not** spill
+  into `ungrouped` (they remain owned by the suppressed section).
+- **No leftovers** → `ungrouped` renders with defaults (with no fields and no
+  configured heading, that is simply nothing visible; a configured `label:`
+  still renders).
+## Files
+- **New** `lib/plutonium/definition/form_layout.rb` — DSL module: `form_layout`
+  block builder, ordered + inheritable section registry, `section` / `ungrouped`,
+  instance readers, validation (duplicate `ungrouped`, etc.).
+- **Modify** `lib/plutonium/definition/base.rb` — `include FormLayout`.
+- **Modify** `lib/plutonium/interaction/base.rb` — `include FormLayout`.
+- **New** `lib/plutonium/ui/form/components/section.rb` — section component.
+- **Modify** `lib/plutonium/ui/form/resource.rb` — `render_fields` grouping; columns→grid helper.
+- **Modify** `lib/plutonium/ui/form/theme.rb` — section heading/description/wrapper tokens.
+## Testing (RSpec)
+- **DSL/registry:** sections recorded in order with options; `ungrouped` spec +
+  position; humanized default label; `label:` override; duplicate `ungrouped`
+  raises; `section :ungrouped` raises; inheritance duplicates registry;
+  re-declaring `form_layout` replaces.
+- **Assignment:** fields land in the right section in declared order; leftovers
+  collect into `ungrouped`; `ungrouped` default position is last; explicit
+  position honored.
+- **Filtering:** a field not in the permitted set (policy-filtered or a typo) is
+  skipped; an empty section still renders with defaults (is **not** hidden).
+- **Conditions:** falsey `condition` hides the section and withholds its fields.
+- **Rendering:** headings/descriptions present; collapsible emits
+  `<details>`/`<summary>` with correct `open`; `columns:` changes grid classes.
+- **Interactions:** an interaction with `form_layout` sections renders grouped
+  via `Form::Interaction`.
+- **Backwards-compat:** a definition with no `form_layout` renders the single
+  grid exactly as before.
+## Out of scope (YAGNI)
+- Applying sections to show/display pages or the index grid (forms only for now;
+  the same registry could later be reused by `Display::Resource`).
+- Nested sections / tabs.
+- Per-field layout hints (e.g. `field :notes, span: 2`) — Style 1 keeps fields
+  positional; this can be added later via the nested-block form if needed.
+- Stimulus-driven animated collapse (native `<details>` chosen for leanness).
+## Amendments (post-implementation)
+Changes made after the original plan landed:
+- **Implicit `ungrouped` placement: first → last.** When no `ungrouped` macro is
+  declared, leftover fields are now appended **after** all declared sections
+  (was: prepended). This matches the convention of the explicit macro ("the
+  rest" trails the sections you care about) and makes "omit it" equivalent to
+  "declare it last." To float leftovers above your sections, declare `ungrouped`
+  explicitly at the top.
+- **`columns:` actually lays out in a grid.** Previously every field wrapper got
+  `col-span-full`, so a section's `columns: N` had no visible effect. Fields in a
+  multi-column section now flow into single grid cells. A field that declares its
+  own span (`input :x, wrapper: {class: "col-span-..."}`) **always wins** — in any
+  section — so authors can opt a field back to full width (or wider) inside a
+  multi-column section.
+- **Dynamic section options.** Every section option except `columns:`
+  (`collapsed`, `collapsible`, `label`, `description`, plus the existing
+  `condition`) may be a **proc**, resolved at render time in the form instance
+  context — the same context as input/section `condition:` (so `object`,
+  `current_user`, `params`, helpers are available). The whole layout is resolved
+  once per render in `Form::Resource#resolve_form_layout` (visibility + option
+  evaluation in one pass); `render_form_section` is pure presentation. `columns:`
+  stays a validated literal (it feeds the grid class).
+- **Unknown / filtered field keys are skipped, not raised.** A `section` key not
+  in the form's permitted set (`submittable_attributes_for(action)`) is silently
+  dropped instead of raising `ArgumentError`. The original raise couldn't tell a
+  typo from a field that's simply not permitted in the current context (per-action
+  `permitted_attributes`, entity scoping, nesting, per-user policy), so it crashed
+  forms that referenced conditionally-permitted fields. Skipping makes one
+  `form_layout` safe across all those contexts. (`resolve_form_sections` only ever
+  saw the filtered list, so it could never reliably distinguish typo from filtered
+  anyway.)
+- **Interactions: verified + exercised.** `Form::Interaction < Form::Resource`
+  already inherited the layout path; this is now covered by a dummy interaction
+  (`ReconfigureKitchenSink`, a record action on `KitchenSink`) and an integration
+  test. In an interaction form `object` is the interaction instance and
+  `object.resource` is the record, so record-aware dynamic options work there too
+  (e.g. `collapsed: -> { object.resource.archived? }`).
+- **Unrelated fix surfaced while driving the dummy in `development`:** the package
+  engine system (`Plutonium::Package::Engine`) called `Rails.application.initializers`
+  from a `before_configuration` hook, prematurely memoizing `Rails.application.railties`
+  and dropping package engines from the autoload paths when a second
+  `Rails::Application` (combustion, in dev) was instantiated before the packages
+  glob ran — surfacing as `uninitialized constant Blogging::Post`. The view-path
+  neutralization was moved to a real initializer (`before: :add_view_paths`).

data/docs/superpowers/specs/2026-06-14-railless-portal-design.md ADDED Viewed

@@ -0,0 +1,275 @@
+# Railless portal support — design
+**Date:** 2026-06-14
+**Status:** Approved (pending spec review)
+**Source:** Bug report — "Plutonium 0.60.0 — railless portal gets phantom icon-rail offsets"
+## Problem
+A portal that intentionally omits the icon rail (a supported customization)
+still inherits layout offsets that assume the 56px icon rail is always present
+on desktop (≥1024px). Symptoms:
+1. Main content pushed ~15.5rem right (empty left gutter / "tilt").
+2. Form sticky action footer has a 56px dead gap on its left edge.
+Both stem from one assumption — *the icon rail always exists* — leaking into
+four places, with no first-class "no rail" opt-out:
+| # | Source | Footprint |
+|---|--------|-----------|
+| 1 | `ResourceLayout#render_pre_paint_scripts` adds `pu-rail-pinned` on initial load (gated only on a `localStorage` flag) → CSS `html.pu-rail-pinned main { padding-left: 15.5rem !important }` | 15.5rem main offset |
+| 2 | `ResourceLayout#main_attributes` `lg:pl-20` (collapsed-rail 80px offset, applied even when unpinned) | 5rem main offset |
+| 3 | `Topbar` `lg:left-14` | 56px topbar inset |
+| 4 | `StickyFooter` `lg:left-14` | 56px footer inset |
+Key existing asymmetry: the `turbo:before-render` listener in
+`Base#render_pre_paint_scripts` *already* keys `pu-rail-pinned` on
+`newBody.querySelector('[data-controller~="icon-rail"]')` — i.e. on actual rail
+presence. Only the **initial-load** path and the static CSS/utility classes
+hardcode the assumption.
+## Goals
+- First-class "no rail" mode, resolvable globally **and** per-portal/per-controller.
+- One source of truth so all four offsets stay consistent.
+- Stable hooks on `Topbar`/`StickyFooter` for consumer overrides (the report's ask).
+- Zero behavior change for existing `:modern` (railed) apps. Low regression risk.
+## Non-goals
+- No full CSS refactor of the rail system (rejected Approach C — largest/riskiest diff).
+- No branding solution for the rail-less topbar (the brand mark lives in
+  `IconRail`'s `with_brand` slot today; `:plain`-shell users add branding to
+  their ejected header). Flagged as a follow-up, out of scope here.
+- `:classic` shell behavior is preserved unchanged (see Classic shell note).
+## Design — Approach A: `rail?` predicate as single source of truth
+A single boolean, `rail?`, resolved through three tiers (each overrides the one
+above), drives every offset. Per the decision: implement the **config** tier and
+the **engine/controller** tier; the layout simply delegates to the controller.
+### Tier 1 — Global: `config.shell`
+`lib/plutonium/configuration.rb`
+- Recognize a new shell value `:plain` (rail-less modern shell). `:modern`
+  keeps today's rail. No validation is added (shell is already a permissive
+  `attr_accessor`); `:plain` is just supported everywhere shell is consumed.
+```ruby
+config.shell = :plain   # whole app rail-less by default
+```
+### Tier 2 — Controller: `rail` DSL (primary per-scope hook)
+`lib/plutonium/core/controller.rb` (the concern that sets `layout "resource"`,
+so it is included in every controller that renders `ResourceLayout`).
+```ruby
+included do
+  class_attribute :_rail_enabled, instance_writer: false, default: nil
+  helper_method :rail?
+end
+class_methods do
+  def rail(enabled)
+    self._rail_enabled = enabled
+  end
+end
+# nil = inherit the shell default; true/false = explicit override
+def rail?
+  return _rail_enabled unless _rail_enabled.nil?
+  Plutonium.configuration.shell == :modern
+end
+```
+Because `_rail_enabled` is a `class_attribute`, it is **inherited**. A portal
+opts its whole surface in/out by setting it once in its engine's controller
+concern — no view ejection:
+```ruby
+module CustomerPortal
+  module Concerns
+    module Controller
+      extend ActiveSupport::Concern
+      included { rail false }   # entire portal rail-less
+    end
+  end
+end
+```
+A single controller can flip it for just its resource. `nil` means "inherit",
+so leaving it unset falls through to the shell default with no accidental
+override.
+### Tier 3 — Layout: delegate to the controller
+`lib/plutonium/ui/layout/resource_layout.rb`
+```ruby
+def rail? = controller.rail?
+```
+`controller` is already available in the layout component (used for
+`@page_title`). A layout subclass *can* still override `rail?` for pure
+view-level logic, but the controller tier covers the portal and per-resource
+cases without ejecting a layout view.
+### What `rail?` gates
+`ResourceLayout`:
+```ruby
+def render_before_main
+  super
+  render partial("resource_header")
+  render partial("resource_sidebar") if rail?   # skip the IconRail when rail-less
+end
+def render_pre_paint_scripts
+  super
+  return unless rail?                            # no initial pu-rail-pinned when rail-less
+  script { ... existing initial-load pin ... }
+end
+def main_attributes
+  classes = case Plutonium.configuration.shell
+  when :modern
+    rail? ? "pt-16 pb-6 px-6 lg:pl-20" : "pt-16 pb-6 px-6"
+  when :plain
+    "pt-16 pb-6 px-6"
+  else # :classic — unchanged
+    "pt-20 lg:ml-64"
+  end
+  mix(super, {class: classes})
+end
+# add a server-rendered root class (no FOUC) so decoupled fixed components
+# can cancel their rail insets. Scoped to the modern family so :classic is
+# byte-for-byte unchanged.
+def html_attributes
+  attrs = super
+  return attrs if Plutonium.configuration.shell == :classic
+  rail? ? attrs : mix(attrs, {class: "pu-no-rail"})
+end
+```
+### Decoupled components — stable hooks + CSS cancel
+`Topbar` and `StickyFooter` are rendered outside the layout's reach (Topbar from
+a partial, StickyFooter from every form), so they can't read `rail?` directly.
+They keep their `lg:left-14` inset and gain a **stable class** so CSS keyed on
+the root `pu-no-rail` class can cancel the inset — this also satisfies the
+report's "stable hook" request.
+- `lib/plutonium/ui/layout/topbar.rb` — add `pu-topbar` to the `nav` class.
+- `lib/plutonium/ui/form/components/sticky_footer.rb` — add `pu-sticky-footer`
+  to the `div` class.
+`src/css/components.css`:
+```css
+@media (min-width: 1024px) {
+  html.pu-no-rail .pu-topbar,
+  html.pu-no-rail .pu-sticky-footer {
+    left: 0 !important;
+  }
+}
+```
+No CSS change is needed for `main`: the 15.5rem pinned padding only applies when
+`pu-rail-pinned` is present (never added when rail-less), and the collapsed
+`lg:pl-20` is dropped in `main_attributes`.
+> **Asset build:** `src/css/components.css` is the source; the shipped
+> `app/assets/plutonium.css` (and `.min`) must be rebuilt with `yarn build`
+> (`yarn dev` while developing).
+### Cross-navigation correctness (already handled)
+The `turbo:before-render` listener in `Base` keys `pu-rail-pinned` on
+`querySelector('[data-controller~="icon-rail"]')`. A rail-less page renders no
+`icon-rail` controller, so navigating rail → rail-less correctly drops the pin,
+matching the server-rendered `pu-no-rail`. No JS change required.
+### Classic shell note
+`:classic` is preserved unchanged: its `main_attributes` branch is untouched,
+`pu-no-rail` is never emitted for it, and the initial-load pin is now gated on
+`rail?` (false for classic) — which also removes a previously latent spurious
+`pu-rail-pinned` emission for classic apps. Net: strictly equal or better.
+## Auth: named `current_<account>` accessor (folds in the report appendix)
+**Finding:** the report's appendix is *not* a generator bug. The portal
+generator (`concerns/controller.rb.tt`) never emits `current_admin` /
+`require_admin_role`, and `Plutonium::Auth::Rodauth(name)`
+(`lib/plutonium/auth/rodauth.rb`) deliberately exposes `current_user`
+(= `rodauth(name).rails_account`) regardless of account name. The `current_admin`
+in the report is hand-written app code; calling it raises `NoMethodError`.
+**Improvement:** expose a **named** accessor alongside `current_user` so
+multi-account code reads naturally and an admin session is distinguishable from
+a user session.
+`lib/plutonium/auth/rodauth.rb` — in addition to `current_user`, define
+`current_<name>` aliased to the same `rails_account`, and register it as a
+helper method:
+```ruby
+included do
+  helper_method :current_user, :current_#{name}
+  helper_method :logout_url, :profile_url
+end
+def current_user
+  rodauth.rails_account
+end
+alias_method :current_#{name}, :current_user
+```
+So `include Plutonium::Auth::Rodauth(:admin)` yields both `current_user` and
+`current_admin`. Additive, backward-compatible. (When `name == :user`,
+`current_#{name}` is just `current_user` — harmless re-definition.)
+Docs: note the correct pattern and the new named accessor in the auth guide /
+`plutonium-auth` skill.
+## Files touched
+- `lib/plutonium/configuration.rb` — support `:plain` shell (doc/comments).
+- `lib/plutonium/core/controller.rb` — `rail` DSL + `rail?` + `helper_method`.
+- `lib/plutonium/ui/layout/resource_layout.rb` — `rail?` delegate; gate
+  `render_before_main`, `render_pre_paint_scripts`, `main_attributes`,
+  `html_attributes`.
+- `lib/plutonium/ui/layout/topbar.rb` — `pu-topbar` class.
+- `lib/plutonium/ui/form/components/sticky_footer.rb` — `pu-sticky-footer` class.
+- `src/css/components.css` — `html.pu-no-rail` inset cancel; rebuild assets.
+- `lib/plutonium/auth/rodauth.rb` — named `current_<account>` accessor.
+- Docs: shell/`:plain` + `rail` DSL (UI/app guide, `plutonium-ui`/`plutonium-app`
+  skills); named accessor (`plutonium-auth` skill).
+## Testing strategy
+- **Controller resolution** (unit): `rail?` returns `true` for `:modern`,
+  `false` for `:plain`/`:classic`; `rail true`/`rail false` override the shell
+  default; `nil` inherits; the class_attribute inherits to subclasses.
+- **Layout rendering** (component/integration): with `rail?` false — sidebar
+  partial absent, no `pu-rail-pinned` script, no `lg:pl-20` on `main`,
+  `pu-no-rail` present on `<html>`. With `rail?` true — current markup unchanged.
+- **Dummy app**: add a controller/portal that sets `rail false`; assert the
+  rendered page has `pu-no-rail` and the form's sticky footer carries
+  `pu-sticky-footer` (so the CSS cancel applies). Use the existing
+  `plutonium-testing` toolkit.
+- **Auth** (unit): `Plutonium::Auth::Rodauth(:admin)` exposes both
+  `current_user` and `current_admin` returning the same account.
+- Run across Rails 7 / 8.0 / 8.1 via Appraisal.
+## Rollout / compatibility
+Fully additive. Existing `:modern` apps emit no `pu-no-rail` and render
+identical markup. `:plain` is opt-in via config; `rail false` is opt-in per
+controller/portal. Asset rebuild required for the CSS rule to ship.

data/gemfiles/rails_7.gemfile.lock CHANGED Viewed

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    plutonium (0.58.1)
+    plutonium (0.59.0)
       action_policy (~> 0.7.0)
       csv
       listen (~> 3.8)

data/gemfiles/rails_8.0.gemfile.lock CHANGED Viewed

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    plutonium (0.58.1)
+    plutonium (0.59.0)
       action_policy (~> 0.7.0)
       csv
       listen (~> 3.8)

data/gemfiles/rails_8.1.gemfile.lock CHANGED Viewed

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    plutonium (0.58.1)
+    plutonium (0.59.0)
       action_policy (~> 0.7.0)
       csv
       listen (~> 3.8)

data/lib/generators/pu/core/install/templates/config/initializers/plutonium.rb CHANGED Viewed

@@ -3,6 +3,7 @@
 Plutonium.configure do |config|
   config.load_defaults 1.0
+  # Shell variant: :modern (icon rail), :plain (no rail), or :classic (legacy).
   config.shell = :modern
   # Configure plutonium above.
 end

data/lib/generators/pu/rodauth/admin_generator.rb CHANGED Viewed

@@ -95,13 +95,16 @@ module Pu
       def create_invite_interaction
         template "app/interactions/invite_admin_interaction.rb",
           "app/interactions/#{normalized_name}/invite_interaction.rb"
+        template "app/interactions/resend_admin_interaction.rb",
+          "app/interactions/#{normalized_name}/resend_invite_interaction.rb"
         inject_into_file "app/definitions/#{normalized_name}_definition.rb",
-          "  action :invite, interaction: #{name.classify}::InviteInteraction, collection: true, category: :primary\n",
+          "  action :invite, interaction: #{name.classify}::InviteInteraction, collection: true, category: :primary\n" \
+          "  action :resend_invite, interaction: #{name.classify}::ResendInviteInteraction, record_action: true, category: :secondary\n",
           after: /class #{name.classify}Definition < .+\n/
         inject_into_file "app/policies/#{normalized_name}_policy.rb",
-          "def invite?\n    true\n  end\n\n  ",
+          "def invite?\n    true\n  end\n\n  def resend_invite?\n    record.unverified?\n  end\n\n  ",
           before: "# Core attributes"
       end

data/lib/generators/pu/rodauth/migration_generator.rb CHANGED Viewed

@@ -20,7 +20,7 @@ module Pu
       desc "Generate migrations for supported features\n\n" \
            "Supported Features\n" \
            "=========================================\n" \
-           "#{MIGRATION_CONFIG.keys.sort.map(&:to_s).join "\n"}\n\n\n\n"
+           "#{MIGRATION_CONFIG.keys.sort.join "\n"}\n\n\n\n"
       class_option :features, required: true, type: :array,
         desc: "Rodauth features to create tables for (otp, sms_codes, single_session, account_expiration etc.)"

data/lib/generators/pu/rodauth/templates/app/interactions/resend_admin_interaction.rb.tt ADDED Viewed

@@ -0,0 +1,18 @@
+# frozen_string_literal: true
+class <%= name.classify %>::ResendInviteInteraction < Plutonium::Resource::Interaction
+  presents label: "Resend Invitation", icon: Phlex::TablerIcons::MailForward
+  attribute :resource
+  def execute
+    unless resource.unverified?
+      return failed("Can only resend invitations to unverified accounts")
+    end
+    RodauthApp.rodauth(:<%= normalized_name %>).verify_account_resend(login: resource.email)
+    succeed(resource).with_message("Invitation resent to #{resource.email}")
+  rescue ::Rodauth::InternalRequestError => e
+    failed(e.message)
+  end
+end