plutonium 0.45.2 → 0.46.0

data/docs/superpowers/specs/2026-04-08-plutonium-skills-overhaul-design.md

@@ -0,0 +1,236 @@
+# Plutonium Skills Overhaul — Design
+
+**Date:** 2026-04-08
+**Status:** Approved (pending user review of this doc)
+
+## Problem
+
+The current Plutonium skills (`.claude/skills/plutonium-*`) are content-correct but
+fail to trigger at the right moments. Concrete failure modes observed in real
+sessions:
+
+1. Agents write `relation_scope` overrides without ever loading `plutonium-policy`,
+   bypassing `default_relation_scope` and breaking entity scoping.
+2. Agents hand-write resource files instead of using `pu:res:scaffold`.
+3. Agents miss cross-cutting concerns (multi-tenancy spans 4 skills; nobody reads 4).
+4. Greenfield onboarding is one-skill-at-a-time as the agent stumbles into mistakes.
+5. The definition concept is split across 3 skills — agents read one and miss the others.
+
+Root cause: skill `description:` fields list **topics** ("authorization, attribute
+visibility, relation scoping..."). Agents triage descriptions against **moments**
+("I am about to write `relation_scope`"). Topic-based descriptions don't fire.
+
+## Goals
+
+1. Skills get invoked at the *moment* an agent is about to make a relevant decision.
+2. The most expensive mistakes live in a fixed 🚨 block at the top of the relevant skill.
+3. Cross-cutting concerns (entity scoping especially) are consolidated and discoverable.
+4. **Generators are the default path.** Every skill that touches a generator-backed
+   concern leads with "use `pu:...`, do not hand-write."
+5. **Greenfield onboarding works.** When an agent starts new work, it loads a bundle
+   of foundational skills upfront via the index skill.
+6. The index skill (`plutonium`) acts as a router AND a greenfield bootstrapper.
+7. Critical workflows are checklists; explanation is prose.
+
+## Non-goals
+
+- Not rewriting prose content wholesale — content is mostly correct.
+- No telemetry/measurement infrastructure.
+- No new code examples beyond what's needed for the 🚨 blocks.
+- No skill renames beyond `plutonium-rodauth → plutonium-auth`.
+
+## Final skill set (20 → 17)
+
+### Merges
+
+| New skill | Absorbs | Rationale |
+|---|---|---|
+| `plutonium-definition` | + `plutonium-definition-actions`, `plutonium-definition-query` | Agents writing a definition need all three; today's split causes "read one, miss two" |
+| `plutonium-auth` (renamed from `plutonium-rodauth`) | + `plutonium-profile` | Profile is a thin layer over rodauth, almost never edited independently |
+| `plutonium-assets` | + `plutonium-theming` | Both are "configure the frontend toolchain" — Tailwind + Stimulus + tokens are one mental model |
+
+### New skill
+
+| Skill | Purpose |
+|---|---|
+| `plutonium-entity-scoping` | Consolidates the entity-scoping/multi-tenancy-specific content currently fragmented across `plutonium-model`, `plutonium-policy`, `plutonium-portal`, and `plutonium-invites`. The single source of truth for: `associated_with` resolution, `default_relation_scope` rules, `relation_scope` override safety, entity strategies (path/custom), and the join-table/grandchild model shapes. |
+
+The four source skills retain their general content but defer to
+`plutonium-entity-scoping` for tenancy specifics via cross-reference.
+
+### Stays separate
+
+`plutonium`, `plutonium-installation`, `plutonium-create-resource`, `plutonium-model`,
+`plutonium-policy`, `plutonium-controller`, `plutonium-interaction`, `plutonium-portal`,
+`plutonium-package`, `plutonium-nested-resources`, `plutonium-invites`,
+`plutonium-forms`, `plutonium-views`.
+
+**Final count: 17 skills** (20 − 3 merges + 1 new − 1 rename effect = 17).
+
+## Skill template
+
+Every skill follows this fixed shape so agents always know where to look:
+
+```markdown
+---
+name: plutonium-<topic>
+description: Use BEFORE <specific verb/construct>. Also when <secondary trigger>. <one-line scope>.
+---
+
+# plutonium-<topic>
+
+## 🚨 Critical (read first)
+- **Use generators, not hand-written files.** `pu:<gen>` — never create <X> manually.
+- **<Top anti-pattern #1>** — one-liner + why.
+- **<Top anti-pattern #2>** — one-liner + why.
+- **Related skills you may also need:** [list with one-line reasons]
+
+## When to use this skill
+Checklist of decision points / code constructs that should trigger loading this skill.
+
+## Quick checklist  (bootstrap + high-traffic skills only)
+Numbered checklist for the most common workflow. Agent can TaskCreate from this.
+
+## <Sections — scaled to topic>
+Prose + code examples.
+
+## Gotchas
+The full anti-pattern list with explanations.
+
+## See also
+Cross-references to related skills.
+```
+
+### Template rules
+
+- **Description starts with `Use BEFORE <verb/construct>`** — verbs and code names,
+  not topic nouns. This is the single biggest triggering fix.
+- **🚨 Critical block is fixed-position** (always right after the H1) and capped at
+  ~5 bullets.
+- **Generator-first** is in the 🚨 block of every skill where a generator exists.
+- **Cross-references in 🚨 are mandatory** — the "Related skills" bullet replaces
+  most of the multi-tenancy discoverability problem.
+- **TOC at top of merged skills** so agents can jump to a section without reading
+  the whole file.
+
+## The index skill (`plutonium`) as router + bootstrapper
+
+```markdown
+---
+name: plutonium
+description: Use BEFORE starting any Plutonium work — new app, new feature, or first edit in an unfamiliar area. Routes you to the right skills and bootstraps greenfield work.
+---
+
+# plutonium
+
+## 🚨 Read this first
+- Plutonium is generator-driven. Almost every file you'd hand-write has a `pu:*`
+  generator. Use it. Hand-written files drift from conventions.
+- For greenfield (new app or substantial new feature), load the **bootstrap bundle**
+  below before writing any code.
+- For targeted edits, use the **router table**.
+- For anything touching tenant scoping, load `plutonium-entity-scoping`.
+
+## Greenfield bootstrap bundle
+Triggers: installing Plutonium, adding the first resource of a new domain, building
+a new portal/package, "set up X from scratch", "build me a Y app".
+
+Load ALL of these before writing code:
+1. `plutonium-installation`
+2. `plutonium-create-resource`
+3. `plutonium-model`
+4. `plutonium-policy`
+5. `plutonium-entity-scoping`   ← new
+6. `plutonium-portal`
+7. `plutonium-definition`
+
+## Router (targeted edits)
+| About to... | Load |
+|---|---|
+| Write/edit a model, add associations | `plutonium-model` |
+| Scope a model to a tenant, write `associated_with`, deal with multi-tenancy | `plutonium-entity-scoping` |
+| Write `relation_scope`, `permitted_attributes`, override a policy | `plutonium-policy` (+ `plutonium-entity-scoping` if scoping) |
+| Add fields, search, filters, custom actions to a resource | `plutonium-definition` |
+| Customize a controller action, hook, redirect | `plutonium-controller` |
+| Encapsulate business logic, multi-step ops | `plutonium-interaction` |
+| Build a custom page, panel, table, layout | `plutonium-views` |
+| Customize forms, field builders, inputs | `plutonium-forms` |
+| Configure Tailwind, Stimulus, design tokens | `plutonium-assets` |
+| Set up Rodauth, accounts, profile pages | `plutonium-auth` |
+| Set up user invitations / membership | `plutonium-invites` (+ `plutonium-entity-scoping`) |
+| Configure parent/child resources, nested routes | `plutonium-nested-resources` |
+| Create a portal or feature package | `plutonium-portal` / `plutonium-package` |
+
+## Generator catalog
+[Table of `pu:*` generators with one-line purpose + which skill covers it.]
+```
+
+## Execution phases
+
+### Phase A — Restructure (mechanical)
+1. Merge `plutonium-definition-actions` + `plutonium-definition-query` into
+   `plutonium-definition` with TOC + sections.
+2. Rename `plutonium-rodauth` → `plutonium-auth`; merge `plutonium-profile` into it.
+3. Merge `plutonium-theming` into `plutonium-assets` with TOC + sections.
+4. Delete merged source skills.
+5. Grep the codebase for references to deleted/renamed skill names; update.
+
+### Phase B — Create `plutonium-entity-scoping`
+- Extract entity-scoping content from `plutonium-model`, `plutonium-policy`,
+  `plutonium-portal`, `plutonium-invites`.
+- Single source of truth for: `associated_with`, `default_relation_scope`,
+  `relation_scope` override safety, entity strategies, and the three model shapes
+  (direct child, join-table, grandchild) with worked examples.
+- Source skills keep general content but link here for tenancy specifics.
+
+### Phase C — Rewrite descriptions (every skill)
+- Format: `Use BEFORE <verb/construct>. Also when <secondary>. <scope>.`
+- Each calls out specific code constructs.
+
+### Phase D — Add 🚨 Critical block to every skill
+- Fixed position (right after H1).
+- ~5 bullets max.
+- Pull existing anti-patterns from gotchas to the top.
+
+### Phase E — Rewrite `plutonium` index skill
+- Bootstrap bundle.
+- Router table.
+- Generator catalog.
+
+### Phase F — Quick checklists
+Add to bootstrap-bundle skills + `plutonium-definition` + `plutonium-entity-scoping`.
+Skip for low-traffic skills.
+
+### Phase G — Cross-references
+- Every tenancy-touching skill links to `plutonium-entity-scoping`.
+- Definition / policy / model get mutual cross-refs.
+- Verify bidirectionality.
+
+## Risks & mitigations
+
+| Risk | Mitigation |
+|---|---|
+| Merged skills are bigger → more tokens per load | TOC at top, section anchors, router tells agent which section to jump to |
+| Renaming `plutonium-rodauth → plutonium-auth` breaks references | Grep + update in Phase A step 5; also update CLAUDE.md if mentioned |
+| Description rewrites are subjective | Same pattern for all (`Use BEFORE <verb>`), reviewed for consistency |
+| `plutonium-entity-scoping` could become a dumping ground | Strict scope: only entity scoping itself. General model/policy stuff stays in source skills. |
+| Source skills' tenancy sections become stubs that drift | Rule: source skill has a 🚨 bullet "for entity scoping, see `plutonium-entity-scoping`" and a one-paragraph teaser, nothing more |
+
+## Out of scope
+
+- New code examples beyond 🚨 blocks and the three model-shape examples in
+  `plutonium-entity-scoping`.
+- Telemetry / measurement.
+- Skill content rewrites beyond what's needed for the new structure.
+- Consolidating below 17 skills.
+
+## Success criteria
+
+1. An agent about to write `relation_scope` loads `plutonium-policy` AND
+   `plutonium-entity-scoping` from description triggering alone.
+2. An agent doing greenfield work loads the bootstrap bundle from a single read of
+   `plutonium`.
+3. Every skill that has a generator mentions "use the generator" in its 🚨 block.
+4. The three model shapes (direct child / join table / grandchild) have worked
+   examples in `plutonium-entity-scoping`.
+5. No skill description starts with a topic noun list; all start with `Use BEFORE`.

data/gemfiles/rails_7.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    plutonium (0.45.0)
+    plutonium (0.45.3)
       action_policy (~> 0.7.0)
       listen (~> 3.8)
       pagy (~> 43.0)

data/gemfiles/rails_8.0.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    plutonium (0.45.0)
+    plutonium (0.45.3)
       action_policy (~> 0.7.0)
       listen (~> 3.8)
       pagy (~> 43.0)

data/gemfiles/rails_8.1.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    plutonium (0.45.0)
+    plutonium (0.45.3)
       action_policy (~> 0.7.0)
       listen (~> 3.8)
       pagy (~> 43.0)

data/lib/generators/pu/core/update/update_generator.rb

@@ -12,12 +12,20 @@ module Pu
       def start
         update_gem
         update_npm_package
+        sync_skills_if_present
       rescue => e
         exception "#{self.class} failed:", e
       end
 
       private
 
+      def sync_skills_if_present
+        return unless File.file?(Rails.root.join(".claude", "skills", "plutonium", "SKILL.md"))
+
+        say_status :update, "Syncing Plutonium Claude skills...", :green
+        Rails::Generators.invoke("pu:skills:sync", [], destination_root: Rails.root)
+      end
+
       def update_gem
         say_status :update, "Updating plutonium gem...", :green
         run "bundle update plutonium"

data/lib/generators/pu/gem/active_shrine/active_shrine_generator.rb

@@ -23,9 +23,65 @@ module Pu
 
         generate "active_shrine:install"
         template "config/initializers/shrine.rb", force: true
+
+        disable_active_storage_railtie
+        include_active_shrine_model_in_application_record
       rescue => e
         exception "#{self.class} failed:", e
       end
+
+      private
+
+      # Active Storage and active_shrine both define `has_one_attached`. Active
+      # Storage is loaded by `require "rails/all"`, so it wins by default and
+      # `has_one_attached :foo` quietly creates Active Storage attachments
+      # (which fail at runtime because the table doesn't exist). Replace
+      # `rails/all` with explicit framework requires that exclude
+      # active_storage/engine.
+      def disable_active_storage_railtie
+        return unless File.exist?("config/application.rb")
+        unless File.read("config/application.rb").include?(%(require "rails/all"))
+          say_status :warn,
+            "config/application.rb does not use `require \"rails/all\"`; skipping Active Storage railtie removal. " \
+            "Ensure active_storage/engine is NOT required, or `has_one_attached` will resolve to Active Storage instead of active_shrine.",
+            :yellow
+          return
+        end
+
+        gsub_file "config/application.rb",
+          /^require "rails\/all"$/,
+          <<~RUBY.strip
+            require "rails"
+            # Active Storage is intentionally excluded — file uploads use active_shrine.
+            %w[
+              active_record/railtie
+              active_model/railtie
+              active_job/railtie
+              action_controller/railtie
+              action_view/railtie
+              action_mailer/railtie
+              action_cable/engine
+              rails/test_unit/railtie
+            ].each { |railtie| require railtie }
+          RUBY
+
+        # Strip per-environment active_storage.service config since the railtie
+        # is gone.
+        Dir.glob("config/environments/*.rb").each do |env_file|
+          gsub_file env_file,
+            /^\s*config\.active_storage\.service\s*=.*\n/,
+            ""
+        end
+      end
+
+      # Include ActiveShrine::Model on ApplicationRecord so the gem's
+      # `has_one_attached` / `has_many_attached` macros are available everywhere.
+      def include_active_shrine_model_in_application_record
+        return unless File.exist?("app/models/application_record.rb")
+        return if File.read("app/models/application_record.rb").include?("ActiveShrine::Model")
+
+        inject_into_class "app/models/application_record.rb", "ApplicationRecord", "  include ActiveShrine::Model\n"
+      end
     end
   end
 end

data/lib/generators/pu/invites/install_generator.rb

@@ -186,7 +186,7 @@ module Pu
   def current_membership
     return unless entity_scope && user
 
-    @current_membership ||= #{membership_model}.find_by(#{entity_association_name}: entity_scope, user: user)
+    @current_membership ||= #{membership_model}.find_by(#{entity_association_name}: entity_scope, #{user_association_name}: user)
   end
         RUBY
 
@@ -382,6 +382,13 @@ module Pu
         PlutoniumGenerators::Generator.derive_association_name(membership_model, entity_model)
       end
 
+      # Returns the association name for user on the membership model.
+      # Same logic as entity_association_name but for the user side.
+      # e.g., RestaurantStaffUser -> StaffUser uses :staff_user (not :user)
+      def user_association_name
+        PlutoniumGenerators::Generator.derive_association_name(membership_model, user_model)
+      end
+
       def entity_in_package?
         options[:dest] != "main_app"
       end

data/lib/generators/pu/lib/plutonium_generators/concerns/actions.rb

@@ -472,6 +472,49 @@ module PlutoniumGenerators
         end
       end
 
+      #
+      # Injects helper methods into a Plutonium Concerns::Controller file,
+      # merging with any existing `included do` and `private` sections.
+      #
+      # ActiveSupport::Concern only permits ONE `included do` block per concern,
+      # so we cannot naively append a new block when multiple generators need to
+      # register helper_methods in the same file.
+      #
+      # @param file [String] path to the concerns/controller.rb file
+      # @param helper_methods [Array<Symbol>] names to expose via `helper_method`
+      # @param methods [String] method definitions (already indented to 6 spaces)
+      #
+      def inject_into_concerns_controller(file, helper_methods:, methods:)
+        helper_list = Array(helper_methods).map { |m| ":#{m}" }.join(", ")
+
+        in_root do
+          # 1. helper_method declaration: merge into existing `included do` block,
+          #    otherwise create a new block right after the `# add concerns above.` marker.
+          content = File.read(file)
+          if (match = content.match(/^(?<indent>[ \t]*)included do\n/))
+            indent = match[:indent]
+            inject_into_file file,
+              "#{indent}  helper_method #{helper_list}\n",
+              after: /^[ \t]*included do\n/
+          else
+            block = "\n      included do\n        helper_method #{helper_list}\n      end\n"
+            inject_into_file file, block, after: /# add concerns above\.\n/
+          end
+
+          # 2. Method definitions: append into the existing `private` section if any,
+          #    otherwise create one just before the closing `    end`s of the concern.
+          content = File.read(file)
+          trimmed_methods = methods.sub(/\A\n+/, "").chomp
+          if content.match?(/^[ \t]*private\n/)
+            inject_into_file file, "\n#{trimmed_methods}\n", after: /^[ \t]*private\n/
+          else
+            inject_into_file file,
+              "\n      private\n\n#{trimmed_methods}\n",
+              before: /^    end\n  end\nend\s*\z/
+          end
+        end
+      end
+
       def file_includes?(path, check)
         destination = File.expand_path(path, destination_root)
         return false unless File.exist?(destination)

data/lib/generators/pu/profile/concerns/profile_arguments.rb

@@ -7,15 +7,21 @@ module Pu
         extend ActiveSupport::Concern
 
         included do
-          argument :name, type: :string, default: "Profile", required: false, banner: "NAME"
+          argument :name, type: :string, required: false, banner: "NAME"
           argument :attributes, type: :array, default: [], banner: "field[:type] field[:type]"
         end
 
-        # Normalize arguments: if name contains ":", treat it as an attribute
+        # Normalize arguments: if name is omitted, default to "{UserModel}Profile";
+        # if name looks like an attribute (contains ":"), treat it as an attribute
+        # and still default the profile name to "{UserModel}Profile".
         def normalize_arguments
-          if name.include?(":")
+          default_name = "#{options[:user_model] || "User"}Profile"
+          if name.nil?
+            @profile_name = default_name
+            @profile_attributes = attributes
+          elsif name.include?(":")
             @profile_attributes = [name, *attributes]
-            @profile_name = "Profile"
+            @profile_name = default_name
           else
             @profile_name = name
             @profile_attributes = attributes

data/lib/generators/pu/profile/conn_generator.rb

@@ -10,7 +10,7 @@ module Pu
 
       desc "Connect a Profile resource to a portal and configure the profile_url helper"
 
-      argument :name, type: :string, default: "Profile", required: false, banner: "RESOURCE"
+      argument :name, type: :string, required: false, banner: "RESOURCE"
 
       class_option :dest, type: :string,
         desc: "Destination portal"
@@ -106,14 +106,7 @@ module Pu
       end
 
       def add_profile_url_helper
-        content = <<-RUBY.chomp
-
-      included do
-        helper_method :profile_url
-      end
-
-      private
-
+        methods = <<-RUBY
       # Returns the URL to the user's profile page.
       def profile_url
         profile = current_user.#{profile_association}
@@ -124,15 +117,19 @@ module Pu
         end
       end
         RUBY
-        inject_into_file concerns_controller_path, content, after: /# add concerns above\.\n/
+        inject_into_concerns_controller concerns_controller_path,
+          helper_methods: [:profile_url],
+          methods: methods
       end
 
       def profile_association
-        resource_class_name.demodulize.underscore
+        # The install generator always exposes the profile as `:profile` on the
+        # user model (via class_name:), regardless of the underlying class name.
+        "profile"
       end
 
       def resource_class_name
-        name.camelize
+        (name.presence || "#{options[:user_model]}Profile").camelize
       end
 
       def user_table

data/lib/generators/pu/profile/install_generator.rb

@@ -37,10 +37,13 @@ module Pu
       end
 
       def add_user_association
+        # Always expose the association as `:profile` on the user model so that
+        # `current_user.profile` works regardless of the underlying class name
+        # (e.g. UserProfile, StaffUserProfile, AccountSettings).
         association = if dest_package?
-          "  has_one :#{file_name}, class_name: \"#{namespaced_class_name}\", dependent: :destroy\n"
+          "  has_one :profile, class_name: \"#{namespaced_class_name}\", dependent: :destroy\n"
         else
-          "  has_one :#{file_name}, dependent: :destroy\n"
+          "  has_one :profile, class_name: \"#{class_name}\", dependent: :destroy\n"
         end
         inject_into_file user_model_path, association,
           before: /^\s*# add has_one associations above\.\n/

data/lib/generators/pu/rodauth/templates/app/rodauth/account_rodauth_plugin.rb.tt

@@ -285,6 +285,9 @@ class <%= account_path.classify %>RodauthPlugin < RodauthPlugin
 <% end -%>
 <% if verify_account? -%>
 
+    # Redirect to login page after requesting account verification email.
+    verify_account_email_sent_redirect { login_path }
+
     # Redirect to wherever login redirects to after account verification.
     verify_account_redirect { login_redirect }
 <% end -%>

data/lib/generators/pu/saas/portal_generator.rb

@@ -70,14 +70,7 @@ module Pu
       end
 
       def add_entity_url_helper
-        content = <<-RUBY
-
-      included do
-        helper_method :entity_url, :user_entities
-      end
-
-      private
-
+        methods = <<-RUBY
       # Returns the URL to the current entity's show page.
       def entity_url
         resource_url_for(current_scoped_entity)
@@ -88,7 +81,9 @@ module Pu
         @user_entities ||= current_user.#{entity_table.pluralize}
       end
         RUBY
-        inject_into_file concerns_controller_path, content, after: /# add concerns above\.\n/
+        inject_into_concerns_controller concerns_controller_path,
+          helper_methods: [:entity_url, :user_entities],
+          methods: methods
       end
 
       def add_entity_link_to_header

data/lib/generators/pu/saas/welcome/templates/app/views/welcome/onboarding.html.erb.tt

@@ -23,7 +23,7 @@
   <%% end %>
 <% if profile? -%>
 
-  <%%= f.fields_for :profile, @profile do |pf| %>
+  <%%= fields_for :profile, @profile do |pf| %>
     <div>
       <%%= pf.label :name, "Your Name", class: "block mb-2 text-sm font-medium text-[var(--pu-text)]" %>
       <%%= pf.text_field :name,
@@ -34,7 +34,7 @@
   <%% end %>
 <% end -%>
 
-  <%%= f.fields_for :<%= entity_table %>, @<%= entity_table %> do |ef| %>
+  <%%= fields_for :<%= entity_table %>, @<%= entity_table %> do |ef| %>
     <div>
       <%%= ef.label :name, "Workspace Name", class: "block mb-2 text-sm font-medium text-[var(--pu-text)]" %>
       <%%= ef.text_field :name,

data/lib/plutonium/engine.rb

@@ -5,17 +5,30 @@ module Plutonium
     extend ActiveSupport::Concern
 
     class_methods do
-      attr_reader :scoped_entity_class, :scoped_entity_strategy, :scoped_entity_param_key, :scoped_entity_route_key
+      attr_reader :scoped_entity_strategy, :scoped_entity_param_key, :scoped_entity_route_key
 
+      # Store the entity class *by name* and resolve it lazily on every call.
+      # Capturing the class object directly causes stale references after Rails
+      # autoreload: the constant is reloaded but @scoped_entity_class still
+      # points at the previous (now-orphaned) class object, which then fails
+      # type checks against freshly reloaded instances.
       def scope_to_entity(entity_class, strategy: :path, param_key: nil, route_key: nil)
-        @scoped_entity_class = entity_class
+        @scoped_entity_class_name = entity_class.is_a?(Class) ? entity_class.name : entity_class.to_s
         @scoped_entity_strategy = strategy
-        @scoped_entity_param_key = param_key || :"#{entity_class.model_name.singular_route_key}_scope"
-        @scoped_entity_route_key = route_key || entity_class.model_name.singular.to_sym
+        # param_key / route_key are derived from the class once at declaration
+        # time — they're stable strings and don't depend on the live class
+        # identity, so caching them is safe.
+        resolved = @scoped_entity_class_name.constantize
+        @scoped_entity_param_key = param_key || :"#{resolved.model_name.singular_route_key}_scope"
+        @scoped_entity_route_key = route_key || resolved.model_name.singular.to_sym
+      end
+
+      def scoped_entity_class
+        @scoped_entity_class_name&.constantize
       end
 
       def scoped_to_entity?
-        scoped_entity_class.present?
+        @scoped_entity_class_name.present?
       end
 
       def dom_id

data/lib/plutonium/ui/layout/rodauth_layout.rb

@@ -19,7 +19,12 @@ module Plutonium
           render_logo
 
           div(class: "w-full bg-[var(--pu-surface)] rounded-[var(--pu-radius-lg)] border border-[var(--pu-border)] md:mt-0 sm:max-w-md xl:p-0", style: "box-shadow: var(--pu-shadow-md)") {
-            div(class: "p-6 space-y-4 md:space-y-6 sm:p-8", &)
+            div(class: "p-6 space-y-4 md:space-y-6 sm:p-8") {
+              if page_title.present?
+                h1(class: "text-xl font-semibold leading-tight tracking-tight text-[var(--pu-text)] md:text-2xl") { page_title }
+              end
+              yield
+            }
           }
 
           render_links

data/lib/plutonium/version.rb

@@ -1,5 +1,5 @@
 module Plutonium
-  VERSION = "0.45.2"
+  VERSION = "0.46.0"
   NEXT_MAJOR_VERSION = VERSION.split(".").tap { |v|
     v[1] = v[1].to_i + 1
     v[2] = 0

data/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@radioactive-labs/plutonium",
-  "version": "0.45.2",
+  "version": "0.46.0",
   "description": "Build production-ready Rails apps in minutes, not days. Convention-driven, fully customizable, AI-ready.",
   "type": "module",
   "main": "src/js/core.js",